Readme for IBM WebSphere Process Server Fix Pack V6.0.1.2
Change History:
Release date: 05 June 2006
06 June 2006: Published
Back to top
WebSphere Process Server and WebSphere Enterprise Service Bus fixes:
| IY82160 | TRYING TO SPECIFY A THRESHOLD IN THE BPC EXPLORER CONFIG |
| IY82199 | URIS are routed to the web server |
| IY83115 | DB SYSTEMS WITH BPC MIGHT FAIL LOADING A PROCESS TEAMP |
| IY83206 | APIEVENTHANDLERPLUGIN CAUSES A NULLPOINTEREXCEPTION. |
| IY83426 | SORTING ISSUE IN THE JSF COMPONENT |
| IY84077 | WSDLEXCEPTION RESOLVING REFERNECE WITH RELATIVE PATH |
| IY84111 | WRONG CONNECTION PROXIMITY SET WHEN CONFIGURING BPC |
| IY84183 | CHECK IF A PROCESS TEMPLATE WITH THE GIVEN NAME AND VALID FROM EXIST |
| IY84504 | HOW INPUT DATA CAN BE RETRIEVED IN CUSTOM JSP IMPLEMENTIN |
| IY84625 | INCORRECT CYCLE DETECTION FOR LDAP GROUPS. |
| IY84662 | JDBC PATHS SET IMPROPERLY WHEN USING BPECONFIG |
| IY84879 | BPC THROWS A FAULT AS A RUNTIME EXCEPTION |
| IY84903 | CALLING GETCUSTOMPROPERTY API WITH PTID FAILS |
| JR23113 | OBJECTEVENTIDS ARE NOT PROPERLY SET IN THE EVENTSUMMARY |
| JR23472 | DataMap throws an exception when mapping the return object |
| JR23478 | Need to back out J9 jit conpiler on Linux |
| JR23655 | ASYNCH SOAP/JMS IMPORT NOT TRULY ASYNCH. WILL REQUEST TIMEOUT |
| JR23690 | WPS MIGRATION TOOL (FROM ICS) FAILED TO CONVERT SOME DATA T |
| JR23697 | SCA XMLResourceFactory, ManagedMessageImpl changes |
Included WebSphere Application Server fixes:
PK21663 - ON SERVER RESTART, CERTAIN APPLICATIONS CAUSE AN INFINITE LOOP
PK23079 - WEBSERVICE RECEIVES WSWS3400I NULLPOINTEREXCEPTION
PK23093 - JMS SESSION USED ON ANOTHER THREAD AFTER ASSOCIATED WITH TRANSACTION.
PK23267 - CONNECTION CLASH DETECTION CAUSES SIGNIFICANT PAUSES
PK20940 - SIINCORRECTCALLEXCEPTION DURING ASYNCHRONOUS CONSUME
PK21246 - WPS PERFORMANCE PROBLEM WITH SCA COMPONENT DISPATCH
PK23696 - REMOTE ME MESSAGE FLOW INTERRUPTED INTERMITTENTLY
Back to top
Prerequisites:
Install the Fix Pack V6.0.1.2 on top of WebSphere Process Server version
6.0.1 or 6.0.1.1
All hardware and software prerequisites are described in the Supported hardware and software Web page.
Back to top
Space requirements:
Space requirements vary depending on what you are installing. The size of each download is available on the Support site. For a fix pack, you need approximately 600 MB of free space in the system temporary directory (typically /tmp on a Linux or UNIX system) and another 600 MB in the file system that hosts the WebSphere Process Server image (typically /usr or /opt on a Linux or UNIX-based platform), or approximately 1.2 GB of free space on the disk drive where you are installing on a Windows platform.
Verify that the free space is available before beginning the installation.
Space is also required for the install_root/updateinstaller directory. The space required is about the same as the size of the fix pack and other included fixes, typically somewhere between 25 MB to 750 MB.
Space is also required for backup files in the install_root/properties/version/update/backup directory. The space required is about the same as the size of the fix pack, somewhere between 25 MB to 750 MB, varying by product and platform.
For more information, see the disk space requirements for the Update Installer.
Back to top
Steps for installing Fix Pack 2
1. Run the backupConfig command to back up configuration files. See Backing up and restoring administrative configurations in the online information center.
2. Before downloading the Update Installer, back up and delete any previous
versions of the Update Installer. To use a newer version of the Update
Installer, you must first remove the older version.
a. If necessary, back up files and subdirectories in the install_root/updateinstaller/maintenance
directory.
b. Delete the install_root/updateinstaller directory and all of its subdirectories.
3. Verify that the required disk space is available, as described in the
readme file for the maintenance package (install_root/updateinstaller/docs/readme_updateinstaller.html).
4. After backing up the configuration files and before installing V6.0.1,
stop all Java processes that use the IBM Developer Kit that WebSphere Process
Server provides to support the Java 2 software development kit (SDK) that
IBM provides for WebSphere Process Server products.
5. Stop all process server processes, the nodeagent process, the deployment
manager process, and all server processes that belong to serviceable products,
such as the IBM HTTP Server. Stop all Java processes, if necessary.
If you install V6.0.1 while a WebSphere Process Server-related Java process
is running, the product might not continue to run successfully.
6. Obtain the V6.0.1.2 downloadable package that you need from the product support Web site.
Download the package into a temporary disk location.
7. Unzip the package into the install_root directory. This process unpacks
the downloaded package automatically into the install_root/updateinstaller
directory and several subdirectories, including the maintenance subdirectory.
For example, to unzip the maintenance package, enter the following command:
cd /opt/IBM/WebSphere/ProcServer
unzip /tmp/downloads/6.0.1-WS-WPS-ESB-AixPPC32-FP0000002.zip
The V6.0.1.2 downloadable package contains the Update Installer, the V6.0.1.2
maintenance package, and a number of required WebSphere Application Server
maintenance packages. The V6.0.2.6 Update Installer for WebSphere Software
is in the install_root/updateinstaller directory. The maintenance package
is in the install_root/updateinstaller/maintenance directory.
8. Check the Recommended Updates page to see if the Update Installer has been updated since the V6.0.1
file was created.
If so, download and unpack the new Update Installer into the installation root directory to replace the Update Installer files that are in V6.0.1.
9. (Optional) Delete the ZIP file if you need more space.
10. Open a command shell window and change directories to the install_root/updateinstaller
directory of the product that you are updating by entering the following
command:
cd install_root/updateinstaller
11. Using the same command shell, begin the update.
Use the update command to install the maintenance packages that you downloaded and unpacked:
Install them in the following order:
a) 6.0.2-WS-WAS-<platform/architecture>-FP0000009.pak (WebSphere Application Server V6.02 Fix Pack 9)
b) 6.0.2-WS-WASJavaSDK-<platform/architecture>-FP0000009.pak (WebSphere
6.0.2.9 Java SDK Fix Pack)
Note: Installing the SDK is a two-step process. The installation panels provide
detailed information about the process.
c) The seven included WebSphere Application Server iFixes (in any order):
6.0.2.5-WS-WAS-IFPK21663.pak
6.0.2.7-WS-WAS-IFPK23079.pak
6.0.2.7-WS-WAS-IFPK23093.pak
6.0.2.7-WS-WAS-IFPK23267.pak
6.0.2.9-WS-WAS-IFPK20940.pak
6.0.2.9-WS-WAS-IFPK21246.pak
6.0.2-WS-WAS-IFPK23696.pak
d) 6.0.1-WS-WPS-ESB-<platform/architecture>-FP0000002.pak (WebSphere Process Server V6.0.1 Fix Pack 2)
For each maintenance package do the following (filenames are examples,
substitute as needed):
For Windows:
update -silent -W maintenance.package=.\maintenance\6.0.2-WS-WAS-WinX32-FP0000009.pak
For UNIX platforms, for example for AIX:
./update -silent -W \
maintenance.package=./maintenance/6.0.2-WS-WAS-AixPPC32-FP0000009.pak
You can also issue the update command without a parameter to start the
graphical user interface:
For Windows, enter the following command:
update
For UNIX platforms:
./update
For detailed information about using the update command, refer to the install_root/updateinstaller/docs/readme_updateinstaller.html
file.
Back to top
Known issues:
Stop all WebSphere Application Server-related Java processes before using the Update Installer for WebSphere Software
Read the technote at the following link for more information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21199141
Problem:
During the installation of the fix pack, the parts of the Business Process Choreographer component that are shipped as EAR files are updated in the file system. However, these files are not automatically deployed to the runtime configuration of WebSphere Process Server.
Solution:
For each standalone profile for which you configured Business Process Choreographer,
do the following:
1. Go to the <install_root>/ProcessChoreographer directory.
2. Make sure the application server where Business Process Choreographer
is configured is stopped.
3. Depending on your platform, run one of the following commands:
On Windows::
..\bin\wsadmin -conntype NONE -profileName <profileName> -f bpeupgrade.jacl
where <profileName> is the name of the profile that contains the
Business Process Choreographer configuration.
On UNIX and Linux:
../bin/wsadmin.sh -conntype NONE -profileName <profileName> -f bpeupgrade.jacl
where <profileName> is the name of the profile that contains the Business Process Choreographer configuration.
4. Restart WebSphere Application Server.
5. For each server or cluster in an Network Deployment (ND) environment
where you configured Business Process Choreographer do the following:
a. On the deployment manager, go to the <install_root>/ProcessChoreographer
directory.
b. Make sure all application servers where Business Process Choreographer
is to be upgraded are stopped.
c. Depending on your platform, run one of the following commands:
On Windows:
..\bin\wsadmin -conntype NONE -profileName <profileName> -f bpeupgrade.jacl
where <profileName> is the name of the profile that contains the Business Process Choreographer configuration. If the deployment manager is running, omit the -conntype NONE parameter.
On UNIX and Linux:
../bin/wsadmin.sh -conntype NONE -profileName <profileName> -f bpeupgrade.jacl
where <profileName> is the name of the profile that contains the Business Process Choreographer configuration. If the deployment manager is running, omit the -conntype NONE parameter.
6. Restart WebSphere Application Server.
The previous steps upgrade the Business Process Choreographer enterprise
applications to the installed fix level.
If you have problems, check the <profileRoot>/logs/bpeupgrade.log file.
Refer to the Readme file for the Update Installer for workarounds to the
following known problems:
Problem
The product uninstall does not remove the product correctly
The relaunch action for SDK updates does not launch the Update Installer
This is a known problem on some HP-UX systems.
Always use the most current version of the Update Installer for WebSphere
Software to install maintenance packages.
Control returns prematurely to the command line when the Update Installer rolls back an updated IBM Software Development Kit (SDK).
The Update Installer fails to relaunch after copying the SDK if not enough
disk space is available for installation
Non-root profiles start with an error after V6.0.2 is installed.
Problem in cloning the SDK for updates to the product SDK
Profile update and undo scripts are limited to SBCS and to characters without pronunciation keys due to operating system limitations
Profiles can exist at the V6.0.2 level after rolling back V6.0.2
Back to top
Additional information:
You can find additional information in the WebSphere Process Server Information Center
For additional information, see also the Recommended Updates page and the IBM update strategy for WebSphere Application Server V6.0 release page.
Back to top
Accessing the readme file for the Update Installer:
See the online readme file for the Update Installer for more information.
After unpacking V6.0.1.2, the readme file is available as the install_root/updateinstaller/docs/readme_updateinstaller.html.
However, the online version is updated periodically while the bundled local
copy is not.
Back to top
Trademarks and service marks:
For trademark attribution, visit the IBM Terms of Use Web site.