|
The Request tab is used to configure properties of the
request to the messaging system. You can configure the following fields:
Destination Type:
You must specify whether the name specified in the Queue or Topic
Name field below is a Queue or Topic.
Queue or Topic Name:
Enter the name of the queue or topic that you want to drop messages on to.
Delivery Mode:
The Enterprise Gateway supports the following delivery modes:
-
Persistent:
Instructs the TIBCO EMS Server to ensure that a message is not lost
in transit if the server fails. A message sent with this delivery
mode is logged to persistent storage when it is sent.
-
Non-persistent:
Does not require the TIBCO EMS Server to store the message. With
this mode, the message may be lost if the server fails.
-
Reliable:
When using reliable mode the TIBCO EMS Server never sends an
acknowledgment or confirmation receipt back to the producer. This
greatly decreases the volume of traffic on the network and can
result in improved performance.
Priority Level:
You can use message priority levels to instruct the TIBCO EMS server to
deliver urgent messages first. The ten levels of priority range from 0
(lowest) to 9 (highest). If you do not specify a priority level, the
default level is 1. The TIBCO EMS Server tries to deliver higher priority
messages before lower priority ones but does not have to deliver messages
in exact order of priority.
Time to Live:
By default, a message never expires. However, if a message becomes obsolete
after a certain period, you may want to set an expiration time (in milliseconds).
If the specified time to live value is 0, the message never expires.
Message ID:
Enter an identifier to be used as the unique identifier for the message. By default,
the unique identifier is the ID assigned to the message by the Enterprise Gateway
(${id}). However, you can use a proprietary correlation system,
perhaps using MIME message IDs instead of Oracle message IDs.
Correlation ID:
Enter an identifier for the message that the Enterprise Gateway uses to correlate response
messages with the corresponding request messages. Usually, if ${id}
is specified in the Message ID field above, it is also used here to
correlate request messages with their correct response messages.
Message Type:
This enables you to specify the type of data to be serialized and sent in the message
to the TIBCO EMS Server. The option selected depends on what part of the message you
want to send to the consumer.
For example, if you wish to send the message body you should select the option to format
the body according to the rules defined in the
SOAP over JMS recommendation. Alternatively, if you wish to serialize a list of
name-value pairs to the message, choose the option to create a MapMessage.
The following list describes the various serialization options available:
-
Use content.body attribute to
create a message in the format specified in the SOAP over Java
Messaging Service recommendation:
If this option is selected, messages are formatted according to
the SOAP over JMS
recommendation. This is the default option.
-
Create a MapMessage from the java.lang.Map in the
attribute named below:
Select this option to create a javax.jms.MapMessage
from the Oracle message attribute (named below) that consists of
name-value pairs.
-
Create a ByteMessage from the attribute named below:
Select this option to create a javax.jms.ByteMessage
from the Oracle message attribute named below.
-
Create an ObjectMessage from the java.lang.Serializable
in the attribute named below:
Select this option to create a javax.jms.ObjectMessage
from the Oracle message attribute named below.
-
Create a TextMessage from the attribute named below:
A javax.jms.TextMessage can be created from
the message attribute named below by selecting this option.
Attribute Name:
Enter the name of the Oracle message attribute that holds the data to be
serialized to a JMS message and sent over the wire to the TIBCO EMS Server.
The type of the attribute named here must correspond to that selected in the
Message Type field above.
Custom Message Properties:
You can set custom properties for messages in addition to the standard JMS header
fields. Custom properties may be useful to pass additional information to the TIBCO
EMS Server. You can use message attributes as property values. For example, you can
create a property called AuthNUser, and set its value to
${authenticated.subject.id}. When this message is routed to the specified queue or
topic, other consumers can then filter on this property (for example, only consume
messages where AuthNUser equals admin).
|