Private Process vs Public Process :
- Public processes and public process using TIBCO BusinessConnect
Private Processes :
- Private processes in TIBCO BusinessConnect are processes internal to your company. They send data to or receive data from the TIBCO BusinessConnect server, and communicate using TIBCO Rendezvous® (Rendezvous Certified Messaging RVCM) or JMS
TIBCO RV – Subject Names :
All TIBCO Rendezvous messages have a unique subject name. This applies to interactions on both the Initiator and Responder side. Subject name formats are :
- Request from Initiator’s private process to the local TIBCO BusinessConnect:
Property name: requestFromPPSubject=prefix.installation.standardID.fixed
Example: AX.BC.BC-ACME.EZComm.INITIATOR.REQUEST
- Response to Initiator’s private process from the local TIBCO BusinessConnect:
Property name: responseToPPSubject=prefix.installation.standardID.fixed
Example: AX.BC.BC-ACME.EZComm.INITIATOR.RESPONSE
- Request to a Responder’s private process from the local TIBCO BusinessConnect:
Property name: requestToPPSubject=prefix.installation.standardID.fixed
Example: AX.BC.BC-ACME.EZComm.RESPONDER.REQUEST
- Response from Responder’s private process to the local TIBCO BusinessConnect:
Property name: responseFromPPSubject=prefix.installation.standardID.fixed
Example: AX.BC.BC-ACME.EDI-X12.RESPONDER.RESPONSE
- Acknowledgment of receipt of asynchronous request/response message:
Property name: ackToPPSubject=prefix.installation.standardID.fixed
Example: AX.BC.BC-ACME.EDI-X12.RESPONDER.ACK
- Error notification: Property name: errorNotifySubject=prefix.installation.standardID.fixed
Example: AX.BC.BC-ACME.EZComm.ERROR
TIBCO Rendezvous publishes this message globally, but a private process can also listen to it.
JMS Transport :
- The JMS messages consist of several properties and header fields, which helps the processing agent, such as BusinessConnect Palette, to dispatch the messages to the corresponding listeners. The destination of the messages is:
- INSTALLATION.MESSAGETYPE_SPECIFIC_SUFFIX .
For example, AX.BC.MYSERVER.RESPONDER.REQUEST
JMS Transport Types Used for Various Messages
Messages use the following JMS transport types:
- Messages that carry either notifications, requests, or responses use the JMS
queue transport type.
See messages sent on destinations with suffixes INITIATOR.REQUEST,
INITIATOR.RESPONSE, RESPONDER.REQUEST, and RESPONDER.RESPONSE,.
- Miscellaneous messages, such as error advisories with the suffix ERROR, use a JMS topic transport type, except for the RESPONDER.ACK advisory which uses a JMS queue transport type. This behavior may be overridden by individual business protocols; if it is not specifically mentioned, the explained behavior should be assumed.
Diagram – Secure JMS Transport
Public Processes :
- Public processes involve exchanges of documents across the Internet using protocols such as HTTP/S, FTP/S, and SMTP.
- These processes can start when the TIBCO BusinessConnect server receives a message in a proper format from the private process.
