Configure the Java Message Service (JMS) queues to enable communication
with the job scheduler message-driver interface application. The application
carries out a message-driven bean (MDB) that requires a connection factory,
an activation specification, and an input queue. The MDB also uses an output
queue for response messaging with its clients.
Before you begin
Ensure that WebSphere platform messaging is the provider for all of
the JMS artifacts.
About this task
Complete the following steps to configure the JMS queues. This task
may be performed by the wsgridConfig script. See
Configuring the job scheduler message-driven interface and associated JMS artifacts for
details.
Procedure
- Define the connection factory.
- Click Resources > JMS > Connection factories in the administrative
console.
- Set the scope as Cluster=Scheduler, and click New.
- Select the JMS resource provider with which to create the Connection
factory, and click OK.
- Define the general properties by first typing com.ibm.ws.grid.ConnectionFactory for Name and jms/com.ibm.ws.grid.ConnectionFactory for JNDI name.
Next, type JobSchedulerBus for Bus
name and type the provider endpoints that correspond to the service integration
bus (SIB) endpoints for the job scheduler. Click OK to save the definition.
Attention: Specify the provider endpoints as triplets in the format
of host:chainName:port. The chainNames for WebSphere platform
messaging are BootstrapBasicMessaging and BootstrapSecureMessaging. The port
numbers are named SIB_ENDPOINT_ADDRESS and SIB_ENDPOINT_SECURE_ADDRESS.
If
a cluster hosts the job scheduler, you must specify one entry for each cluster
member. Entries are comma delimited. For example, zwasc013.rtp.raleigh.ibm.com:7278:BootstrapBasicMessaging.
- Define the input and output queues.
- Click Resources > JMS > Queues in the administrative console.
- Set the scope as Cluster=Scheduler, and click New.
- Select the JMS resource provider, and click OK.
- Use the following values to specify the attributes:
- For the input queue:
- Type com.ibm.ws.grid.InputQueue for Name.
- Type jms/com.ibm.ws.grid.InputQueue for JNDI name.
- Type JobSchedulerBus for Bus name.
- Type com.ibm.ws.grid.InputQueue as the name of the queue,
which is actually a bus destination name. Click OK to save the definition.
- For the output queue:
- Type com.ibm.ws.grid.OutputQueue for Name.
- Type jms/com.ibm.ws.grid.OutputQueue for JNDI name.
- Type JobSchedulerBus for Bus name.
- Type com.ibm.ws.grid.OutputQueue as the destination name.
Click OK to save the definition.
- Define the activation specification.
- Click Resources > JMS > Activation specifications.
- Set the scope as Cluster=Scheduler, and click New.
- Select the JMS resource provider, and click OK.
- Define the general properties by first typing com.ibm.ws.grid.ActivationSpec for Name and eis/com.ibm.ws.grid.ActivationSpec for JNDI name.
Next, type the JNDI name of the JMS
input queue, and type JobSchedulerBus for Bus name.
Click OK to save the definition.
What to do next
Restart the job scheduler to implement the configuration changes
that you just made to each of the three elements.