Creating an Websphere MQ Queue Manager (from scratch)

This guide gives an example of how to create a queue manager configuration and deploy it to create a queue manager on a target. It does not explain all of the permutations for queue managers, these can be gleaned from a combination of fully understanding this example and using the task reference and template help within the product. By the end of this guide you will have created a queue manager called QMGRD1 (representing a Development instance of a queue manager). Further guides may build on this example.

The following steps need to be completed

  1. Create a WMQ codeDeploy project (pre-requisite)
  2. Create an Environment Configuration for this project
    • Specify the logical names for the RapidDeploy objects
    • Configure the Server object to connect to your target
  3. Create a deployment package
  4. Execute a deployment

Create an Environment Configuration for QMGRD1

  • Assuming that you have created a Websphere MQ codeDeploy project navigate using the left menu to:
    • Configuration > Edit/Promote
  • Click on New Environment
  • Enter appropriate values for your Server, Environment, instance and application. The key values are the Server and the Environment, it is recommended that this reflects your queue manager name, the remainder of the fields are logical and could be used to assist with your sorting of different environment configurations
    • e.g. localhost, QMGRD1, QMGRD1, QMGRD1
  • Click on the Settings tab and fill in the form for all of the specific configuration that the queue manager requires. Use the help buttons to get a description of the field.
    • The last section of the form allows you to create a pre-written orchestration for this task. Select the orchestration that allows you to Create And Deploy To Queue Manager. This will provide correctly configured tasks within your Project's orchestration to create and deploy to a queue manager.
    • When complete save the Environment Configuration

The environment configuration creates a number of RapidDeploy objects, chief of which is the target server which needs configuring to successfully connect.

  • Configure the server to use one of the supplied transports (e.g. SSH or Remoting agent). Once done, ensure that the connection is successful by testing and also ensure you are using a user with the appropriate privileges
  • In addition to the Server object, you will also have created an Environment which will require configuring in the first instance. To do so;
    • Navigate to Resources > Targets > Environments and select the Environment we just created QMGRD1.
    • Set the Owner field to mvadmin and click on the Product tab.
    • Fill in the details to the queue manager, fully qualify any fields with a path in (for example /midvision/snapshots/wmq) and save the environment.

Create a deployment package

  • Navigate to Resources > Software Management > Packages
  • Select the WMQ_DEPLOY project (or the one you created as a pre-requisite for this task
  • Use the Add Package wizard to create a jarfile for this project (note it must contain the string used in the project)

Perform a deployment

  • Navigate to Jobs > New Job and select the project used for this technology
  • Select the Application created in this guide
  • Click Next and select the deployment package created previously, skip to finish and Execute this request.
  • The queue manager will be created on the specified target.

Creating Queue Manager in IBM MQ on remote WINDOWS server step by step tutorial

  1. Create RD project (code deploy) and as a Product choose WMQ plugin.
  2. In environment tab select server if it is created (it is the same server you used when you performed IBM MQ installation )and at the beginning put new name of Environment (you will configure it later).
  3. Go to Environment and specify Owner/binary path and display name.
  4. Go to Product tab in Environment and specify the name of new QueueManager, hostname (can be localhost), port, and channelEnvironment configuration
  5. The rest you can leave with default values
  6. Go back to your RD project to the Orchestration tab and add new task from WMQ WmqDefaultManageQueueManagerTaskOrchestration tab qm
  7. Now if you run the deployment you will have error because "wmq.qmgr.names" is not specified - please go to the project/environment tab then click edit and find EnvironmentConfiguration. Add new property: wmq.qmgr.names, wmq.qmgr.TestQM1.createqmgr, wmq.qmgr.TestQM1.connection and wmq.qmgr.TestQM1.versionProject env
  8. Now everything is ready, so you need to create package and start the deployment.
  9. When it is finished successfully you can check the status of the newly created Queue Manager by running dspmq command on your remote server