Setting up the WebSphere Service Registry and Repository Connectivity sample

When you have imported the WebSphere Service Registry and Repository (WSRR) Connectivity sample, you must configure IBM Integration Bus to connect to the WebSphere Service Registry and Repository before you can run the sample. The following steps are required in order to run the WebSphere Service Registry and Repository Connectivity sample:

1. Import the WSDL documents to the Service Registry
2. Configure the broker to connect to the Service Registry

Import the WSDL documents to the Service Registry

After importing the WebSphere Service Registry and Repository Connectivity sample (see WebSphere Service Registry and Repository Connectivity sample), the required WSDL documents DemoCustomer_v10.wsdl and DemoCustomer_v20.wsdl are included in the WSRR Connectivity Message Flows project. Export these files to your local file system and, by using your preferred tools, import the two WSDL files to the Service Registry, setting the Version property appropriately. See your WebSphere Service Registry and Repository documentation for detailed instructions.

After importing the WSDL documents to the Service Registry, the WSDL documents are available with the appropriate versions, as shown in the following screen capture.

Configure the broker to connect to the Service Registry

To find out more about displaying and changing properties of the service registry, see Displaying the configuration parameters for the WebSphere Service Registry and Repository nodes and Changing the configuration parameters for the WebSphere Service Registry and Repository nodes in the IBM Integration Bus documentation.

For information about how to configure the broker to connect to a secure Service Registry, see Accessing a secure WSRR repository.

The following steps show the minimum configuration that is required to run the sample:

1. From the command console, run the following command, substituting broker name for the name of your broker to display the properties of your broker:

   mqsireportproperties broker name -c ServiceRegistries -o DefaultWSRR -r

   This command produces a response similar to the following output:

   ReportableEntityName=''
   ServiceRegistries
     DefaultWSRR=''
       connectionFactoryName='jms/SRConnectionFactory'
       enableCacheNotification='false'
       endpointAddress='http://fill.in.your.host.here:9080/WSRRCoreSDO/services/WSRRCoreSDOPort'
       initialContextFactory='com.ibm.websphere.naming.WsnInitialContextFactory'
       locationJNDIBinding='iiop://fill.in.your.host.here:2809/'
       needCache='true'
       predefinedCacheQueries=''
       refreshQueriesAfterNotification='true'
       subscriptionTopic='jms/SuccessTopic'
       timeout='100000000'
   

2. Run the following command to change the properties of your broker, replacing the values for broker name and hostname with the names of your broker and host name:

   mqsichangeproperties broker name 
   -c ServiceRegistries -o DefaultWSRR -n endpointAddress 
   -v http://hostname:9080/WSRRCoreSDO/services/WSRRCoreSDOPort

   Repeat step 1 to view your updated broker properties. Ensure the endpointAddress is set appropriately, for example:

   endpointAddress='http://myHostName.myDomain.com:9080/WSRRCoreSDO/services/WSRRCoreSDOPort'
   

3. Stop and restart your broker to pick up the changed properties.

You can now run the WebSphere Service Registry and Repository Connectivity sample, see Running the WebSphere Service Registry and Repository Connectivity sample.

For information about the specific levels of WSRR that are supported with IBM Integration Bus, see IBM Integration Bus Requirements.

Back to sample home