TIBCO EMS Consumers are added at the Process level in the Policy Studio.
To add a consumer, right-click the "Oracle Enterprise Gateway" node
under "Processes" in the tree view of the Policy Studio. Select the
TIBCO -> Enterprise Messaging Consumer Service -> Add
options from the context menus. The following tabs and fields should be
configured on the
TIBCO Enterprise Messaging Service Consumer dialog.
Connection Tab:
Select a previously configured TIBCO EMS Connection for this consumer to
connect to. TIBCO EMS Connections are configured globally under the
"External Connection" node in the tree view of the Policy Studio. Take a
look at the
TIBCO EMS Connection
page for more information.
Settings Tab:
Configure the following fields on the Settings tab:
Destination Type:
Select whether this consumer will read messages off a queue or topic.
Queue/Topic Name:
Enter the name of the queue or topic here.
Selector:
Enter a filter to restrict the messages that are read off the queue or
topic.
Do Not Receive Local Messages:
Check this option if you do not want to consume messages that have been
produced by the Enterprise Gateway. For example, if you have configured a
TIBCO EMS Routing filter to place messages on to a queue and have also
configured a TIBCO EMS Consumer to read messages from the same queue, you
can check this option to ensure that the consumer will ignore these
locally generated messages.
Extraction Method:
The option selected here determines how the Enterprise Gateway will serialize
the JMS message consumed from the queue or topic so that it can be
passed into the policy selected on the Policy tab. The
following options are available:
-
Create a content.body attribute based on the SOAP over
JMS draft specification:
If this option is selected, messages are formatted according to
the SOAP over JMS
recommendation, and stored in the content.body
message attribute.
-
Insert the JMS message directly into the attribute
named below:
Select this option to simply store the JMS message directly into
the attribute specified in the Attribute Name
field below.
-
Populate the attribute below with the value inferred
from message type to Java:
Select this option if you wish to infer the data type of the JMS
message from the underlying TIBCO EMS data type. In this case a
TIBCO EMS TextMessage, BytesMessage, and MapMessage, will be
converted into a java.lang.String, a byte[], and a java.lang.Map,
respectively, while a JMS ObjectMessage will be deserialized into
the attribute specified in the Attribute Name
field below.
Attribute Name:
Once the message has been consumed it will be stored in the Oracle
message attribute specified here. The Extraction Method
selected above will determine how the raw JMS message is deserialized to
the specified attribute. The consumed message can be processed
at any stage hereafter in the policy selected on the
Policy tab by accessing this attribute. By default
the message is stored in the ems.message attribute.
Policy Tab:
Select a previously configured policy that you want to pass messages to
after consuming the messages from the queue or topic configured on the
Settings tab.
|