ReceiveMiscMsg

Any message that is not an inbound or outbound request or response is a miscellaneous message. You can use the ReceiveMiscMsg activity to start a process when a miscellaneous message is received from TIBCO BusinessConnect.

Not all business protocols support miscellaneous messages. The ReceiveMiscMsg activity requires a BC Connection shared resource that is configured for a specific protocol. If no miscellaneous messages exist for the specified protocol, the ReceiveMiscMsg activity cannot be used for that protocol.

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 ReceiveMiscMsg 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.
Message Name Yes Select one of the available miscellaneous messages from the list. This field contains a list of the available miscellaneous messages for the BC Connection shared resource selected for the Server Details field.

Some miscellaneous messages are related to message disposition notifications.

A message disposition notification (MDN) receipt is a transport level acknowledgment.

Some of the protocols, such as TIBCO BusinessConnect Services™ Plug-in and tibEDI, do not suppress these messages, and some of them do (RosettaNet, cXML). For more information, see the documentation for a specific business protocol.

These messages can occur when the AS1, AS2 or Email transports are used and receipts (MDNs) are utilized.

An MDNAlert message is sent to the private process when a receipt is requested with an outbound message that is sent to a trading partner, and TIBCO BusinessConnect successfully receives and verifies the receipt returned by the trading partner.
In this scenario, the notification to the private process is sent on the following subjects:
  • TIBCO Rendezvous subject

    prefix.installation_name.standardID.INFO.RECEIPT.RECEIVED

  • JMS subject

    prefix.installation_name.INFO.RECEIPT.RECEIVED

An MDNAlertError message is sent to the private process when a receipt is requested with an outbound message that is sent to a trading partner, and the trading partner returns a receipt which indicates that the trading partner encounters an error in the outbound message it receives.
In this scenario, the notification to the private process is sent on the following subjects:
  • TIBCO Rendezvous subject

    prefix.installation_name.standardID.ERROR.RECEIPT.RECEIVED

  • JMS subject

    prefix.installation_name.ERROR.RECEIPT.RECEIVED

An MDNResponseAlert message is sent to the private process when all the following listed conditions are met:
  • TIBCO BusinessConnect receives a receipt request for an inbound document.
  • TIBCO BusinessConnect can successfully un-package the inbound document for which a receipt is requested; for example, the signature of the inbound document can be verified if the document is signed.
  • TIBCO BusinessConnect returns a receipt to the trading partner indicating that the inbound document is received and unpackaged successfully.
In this scenario, the notification to the private process is sent on the following subjects:
  • TIBCO Rendezvous subject

    prefix.installation_name.standardID.INFO.RECEIPT.SENT

  • JMS subject

    prefix.installation_name.INFO.RECEIPT.SENT

An MDNErrorResponseAlert message is sent to the private process in the following cases:
  • TIBCO BusinessConnect receives a receipt request for an inbound document.
  • TIBCO BusinessConnect cannot successfully verify the signature for the document, and it returns a receipt to the trading partner indicating that the inbound document is received but the signature cannot be successfully verified.
In this scenario, the notification to the private process is sent on the following subjects:
  • TIBCO Rendezvous subject

    prefix.installation_name.standardID.ERROR.RECEIPT.SENT

  • JMS subject

    prefix.installation_name.ERROR.RECEIPT.SENT

An MDNTimeout message is sent to the private process when a receipt is requested for an outbound document, but the trading partner does not return a receipt within the receipt timeout period.
In this scenario, the notification to the private process is sent on the following subjects:
  • TIBCO Rendezvous subject

    prefix.installation_name.standardID.ERROR.TIMEOUT.RECEIPT

  • JMS subject

    prefix.installation_name.ERROR.TIMEOUT.RECEIPT

An ErrorNotify message is sent to the private process whenever TIBCO BusinessConnect encounters an error during the processing of an inbound or outbound messages.
When an error occurs, the notification to the private process is sent on the following subjects:
  • TIBCO Rendezvous subject

    prefix.installation_name.standardID.ERROR.

  • JMS subject

    prefix.installation_name.ERROR.

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 Yes 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 ReceiveMiscMsg activity.

Advanced

In the Advanced tab, you can configure advanced settings.

The following table lists the configurations in the Advanced tab of the ReceiveMiscMsg 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 message selected in the General tab for this activity.

Fault

In the Fault tab, you can find the error code and error message of the ReceiveMiscMsg activity. See Error Codes for more detailed explanation of errors.

The following table lists error schema elements in the Fault tab of the ReceiveMiscMsg activity:

Error Element Data Type Description
msg String Displays the error message.
msgCode String Displays the error code.