Fix (APAR): PQ81859 Status: Fix Release: 5.1.0 Operating System: All Supersedes Fixes: None CMVC Defect: PQ81859 Byte size of APAR: 1558290 Date: 2003-12-10 Abstract: SOAP messages which contain the header element are rejected by UDDI Description/symptom of problem: Interoperability problems can occur when sending SOAP messages to UDDI. A SOAP message sent by a client to one manufacturer's UDDI should work on any other manufacturer's UDDI, however SOAP messages which contain the header element are rejected by the UDDI Web Services component of WebSphere Application Server. Directions to apply fix: NOTE: YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Update Installer can be downloaded from the following link: http://www-3.ibm.com/software/webservers/appserv/support/index.html 1) Create temporary "fix" directory to store the jar file: UNIX: /tmp/WebSphere/fix Windows: c:\temp\WebSphere\fix 2) Copy jar file to the directory 3) Shutdown WebSphere 4) Follow the Fix installation instructions that are packaged with the Update Installer on how to install the Fix. NOTE: This iFix must be applied to the WebSphere Deployment Manager, not to an individual application server. Instructions below explain how to propagate the fix to the application server(s) on which UDDI is deployed. 5) Restart WebSphere 6) The temp directory may be removed. 7) You have now updated the UDDI application file, uddi.ear, in the installableApps directory on the WebSphere Deployment Manager so that it incorporates the Fix. The fixed UDDI application needs to be redeployed on any application servers on which you have previously deployed UDDI, in order to take advantage of the Fix. This should be done as follows: If using a Deployment Manager Configuration If you have previously deployed UDDI in an application server within a deployment manager cell, then you should re-run the setupuddi.jacl script by following the instructions in the WebSphere Application Server Network Deployment 5.1 Information Center under the appropriate section: "Setting up the UDDI Registry to use Cloudscape within a deployment manager cell" or "Setting up the UDDI Registry to use DB2 within a deployment manager cell", depending on which database product you are using (these sections will be found under the topic of "Installing and setting up a UDDI Registry"). This will deploy the fixed version of the UDDI Registry application into the specified application server. If using a standalone application server Configuration If you have previously deployed UDDI in a standalone application server, then you must first copy the new uddi.ear file from the installableApps directory on the deployment manager to the installableApps directory on the application server. You should then re-run the appserversetupuddi.jacl script by following the instructions in the WebSphere Application Server Network Deployment 5.1 Information Center under the appropriate section: "Setting up the UDDI Registry to use Cloudscape in a single application server" or "Setting up the UDDI Registry to use DB2 in a single application server", depending on which database product you are using (these sections will be found under the topic of "Installing and setting up a UDDI Registry"). This will deploy the fixed version of the UDDI Registry application into the application server. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE ORDER 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, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere 2) Follow the instructions that are packaged with the Update Installer on how to uninstall the Fix. 3) Restart WebSphere 4) You have now reverted to the pre-Fix version of the UDDI application file, uddi.ear, in the installableApps directory on the WebSphere Deployment Manager. The pre-Fix version of the UDDI application needs to be redeployed on any application servers on which you deployed the fixed version of UDDI, in order to remove the Fix. This should be done as follows: If using a Deployment Manager Configuration If you deployed the fixed UDDI in a deployment manager cell, then you should re-run the setupuddi.jacl script by following the instructions in the WebSphere Application Server Network Deployment 5.1 Information Center under the appropriate section: "Setting up the UDDI Registry to use Cloudscape within a deployment manager cell" or "Setting up the UDDI Registry to use DB2 within a deployment manager cell", depending on which database product you are using (these sections will be found under the topic of "Installing and setting up a UDDI Registry"). This will deploy the pre-Fix version of the UDDI Registry application into the specified application server within the deployment manager cell. If using a standalone application server Configuration If you deployed the fixed UDDI in a standalone application server, then you must first copy the pre-Fix version of the uddi.ear file from the installableApps directory on the deployment manager to the installableApps directory on the application server. You should then re-run the appserversetupuddi.jacl script by following the instructions in the WebSphere Application Server Network Deployment 5.1 Information Center under the appropriate section: "Setting up the UDDI Registry to use Cloudscape in a single application server" or "Setting up the UDDI Registry to use DB2 in a single application server", depending on which database product you are using (these sections will be found under the topic of "Installing and setting up a UDDI Registry"). This will deploy the pre-fix version of the UDDI Registry application into the application server. Directions to re-apply fix: 1) Follow the instructions for uninstalling a Fix 2) Follow the instructions for installing a Fix Additional Information: None