ReceiveRequest/Notification
You can use the ReceiveRequest/Notification activity to process an incoming request/reply message forwarded by the TIBCO BusinessConnect server, or to process an incoming notify message forwarded by the TIBCO BusinessConnect server.
General
In the General tab, you can establish a connection to a TIBCO BusinessConnect server, and configure smart routing.
The following table lists the configurations in the General tab of the ReceiveRequest/Notification activity.
| Field | Module Property? | Description |
|---|---|---|
| Name | No | Specify the name to be displayed as the label for the activity in the process. |
| Server Details | Yes | Specify the BC Connection shared resource used to connect to the TIBCO BusinessConnect server. |
| Operation Name | Yes | Specify the pre-configured operations that are available for the protocol associated with the server configuration. |
| Parse XML Payload | Yes | Select this check box to parse and validate the document in received messages.
If the Parse XML Payload check box is cleared, the event sources list a wildcard (*) entry in the list. You can select this entry (*) to start receiving multiple operations on the given event source instance, assuming that the operations belong to the same business protocol. In this case, no parsing or validation of the message happens at the event source level. If parsing or validation is required for the messages that are received on these wildcard listeners, a parse/validate task can be used after the event source. |
| Use Smart Routing | No | Select this check box to enable smart routing, and then provide an identifier for the private process instance. Event sources that reference a shared resource can inherit the smart ID if you enable smart routing for the event source. You can also override an inherited smart ID by providing a different smart ID in the event source. |
| Shared Smart ID | No | Select this check box to inherit the smart ID from the shared resource directly into this event source. In this case, the event source uses the same smart ID as the shared resource.
This check box is displayed only when you select the Use Smart Routing check box. |
| Smart Routing ID | No | Type the required smart ID in this field to have a different smart ID at the event source level. The messages are routed to this private process event source.
This field is displayed only when you select the Use Smart Routing check box. |
Description
In the Description tab, you can enter a short description for the ReceiveRequest/Notification activity.
Advanced
In the Advanced tab, you can configure advanced settings.
The following table lists the configurations in the Advanced tab of the ReceiveRequest/Notification activity:
| Field | Description |
|---|---|
| Sequence Key | This field contains an XPath expression that specifies the order in which the process run. Process instances with sequencing keys that have the same value are executed sequentially in the order in which the process instances were created. |
| Custom Job Id | This field contains an XPath expression that specifies a custom job ID for the process instance. This ID is displayed in the TIBCO Administrator View Service dialog, and it is also available in the $_processContext process variable. |
Conversations
In the
Conversations tab, you can click
Add New Conversation
to initiate a conversation. A conversation represents two or more related message exchanges in the same process that are correlated by the BusinessWorks engine.
See TIBCO ActiveMatrix BusinessWorks Application Development for more details about how to use conversations.
Output
The Output tab lists output schema information. The schema that is displayed depends on the input of the operation selected in the General tab for this activity.
Fault
In the Fault tab, you can find the error code and error message of the ReceiveRequest/Notification activity. See Error Codes for more detailed explanation of errors.
The following table lists error schema elements in the Fault tab of the ReceiveRequest/Notification activity: