WebSphere Message Broker Registry Lookup Node Configuration

When configuring WebSphere Message Broke to call services loaded into WSRR the following two node can be used:
1. Registry Lookup
2. Endpoint Lookup

When using any of the two nodes the following configuration needs to be done:
Make sure Broker has been started when running the config: mqsistart.exe / mqsistart.sh
1. WSRR unsecure (No security enabled on WAS and URL start with http://)
mqsichangeproperties -c ServiceRegistries -o DefaultWSRR -n endpointAddress -v https://localhost:9443/WSRR6_3/services/WSRRCoreSDOPort

2. WSRR secure (Security enabled on WAS and URL start with https://)
Step 1: mqsichangeproperties -c ServiceRegistries -o DefaultWSRR -n endpointAddress -v https://localhost:9443/WSRR6_3/services/WSRRCoreSDOPort
Step 2: mqsireportproperties -o BrokerRegistry -r
Step 3: mqsichangeproperties -o BrokerRegistry -n brokerKeystoreFile -v C:\WSRR\SSL\DummyClientKeyFile.jks
Step 4: mqsichangeproperties -o BrokerRegistry -n brokerTruststoreFile -v C:\WSRR\SSL\DummyClientTrustFile.jks
Step 5: Stop the Broker: mqsistop.exe/mqsistop.sh
Step 6: mqsisetdbparms -n DefaultWSRR::WSRR -u wasadmin -p wasadmin
Step 7: mqsisetdbparms -n brokerKeystore::password -u dummy -p WebAS
Step 8: mqsisetdbparms MB7BROKER -n brokerTruststore::password -u dummy -p WebAS
Step 9: Start the Broker: mqsistart.sh/mqsistart.exe