Rational Automation Framework for WebSphere, Version 7.1.1.3 Release Information

Content

• About this release
• System requirements
• Download information
• Installation information
• Fixes for version 7.1.1.3
• Features, fixes, and enhancements for version 7.1.1.2
• Features, fixes, and enhancements for version 7.1.1

About this release
This version contains fixes that were provided in the 7.1.1.3 fix pack.

---

System requirements
There are no new hardware or software requirements for installing this fix pack.

For details about hardware and software requirements, see the Installing and upgrading section of the information center at:
http://publib.boulder.ibm.com/infocenter/rafwhelp/v7r1/index.jsp

---

Download information
Rational Automation Framework for WebSphere is installed as an optional component of IBM® Rational® Build Forge®.

To download Rational Build Forge and Rational Automation Framework for WebSphere, go to the Download Document for Rational Build Forge.

---

Installation information
This fix pack can be installed as an initial installation or as an upgrade to the 7.1.1 release.

Before you install or upgrade, read the prerequisites and installation instructions in the Installing and upgrading section of the information center at: http://publib.boulder.ibm.com/infocenter/rafwhelp/v7r1/index.jsp

---

Installation information for z/Linux users
If you are running Rational Build Forge and Rational Automation Framework for WebSphere on a z/Linux platform, contact IBM Rational Support for installation and configuration assistance.

---

Product documentation
Documentation is available as an online information center and as a PDF file.

The PDF is included with the product images in the docs directory: BF_HOME/rafw/docs, where BF_HOME is your Build Forge installation directory.

The PDF is also available online at the IBM Publications Center . Go to the Quick Publications Search page; in the Publication number field, type SC14-7278-00.

To access the information center, select the following link:
http://publib.boulder.ibm.com/infocenter/rafwhelp/v7r1/index.jsp

---

Fixes for version 7.1.1.3
This version of Rational Automation Framework for WebSphere includes the following fixes:

Fix	Description
WI 13707: Restriction removed for connecting to a WebSphere target system running UNIX or Linux from a Windows framework server.	In 7.1.1.3, a Windows framework server can be used to manage UNIX or Linux target systems. For versions prior to 7.1.1.3, this restriction still exists and Windows framework servers can only be used to manage WebSphere target systems running Windows.
WI 11315: Removed Bash shell dependency for WebSphere target systems running UNIX or Linux.	In 7.1.1.3, the requirement to install the Bash shell on UNIX and Linux target systems no longer exists. For versions prior to 7.1.1.3, this restriction still exists.
WI 14030: RXA does not support NTLMv2 authentication protocol on Windows.	RXA only supports NTLMv1 authentication protocol on Windows RXA restriction added to product documentation.
TN 1410052: Uninstall actions for all products fail in 7.1.1.2.	In 7.1.1.3, the syntax error introduced in 7.1.1.2 that caused IHS, WP, and WAS uninstall actions to fail was fixed.
APAR PK99660: Due to encrypted password, IHS Web server cannot be started after was_common_configure_federate_ihs action is run.	In 7.1.1.3, the Windows service password is now decrypted before it is stored.
WI 13415: Actions run with the preview flag failed if required <type>.xml file was not present in the environment tree.	In 7.1.1.3, if the <type>.xml file does not exist and the action is run with the preview flag, the action passes and a warning message is printed.
TN 1413940: Actions to start and stop the IBM HTTP Server administration server fail on Windows for 7.1.1.2 and earlier versions of Rational Automation Framework for WebSphere	For 7.1.1.2 and earlier cell definitions, manually edit the install.properties to fix this problem. In 7.1.1.3, the problem has been fixed; if your 7.1.1.3 cell definitions contain IHS nodes on Windows, the actions work and no manual edits are required.
WI 13396: Fix pack install actions for all products failed to stop servers prefixed with WebSphere_Portal when shutting down all servers prior to initiating install actions.	In 7.1.1.3, fix pack install actions for all products now successfully stop all servers regardless of server name.

---

Features, fixes, and enhancements for version 7.1.1.2
For information about 7.1.1.2, see the release information on the Support site:
http://www.ibm.com/support/docview.wss?rs=4021&uid=swg27017006

---

Features, fixes, and enhancements for version 7.1.1
For information about 7.1.1, see the release information on the Support site:
http://www.ibm.com/support/docview.wss?rs=4021&uid=swg27016246

---

Known limitations, problems, and workarounds
To learn about all the documented known problems and limitations in Rational Automation Framework for WebSphere, Version 7.1.1.3, and any workarounds or solutions that are available, see http://www.ibm.com/support/search.wss?rs=4021&tc=SSYPT4&q=RN7.1.1

Known problems are documented in the form of individual technotes in the Support knowledge base:
http://www.ibm.com/software/rational/support/.

As problems are discovered and resolved, the knowledge base will be updated and maintained with any new information. By searching the knowledge base, you can quickly find workarounds or solutions to problems.

---

IBM Rational Software Support

For contact information and guidelines or reference materials that you will need when you require support, see the IBM Software Support Handbook.

Before you contact IBM Rational Software Support, gather the background information that you will need to describe your problem. When describing a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

• What software versions were you running when the problem occurred?
• Do you have logs, traces, or messages that are related to the problem?
• Can you reproduce the problem? If so, what steps do you take to reproduce it?
• Is there a workaround for the problem? If so, be prepared to describe the workaround.