Manually creating queues in WebSphere MQ

You can manually create WebSphere® MQ queues to replace the queues that are automatically created when you install AS4 Microservice.

Before you begin

Important: Do not use this procedure as a stand-alone procedure. Use this procedure only when it is referenced by another installation procedure.

Procedure

To manually create queues in WebSphere MQ, complete the following steps:

  1. In the administrative console of WebSphere MQ, create the following items if they differ from what you entered when you installed AS4 Microservice:
    • Queue manager
      Important: IBM® recommends that you authenticate to the queue manager with a user ID and password.
    • Server-connection channel

      You can define your own channel or use the default SYSTEM.DEF.SVRCONN channel.

    • Listener

      This listener must be of the transmission type tcp with an unused port. After you define the listener, you must start it.

      Important: Use more than one host and port to achieve high availability. The list of host names and ports all must refer to the same multi-instance queue manager.
    • User ID
    • Password
  2. Access the MEG_QUEUES.mqsc file that defines the queues in AS4 Microservice. The MEG_QUEUES.mqsc file is in the install_dir\resources\wmq directory.
  3. As a WebSphere MQ administrative user, create the queues that are defined in the MEG_QUEUES.mqsc file.
  4. Ensure that a user account has the following WebSphere MQ permissions for the queues that you created from the MEG_QUEUES.mqsc file. In WebSphere MQ, an authorization is the permission to do an action.
    • chg
    • clr
    • dlt
    • dsp
    • passall
    • passid
    • setall
    • setid
    • browse
    • get
    • inq
    • put
    • set
  5. Access the message fabric properties file that was created when you installed AS4 Microservice. The message fabric properties file is the SystemConfigurationMFLoader.properties file in the install_dir\Members\resources directory. If necessary, update the following properties with information that you entered through the administrative console of WebSphere MQ:
    Important: This same information is used to configure the message fabric adapter and message fabric server adapter in Sterling B2B Integrator to enable Sterling B2B Integrator to communicate with AS4 Microservice.
    • messagefabric.jms.webspheremq.XMSC_WMQ_QUEUE_MANAGER (queue manager)
    • messagefabric.jms.webspheremq.XMSC_WMQ_CHANNEL (server-connection channel)
    • messagefabric.jms.webspheremq.WMQ_CONNECTION_NAME_LIST (listener)
    • messagefabric.jms.webspheremq.userid (user ID)
    • messagefabric.jms.webspheremq.password (password)
  6. Add the following line to the SystemConfigurationMFLoader.properties file to prevent updates to AS4 Microservice from automatically creating queues:
    messagefabric.meg.configuration.webspheremq.automaticDestinationCreation=false
  7. Enter the following commands to update AS4 Microservice with the changes that you made to the SystemConfigurationMFLoader.properties file.
    1. execute config load fabric
    2. execute member config all fabric
  8. Resume the installation of AS4 Microservice.