The Configure JMS Import Service dialog box
opens. An interface with a one-way operation results in the dialog shown below.

An interface with a request-response operation produces a similar
dialog as shown below with an additional field for a receive destination.

Select the messaging domain: Point-to-Point or Publish-Subscribe.
Publish-subscribe is selectable if the interface only has one-way operations.
Select
if you wish to Configure new messaging provider resources (the
default) or Use pre-configured messaging provider resources.
If you choose pre-configured, then add the JNDI names for the connection factory
and the send destination for a one-way operation, and send and receive destinations
for a request-response operation.
In the Security configuration section,
enter the J2EE Connector (J2C) authentication data entries, if used by your
organization.
In the Data format section, select how the data
will be serialized between the business object and the JMS message. For data
bindings beginning Simple JMS, you must have previously
created the business objects required (see the Prerequisites section).
The default data bindings are:
- Serialized Business Object using JMS ObjectMessage sends
the business object whose underlying implementation is a service data object
(SDO) in a JMS object message to and from the JMS client. This serialization
type is preferred when dealing with other SOA components using JMS.
- Business Object XML Using JMS TextMessage serializes
the business object to and from XML and uses a JMS text message to communicate
with the JMS client. To see how the business object is serialized to XML,
see Business object XML using JMS text message serialization. Your wrapped data objects
must be a complex type; they can not be a simple type.
- Simple JMS TextMessage Data Binding sends the JMSTextBody
business object in a TextMessage message body to the client. The message body
type is a String.
- Simple JMS BytesMessage Data Binding sends the
JMSBytesBody business object in a BytesMessage message body to the client.
The message body type is a byte array.
- Simple JMS MapMessage Data Binding sends the JMSMapBody
business object in a MapMessage message body to the client. The message body
type is a set of name/value pairs that can be addressed by name. The data
type of the value is a Java primitive.
- Simple JMS StreamMessage Data Binding sends the
JMSStreamBody business object in a StreamMessage message body to the client.
The message body type is a stream of Java primitives.
- Simple JMS ObjectMessage Data Binding sends the
JMSObjectBody business object in an ObjectMessage message body to the client.
The message body type is a serialized Java Object.
- Simple JMS Message Data Binding does not have a
message body. It can be used to notify the JMS client of an event or to send
some simple data in the message headers or properties.
The alternative is for you to provide your own data binding for
the serialization, in which case select User Supplied.
The implementation has to conform to the JMS data binding interface.
The
FunctionSelector class provides a valuable service at run time. It selects
an operation to invoke on the component. The operation maps to a function
to be performed based on the content of the JMS message. For example, the
message may contain an Employee record and be used to create, update, retrieve,
or delete the an Employee record. The actual operation to invoke is determined
from content in the header or body of the JMS message. In the Function
selector section, if you do not wish to use the TargetFunctionName
message header property for the default JMS function selector class, deselect
it.
Click OK. The JMS binding is created and shown in the properties
view when the Binding tab is selected.
Note: The JMS binding is
complete as is and only if you need to change the values do you need to change
them in the fields discussed below. Some of the values will need to match
those specified on the server such as the resource adapter name and bus name.
If you have runtime documentation, these properties will be specified there
as well. There is a link in the next paragraph to the runtime documentation.
The
following sections describe the major binding properties. After generating
a JMS binding with the wizard, you can use hover help to get descriptions
of all the properties. These properties are also fully described in the administration reference of the WebSphere Process
Server.