You can use a JMS Adapter in a BP Server application in any of the three modes namely, Send-Only, Send/Receive, and Receive-Only. However, you can use a JMS Adapter in a Web application only in Send-Only mode; it cannot be used in Send/Receive mode and Receive-Only modes.
The Configuration tab in the Adapter workstep Properties view includes the following options:
Configure
Changemapping
Advanced properties
To perform the JMS Adapter configuration follow the steps:
1. Click Configure, to open the JMS Adapter Configurator.
Note: You can also open the JMS Adapter Configurator using the new Managed Adapter Browser (available only from Progress Developer Studio for OpenEdge) functionality. In addition to configuring, you can use the Managed Adapter Browser to perform functions like creating a copy, renaming, deleting, as well as importing and exporting the configuration information. For more information, refer to the "Using the Managed Adapter Browser" section of the Progress Developer Studio for OpenEdge User’s Guide.
The JMS Adapter Configurator has three tabs:
2. In the Configuration tab, specify general configuration parameters for the adapter, such as connection mode for the Adapter (Send, Send/Receive, and Receive options in the Adapter Mode list), connection factory, and destination (queue) name. Depending on the selected connection mode, the tabs Outgoing Message and Incoming Message may become disabled.
3. Click the Outgoing Message tab to define the format of the outgoing message. Currently, the JMS Adapter supports JMS Map message format, in which the message content is a set of name/value pairs. The Outgoing Message tab in turn includes two tabs:
Payload. Helps define the content of the message payload (body).
Properties. Lists message header properties that have to be set by the adapter.
4. Click the Payload tab to view a list of fields, each field associated with a parameter name and data type. To add a new parameter, click Add, to open the Parameter Editor dialog box. To modify existing parameters, select a parameter from those listed, click Modify, and make the required changes in the Parameter Editor dialog box.
Note: The JMS Adapter supports several numerical data types that Business Process Server does not support, and these include: Integer, Byte, Float, and Short. There is the possibility of data loss for numerical data types if a Business Process Server data type is mapped to one of the JMS Adapter data types that is not supported in Business Process Server; and if the incoming data value for the Business Process Server data is more than the boundary value of the mapped JMS Adapter data type.
5. Click the Properties tab to view a list of properties that have to be explicitly set by the JMS Adapter in the outgoing message’s header.
You can edit the header properties using the Property Editor dialog box.
6. Click the Incoming Message tab (enabled when the Adapter Mode is set to Send/Receive or Receive) to define the format of the incoming message (the response expected from the external system).
Currently, the JMS Adapter requires the response message to be a JMS Map message, where the message body is a set of name/value pairs. Here, the list in the Payload tab defines a number of parameters that have to be extracted from the message body of the response. Similarly, the Properties tab includes the list of message properties that have to be extracted from the header.
Note that while any property name can be manually entered, the name can be also selected from a list of predefined properties (the Name field is an edit-enabled combo box that provides a listing of various system properties). Selecting a predefined property also automatically adjusts the property type.
Note: The list of property names is provided for your convenience only. Keep in mind that some message properties are read-only. The Property Editor dialog does not enforce correct property usage.
Configure