Test your Application Locally in a Docker Setup

Procedure

  1. Execute the command in a docker terminal. 
    docker run -ti -e "EMSSSL_URL=ssl://54.167.122.175:7243" -e "SSL_QUEUE=emsssl.queue" bwce-jms-ssl-app
  2. Execute the following command to views the logs to make sure that the application has successfully started. 
    docker logs <container name>
  3. Check the logs to make sure application has run successfully.
    You should see some message like below: 
    16:19:48.00023:19:48.225 INFO [Thread-22] com.tibco.thor.frwk.Application - TIBCO-THOR-FRWK-300006: Started BW Application [tibco.bwce.sample.palette.jms.SSL.application:1.0]
16:19:48.00023:19:48.664 INFO [bwEngThread:In-Memory Process Worker-1] c.t.b.p.g.L.t.b.s.p.jms.SSL.Log - Sending 5 Queue Messages
16:19:49.00023:19:49.962 INFO [bwEngThread:In-Memory Process Worker-2] c.t.b.p.g.L.t.b.s.p.jms.SSL.Log1 - Getting 5 Queue messages... ==This is message number 1
16:19:50.00023:19:50.222 INFO [bwEngThread:In-Memory Process Worker-3] c.t.b.p.g.L.t.b.s.p.jms.SSL.Log1 - Getting 5 Queue messages... ==This is message number 2
16:19:50.00023:19:50.471 INFO [bwEngThread:In-Memory Process Worker-4] c.t.b.p.g.L.t.b.s.p.jms.SSL.Log1 - Getting 5 Queue messages... ==This is message number 3
16:19:50.00023:19:50.725 INFO [bwEngThread:In-Memory Process Worker-5] c.t.b.p.g.L.t.b.s.p.jms.SSL.Log1 - Getting 5 Queue messages... ==This is message number 4
16:19:50.00023:19:50.975 INFO [bwEngThread:In-Memory Process Worker-6] c.t.b.p.g.L.t.b.s.p.jms.SSL.Log1 - Getting 5 Queue messages... ==This is message number 5