SAP Connector > Connections for SAP > Prerequisites
  

Prerequisites

Before you use an SAP connection, the SAP administrator needs to perform certain prerequisite tasks to configure the Secure Agent machine and SAP system.
To process IDocs and SAP BAPI/RFC functions, you also need to verify if the required licenses are enabled for the SAP system.

Download and configure the SAP libraries

To access SAP data through the Intermediate Documents (IDocs) or BAPI/RFC interface, you need to download and configure the SAP NetWeaver RFC SDK libraries and SAP JCo libraries on the Secure Agent machine. If you encounter any issues while you download libraries, contact SAP Customer Support.
  1. 1Go to the SAP Support Portal, and then click Software Downloads.
    2. Note: You need to have SAP credentials to access Software Downloads from the SAP Support Portal.
  2. 2Download the latest version of the SAP NetWeaver RFC SDK 7.50 libraries that are specific to the operating system that hosts the Secure Agent.
    3. The following table lists the libraries corresponding to the different operating systems:
    Operating System
    SAP NetWeaver RFC SDK Libraries
    Linux 64
    • - libicudata.so.50
    • - libicui18n.so.50
    • - libicuuc.so.50
    • - libsapnwrfc.so
    • - libsapucum.so
    Windows 64
    • - icudt50.dll
    • - icuin50.dll
    • - icuuc50.dll
    • - libsapucum.dll
    • - sapnwrfc.dll
  3. 3Copy the SAP NetWeaver RFC SDK 7.50 libraries to the following directory:
    4. <Informatica Secure Agent installation directory>\apps\Data_Integration_Server\ext\deploy_to_main\bin\rdtm
    Create the deploy_to_main\bin\rdtm directory if it does not already exist.
  4. 4Set the following permissions for each SAP NetWeaver RFC SDK library:
  5. 5From the SAP Support Portal, download the latest version of the 64-bit SAP JCo libraries based on the operating system of the machine on which the Secure Agent runs:
    6. Secure Agent System
    SAP JCo Libraries
    Windows
    sapjco3.jar
    sapjco3.dll
    Linux
    sapjco3.jar
    libsapjco3.so
  6. 6Copy the JCo libraries to the following directory:
    7. <Informatica Secure Agent installation directory>\apps\Data_Integration_Server\ext\deploy_to_main\bin\rdtm-extra\tpl\sap
    Create the deploy_to_main\bin\rdtm-extra\tpl\sap directory if it does not already exist.
  7. 7Log in to Informatica Intelligent Cloud Services and configure the JAVA_LIBS property for the Secure Agent.
    1. aSelect Administrator > Runtime Environments.
    2. bClick Runtime Environments to access the Runtime Environments page.
    3. cTo the left of the agent name, click Edit Secure Agent.
    4. dFrom the Service list, select Data Integration Server.
    5. eFrom the Type list, select Tomcat JRE.
    6. fEnter the JAVA_LIBS value based on the operating system of the machine on which the Secure Agent runs.
      7. Operating System
      Value
      Windows
      ../bin/rdtm-extra/tpl/sap/sapjco3.jar;../bin/rdtm/javalib/sap/sap-adapter-common.jar
      Linux
      ../bin/rdtm-extra/tpl/sap/sapjco3.jar:../bin/rdtm/javalib/sap/sap-adapter-common.jar
      Warning: If you copy the value directly from the table, the hyphens (-) in the value might be incorrectly copied. Copy the value to a text editor and make sure that the value you copied is not corrupted.
      The configured JAVA_LIBS property for the Secure Agent on Windows.
    7. gClick Save.
    8. hRepeat steps 2 through 7 on every machine where you installed the Secure Agent.
  8. 8Restart the Secure Agent.

Configure SAP user authorization

Configure the SAP user account in the SAP system to enable data exchange through Intermediate Documents (IDocs) and BAPI/RFC interfaces.
You need to add the authorization object in SAP to process IDocs and SAP BAPI/RFC functions that helps you interact with SAP at run time. You also need access to specific IDoc and SAP BAPI/RFC functions for the transactions that you want to process.
The following table describes the required authorization to process IDocs and SAP BAPI/RFC functions:
Function
Object Name
Authorization
SAP BAPI/RFC
S_RFC
SYST, SDTX, SDIFRUNTIME, RFC_METADATA, RFC1, RFC2, ABAP4_COMMIT_WORK, BAPI_TRANSACTION_COMMIT
IDocs
S_RFC
SYST, SDTX, SDIFRUNTIME, RFC1, RFC2, EDIMEXT
For more information about how to configure SAP user authorization in the SAP system, see SAP user authorizations.

Configure the sapnwrfc.ini file

SAP uses the communications protocol, Remote Function Call (RFC), to interact with external systems.
You need the sapnwrfc.ini file to process SAP IDocs or SAP BAPI/RFC functions that facilitate transfer of data when you read from or write to SAP through the SAP IDoc or SAP BAPI/RFC interface.
Create the sapnwrfc.ini file and include the necessary connection information and RFC-specific parameters required by the SAP connection type. You can use a DOS editor or WordPad to create the sapnwrfc.ini file, so that you can avoid errors commonly introduced by Notepad. Check out Sample sapnwrfc.ini files for connection types to know more about the sapnwrfc.ini file samples that you can use for different connection types.
After you create the sapnwrfc.ini file, you need to place the sapnwrfc.ini file in the agent directory. The agent verifies the sapnwrfc.ini file, and then use it for the configured connection.
Placing the sapnwrfc.ini file in the agent directory
You can use the Secure Agent or serverless runtime environment to connect to the SAP system as an RFC client, as follows:
Note: Ensure the deploy_to_main\bin\rdtm directory exists. If it does not, create it and then place the files.
Restart the agent after placing the file in the required directory.
Upgrading from an earlier version
If you are upgrading from an earlier version, you do not need to create an sapnwrfc.ini file. The Secure Agent copies the sapnwrfc.ini file to the deploy_to_main\bin\rdtm directory.
Verifying the sapnwrfc.ini file
When you create a connection, the Secure Agent first verifies if an sapnwrfc.ini file exists in the directory. If the sapnwrfc.ini file exists, the Secure Agent uses the sapnwrfc.ini file. Else, an exception occurs.

