IBM Support

Creating Additional Continuous Queues and MDBs

Question & Answer


How to you create additional continuous queues in WebSphere for Maximo 7?


In WebSphere, you will need a new destination, queue, and activation specification as well as a new MDB and queue definition within Maximo.

Follow the steps below to create an additional continuous queue.

Additional Continuous Queue Destination:
1. Log in to your WebSphere console and navigate in the left pane to Service Integration/buses
2. Select your bus, i.e. meajmsbus
3. Under "destination resources" click "destinations"
4. click the "new" button
5. Set the destination type as "queue" and click “next”
6. In the identifier field, enter "cqin2bd" and click “next”
7. Assign the queue in the next screen to the MEA application server or cluster if a cluster of MEA servers exists
8. Click “next”
9. Click “finish” and save the changes
10. Navigate back to this destination, and set the exception destination radio button to “specify” and set the value in the textbox to cqinbderr (this will be the name of your continuous error queue on the same bus)
11. Set the “maximum failed deliveries” to 5
12. Click “apply” and save the changes

Additional Continuous Inbound Queue:
1. Navigate to Resources/JMS providers
2. Select the default message provider at the cell scope and under "additional properties", click “queues”
3. Click the "new" button
4. Enter the name as "cqin2"
5. In the JNDI name field, enter "jms/maximo/int/queues/cqin2”
6. Select the meajmsbus as the bus for this queue from the bus name drop down (be sure to select the correct bus if you have multiple buses)
7. Select the cqin2bd queue from the queue name drop down
8. Click "apply" and save the changes

Additional Activation Specification for new Continuous Queue:

1. Navigate to Resources/JMS providers
2. Select the default message provider at the cell scope and under "additional properties", click “activation specifications”
3. Click the "new" button
4. In the name field, enter "intjmsact2"
5. In the JNDI name field, enter "intjmsact2"
6. In the "Destination JNDI name" field, enter "jms/maximo/int/queues/cqin2"
7. Make sure the destination type is "queue"
8. Select the bus "meajmsbus" from the bus name drop down (be sure to select the correct bus as per above)
9. Set Maximum batch size to 10
10. Set Maximum end points to 5
11. Click OK and save the changes

Adding the MDB in Maximo for the new Continuous Queue:

1. locate the file under maximo/applications/maximo/mboejb/ejbmodule/meta-inf/ejb-jar.xml

2. Edit the file and add the following two sections:

<!-- MEA MDB for Second Inbound Continuous Queue -->
<message-driven id="MessageDriven_JMSContQueueProcessor_3">
<env-entry-type>java.lang.String </env-entry-type>

<!-- MEA MDB for Second Inbound Continuous Queue -->

3. locate the file under maximo/applications/maximo/mboejb/ejbmodule/meta-inf/ibm-ejb-jar-bnd.xmi

4. Edit the file using a text editor and add the following section:

<!-- MEA MDB For Second Inbound Continuous Queue -->
<ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="MessageDrivenBeanBinding_3" activationSpecJndiName="intjmsact2">
<enterpriseBean xmi:type="ejb:MessageDriven" href="META-INF/ejb-jar.xml#MessageDriven_JMSContQueueProcessor_3"/>

5. Build the maximo.ear

Create this new queue in Maximo:

1. Launch the Maximo application and log in:


2. Navigate to the Integration/External Systems application

3. Select any external system and then from the action menu, select add/modify queues

4. Create a new queue called cqin2:

Continuous inbound queue:
Queue JNDI name: jms/maximo/int/queues/cqin2
Queue Connection Factory: jms/maximo/int/cf/intcfmea (make sure this connection factory name matches the same name as the one on your original cqin queue)
Make sure sequential flag is false (unchecked)
Set inbound flag to true (checked)
Maximum Try count: 0
Click OK

Modify the external system that will process messages from this queue to use the new queue.

Redeploy the maximo.ear and restart the application server.

[{"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Component":"MEA: Generic","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.5;7.6","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}},{"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}},{"Product":{"code":"SSLKYL","label":"Maximo Enterprise Adapter"},"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
17 June 2018