Before you begin
When installing the Unit Test UDDI Registry on Linux when using DB2®,
the Unit Test UDDI Registry with DB2 Configuration
Page has an empty field for the driver location if you are running
as root. To solve this problem, source the db2profile before launching
the workbench. To do this type the following:
source {db2_instance_user_home}/sqllib/db2profile.
This will initialize environment variables that are used by the tools
to find the DB2 Driver location.
About this task
To configure the Unit Test UDDI registry, do the following
steps:
Procedure
- Click File > New > Other. Select Web
Services in order to display the various web service wizards.
Select the Unit Test UDDI wizard. Click Next.
- Select the Private UDDI Registry type that you want to
configure or update, and click Next.
- Depending on the UDDI registry type you have chosen you
need to provide the following information:
- If you have selected a DB2-based registry you need to provide
the database user ID, password, and driver location.
- Add the user-defined categories. For more information refer
to: Defining UDDI categories.
- Select if you want to create a new server for the UDDI registry
or if it should be on an existing server.
- You can optionally choose to launch the Web Service Explorer
which provides you with additional tools for working with UDDI registries.
For additional information refer to: Publishing web services and business entities
What to do next
Notes®:- The combo box lists all combinations of Databases and Servers
available. If the WebSphere® runtimes
are not enabled, you will get an error if you select a WebSphere-based
Registry. If you encounter this problem, add the WebSphere Runtime from Windows
> Preferences > Server > Installed Runtimes, then add
the WebSphere Runtime
and specify the installation path. Run the Unit Test UDDI Registry
Wizard again, the Registry will be enabled.
- The Private UDDI Registry should only be configured with the Derby
database for very basic testing purposes (do not use Derby for production
work as there are currently difficulties with actions such as complex
queries). For more information on the Private UDDI Registry, please
refer to the Network Deployment documentation in the WebSphere Application Server Information
Center.
- When you attempt to publish to a Unit Test UDDI Registry, remember
that WebSphere Application
Server must be started before you do so. Otherwise you may encounter
an error similar to: An unexpected error has occurred. UDDI
Exception java.net.ConnectionException: connection refused: connect