Private Messages in Sessions

When real-time transactions are used, all requests are immediately executed by the CMI Protocol engine. The real-time transactions between private processes and CMI Protocol are called sessions.

For more information, see Sessions.

When you use private processes in sessions, the following happen:

1. The private process sends an INITIATOR.REQUEST message to CMI Protocol.
2. CMI Protocol responds in one of these three ways:
Execution succeeded: It sends an INITIATOR.RESPONSE message back.
Execution failed: It sends an ERROR message and an INITIATOR.RESPONSE message including error code and error details.
Session timed out: Session Timeout Advisory is triggered by the TIBCO BusinessConnect engine after the time has passed.

If the sessionID has already timed out at the time when a request comes in, TIBCO BusinessConnect returns a normal ERROR message with the code that points to the invalid sessionID.