Rational Automation Framework Fix Pack 5 (3.0.0.5) for 3.0

Table of Contents

Sections	Description
What's new	This section provides an overview of what is new in this release with a description of any new functionality or enhancements where applicable.
Impact assessment	This section provides information related to the impact of this release to allow you to assess how your environment may be affected.
Prerequisites	This section provides important information to review prior to the installation of this release.
Download package	This section provides the direct link to obtain the download package for installation in your environment.
Installation instructions	This section provides the installation instructions necessary to apply this release to your environment.
Known problems	This section contains a link to the known problems (open defects) identified at the time of this release.

Supporting Documentation

Document	Description
Detailed System Requirements	Click the link to navigate to the system requirement report page. To run the report, select your Product, Version and Operating System.  Note: Choose the parent version of your product to see the system requirements for fix pack releases.
Information Center	Click to browse for the version of your product information center available on the product information library page.
Fix List	Click to review the list of defects (APARs) resolved in this release and resolved in previous releases of this version (3.0.0.x).

Rational Automation Framework 3.0 or a later fix pack is a prerequisite for this fix pack.

Back up the following items before installing this fix pack:

• Installation directory for Rational Automation Framework. These are the default directories:
  • UNIX or Linux systems: /opt/IBM/RAFServer
  • Windows systems: C:\IBM\RAFServer
• Metadata for Installation Manager.
  • UNIX or Linux systems: /var/ibm/InstallationManager
  • Windows systems (Windows 7 or Windows 2008 and later):
    %ALLUSERSPROFILE%\IBM\Installation Manager
  • Windows systems (previous versions):
    %ALLUSERSPROFILE%\Application Data\IBM\Installation Manager

The following sections provide detailed information related to this release.

Impact Assessment

Impact	Description
Corrective	This release is a maintenance release of Rational Automation Framework version 3.0. It contains fixes for client-reported and internally-found defects.

Click the Fix List link in the table of contents above to review a list of the problems solved in this release.

The following issues are known to affect this release.

Change to configure_all composite action for WebSphere Application Server 8.5: If you installed the WebSphere Application Server version 8.5 base image (rather than the network deployment image), two actions cause exceptions:

was_common_configure_health_policies
was_common_configure_service_policies

Because of this problem, these actions have been excluded from the was_common_configure_all composite action.

Workaround: If you installed the WebSphere Application Server version 8.5 network deployment image, you can run these actions separately. Base image users cannot run these actions.

 

WebSphere Virtual Enterprise 7.0 and WebSphere Application Server version 8.0 or later: Rational Automation Framework does not currently support the installation of WebSphere Virtual Enterprise version 7.0 where WebSphere Application Server version 8.0 or later is installed. WebSphere Application Server 8.0 and later requires that you use IBM Installation Manager to install WebSphere Virtual Enterprise. The WebSphere Virtual Enterprise installation actions currently use IBM Update Installer.

If you attempt this installation, the following error message is displayed:

org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)

Workaround: You can install WebSphere Virtual Enterprise version 7.0 on WebSphere Application Server version 7.0 and earlier.

 

was_common_configure_all fails with On Demand Router server: When the action runs, the following exception is returned:

[exec] WASX7017E: Exception received while running file 
"c:/RAFW/product/actions/configure/was/common/scripts/manageServer.py"; 
exception information: 
com.ibm.websphere.management.exception.InvalidConfigDataTypeException: 
ADMG0007E: The configuration data type CustomProperty is not valid.

The problem is caused by a problem with WebSphere Application Server.

Workaround: Manually configure On Demand Router servers using WebSphere Application Server tools.

 

Dragging configuration definition to the Configuration Workspace fails for large files: If you see a copy/paste failure message when you drag a configuration definition to the Configuration Workspace in the Eclipse client, and you see an OutOfMemoryError in the log, you might have an archive file in the configuration that is larger than the Eclipse client can currently copy.

Workaround: To install an application from a large archive file, copy the archive directly to the server.

 

Cannot use parentheses in directory name in Windows: If you use parentheses in a directory name in the Environment Generation wizard (for example, "C:\Program Files (x86)"), the value is flagged as invalid.

Workaround: Use a short directory name instead. To get a list of short directory names, run the following command in a command prompt:

dir /x \

 

Missing application options when importing from WebSphere Application Server version 8.0 or later: When you run the was_common_deploy_install_app action in import mode to capture a WebSphere Application Server 8.0 or later configuration, some options might not be captured. Warning messages are generated in the following form:

CRWWA1001W Support for the deployment task 'xxx' is not implemented in the product.

Review the What's new topic in the on-line information center for a full list of what's new in the 3.0.0.5 release.