...

How to test the new broker

1. Verify TEST FIREWALL
   
   • This is to verify that you won't have issues with the new firewall:
   • Login to the system where your production application runs and connects to the UH Message Broker:
   • Run this openssl command:

     • openssl s_client -connect 128.171.138.176:5671
       The first few lines should look like this ( it is not enough to get a single CONNECTED line!):

       No Format
       CONNECTED(00000003) depth=2 C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority verify return:1 depth=1 C = US, O = Internet2, CN = InCommon RSA Server CA 2 verify return:1 ...

       
       

2. TEST CONSUMING MESSAGES
   
   • Set up or go to a test instance of your application
     
   • If you need to test from a host that has never connected to esb-test1 or esb-test2, please send us the IP address of this test host to its-iam-help@lists.hawaii.edu and wait for us to allow it through our firewall. You can also run the openssl command from step 1 above to check whether you are already allowed to connect.
   • Connect the test instance of your application to the following test broker:
     • Test broker host: esb-test1.its.hawaii.edu
     • Test broker port: 5671 (TLS 1.1 no longer supported, must use TLS 1.2 or 1.3)
     • Test broker account and password: (same as esb-test2, contact us if you've never connected to esb-test2 before)
     • Test broker vhost: (same as esb-test2)
     • Test broker exchanges and queues: (same as esb-test2)
   • Verify that the test instance of your application can consume messages from the above test broker.

Have more questions? Contact its-iam-help@lists.hawaii.edu

...