Scenario : Based on input coming into our consumer flow , We will get the corresponding Porttype and Name Space and Version details ,which are configured in WSRR , and based on end point URL our flow need to request the Service Provider and get the response.

Accessing a secure WSRR repository from MB

To access a secure WebSphere® Service Registry and Repository (WSRR) repository, set the configuration parameters by using the mqsichangeproperties command.

You must connect over HTTPS, not HTTP, which is specified in the endpointAddress configuration parameter of the default WSRR profile, DefaultWSRR.

To access a secure WebSphere Service Registry and Repository, enter the following sequence of commands:

Ensure that the broker is running. If it is not, use the mqsistart command to start it.
Use the ServiceRegistries configurable service to configure the broker to use HTTPS to communicate with the WSRR server. You can view the current configuration parameters for the ServiceRegistries configurable service by using the following command:

mqsireportproperties WSSRIntegrationBroker -c ServiceRegistries -o DefaultWSRR -r

where:

-c specifies the configurable service (in this case, ServiceRegistries)

-o specifies the name of the object (in this case, BrokerRegistry)

-r specifies that all property values of the object are displayed, including the

child values, if appropriate.

To change the endpointAddress configuration parameter to specify HTTPS and the secure port for the DefaultWSRR of the ServiceRegistries configurable service, use the following command.

mqsichangeproperties WSRRIntegration -c ServiceRegistries -o DefaultWSRR -n endpointAddress -v https://172.17.3.161:9443/WSRR6_1/services/WSRRCoreSDOPort

-n specifies the names of the properties to be changed

(in this case, endpointAddress)

-v specifies the values of properties defined by the -n parameter

(in this case, https://localhost:9443/WSRR6_1/services/WSRRCoreSDOPort)

Configure the broker keystore to contain your WSRR server certificate keys;Obtain these certificate keys from the installation of the WebSphere Application Server that hosts your WSRR server. The broker uses a single keystore, therefore, if your broker also implements WS-Security, HTTPS, or SSL-secured WebSphere MQ, you might need to merge the provided keys into an existing keystore file. The broker keystore is configured by using the mqsichangeproperties command to change configuration parameters for the broker. Display the current configuration parameters of the broker by using the following command:

mqsireportproperties WSRRIntegration -o BrokerRegistry -r

To change the brokerKeystoreFile configuration parameters for the broker, use the following command:

mqsichangeproperties WSRRIntegration -o BrokerRegistry -n brokerKeystoreFile -v C:\IBM\WebSphere\WSRR\v8.0\profiles\WSRRSrv01\etc\DummyClientKeyFile.jks

Configure the broker truststore to contain signer certificates for your WSRR server. As described previously for the keystore, the broker uses a single truststore, therefore certificates might need to be merged into an existing truststore file. The broker truststore is configured by using the mqsichangeproperties command. To change the brokerTruststoreFile configuration parameters for the broker, use the following command:

mqsichangeproperties WSRRIntegration -o BrokerRegistry -n brokerTruststoreFile -v C:\IBM\WebSphere\WSRR\v8.0\profiles\WSRRSrv01\etc\DummyClientTrustFile.jks

Stop the broker by using the mqsistop command. You must stop the broker to complete the following step.
Set the WebSphere Application Server user name and password by using the following command:

mqsisetdbparms WSRRIntegration -n DefaultWSRR::WSRR -u wasadmin -p miracle

Set the brokerKeystore user name and password by using the following command:

mqsisetdbparms WSRRIntegration -n brokerKeystore::password -u dummy -p WebAS

Set the brokerTrustStore user name and password by using the following command:

mqsisetdbparms WSRRIntegration -n brokerTruststore::password -u dummy -p WebAS

To use cache notification with your secure WSRR server, you must specify a valid user ID and password for the broker to use when connecting to the WSRR JMS cache notification topic. To set the user ID and password that the broker will use to make the JMS cache notification connection, use the following command: