Setting Up Credit Card Integration for Integration Broker

This section discusses how to configure integration for Integration Broker.

To set up Integration Broker for credit card processing:

  1. Define the Integration Broker Gateway if it's not already done.

  2. Activate the delivered service (EOEC_CCI_SYNC) that is used for the credit card integration.

  3. Set up an external node to use when using the XML-based interface to which the XML messages should be sent and to indicate where the processor is located.

    Also specify the authentication option that you arranged with the credit card processor.

  4. Set up routings.

    Use the Routings tab in the Node component to add the EOEC_CCI_SYNC service to the node. To see the XML data before and after transformations, set the log detail to Header & Detail. This is helpful when troubleshooting your new integration.

  5. Test the integration.

    You can use the test component described below.

If you receive error messages when using Integration Broker, see the Troubleshooting the Integration Broker Setup section below:

Troubleshooting the Integration Broker Setup

Several sources of information are available when the setup is not successful. These include but are not limited to:

  • Error messages stored on the message instance (view with the message monitor).

  • IB gateway error log (http://<GatewayMachine>:<Port>/PSIGW/errorLog.html).

  • IB gateway message log (http://<GatewayMachine>:<Port>/PSIGW/msgLog.html).

  • Application server log for the active IB domain server on the database.

  • Web server logs.

You can also do the following:

  • Increase the log fence on the gateway properties file. This file is located in the following directory: PS_CFG_HOME\webserv\<web-server>\applications\peoplesfoft\PSIGW

    If you set the log fence to five in the integration Gateway properties, you will receive more details in the error and message logs.

  • Check the Service Operations Monitor to view the XML messages before and after the transformations (PeopleTools, Integration Broker, Monitor, Service Operations, Synchronous Services).

  • Check the Header and Detail logs on the Synchronous Detail page (PeopleTools, Integration Broker, Service Operations Monitor, Monitor, Synchronous Details).

    Problems are usually due to incorrect transformations between the two systems. Use these logs to ensure that your transformations are correct.

    Your Response-Transformed message structure should look similar to this:

    <?xml version="1.0"?>
<EOEC_CCI_RESPONSE xmlns:c="yourcompany.com">
  <FieldTypes>
    <EOEC_CCI_XMLRSP class="R"/>
    <EOEC_CCI_TRRSLT class="R">
      <RESULT type="NUMBER"/>
    </EOEC_CCI_TRRSLT>
    <EOEC_CCI_AVRSLT class="R"/>
    <EOEC_CCI_RSPNS class="R"/>
    <PSCAMA class="R"/>
  </FieldTypes>
  <MsgData>
    <Transaction>
      <EOEC_CCI_XMLRSP class="R">
        <UNIQUEID/>
        <EOEC_CCI_RSPNS class="R">
          <VENDOR/>
          <PARTNER/>
          <EOEC_CCI_TRRSLT class="R">
            <TRANSACTIONID>177</TRANSACTIONID>
            <RESULT>0</RESULT>
            <AVS/>
            <CVRESULT/>
            <MESSAGE/>
            <AUTHCODE>123456</AUTHCODE>
            <HOSTCODE/>
            <HOSTURL/>
            <ORIGRESULT/>
            <TRSTATUS/>
            <EOEC_RET_STATUSMSG/>
            <EOEC_RET_AUTHDTTM/>
            <EOEC_CCI_AVRSLT class="R">
              <STREETMATCH/>
            </EOEC_CCI_AVRSLT>
          </EOEC_CCI_TRRSLT>
        </EOEC_CCI_RSPNS>
      </EOEC_CCI_XMLRSP>
    </Transaction>
  </MsgData>
</EOEC_CCI_RESPONSE>