Java™ Message Service
(JMS) modules are configuration containers for JMS resources. The
JMS modules store the information for the connection factories that
queues are configured to use.
Procedure
- Create a JMS module for the sequential outbound queue,
and name the module intjmssqoutuimodule. Target
the intjmssqoutuimodule module to the user interface cluster.
- Create a sequential outbound queue for the intjmssqoutuimodule
module with the following values:
- Name
- sqout
- JNDI Name
- jms/maximo/int/queues/sqout
Using the default name, sqout, create a subdeployment
for the sequential outbound queue that you created, and target it
to the sqoutuiserver JMS server.
- Create a connection factory for the queues that you
created with the following values:
- Name
- intjmssqconfact
- JNDI Name
- jms/maximo/int/cf/intsqcf
Do not create a subdeployment because the connection
factory inherits the JMS module target, which is the integration framework
cluster.
Set the connection factory XA transaction to enabled.
- Create a JMS module for the sequential queues, and name
the module intjmssqintmodule. Target the intjmssqintmodule
module to the integration framework cluster.
- Create a sequential inbound queue for the intjmssqintmodule
module with the following values:
- Name
- sqin
- JNDI Name
- jms/maximo/int/queues/sqin
Using the default name, sqin, create a subdeployment
for the sequential inbound queue that you created, and target it to
the sqinserver JMS server.
- Create a sequential outbound queue for the intjmssqintmodule
module with the following values:
- Name
- sqout
- JNDI Name
- jms/maximo/int/queues/sqout
Using the default name, sqout, create a subdeployment
for the sequential outbound queue that you created, and target it
to the sqoutserver JMS server.
- Create a connection factory for the queues that you
created with the following values:
- Name
- intjmssqconfact
- JNDI Name
- jms/maximo/int/cf/intsqcf
Do not create a subdeployment because the connection
factory inherits the JMS module target, which is the integration framework
cluster.
Set the connection factory XA transaction to enabled.
- Create a JMS module for the sequential outbound queue,
and name the module intjmssqoutcronmodule.
Target the intjmssqoutcronmodule module to the cron task cluster.
- Create a sequential outbound queue for the intjmssqintmodule
module, with the following values:
- Name
- sqout
- JNDI Name
- jms/maximo/int/queues/sqout
Using the default name, sqout, create a subdeployment
for the sequential outbound queue, and target it to the sqoutcronserver
JMS server.
- Create a connection factory for the queues that you
created with the following values:
- Name
- intjmssqconfact
- JNDI Name
- jms/maximo/int/cf/intsqcf
Do not create a subdeployment because the connection
factory inherits the JMS module target, which is the integration framework
cluster.
Set the connection factory XA transaction to enabled.
- Create a JMS module for the continuous queue and name it intjmscqmodule.
Target the intjmscqmodule module to the integration framework cluster.
- Create a continuous inbound queue for intjmscqmodule
with the following values:
- Name
- cqin
- JNDI Name
- jms/maximo/int/queues/cqin
Create a subdeployment for this queue with the default
name, cqin, and target it to the cqinserver JMS server.
- Create a connection factory for the queue that you created
with the following values:
- Name
- intjmscqconfact
- JNDI Name
- jms/maximo/int/cf/intcqcf
Do not create a subdeployment; the connection factory
inherits the JMS module target, which is the integration framework
cluster.
Set the connection factory XA transaction to enabled.
Set the Messages Maximum field to -1.