Configuring MQ resources for the business process container using the administrative console

You must have already created the queues for the business process container.
It is recommended that you configure the resources using the script provided. If you must create the resources manually, this topic describes how to complete this task using the administrative console:
  1. In Resources > JMS Providers > WebSphere MQ > WebSphere MQ queue connection factories, click New.
    1. Enter the following values:
      Field Example value
      Name BPECF
      JNDI Name jms/BPECF
      Queue Manager WAS_nodename_servername
    2. Fill in the appropriate values for your WebSphere MQ installation for host, port, channel, and transport type.
    3. For authentication alias, perform one of the following:
      • If you use the WebSphere MQ JMS provider (external MQ) with the transport type bindings, no authentication alias is needed.
      • Otherwise, select component-managed authentication alias.
  2. Click Apply, and click Save. The MQ Queue Connection factory BPECF has been created and is listed on the MQ queue connection factory panel.
  3. Select Resources > JMS Providers > WebSphere MQ > WebSphere MQ queue connection factories.
  4. Click New.
    1. Enter the following values:
      Field Example value
      Name BPECFC
      JNDI Name jms/BPECFC
      Queue Manager WAS_nodename_servername
    2. Fill in the appropriate values for your WebSphere MQ installation for host, port, channel, and transport type.
    3. For authentication alias, perform one of the following:
      • If you use the WebSphere MQ JMS provider (external MQ) with the transport type bindings, no authentication alias is needed.
      • Otherwise, select component-managed authentication alias.
  5. Click Apply, and click Save. The MQ Queue Connection factory BPECFC has been created and is listed on the MQ queue connection factory panel.
  6. Define the MQ Queue Destination for the external message queue:
    1. In Resources > JMS Providers > WebSphere MQ > WebSphere MQ queue destination, click New.
    2. Enter the following values:
      Field Example value
      Name BPEApiQueue
      JNDI Name jms/BPEApiQueue
      Specified Priority 3
      Specified Expiry 3
      Base Queue Name BPEApiQueue
      Leave the other fields blank or accept the default values.
    3. Click Apply then Save.
  7. Define the MQ Queue Destination for the internal messages queue:
    1. In Resources > JMS Providers > WebSphere MQ > WebSphere MQ queue destination, click New.
    2. Enter the following values:
      Field Example value
      Name BPEIntQueue
      JNDI Name jms/BPEIntQueue
      Specified Priority 3
      Specified Expiry 3
      Base Queue Name BPEIntQueue
      Leave the other fields blank or accept the default values.
    3. Click Apply, then Save.
  8. Define the MQ Queue Destination for the hold queue:
    1. In Resources > JMS Providers > WebSphere MQ > WebSphere MQ queue destination, click New.
    2. Enter the following values:
      Field Example value
      Name BPEHldQueue
      JNDI Name jms/BPEHldQueue
      Specified Priority 3
      Specified Expiry 3
      Base Queue Name BPEHldQueue
      Leave the other fields blank or accept the default values.
    3. Click Apply, then Save.
  9. Define the MQ Queue Destination for the retention queue:
    1. In Resources > JMS Providers > WebSphere MQ > WebSphere MQ queue destination, click New.
    2. Enter the following values:
      Field Example value
      Name BPERetQueue
      JNDI Name jms/BPERetQueue
      Specified Priority 3
      Specified Expiry 3
      Base Queue Name BPERetQueue
      Leave the other fields blank or accept the default values.
    3. Click Apply, then Save.
    Now the four queue destinations have been defined and are listed on the queue panel.
  10. Create the listener port for external messages:
    1. In Servers > Application servers > YourServer > Messaging > Message Listener Service > Listener Ports, click New.
    2. Enter the following values:
      Field Example value
      Name BPEApiListenerPort
      Description Business Process Choreographer API
      Connection Factory JNDI Name jms/BPECF
      Destination JNDI Name jms/BPEApiQueue
      Max Sessions 5
      Max Retries 10
      Max Messages 1
    3. Click Apply, then Save.
  11. Create the listener port for the hold queue:
    1. In Servers > Application servers > YourServer > Messaging > Message Listener Service > Listener Ports, click New.
    2. Enter the following values:
      Field Example value
      Name BPEHoldListenerPort
      Description Business Process Choreographer hold
      Connection Factory JNDI Name jms/BPECF
      Destination JNDI Name jms/BPEHldQueue
      Max Sessions 5
      Max Retries 10
      Max Messages 1
    3. Click Apply, then Save.
  12. Create the listener port for internal messages:
    1. In Servers > Application servers > YourServer > Messaging > Message Listener Service > Listener Ports, click New.
    2. Enter the following values:
      Field Example value
      Name BPEInternalListenerPort
      Description Business Process Choreographer internal
      Connection Factory JNDI Name jms/BPECF
      Destination JNDI Name jms/BPEIntQueue
      Max Sessions 5
      Max Retries 10
      Max Messages 1
    3. Click Apply, then Save.
    The three listener ports have been created and are listed on the listener port panel.
The queue resources needed by the business process container have been created.
Create and configure the scheduler.

Parent topic: Configuring the queue resources for the business process container using WebSphere MQ