Set up a UDDI migration datasource
Use this topic to set up a UDDI migration datasource, to be used to reference a V2 UDDI registry database.
Overview
Migration is only supported from DB2, so these instructions describe how to set up a DB2 datasource.
Procedure
- If a suitable JDBC Provider for DB2 does not already exist, then create one, selecting the options DB2 Universal JDBC Driver Provider and Connection Pool datasource.
For details on how to create a JDBC provider, see Creating and configuring a JDBC provider using the console.
- Create a datasource for the V2 UDDI registry by following these steps:
- Expand Resources and JDBC Providers. Click Resources > JDBC > JDBC Providers.
- Select the desired 'scope' of the JDBC provider you selected or created earlier. For example, select:
Server: yourservernameto show the JDBC providers at the server level.
- Select the JDBC provider created earlier. Under Additional Properties, select Data sources (not the Data sources (WAS V4) option).
- Click New to create a new datasource. In the Create a data source wizard, enter the following data:
- Name
- a suitable name, such as UDDI Datasource
- JNDI name
- set to datasources/uddimigration - this value is compulsory, and must be as shown.
- Component-managed authentication alias
- select the alias for the DB2 userid used to access UDDI V2 data, for example MyNode/UDDIAlias (refer to step 2 of Setting up a customized UDDI node if you do not have such an alias)
- Click Next.
- On the database specific properties page of the wizard, enter the following data:
- Database name
- UDDI20, or the name given to your V2 UDDI DB2 database.
- Use this Data Source in container-managed persistence (CMP)
- ensure the check box is cleared.
- Click Next, then check the summary and click Finish.
- Click the data source to display its properties, and add the following information:
- Description
- a suitable description
- Category
- set to uddi
- Data store helper class name
- filled in for you as: com.ibm.websphere.rsadapter.DB2DataStoreHelper
- Mapping-configuration alias
- set to DefaultPrincipalMapping
- Click Apply and save the changes to the master configuration.
- Test the connection to your UDDI database by selecting the check box next to the datasource and clicking Test connection. You will see a message similar to "Test Connection for datasource UDDI Datasource on server server1 at node MyNode was successful". If you do not see this message investigate the problem with the help of the error message.
What to do next
Continue with the migration as detailed in Migrating to V3 of the UDDI registry.
Related tasks
Migrating to V3 of the UDDI registry