Configuring and running agents in containerized developer toolkit

Configure and run agents from the runtime extracted from the containerized developer toolkit.

Procedure

  1. Ensure that you have a copy of the extracted runtime as documented in Step 5 of Setting up the containerized developer toolkit environment.
  2. By default, the following Dev queues are created during setup and the bindings are automatically updated.
    DEV.QUEUE.1, DEV.QUEUE.2, DEV.QUEUE.3, similarly, up to DEV.QUEUE.10.
    You can use these queues for all your development needs. If you want to create custom queues, run the following command:
    ./om-compose.sh add-queue NEW_QUEUE_NAME
    Note: The value for NEW_QUEUE_NAME must be in uppercase.

    This command creates the queue in the IBM MQ server and also updates the IBM MQ .bindings file. You can also review or monitor your IBM MQ in the IBM MQ console. To launch the IBM MQ console, in the address bar of any supported browser, type https://IP address:9444/ibmmq/console/. By default, the password for IBM MQ console is set in the compose/docker/docker-compose.properties file. The MQ_PASS variable contains a password for the admin user and MQ_PASS2 contains a password for the reader user. For more information about updating the IBM MQ console password, see Docker Compose commands reference.
    Note: If the application is deployed locally, you can use localhost.

    If your developer toolkit is running on a Windows system, use the IP address of your WSL 2 system. If you want to use localhost, you must forward the relevant port to the IP address of your WSL 2 system. For more information, see Prerequisites for setting up containerized developer toolkit on a Windows environment.

  3. Configure and run agent servers.
    Use the following criteria to configure an agent by using the Applications Manager:
    Criteria Value
    JMS Queue Name Any Queue. For example, DEV.QUEUE.1
    QCF Lookup AGENT_QCF
    Initial Context Factory File
    Provider URL If you are not overriding the MQ_JNDI_DIR property, your PROVIDER_URL is file://<full path to devtoolkit_docker directory>/jndi

    If you have overridden the MQ_JNDI_DIR property, your Provider URL becomes file://<MQ_JNDI_DIR>

    For more information, see Specifying a time-triggered transaction.

    Go to your extracted runtime/bin directory and run the agent server.