Fix (APAR): JR31341 Status: Fix Release: 6.2.0,6.1.2 Operating System: AIX,Windows Supersedes Fixes: CMVC Defect: JR31341 Byte size of APAR: 43845 Date: 2009-01-26 Abstract: Error when create profile using manageprofiles.sh on WebSphere Enterprise Service Bus when there is a web server in the profiles. Description/symptom of problem: JR31341 resolves the following problem: ERROR DESCRIPTION:? Problem : When a profile is created using manageprofiles.sh with web server definition, the resulting profile produces CWLAA6003 error at the WESB version information section on the welcome panel of the administrative console. If the admin console is uninstalled and re-installed, then the WESB version information section disappears altogether. If a profile is created without web server definition, the created profile does not show any problem. The version information shows up correctly on the welcome panel. The WAS version information always shows up correctly whether the profile has web server definition or not. . AIX 6.1, 64 bit, Ja_JP WESB 6.1.2 . Bad case : ./manageprofiles.sh -create -templatePath /usr/IBM/WebSphere/ESB/profileTemplates/default.esbserver -profileName STSC01 -cellName STSC01Cell -nodeName STSC01Node01 -hostName -dbType DERBY_EMBEDDED -webServerCheck true -webServerHostname localhost -webServerInstallPath /usr/IBM/HTTPServer -webServerName STSC01Web -webServerOS aix -webServerPluginPath /usr/IBM/HTTPServer/Plugins -webServerPort 80 -webServerType IHS . Good case : ./manageprofiles.sh -create -templatePath /usr/IBM/WebSphere/ESB/profileTemplates/default.esbserver -profileName STSC01 -cellName STSC01Cell -nodeName STSC01Node01 -hostName -dbType DERBY_EMBEDDED -webServerCheck false LOCAL FIX:? reinstall the ISC application PROBLEM SUMMARY:? USERS AFFECTED: WebSphere Process Server and WebSphere Enterprise Service Bus V6.1.2 and V6.2. PROBLEM DESCRIPTION: Error when create profile using manageprofiles.sh on WebSphere Enterprise Service Bus when there is a web server in the profiles. RECOMMENDATION: None The problematic WebSphere Enterprise Service Bus installation has web server besides application server and dmgr. When the create profile script tried to install the portlet on webserver, it failed. PROBLEM CONCLUSION:? The script should check for the server type and install the portlet ONLY for application server and deployment manager. Applying this interim fix will resolve the solution. Directions to apply fix: Download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Process Server. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed 1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Process Server. Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server. Additional Information: