IBM released group PTFs that upgrade WebSphere Advanced Edition and Advanced Edition Single Server to the cross-platform 4.02 build level. And if you're a serious WebSphere developer, you will definitely want to upgrade. But be warned: You have to pay close attention to the details. Miss one small step in the upgrade process, and you'll be left scratching your head.
This tip will hopefully help you avoid any problems ensure a smooth upgrade.
Plan for this upgrade
The good news is that the upgrade goes very smoothly once you know exactly what you must do. IBM has done a superb job in delivering very reliable code in this version. Unfortunately, the devil is in the details and you must carefully read the appropriate PTF cover letter and the release notes that are located only on IBM's Web site.
The group PTFs:
V4R5 WebSphere Advanced Edition Single Server -- SF99240
V4R5 WebSphere Advanced Edition -- SF99239
V5R1 WebSphere Advanced Edition Single Server -- SF99242
V5R1 WebSphere Advanced Edition -- SF99241
First Steps
- The PTF cover letter informs you to order and apply the current cum for your release of OS/400. The CUM is mandatory.
V5R1 -- the cum is C1302510
V4R5 -- the cum is C1296450
- You may then apply your WebSphere group PTF. Be forewarned, these WebSphere group PTFs include the current Group PTFs for the IBM HTTP Server, Database and Java.
- You need to be aware of an annoying anomaly for the 57xx-DG1 (HTTP) group PTF. It reinstalls and enables the APACHEDFT HTTP Server, which is configured to bind to all IP addresses on your machine. You must manually use the ADMIN facility after installing the PTF to stop this server, then go into the server configuration for APACHEDFT, select "Basic Configuration" and set the AUTOSTART option to "NO"! (Many users are asking IBM to fix this.)
- Hidden in the Release notes (read them carefully) is a special instruction to run the WebSphere Instance Updater program from Qshell (QSH) after you have applied the group PTF and before starting WebSphere and your HTTP Servers.
/QIBM/ProdData/WebASAdv4/bin/InstanceUpdater -instance instance-name
Where instance name is the subdirectory names found in:
/QIBM/UserData/WebASAdv4/
- A critical step that was not documented anywhere is the need to regenerate your HTTP plug-in files (plugin-cfg.xml) and copy them to any remote HTTP server instance machines you may have before starting your HTTP Servers.
- Finally, be sure to follow the instructions in the release notes (Advanced Edition users) to upgrade your client based console and tools (AAT, etc.) software to the proper version. There are two steps. The files you need are installed on the iSeries by the Group PTF, so you should have everything.
Overall this is far and away the smoothest WebSphere upgrade I have done, but be careful and read the release notes on the WebSphere Web site. IBM has promised to put a link in the PTF cover letter special instructions referring to the release notes. I have been told that the WebSphere Web site will be updated constantly with new information and documentation enhancements. Keep a close eye on this site. Check it at least once every couple of weeks for updates.
-------------------------
About the author: Bob Cancilla is managing director of IGNITe/400, an electronic iSeries 400 Internet users group. He is also author of the book Getting Down to e-business with AS/400.
=======================
MORE INFORMATION
=======================
