Why and when to perform this task
When the IBM WebSphere UDDI Registry is running, it might issue messages to report events or errors. You can use these messages, described in Messages as your first aid to problem determination. If you need more details about the causes of a problem, you can turn on tracing for UDDI, as described in:
Below are a few of the common causes of errors that might be found and their suggested solutions.
"Error 500: JSPG0059E: Unable to compile class for JSP".
If this occurs, then you should clear out the temp directory of the WebSphere AppServer.
WASX7017E: Exception received while running file "setupuddi.jacl"; exception information: com.ibm.bsf.BSFException: error while eval'ing Jacl expression: java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key ErrMsgIncorrectNumArgs
ensure that the file setupuddimessages.jar is located in the lib subdirectory of the WebSphere deployment manager or application server under which you are running the script.
Applicability of the following list: [Version 5.0.1 and later]
>su db2inst1 (or name of your db2 instance) >db2 CATALOG DATABASE UDDI20
Note: If you have a copy of the file
SetupDB2UDDI.jar in your appserver directory, the application of the base
and Network Deployment PTFs will not update SetupDB2UDDI.jar in your appserver
directory. You must apply the PTF for Network Deployment to your DeploymentManager
file structure to update the SetupDB2UDDI.jar located there (in the /UDDIReg/scripts
subdirectory), and then manually copy this jar file to any application server
you may wish to run it on.
During installation, if you see the following error at the end of running the appserversetupuddi.jacl command, you can safely ignore the error. It is recommended that you start (or stop and restart) the application server and then continue.
Here is an example of the error:
UDIN2041I: Starting UDDI application. UDIN8019E: startApplication command for appname caught exception Exc. Values are: appname=UDDIRegistry, Exc=com.ibm.ws.scripting.Scripting Exception: com.ibm.websphere.management.exception.Connector Exception: ADMC0009E: Failed to make the SOAP RPC call: invoke
If attempting to use a remote DB2 database and you are experiencing problems attaching to the remote system, one of the possible causes might be IP addressing. You should not have this problem if the remote system is using a static IP address. If, however, the remote system is using DHCP, the two systems must be aware of each others subnet mask.
There are known limitations with the UDDI Utility Tools and a workaround for each:
Workaround: Add the referenced business that will 'own' the projected service to the EDF. If the business is not present in the target registry, it should be placed before the service's owning business in the EDF.
Workaround: If a circular reference is present between two or more service projections, break the cycle by removing one of the projections temporarily, perform the import and update the changed entity to reestablish the cycle in the target registry.
Workaround: After importing the tModel, perform a delete. This is done using the UDDI Utility Tools delete function, or any other UDDI Registry API access method.
Workaround: Add the referenced bindingTemplate to the EDF.
Workaround: Import the referenced business into the target registry before importing the tModel that references it.