Setting up the SAP call out to a synchronous system sample

The SAP call out to a synchronous system sample was developed for a level of SAP that has a given definition of various SAP objects. If you encounter any problems when you run the sample, ensure that the definitions are correct by regenerating these objects for the local SAP system against which you want to run the sample. You can perform this action by running the Adapter Connection wizard from the Integration Development perspective:

1. Click File > New > Adapter Connection, and select REPLYSAMPLE_SAPAdapter_Tx.
2. For instructions about how to complete the rest of the wizard, see Building the SAP call out to a synchronous system sample.

The following sections describe the configuration setup that is required to run the samples that demonstrate the SAPInput node.

• Enable the Adapter Connection project to locate the SAP JCo Libraries and JAR file
• Configure the SAP system for the SAP Inbound sample
• Configure the integration node runtime with SAP JCo Libraries
• Configure the connection details for the SAP inbound adapter

Enable the Adapter Connection project to locate the SAP JCo Libraries and JAR file and SAP IDoc JAR file

1. You must make the SAP Java Connector (SAP JCo) interface libraries and JAR file and SAP IDoc JAR file available to the Adapter Connection project so that the SAP samples can be built successfully after you have imported them:
   • On Windows:
     1. Copy the sapjco3.dll dependency library to the local subdirectory C:\SAP_JARS.
     2. Copy the sapjco3.jar JAR file into the same local subdirectory C:\SAP_JARS (the sample references this subdirectory). To use a different location, see Step 2.
     3. Copy the sapidoc3.jar JAR file into the same local subdirectory C:\SAP_JARS (the sample references this subdirectory). To use a different location, see Step 2.
   • On Linux:
     1. Copy the libsapjco3.so dependency library to the local subdirectory /opt/SAP_JARS.
     2. Copy sapjco3.jar into the same local subdirectory /opt/SAP_JARS.
     3. Copy sapidoc3.jar into the same local subdirectory /opt/SAP_JARS.
     4. Modify the attributes of the files so that you have read and execute access to all of the the files.
2. Optional: Update the SAP JCo and IDoc JAR location:
   1. Import the sample.
   2. Right-click the Adapter Connection project, REPLYSAMPLE_SAPAdapter_Tx, select Properties > Java Build Path > Library Tab and specify the correct location of sapjco3.jar and sapidoc3.jar for the appropriate operating system.

Configure the SAP system for the SAP Inbound sample

When you are using integration node inbound messaging, you must configure the SAP system so that it can uniquely identify the integration node as a target destination.

Create the RFC connection from the SAP system to the integration node :

1. Log in to your SAP system.
2. Go to the SM59 transaction, Configuration of RFC connections.
3. Click TCP/IP connections, click Create.
4. Check that the connection type is set to T.
5. Set RFC Destination name to an appropriate value; for example, SAMPSCI. Ensure that the name of the RFC Destination is eight characters or fewer, and use the same name to replace SAMPSCI wherever it is used in this sample. To understand how you can use different names for the following steps, consult the documentation for your SAP system. However, for this sample, use the same name for all created objects.
6. On the Technical Settings tab, click Registered Server Program.
7. Set Program ID to match the Program ID that is specified in the integration node adapter; for example, SAMPSCI.
8. Click Save to save the settings.
9. Enter a description in the Description 1 field; for example, RFC for Sample.
10. Enter a description in the Description 2 field; for example, your name.
11. Click MDMP & Unicode.
12. Select Unicode.
13. In the window that is displayed, click the green tick.
14. Click Save.

Configure the integration node runtime with SAP JCo Libraries

To deploy message flows with SAP nodes, you must configure the integration node runtime with the prerequisite SAP JCo Libraries. These libraries are used by the underlying SAP adapter component to establish connections with the SAP system.

You must run the following mqsichangeproperties commands from a command environment to set the location of the directories that contain the SAP JCo Libraries.

1. Run the following commands, changing the SAP client directory to match your operating system and choice of location:

   mqsichangeproperties  IB9NODE -c EISProviders -o SAP -n jarsURL -v C:\SAP_JARS

   mqsichangeproperties IB9NODE -c EISProviders -o SAP -n nativeLibs -v C:\SAP_JARS

2. To verify that the properties are set up correctly, run the following command:

   mqsireportproperties IB9NODE -c EISProviders -o SAP -r

3. Stop and restart the integration node by using the following commands:

   mqsistop IB9NODE

   mqsistart IB9NODE

Configure the connection details for the SAP inbound adapter

1. Import the SAP sample into your workspace.
2. Expand the SapInboundSyncCustomerSampleMessageSet message set project.
3. Click Adapters > Inbound > SAP.
4. To open an editor in which you can specify the connection parameters that are required to access your SAP system, double-click sapinboundsync.inadapter.
5. Enter the following settings in the editor:
   1. Gateway host name or IP address.
   2. Gateway service; for example, sapgw00. To find the Gateway Service use the transaction code SMGW (Gateway monitor) in the Remote TP Name column.
   3. RFC Program ID; for example, SAMPSCI.
   4. SAP Client ID (from SAP txn SCC4 ).
   5. Username. The user name for the SAP system.
   6. Password. The password that corresponds to the user name.
   7. Language Code. The language code, if the language is not English.
   8. Hostname or IP address. The host name or IP address of the SAP application server.
   9. SAP System Number.
6. Save the updated adapter.
7. Expand the SapInboundSyncCustomerSampleMFlow Integration project.
8. To open the Broker Archive editor, double-click SapInboundSyncCustomerSample.bar.
9. Click the Prepare tab.
10. Click Build broker archive.
11. Save the broker archive.
12. Deploy the SapInboundSyncCustomerSample.bar BAR file to the SapSample integration server: Right-click the BAR file and select deploy, or drag the BAR file to the integration server.

Back to sample home