Sample sapnwrfc.ini files for connection types

You can use the sapnwrfc.ini file to configure the following types of connections:
Connection to an SAP application server
Create this connection to enable communication between an RFC client and an SAP system. Each connection entry specifies one application server and one SAP system.
The following sample shows a connection entry for a specific SAP application server in the sapnwrfc.ini file:
DEST=sapr3
ASHOST=sapr3
SYSNR=00
Connection for SAP load balancing
Create this connection to enable SAP to create an RFC connection to the application server with the least load at run time. Use this connection when you want to use SAP load balancing.
The following sample shows a connection entry for SAP load balancing in the sapnwrfc.ini file:
DEST=sapr3
R3NAME=ABV
MSHOST=infamessageserver.informatica.com
GROUP=INFADEV
Connection to an RFC server program registered at an SAP gateway
Create this connection to connect to an SAP system from which you want to receive outbound IDocs.
The following sample shows a connection entry for an RFC server program registered at an SAP gateway in the sapnwrfc.ini file:
DEST=sapr346CLSQA
PROGRAM_ID=PID_LSRECEIVE
GWHOST=sapr346c
GWSERV=sapgw00
You can configure the following parameters in the sapnwrfc.ini file for various connection types:
sapnwrfc.ini Parameter
Description
Applicable Connection Types
DEST
Logical name of the SAP system for the connection.
All DEST entries must be unique. You need to have only one DEST entry for each SAP system.
For SAP versions 4.6C and later, use up to 32 characters. For earlier versions, use up to eight characters.
Use this parameter for the following types of connections:
  • - Connection to a specific SAP application server
  • - Connection to use load balancing
  • - Connection to an RFC server program registered at an SAP gateway
ASHOST
Host name or IP address of the SAP application. The Secure Agent uses this entry to attach to the application server.
Use this parameter to create a connection to a specific SAP application server.
SYSNR
SAP system number.
Use this parameter to create a connection to a specific SAP application server.
R3NAME
Name of the SAP system.
Use this parameter to create a connection to use SAP load balancing.
MSHOST
Host name of the SAP message server.
Use this parameter to create a connection to use SAP load balancing.
GROUP
Group name of the SAP application server.
Use this parameter to create a connection to use SAP load balancing.
PROGRAM_ID
Program ID. The Program ID must be the same as the Program ID for the logical system that you define in the SAP system to send or receive IDocs.
Use this parameter to create a connection to an RFC server program registered at an SAP gateway.
GWHOST
Host name of the SAP gateway.
Use this parameter to create a connection to an RFC server program registered at an SAP gateway.
GWSERV
Server name of the SAP gateway.
Use this parameter to create a connection to an RFC server program registered at an SAP gateway.
TRACE
Debugs RFC connection-related problems.
Set one of the following values based on the level of detail that you want in the trace:
  • - 0. Off
  • - 1. Brief
  • - 2. Verbose
  • - 3. Full
Use this parameter for the following types of connections:
  • - Connection to a specific SAP application server
  • - Connection to use load balancing
  • - Connection to an RFC server program registered at an SAP gateway
The following snippet shows a sample sapnwrfc.ini file:
/*===================================================================*/
/* Connection to an RFC server program registered at an SAP gateway */
/*===================================================================*/
DEST=<destination in RfcRegisterServer>
PROGRAM_ID=<program-ID, optional; default: destination>
GWHOST=<host name of the SAP gateway>
GWSERV=<service name of the SAP gateway>
*===================================================================*/
/* Connection to a specific SAP application server */
/*===================================================================*/
DEST=<destination in RfcOpenConnection>
ASHOST=<Host name of the application server.>
SYSNR=<The back-end system number.>
/*===================================================================*/
/* Connection to use SAP load balancing */
/* The application server will be determined at run time. */
/*===================================================================*/
DEST=<destination in RfcOpenConnection>
R3NAME=<name of SAP system, optional; default: destination>
MSHOST=<host name of the message server>
GROUP=<group name of the application servers, optional; default: PUBLIC>

Define SAP Connector as a logical system in SAP

To receive IDocs from and send IDocs to SAP, you need to define SAP Connector as an external logical system in SAP.
To define SAP Connector as an external logical system, create a single logical system in SAP for IDoc ALE integration with SAP Connector, and then create an RFC destination configured with a tRFC port in the SAP system to communicate with SAP Connector.
To identify the external logical system, you also need to create a partner profile for the logical system that you created.
When you define SAP Connector as a logical system, SAP acknowledges SAP Connector as an external system that can receive outbound IDocs from SAP and send inbound IDocs to SAP.
Note: These instructions apply on the SAP version 4.6C. If you use a different version, the instructions may differ. For more information about how to create a logical system in SAP, see the SAP documentation.