Customer 360 Extension for SAP > Deploying Customer 360 Extension for SAP > Configuring SAP connection
  

Configuring SAP connection

You can use SAP Table connection to integrate SAP ECC and SAP S/4HANA with Customer 360 in batches.
    1To configure a SAP Table connection, perform the following steps:
    1. aVerify if the required licences are available for SAP Table Connector to create an SAP table connection and process SAP table data.
    2. bDownload and install the Microsoft Visual C++ Redistributable package on the Windows machine that hosts the Secure Agent.
    3. cDownload and configure the SAP libraries on the Secure Agent machine to read from and write to SAP tables.
    4. dTo enable the Secure Agent to connect to the SAP system as a Remote Function Call (RFC) client, create and configure the sapnwrfc.ini file on the machines that host the Secure Agent.
    5. eConfigure the SAP user account to process SAP table data.
    6. fInstall the SAP Table connection transport files on the SAP machines that you want to access.
    7. gTo connect to SAP through HTTPS and read SAP table sources, configure the machine that hosts the Secure Agent and the machine that hosts the SAP system.
    For more information about the SAP Table Connector, see https://onlinehelp.informatica.com/IICS/prod/CDI/en/index.htm#page/cloud-data-integration-sap-connector/SAP_Table_Connector_administration.html
    2Configure the following connections:
    The following table describes the SAP Table connection properties:
    Connection property
    Description
    Runtime Environment
    Required. Runtime environment that contains the Secure Agent that you want to use to access SAP tables.
    Username
    Required. SAP user name with the appropriate user authorization.
    Password
    Required. SAP password.
    Client
    Required. SAP client number.
    Language
    Language code that corresponds to the SAP language.
    Saprfc.ini Path
    Required. Local directory to the sapnwrfc.ini file.
    To write to SAP tables, use the following directory:
    <Informatica Secure Agent installation directory>/main/bin/rdtm
    Destination
    Required. DEST entry that you specified in the sapnwrfc.ini file for the SAP application server.
    Destination is case sensitive.
    Note: Use all uppercase letters for the destination.
    Port Range
    HTTP port range. The SAP Table connection uses the specified port numbers to connect to SAP tables using the HTTP protocol. Ensure that you specify valid numbers to prevent connection errors. Default: 10000-65535.
    Enter a range in the default range, for example, 10000-20000. When a range is outside the default range, the connection uses the default range.
    Test Streaming
    Tests the connection. When selected, tests the connection using both RFC and HTTP protocol. When not selected, tests connection using HTTP protocol.
    Https Connection
    When selected, connects to SAP through HTTPS protocol. To successfully connect to SAP through HTTPS, verify that an administrator has configured the machines that host the Secure Agent and the SAP system.
    Keystore Location
    The absolute path to the JKS keystore file.
    Keystore Password
    The destination password specified for the .JKS file.
    Private Key Password
    The export password specified for the .P12 file.
    3Test the connections, and ensure that the connections are successful.
    For more information about the SAP Connector, see https://onlinehelp.informatica.com/IICS/prod/CDI/en/index.htm#page/cloud-data-integration-sap-connector/SAP_IDocs_and_RFCsBAPI_Connector_administration.html
    4If the SAP instance and the Secure Agent are installed in the same Virtual Private Cloud (VPC) network, perform the following steps:
    1. aConfigure the Secure Agent host to use the private IP address to access the SAP instance.
      1. aOpen the following file on the Secure Agent:
        • ▪ On Windows. \Windows\System32\drivers\etc\hosts
        • ▪ On Linux. /etc/hosts
      2. bAdd an entry for the SAP instance in the following format:
        3. <SAP Hostname> <Private IP address of SAP Host>
      3. cRepeat steps 4.a.i through 4.a.ii for all the SAP instances available in VPC as Secure Agent host.
    2. bFor communication between SAP instance and Secure Agent, add a custom DTM configuration property to use the private IP address of the Secure Agent host.
      1. aIn Administrator, click Runtime Environments.
      2. bExpand the Actions menu for the Secure Agent, and select Edit Secure Agent.
      3. cIn the Custom Configuration Details section, enter the following details:
        4. Field Name
        Value
        Services
        Data Integration Server
        Type
        DTM
        Name
        SapTableReaderNatIpAddress
        Value
        <Private IP address of Secure Agent host>
      4. dClick Save.
        5. The Secure Agent restarts automatically within 10 minutes. To apply the properties immediately, you can restart manually. Ensure that no tasks run to avoid failure of any running task.
    3. c Test the connection to verify the connectivity between SAP and the Secure Agent host.
      4. If the connection test is unsuccessful, disable the firewall to resolve the issue.