Configuring and running agents in containerized developer toolkit
The procedure to configure and run agents from the runtime extracted from containerized developer toolkit.
Procedure
- Ensure that you have a copy of the extracted runtime as documented in Step 5 of Setting up the containerized developer toolkit environment
- 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 need to create custom queues, then run the following command:
./om-compose.sh add-queue NEW_QUEUE_NAMENote: The value forNEW_QUEUE_NAME
must be given in uppercase.
This command creates the queue on the MQ server and also updates the MQ .bindings file. You can also review or monitor your MQ resources by browsing the IBM MQ console athttps://IP address:9444/ibmmq/console/
by using the credentials admin/passw0rd.Note: You can uselocalhost
if it is deployed locally. - 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>/jndiIf you have overridden the
MQ_JNDI_DIR
property, then 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.