Topic list

Glossary

Print this page

Bookmark

Sample Business Process Scenario for Connect:Direct Interoperability

This business process scenario consists of two fictitious companies, MaxxMart and Contempo Bank, in which Contempo Bank, an online bank, provides loans for high-ticket items (such as high-end electronics) to customers of MaxxMart, a large retailer.

As part of the agreement, MaxxMart has setup several PCs in its store with a web-based interface through which customers can complete online applications for financing MaxxMart's high-ticket items. The agreement between MaxxMart and Contempo requires quick approval with no more than a 30-minute turnaround on loan applications.

Contempo, who has the role of main trading partner, has Connect:Direct installed. MaxxMart, who has the role of external trading partner, has Gentran Integration Suite installed and uses the Connect:Direct Server adapter and Web Extensions.

MaxxMart has configured an instance of the Connect:Direct Server adapter with a node defined for Contempo. MaxxMart uses a customized Web Extensions interface for the online application. Contempo has added an entry for the MaxxMart Connect:Direct Server adapter node to its network map.

When MaxxMart receives the loan request, it forwards the application to Contempo, where a back end system either approves or denies the request. Contempo returns the approval (or denial) to MaxxMart. For approved loans, MaxxMart also initiates a Connect:Direct Process that causes Contempo to transfer funds for the approved loan to the MaxxMart bank account as an ACH transaction. The MaxxMart bank requires that ACH transactions be handled through AS2.

The CDInterop_AppProcess business process, Connect:Direct Server adapter, HTTP Server adapter, and the following services are used in this scenario:

Connect:Direct Server Begin Session service
Connect:Direct Server CopyTo service
Connect:Direct Server Run Task service
SMTP Send adapter
Connect:Direct Server Submit service
EDIINT Message service
Connect:Direct Server End Session service

The following steps outline the business process scenario being addressed by Gentran Integration Suite and Connect:Direct Interoperability:

A MaxxMart customer completes an online loan application using the Web Extensions custom interface and submits the application.
The MaxxMart Gentran Integration Suite system initiates the CDInterop_AppProcess business process, which establishes a connection with the Contempo Connect:Direct server using the Connect:Direct Server Begin Session service. The Begin Session service is configured to use a specific Connect:Direct Server adapter for the connection.
The Connect:Direct Server adapter specified in the Begin Session service retrieves node information for the Contempo node from its configuration.
The adapter then passes its identification information to the Contempo node through a perimeter server in the DMZ, and the Contempo node returns its identification information to MaxxMart's node.
The MaxxMart node sends a user ID and password to the Contempo node, and the Contempo node verifies the user ID and password. After this verification, the Contempo node authorizes the session.
At this point, the MaxxMart node copies the customer loan application to a specified location at Contempo using the Connect:Direct Server CopyTo service. This loan application is included as the primary document in the CDInterop_AppProcess business process, which initiated when the customer submitted the application. The location where the loan application is copied is the starting point for all loan applications at Contempo. A process already exists in the Contempo business environment that takes loan applications from this location and processes them using a back-office system.
The next activity in the business process uses the Connect:Direct Server Run Task service and executes the back-office system at Contempo that processes (approves/denies) loan applications. The business process waits for a synchronous response from the back-office system as a result of the Run Task activity.
The Contempo back-office system processes the loan application using the copied file and approves the loan. The back office system returns an approval response to the CDInterop_AppProcess business process, specifying the name and location of the approval document.
The approval response is forwarded to a MaxxMart e-mail address using the SMTP Send adapter and a MaxxMart associate receives the approval notification.
After receiving the approval response, the CDInterop_AppProcess uses the Connect:Direct Server Submit service to start a Connect:Direct Process that exists on the Contempo node. The Connect:Direct Process causes an ACH transfer to deposit the loan funds into MaxxMart's account.
The Connect:Direct Process is initiated and the ACH file is generated through an internal ACH application at Contempo. The generated ACH file is then transferred (copied) to the CDInterop_AppProcess business process.
When the business process receives the ACH file, it uses the EDIINT Message service to transform the file into an EDIINT message, which it then transfers to MaxxMart's bank account through the HTTP Server adapter.
The business process receives the synchronous MDN response from the bank acknowledging receipt of the ACH transfer.
The final activity in the CDInterop_AppProcess ends the session with Contempo node using the Connect:Direct Server End Session service. The End Session service uses the session token available in the business process data and closes the connection with the Contempo node.
If the business process fails, the failure is recorded at the close of the session.

In the Graphical Process Modeler, the business process is displayed as in the following figure:

The BPML associated with this business process is as follows:

<process name="default"> 
  <sequence> 
    <operation name="CD Server Begin Session Service"> 
      <participant name="CDServerBeginSession"/> 
      <output message="CDServerBeginSessionServiceTypeInputMessage"> 
        <assign to="LocalCDNodeName">TEST5_CDSERVER_ADAPTER</assign> 
        <assign to="." from="*"></assign> 
      </output> 
      <input message="inmsg"> 
        <assign to="." from="*"></assign> 
      </input> 
    </operation> 
    <operation name="CD Server CopyTo Service"> 
      <participant name="CDServerCopyTo"/> 
      <output message="CDServerCopyToServiceTypeInputMessage"> 
        <assign to="LocalDocumentId">loanapp</assign> 
        <assign to="RemoteFileName">approval</assign> 
        <assign to="SessionToken">token</assign> 
        <assign to="." from="*"></assign> 
      </output> 
      <input message="inmsg"> 
        <assign to="." from="*"></assign> 
      </input> 
    </operation> 
    <operation name="CD Server Run Task Service"> 
      <participant name="CDServerRunTask"/> 
      <output message="CDServerRunTaskServiceTypeInputMessage"> 
        <assign to="Program">Connect:Direct</assign> 
        <assign to="SessionToken">token2</assign> 
        <assign to="." from="*"></assign> 
      </output> 
      <input message="inmsg"> 
        <assign to="." from="*"></assign> 
      </input> 
    </operation> 
    <operation name="SMTP Send Adapter"> 
      <participant name="SMTP_SEND_ADAPTER"/> 
      <output message="SMTP_SEND_ADAPTERInputMessage"> 
        <assign to="." from="*"></assign> 
      </output> 
      <input message="inmsg"> 
        <assign to="." from="*"></assign> 
      </input> 
    </operation> 
    <operation name="CD Server Submit Service"> 
      <participant name="CDServerSubmit"/> 
      <output message="CDServerSubmitServiceTypeInputMessage"> 
        <assign to="RemoteProcessFile">denial</assign> 
        <assign to="SessionToken">token3</assign> 
        <assign to="." from="*"></assign> 
      </output> 
      <input message="inmsg"> 
        <assign to="." from="*"></assign> 
      </input> 
    </operation> 
    <operation name="EDIINT Message Service"> 
      <participant name="TestEDIINTParse"/> 
      <output message="EDIINTMessageServiceInputMessage"> 
        <assign to="." from="*"></assign> 
      </output> 
<input message="inmsg"> 
        <assign to="." from="*"></assign> 
      </input> 
    </operation> 
    <operation name="CD Server End Session Service"> 
      <participant name="CDServerEndSession"/> 
      <output message="CDServerEndSessionServiceTypeInputMessage"> 
        <assign to="SessionToken">token4</assign> 
        <assign to="." from="*"></assign> 
      </output> 
      <input message="inmsg"> 
        <assign to="." from="*"></assign> 
      </input> 
    </operation> 
  </sequence> 
</process>