Publish to Adapter

The Publish to Adapter activity publishes messages, which are received by Subscription Service.

Subscription Service is configured during adapter configuration, and the activity uses the information in the adapter configuration to configure this activity.

The following figure illustrates a Publish to Adapter activity sending a message to a preconfigured Subscription Service.

General

The General tab has the following fields:
Field Module Property? Description
Name No The name displayed as the label for the activity in the process definition.

The default value is PublishtoAdapter.

Adapter Service No The preconfigured Subscription Service. You must specify the adapter service when configuring the adapter.

Click to locate the appropriate service for this activity.

RequestReply No Select or clear the check box to specify whether the activity is sending a request message and expecting a response message.

When this check box is selected, the Custom Schema check box is selected automatically. The Publish to Adapter activity uses the RequestReply schema specified by a user, rather than the schema from the adapter service.

Custom Schema No Select or clear the check box to specify whether you want to supply an output class for this activity.
  • Cleared (default): The Input Editor tab and the Output Editor tab are read-only.
  • Selected: The Input Editor tab and the Output Editor tab are editable.
Note: The feature of Custom Schema in TIBCO ActiveMatrix BusinessWorks 6 is the same as CustomAESchema in TIBCO ActiveMatrix BusinessWorks 5.
Transport Configuration Click the Transport Configuration link to configure a transport in the Advanced tab.

Description

In the Description tab, you can enter a short description for the activity.

Advanced

The Advanced tab contains the Transport Type field. You can select a transport type in the Transport Type list. For more information, see Transport Type.

Input Editor

The Input Editor tab defines the schema used for messages: Map, Stream, or XML Text. Map messages are name or value pairs.

You can use the schema to define the structure of the outgoing request and the incoming reply. The schema defined in the Input Editor tab becomes the body of the message in the Input tab.

Output Editor

The Output Editor tab defines the schema used for messages: Map, Stream, or XML Text. Map messages are name or value pairs.

You can use the schema to define the structure of the outgoing request and the incoming reply. The schema defined in the Output Editor tab becomes the body of the message in the Output tab.

Input

The following table lists the input items for this activity:
Input Item Data Type Description
subject String The subject of the message.
requestTimeout Integer When publishing in request/reply mode, you can specify the timeout (in milliseconds) to wait for the reply.
preRegisterListener String When using TIBCO Rendezvous Certified Messaging (RVCM), you can specify the CM name(s) of the RVCM subscriber(s). With preRegisterListener, the publisher can preregister with any expected listeners.

If multiple CM names are specified, separate each CM name with a comma.

Any listener preregistered on the Transport tab is also preregistered with the listeners specified in this element.

See the TIBCO Rendezvous documentation for more information about RVCM.

replySubject String The reply subject of the message.
businessKey String This string is appended to the AE tracking in the trackingInfo field.
Note: It is good practice to have all publishers in a process use the same business key. Only the most recent business key of the publisher is used in the tracking info for the message.
OtherProperties Complex This element contains the message properties for the message. Only properties applicable to this type of message are displayed.

It is available only when JMS Queue or JMS Topic is the transport and JMS Application Properties in the Transport Type configuration are specified.

For more information about message properties, see "JMS Properties" in TIBCO ActiveMatrix BusinessWorks Bindings and Palette Reference.

body Complex A complex schema type specified for the adapter service or a complex schema type designated by a user.

Output

The following table lists the output items for this activity:
Output Item Data Type Description
replyDestination String A reply message can optionally have a reply destination, so that the two applications can communicate with incoming messages.

This element contains the reply subject (RV) or destination (JMS) set on the reply message, if one is set. If no reply subject or destination is set on the reply message, this element is not populated.

trackingInfo Complex The AE tracking information of the sender.

This element is a concatenation of "BW." + Application_Name + Module_Name + Process_Name + Activity_Name + User_Part (Business_Key).

MessageID String The ID of the message.

This element is available only when JMS Queue or JMS Topic is the transport.

JMSHeaders Complex This element contains the message header fields for the message. Only properties applicable to this type of message are displayed.

It is available only when JMS Queue or JMS Topic is the transport.

For more information about message header fields, see "JMS Properties" in TIBCO ActiveMatrix BusinessWorks Bindings and Palette Reference.

OtherProperties Complex This element contains the message properties for the message. Only properties applicable to this type of message are displayed.

It is available only when JMS Queue or JMS Topic is the transport and JMS Application Properties in the Transport Type configuration are specified.

For more information about message properties, see "JMS Properties" in TIBCO ActiveMatrix BusinessWorks Bindings and Palette Reference.

body Complex A complex schema type specified for the adapter service or a complex schema type designated by a user.

Fault

The Fault tab lists the possible exceptions thrown by this activity.

Note: This tab plays the same role as the Error Output tab in TIBCO ActiveMatrix BusinessWorks 5.x.
Fault Thrown When...
TransportException The transport cannot be created.
SerializationException The outgoing message cannot be serialized.
TimeoutException The specified timeout has been reached for the request/reply operation.