ReceiveRequest/Notification

The ReceiveRequest/Notification process starter is used 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.

The ReceiveRequest/Notification activity receives messages that are published on the following subjects:
  • TIBCO Rendezvous subject:

    prefix.installation_name.standardID.RESPONDER.REQUEST

  • JMS subject:

    prefix.installation_name.RESPONDER.REQUEST

General

The General tab contains the following field.

Field Module Property? Description
Name No The name to be displayed as the label for the activity.
Server Details Yes The BC Connection shared resource used to connect to the TIBCO BusinessConnect server.
Operation Name Yes Pre-configured operations that are available for the protocol associated with the server configuration.
Parse XML Payload Yes
  • Check box selected:

    The document in the received message is parsed and validated according to the corresponding Schema defined for this B2B operation.

  • Check box cleared:

    The XML document in the message is treated as a string. This is particularly useful in cases where the document does not need to be processed (parsed) immediately in the TIBCO BusinessConnect activity.

If the Parse XML Payload check box is cleared, the event sources lists a wild card ("*") entry in the list. You can select this entry ("*") in order 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 are 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 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.
Smart Routing ID No Type the desired Smart ID into this field in order to have a different Smart ID on the event source level . The messages are routed to this private process event source.

Description

Provide a short description for the activity.

Advanced

The Advanced tab contains the following fields.

Field Description
Sequence Key This field can contain an XPath expression that specifies which processes should run in order. Process instances with sequencing keys that evaluate to the same value are executed sequentially in the order the process instance is created.
Custom Job Id This field can contain an XPath expression that specifies a custom ID for the process instance.

Conversations

You can initiate the Conversation here. Click the Add New Conversation icon to initiate multiple Conversations.

Output

The Output tab lists output schema information, which is based on the input of the operation selected in the General tab for this activity

Fault

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

Fault Thrown when..
msg The descriptive text provided by this exception object.
msgCode If the message has a BW message code, it will be mapped to this field.