Setting up a UDDI migration data source

For DB2®, you can set up a UDDI migration data source that you can use to reference a Version 2 UDDI registry database.

About this task

Only migration from DB2 is supported, so this procedure describes how to set up a DB2 data source.

Procedure

  1. If a suitable JDBC Provider for DB2 does not already exist, create one. Select the following options:
    • Database type: DB2
    • Provider type: DB2 Legacy CLI-based Type 2 JDBC Driver
    • Implementation type: Connection pool data source
  2. Create a data source for the Version 2 UDDI registry by following these steps:
    1. Click Resources > JDBC Providers.
    2. Select the scope of the JDBC provider that you selected or created earlier. For example, select the following to show the JDBC providers at the server level:
      Node=your_node_name, Server=your_server_name
    3. Select the JDBC provider that you created earlier.
    4. Select [Additional Properties] Data sources. Do not select [Additional Properties] Data Sources Version 4 .
    5. Click New to create a new data source.
    6. Enter the details for the data source as follows:
      Name
      Type a suitable name, such as UDDI Datasource.
      JNDI name
      Type datasources/uddimigration . This value is compulsory, and you must set it as it is shown.
      Use this Data Source in container-managed persistence (CMP)
      Ensure that the check box is cleared.
      Description
      Type a suitable description of the data source.
      Category
      Type uddi.
      Data store helper class name
      Ensure that this is set to com.ibm.websphere.rsadapter.DB2DataStoreHelper.
      Component-managed authentication alias
      Select the alias for the DB2 user id that is used to access UDDI Version 2 data, for example MyNode/UDDIAlias (refer to step 2 of Setting up a customized UDDI node if you do not have such an alias).
      Container-managed authentication alias
      Select (none).
      Mapping-configuration alias
      Select DefaultPrincipalMapping.
      DB2 legacy CLI-based type 2 data source properties
      Set Database name to UDDI20, or the name of the Version 2 UDDI DB2 database.
      Leave all other fields unchanged.
  3. Click Apply, then save the changes to the master configuration.
  4. Test the connection to your UDDI database by selecting the check box next to the data source and clicking Test connection. A message similar to Test Connection for datasource UDDI Datasource on server server1 at node MyNode was successful is displayed. If this message is not displayed, investigate the problem with the help of the error message.

What to do next

Continue with the migration, as detailed in Migrating to Version 3 of the UDDI registry.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 9:31:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=twsu_migrate_dsource
File name: twsu_migrate_dsource.html