Versions Compared

Version Old Version 16 New Version 17
Changes made by

Julio Polo

Julio Polo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Login to your PRODUCTION server where your application runs and connects to esb.hawaii.edu
  2. Verify that there are no firewall issues (including firewalls on your end) by testing a connection to 128.171.224.56 port 5671.  If you can run openssl, you can do this test:
    • openssl s_client -connect esb-cluster.its.hawaii.edu:5671
  3. If you can run a program to connect to a different broker in this production environment without affecting your application's real data, continue.  STOP OTHERWISE.
  4. Test a connection to our future broker server using these settings: (DO NOT CONSUME MESSAGES YET IF POSSIBLE)
    • Host: esb-cluster.its.hawaii.edu (temporary name until we switch to esb.hawaii.edu for the upgrade)
    • Port: 5671
    • Vhost: (whatever vhost your application is currently using, this should be uhims for those using UHIMS Events)
    • User and password: same as your production application accounts in esb.hawaii.edu
    • Queues: same as your production queues
    • IP addresses: we allowed the same IP addresses you provided for esb.hawaii.edu.  Let us know if you need additional IP addresses allowed, ESPECIALLY IF YOU WERE USING esbprod1.pvt.hawaii.edu
  5. Test consuming messages
    • Once you are connected to the above broker, you can proceed to test consumption of messages.
    • The queues in this broker will become the real queues on the day of the upgrade, so they are getting live copies from production and they will be trimmed to match where the old server stopped during the upgrade.
    • DO NOT RUN THESE TESTS AFTER 10/17/2019 4:30 PM.  The queues will begin synchronizing in preparation for the upgrade.
    • You have three options to run tests for consuming messages:
      • If possible, consume only one message and disconnect.  You are done testing.
      • Otherwise, see if you can consume without ack, then disconnect.  This will put back the messages.
      • If none of the above are possible, go ahead and consume and ack as little messages as you can.
  6. Don't forget to stop any consumers and disconnect from the future broker.
  7. You should not use esb-cluster.its.hawaii.edu for anything other than these pre-deployment tests! On the day of the upgrade, esb-cluster.its.hawaii.edu may still point to the production server but the cert's host name won't match since it will become esb.hawaii.edu.