Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 TIBCO ActiveMatrix BusinessWorks Private Processes Tutorial : Introduction of Process Definitions

Introduction of Process Definitions
After you have opened the TIBCO ActiveMatrix BusinessWorks project, and configured connections to TIBCO BusinessConnect, you can access the initiator and responder process definitions:
You can also access the NHIN/esMD process definitions: Introducing NHIN/esMD Process Definitions.
Process names are different in TIBCO Designer and TIBCO Business Studio. For example, the Send Notify process in TIBCO Designer equals the SendNotify process in TIBCO Business Studio. The following description takes processes in TIBCO Designer as an example.
Introducing Initiator Process Definitions
In TIBCO Designer, you can access the initiator process definitions by clicking the Project tab, and then expanding the Initiator folder. The following processes are available:
Only the Send Notify operation is used in this tutorial.
Send Notify
This process uses the TIBCO ActiveMatrix BusinessWorks Read File activity to read the notify document stored in the samples directory. This process uses the Parse XML activity to parse the content into an XML tree and pass the tree to the Send Request/Notification activity.
This process includes a subprocess, the password process. This process converts the clear text password to base64 encoded data. This is used for sending the user name and password information to TIBCO BusinessConnect, so you can send a SOAP message with WSS UsernameToken.
The Send Request/Notification activity creates a notify message and sends it to the initiator BusinessConnect server, as shown in Figure 7.
Figure 7 Send Notify
The initiator BusinessConnect server validates the notification message, and converts it into a well-formed SOAP document. The initiator BusinessConnect server transmits the SOAP document to the responder BusinessConnect server, which sends the message to the responder private process.
Send Request and Receive Response
This process uses the Read File activity to read the request document stored in the samples directory. The process uses the Parse XML activity to parse the content into an XML tree and pass the tree to the Send Request/Notification activity.
This process includes a subprocess, the password process. This process converts the clear text password to base64 encoded data.
The Send Request/Notification activity creates a request message and sends it synchronously to the initiator BusinessConnect server. The activity waits for the response from the trading partner, as shown in Figure 8.
Figure 8 Send Request and Receive Response
When the response document arrives, the initiator BusinessConnect server validates the response document for syntactical correctness and sends it to the TIBCO ActiveMatrix BusinessWorks private process.
The document is received by the Send Request/Notification activity, which is waiting for the response.
Receive Response
The response from the trading partner could be a SOAP message with a business document or a SOAP fault. If the trading partner response is a SOAP fault, BusinessConnect server sends this fault message to the TIBCO ActiveMatrix BusinessWorks private process. The Send Request/Notification activity parses the fault message. The fault message fields can be retrieved from this activity.
Introducing Responder Process Definitions
In TIBCO Designer, you can access the responder process definitions by clicking the Project tab, and then expanding the Responder folder. The following processes are available:
Only the Receive Notification Message operation is used in this tutorial.
Receive Notification Message
This process shows how a TIBCO ActiveMatrix BusinessWorks private process receives a SOAP notify message initiated by a trading partner. The process uses the Receive Request/Notification activity.
The Receive Request/Notification activity is configured to wait for a request from BusinessConnect server, as shown in Figure 9.
Figure 9 Receive Notification Message
When the responder BusinessConnect server receives a SOAP document from a trading partner, it validates the SOAP message. After that, the message is sent to a TIBCO ActiveMatrix BusinessWorks private process for processing.
Receive Request and Send Fault
This process shows how TIBCO ActiveMatrix BusinessWorks can act as a responder by receiving a SOAP message initiated by a trading partner and sending back a response. If the received SOAP message is rejected by default, and a SOAP fault is generated and sent back to the trading partner.
The process uses the Receive Request/Notification and Send Response activities to process, as shown in Figure 10.
Figure 10 Receive Request and Send Fault
When the responder BusinessConnect server receives a SOAP document from a trading partner, it validates the SOAP message. After that, the message is sent to a TIBCO ActiveMatrix BusinessWorks private process for processing. In this process, the Send Response activity sends a fault message to the trading partner.
Receive Request and Send Response
This process shows how TIBCO ActiveMatrix BusinessWorks can act as a responder by receiving a SOAP message initiated by a trading partner and sending a response to the trading partner.
The process uses the Receive Request/Notification, Read File, and Send Response activities to process, read, and respond to the request message. This process includes a subprocess, the password process. This process converts the clear text password to base64 encoded data. This is used for sending the user name and password information to TIBCO BusinessConnect, so you can send a SOAP message with WSS UsernameToken.
See Figure 11.
Figure 11 Receive Request and Send Response
When the responder BusinessConnect server receives a SOAP document from a trading partner, it validates the SOAP message. After that, the message is sent to a TIBCO ActiveMatrix BusinessWorks private process for processing. In this process, the Send Response activity sends a SOAP message back to the trading partner.
Introducing NHIN/esMD Process Definitions
In TIBCO Designer, you can access the NHIN/esMD process definitions by clicking the Project tab, and then expand the NHIN/esMD folder. This folder contains two subfolders: the Initiator and Responder folders.
These processes are samples of how to use the NHIN/esMD SAML feature for initiators and responders. You do not have to implement your private process exactly the same way as these samples do, but you might learn detailed information, such as the AttributeStatement element, the AuthzDecisionStatement element, and so on. You can also learn how to handle these elements on the responder side, and how to prepare these elements on the initiator side.
In TIBCO ActiveMatrix BusinessWorks private process, the CAQH Send RealTime Request process and the CAQH Receive RealTime Request Send Response processes constitute a synchronous request-response transaction for RealTime scenario. The CAQH Send Batch Request process and the CAQH Receive Batch Request Send Response constitute a synchronous request-response transaction for Batch Submission scenario. These transactions are implemented with WS-Addressing to convey routing information..
Before you run this NHIN/esMD Process sample, you must enable Require Digital Signature and NHIN/esMD Authorization Framework in the Request Action tab and you must enable NHIN/esMD Authorization Framework in the Response Action tab for SOAP sample operation CAQH/2.2.0/RealTimeTransaction and CAQH/2.2.0/BatchSubmitTransaction.
CAQH Batch/Real time Transactions
Below are the CAQH operations available at CORERule2.2.0.xsd and CORERule 4.0.0.xsd:
CORE Rule 2.2.0
Batch Results Acknowledgement Transaction (Operation name is CAQH/2.2.0/BatchResultsAckSubmit Transaction)
Batch Results Retrieval Transaction (Operation name is CAQH/2.2.0/BatchResultsRetrievalTransaction)
Batch Submit Transaction (Operation name is CAQH/2.2.0/BatchSubmit Transaction)
Generic Batch Receipt Confirmation Transaction (Operation name is CAQH/2.2.0/GenericBatchReceiptConfirmationTransaction)
Generic Batch Retrieval Transaction (Operation name is CAQH/2.2.0/GenericBatchRetrievalTransaction)
Generic Batch Submission Acknowledgement Retrieval Transaction (Operation name is CAQH/2.2.0/GenericBatchSubmissionAckRetrievalTransaction)
Generic Batch Submission Transaction (Operation name is CAQH/2.2.0/GenericBatchSubmissionTransaction)
Real Time Transaction (Opration name is CAQH/2.2.0/RealTimeTransaction)
CORE Rule 4.0.0
Batch Results Acknowledgement Transaction (Operation name is CAQH/4.0.0/BatchResultsAckSubmitTransaction)
Batch Results Retrieval Transaction (Operation name is CAQH/4.0.0/BatchresultsRetrievalTransaction)
Batch Submit Transaction (Operation name is CAQH/4.0.0/BatchSubmitTransaction)
Generic Batch Receipt Confirmation Transaction (Operation name is CAQH/4.0.0/GenericBatchReceiptConfirmationTransaction)
Generic Batch Retrieval Transaction (Operation name is CAQH/4.0.0/GenericBatchRetrievalTransaction)
Generic Batch Submission Acknowledgement Retrieval Transaction (Operation name is CAQH/4.0.0/GenericBatchSubmissionAckretrievalTransaction)
Generic batch Submission Transaction (Operation name is CAQH/4.0.0/GenericBatchSubmissionTransaction)
Real Time Transaction (Operation name is CAQH/4.0.0/RealTimeTransaction)

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved