Specifying the queues used for events
You can configure the hub to deliver
events to an external queue that is configured using JMS configuration.
The default JMS configuration is established when you install
the hub. You can see some of these values on the Event Publishing
Properties page. If you do not provide a value in the Provider URL Packages or
the JMS Provider URL fields, the defaults that
are in the MQ Properties section of the bcg.properties file are
used. These defaults use the JMS bindings that were generated at
installation time. If you took the defaults, the JMS bindings use
port 9999 on the MQ Server that you named during installation.
To point to a different set of JMS bindings, change the Provider URL Packages to point
to a directory containing a JMS bindings file that you have prepared
yourself. Also change the Queue Connection Factory name
and the Queue name to match the names you
chose in your JMS bindings. You would do this if you want to publish
the events to a queue on a different MQ server than the one you
specified during installation.
To indicate where events should be delivered:
- From the main menu, click System Administration > Event Processing > Event Delivery Information.
- Click the Edit icon next to Enable Event Delivery.
- Select the Enable Event Delivery check
box to activate event publishing.
- If the default values are correct for your installation, leave
them as is. The default values support event delivery to the queue
named DeliveryQ provided by the JMS Server that you configured at
installation.
If you want to change where events are delivered, update the
fields, using the following information as reference:
- Enter values for User ID and Password,
if a user ID and password are required to access the queue
- For JMS Queue Factory Name, enter the
name of the JMS Queue Connection Factory from the JMS .bindings
file that you are using.
Note: On some Windows versions (prior to XP), you might
need to change the default value of the JMS Queue Factory Name field
if you want to use the default Event Delivery feature. You will
need to change the value for JMS Queue Factory Name from: WBIC/QCF to WBIC\\QCF.
- For JMS Message Type, enter the type of
message that will be delivered. The choices are byte or text.
- For JMS Queue Name, enter the name of
the JMS queue to which the events will be published. This queue
must already be defined in the JMS .bindings file that you are using
in WebSphere MQ.
Note: On some Windows versions (prior to XP), you might
need to change the default value of the JMS Queue Name field
if you want to use the default Event Delivery feature. You will
need to change the value for JMS Queue Name from WBIC/DeliveryQ to WBIC\\DeliveryQ. WBIC/QCF.
- For JNDI Factory Name, enter the name
used to access the .bindings file. The default value provides access
to the default binding in the file system.
- For Provider URL Packages, enter a URL
that provides access to the JMS bindings file. This URL must be
consistent with the JNDI Factory Name. This field is optional and,
when not filled in, it uses the default file system location for
JMS bindings.
- For Message Char Set, enter the character
set to be used when creating the byte message on the JMS queue.
The default value is UTF-8. This field is relevant only for byte
messages.
- For JMS Provider URL, enter the URL of
the JMS provider. This field is optional and when not filled in,
it uses the default JMS provider that was identified at installation.
- Click Save.
