Flash plug-in requirement
In order to properly view multimedia user assistance, such as Tours, Tutorials, and Show me viewlets, you need to have Flash Player for Linux version 6.0r69 or later installed.
Mozilla 1.4 GTK2, or Mozilla 1.5 GTK2, or Mozilla 1.6 GTK2 with SWT3.0, or Mozilla 1.7 GTK2 and above with SWT3.1 V3104 must be installed. The version of Mozilla installed on your system will vary with your Linux distribution. For more details on supported software and specification for Rational Developer, refer to the Installation Guide.
To find Mozilla download and installation instructions, refer to www.mozilla.org.
If Mozilla is not installed, you will receive the following error message when opening the online help:
An exception occurred while launching help. Refer to the log for more details.
If Mozilla is not installed you will receive the following error message when invoking RUP®:
An SWT error has occurred.
You are recommended to exit the workbench.
Subsequent errors may happen and may terminate the workbench without warning.
See the .log file for more details.
Due to differences in plugin loading behavior on different systems, links to wizards and information on optionally installable features may not be displayed in the Welcome.
Some wizards and windows are modal, which means that until you finish working in them, you cannot switch to a different window in the product. This is an issue when you refer to help topics in the help browser, or tutorials in the Tutorials Gallery for guidance on how to complete a wizard.
To view the online help while you work in a modal window, either print the help information, or set the online help to open in an external browser.
To set the online help to open in an external browser:
- Click Windows > Preferences.
- Click Help.
- Select the Always use external browsers check box.
- Click Apply.
- Click OK.
Note: Some help information is available in PDF. You can view this information in Adobe Acrobat Reader while working with a modal window.
When upgrading from one Rational Software Development Platform product to another using the ESD images, ensure that you download and extract the same set of images for the new product that you downloaded and extracted for the original product. The same components installed in the original product will be automatically installed in the upgraded product.
For example, if the Language Pack was originally installed, when upgrading you will need to have the Language Pack downloaded and extracted into the new product installation image.
Information on the following items may be missing from early versions of the online help topic "Migrating JavaServer Faces resources with Faces Client Components":
If your online help topic "Migrating JavaServer Faces resources with Faces Client Components" is missing this information, refer the the html version of the Migration Guide, which is located at root of the first CD or under disk1/migrate.html of the electronic images.
- Two problems that may occur when changing the target server of a project containing Faces Client Components from WebSphere Application Server V5.1 to V6.0:
- Client Data mediator classes that have already been generated will no longer compile.
- Tree View Faces Client Components bound to WDOs fail to run on server after changing the project's target server to WebSphere Application Server V6.0.
- Information regarding working in the Linux platform or a non-English locale.
The Installation Guide may have incorrect instructions for installing Crystal Enterprise V10 Professional Edition on Linux. To install the Crystal Enterprise V10 Professional Edition on Linux, follow these steps:
- Insert the Crystal Enterprise V10 Professional Edition disk for Linux and mount the cdrom.
- Open the install.html file located in the root directory of the installation disk. This file contains complete instructions for installing Crystal Enterprise V10 Professional Edition on Linux. You will need to refer to the instructions in this file to prepare your system and complete the installation process. You should also review the "Installation" section of the release.htm file, which is located in the root directory of the installation disk, prior to installing the product.
- Review the "Setting up your Linux system" section of the install.html file and perform all necessary actions before proceeding with running the installation script.
- Disable any antivirus software before installing the product.
- Follow the "Running the installation script" instructions in the install.html file to complete the installation process. It describes the procedure for a user installation.
Notes:
- In the "Running the installation script" instructions you are told to copy the licensetext file (included with your product distribution), and the files containing the Crystal Enterprise binaries (with the extension .gz) to your HOME directory. These files are located in the linux_x86 directory of the installation disk.
- In "Running the installation script" there is a step that indicates you should enter a product activation keycode. You can ignore this step.
- When the installation script completes, you must deploy the Crystal Enterprise Web desktop and the Crystal Enterprise Launchpads. Refer to the "Deploying the Crystal Enterprise web desktop" section in the install.html file.
- For information on deploying the Web Component Adapter (WCA), including information on deploying multiple WCAs, refer to the "Deploying the Web Component Adapter" section of the install.html file.
- Enable your antivirus software, if you disabled it prior to beginning the installation.
You can also install Crystal Enterprise V10 Professional Edition in Japanese. Follow the same instructions as listed above using the Japanese version of the Crystal Enterprise V10 Professional Edition Japanese on Linux CD.
To run site_prep and install_release, you should change to the following directory:
cd /usr/ccase_lt_rls/rational_clearcase_lt/rhat_x86/clearcase/install
assuming
/usr/ccase_lt_rls/
is the directory name for your release area.
You must update the online help, tutorials, samples, and welcome for this product release by using the Rational® Product Updater.
To update this information, on the main menu of the product, click Help > Software Updates > IBM Rational Product Updater.
The English version of these release notes contain updated information. To download the latest version of these release notes, visit www3.software.ibm.com/ibmdl/pub/software/rationalsdp/rsa/60/html/readme.html.
In the "Getting started" section of the C++ transformation documentation, the instructions for transforming a model to C++ code should read as follows:
- In the Model Explorer view, right-click the UML model; then click Transform > Run Transformation > UML to C++.
- In the Run Transform window, on the Target page, click New Project to create a new destination C++ project.
- In the New Project wizard, in the Project Name field, type Hello World and click Finish.
- In the Run Transform window, click Run.
In the "Getting started" section of the Java™ transformation documentation, the instructions for transforming a model to Java code should read as follows:
- Switch to the Modeling perspective.
- In the Model Explorer view, right-click a UML class (for example, Class1); then click Transform > Run Transformation > UML2 to Java.
- In the Run Transformation window, click Create Target Container.
- In the New Java Project window, in the Project Name field, type simple, and click Finish.
- In the Run Transformation window, click Finish.
In section 3.2, "Transformation mapping", step 3 should read as follows:
- On the menu bar, click Modeling > Transform > Configure Transformations.
In section 3.3, "In-place visualization support", and section 3.6, "Traceability", all instances of the text "Configure Transforms" should be replaced with "Configure Transformations."
When you open the installation guide and the release notes for the first time, some of the links might appear as if they were visited.
Some navigation links in the release note subcomponents, such as Installation and Documentation, might not work properly.
The table of contents in the Spanish version of the installation guide appears smaller than it should. Also, the titles throughout the installation guide do not link back to the table of contents. These are formatting issues that do not affect the content in the installation guide.
Return to the main readme file