Skip to content

Latest commit

 

History

History
142 lines (109 loc) · 4.69 KB

README.md

File metadata and controls

142 lines (109 loc) · 4.69 KB

MQ Badge developer challenge

This is the Java template with code stubs for the MQ Badge developer challenge. You can use this code as a starting point as you build a messaging application that integrates a ticket reseller with an event booking system.

Take a look at the IBM Developer Essentials course

Prerequisites

You will need to download and install Maven for this application to work.

note if you are using podman, replace 'docker' in the commands below with 'podman'

Ticket Service

For convenience the Ticket Service is provided as MQ docker image. When started it will start both MQ server and the Ticket service. The MQ Server is configured to create and configure the queues and topics that the Ticket Service requires.

Docker FROM

The Dockerfile bases its image on icr.io/ibm-messaging/mq:latest by default(for AMD64 and x86-64 architecture). This image is pulled from the IBM Container Registry.

If you are using a MacOS Silicon (ARM64) system, you will need to build and run an IBM MQ container image natively. You can do so using the link below: https://community.ibm.com/community/user/integration/blogs/richard-coppen/2023/06/30/ibm-mq-9330-container-image-now-available-for-appl

Then check which image you have:

docker images

Your baseImageRunStage argument will be "repositoryName:tagName", which will be used when building your docker image. For example: baseImageRunStage="localhost/ibm-mqadvanced-server-dev:9.4.0.0-arm64"

The ticker reseller docker file will not run with

  • 9.1.4.0-r1 or earlier.

Running the following command will determine which version you are using.

docker image inspect <your image id> --format '{{.ContainerConfig.Labels.version}}'

Docker Build

To build the docker image, open a terminal, navigate to the MQTicketService directory, then run

For Mac or Linux users: The default arguments must be overidden with the correct platform architecture and images. note --build-arg baseImageRunStage

docker build --build-arg platformArch=arm64 --build-arg baseImageRunStage="localhost/ibm-mqadvanced-server-dev:9.4.0.0-arm64" . -t mqbadge:latest

For Windows users:

docker build . -t mqbadge:latest

Docker Run

To start the container, run

docker run -e LICENSE=accept -e MQ_QMGR_NAME=QM1 -e LOG_FORMAT=json -e MQ_APP_PASSWORD=passw0rd -p 1414:1414 -p 9443:9443 --detach -ti --name mqebs mqbadge:latest

This will configure and start the MQ Server, then will start the Ticket Service application.

Docker Restart

The Ticket Service will time it self out. To restart a stopped container run

docker restart mqebs

Then you can attach to the container to see its output:

docker attach mqebs

ModelAnswer

Open another terminal alongside the TicketService.

If you have installed Maven, change your working directory to ModelAnswer.

To create the .jar file with the dependencies required for the application, run the following command:

mvn clean package

Reseller.java

The main entry point for the reseller application is in Reseller.java

Challenge Code Changes

For the challenge you will make code updates to SessionBuilder.java, TicketSubscriber.java and TicketRequester.java.

Application

The application will run as a code stub. When run the application logs will indicate where code changes need to be made.

To run the application

For Mac and Linux users:

java -cp target/ModelAnswer-1.4.jar:. com.ibm.mq.demo.Reseller

For Windows users:

java -cp target/ModelAnswer-1.4.jar com.ibm.mq.demo.Reseller

Environment variables

You can override the default MQ connection settings using environment variables on the system where you run your Reseller application code.

  • MQ_BADGE_QM_HOSTNAME - Specify the Host name or IP address of your queue manager
  • MQ_BADGE_QM_NAME - Set the queue manager name
  • MQ_BADGE_QM_PORT - Listener port for your queue manager
  • MQ_BADGE_CHANNEL - MQ Channel name
  • MQ_BADGE_USER - User name that application uses to connect to MQ
  • MQ_BADGE_PASSWORD - Password that the application uses to connect to MQ

This is the default configuration. Run the following in your command terminal.

For Mac and Linux users:

export MQ_BADGE_QM_HOSTNAME = "localhost"
export MQ_BADGE_QM_NAME = "QM1"
export MQ_BADGE_QM_PORT = 1414
export MQ_BADGE_CHANNEL = "DEV.APP.SVRCONN"
export MQ_BADGE_USER = "app"
export MQ_BADGE_PASSWORD = "passw0rd"

For Windows users:

set MQ_BADGE_QM_HOSTNAME = "localhost"
set MQ_BADGE_QM_NAME = "QM1"
set MQ_BADGE_QM_PORT = 1414
set MQ_BADGE_CHANNEL = "DEV.APP.SVRCONN"
set MQ_BADGE_USER = "app"
set MQ_BADGE_PASSWORD = "passw0rd"