![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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.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: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 NotifyThis 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 ResponseIntroducing Responder Process DefinitionsIn 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:The Receive Request/Notification activity is configured to wait for a request from BusinessConnect server, as shown in Figure 9.Figure 9 Receive Notification MessageThe process uses the Receive Request/Notification and Send Response activities to process, as shown in Figure 10.Figure 10 Receive Request and Send FaultThe 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.Figure 11 Receive Request and Send ResponseIn 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.
• The following processes are available in the Initiator folder:
• The following processes are available in the Responder folder: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.
• 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 Acknowledgement Retrieval Transaction (Operation name is CAQH/2.2.0/BatchSubmitAckRetrievalTransaction)
• 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)
• 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 Acknowledgement Retrieval Transaction (Operation name is CAQH/4.0.0/BatchSubmitAckRetrievalTransaction)
• 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 |