Adapter Subscriber
The Adapter Subscriber activity is a process starter activity. It starts a process based on the receipt of a message from Publication Service of the specified adapter.
Publication Service is configured during adapter configuration, and the activity uses the information in the adapter configuration to configure this activity.
The following figure illustrates Publication Service publishing a message and Adapter Subscriber starting a business process.
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 AdapterSubscriber. |
Adapter Service | No | The preconfigured Publication Service. Specify the adapter service when configuring the adapter.
Click
|
Custom Schema | No | Select or clear the checkbox to specify whether you want to supply an output class for the activity.
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 has the following fields:
Field | Module Property? | Description |
---|---|---|
Transport Type | No | Select a transport type. See Transport Type for more information. |
Sequence Key | No | This field contains an XPath expression that specifies how processes run in order. Process instances with sequencing keys that evaluate to the same value are executed sequentially in the order the process instances were created.
To edit the XPath expression, click
For more information about XPath expressions and how to control the execution of process instances in order, see TIBCO ActiveMatrix BusinessWorks Application Development. |
Custom Job Id | No | This field contains an XPath expression that specifies a custom ID for the process instance. This ID is also available in the
$_process context process variable.
To edit the XPath expression, click
|
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 retrieved messages. The schema defined in the Output Editor tab becomes the body of the message in the Output tab.
Conversations
You can initiate the conversation. Click
Add New Conversation to initiate multiple conversations.
For details about conversations, see TIBCO ActiveMatrix BusinessWorks Application Development.
Output
The following table lists the output items for this activity:
Output Item | Data Type | Description |
---|---|---|
subject | String | The subject of the message. |
replySubject | String | The reply subject of the message. |
certifiedSequence Number | String | This element contains the sequence number in which this message was received.
It is available only when Tibrv Certified is the transport. |
certifiedSender | String | This element contains the CM name of the message sender.
It is available only when Tibrv Certified is the transport. |
MessageID | String | The ID of the message.
This element is available only when JMS Queue or JMS Topic is the transport. |
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). |
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. |
disable.adsub.autoconfirm
Java property to true when running the BusinessWorks application. When the Java property is enabled, the BusinessWorks process must contain the Confirm activity to confirm the message. In the Confirm activity, the Adapter Subscriber activity is always available for confirmation in all cases. If the Java property is not set to true and the Confirm activity is used, then the confirmation by the Confirm activity is ignored as the message is already confirmed.