Setting Up a Connection with a SAP System

The ERP Integrator allows you to setup a connection to a SAP System using any of the following methods:

• NetWeaver SDK
• Classic SDK
• Classic SDK with Unicode support
• SOAP
• Java Connector (JCo)

The type of connection can be set in the SapConnectionType property.

The first thing you will need to do is set the appropriate properties. To establish a client connection using SOAP you can do something like this:

  SapClient1.SapConnectionConnectionType = ctSOAP
  SapClient1.SapConnectionSoapURL = "http://localhost:8000/sap/bc/soap/rfc"
  SapClient1.SapConnectionClient = "000"
  SapClient1.SapConnectionDestination = ""
  SapClient1.SapConnectionHost = "localhost"
  SapClient1.SapConnectionUser = "BCUSER"
  SapClient1.SapConnectionPassword = "minisap"
  SapClient1.SapConnectionSystemNumber = 0

If you are establishing a client to connection using the RFC SDKs, you can follow this example:

  SapClient1.SapConnectionConnectionType = ctNetWeaver
  SapClient1.SapConnectionClient = "000"
  SapClient1.SapConnectionDestination = ""
  SapClient1.SapConnectionHost = "localhost"
  SapClient1.SapConnectionUser = "BCUSER"
  SapClient1.SapConnectionPassword = "minisap"
  SapClient1.SapConnectionSystemNumber = 0
  SapClient1.OpenConnection()

Note that the credentials above are for connecting to a trial NetWeaver installation. You will need to provide your own credentials when connecting to your own SAP installation.

Using NetWeaver RFC SDK

The following libraries from the NetWeaver RFC SDK must be available at runtime:

• sapnwrfc.dll
• icudt30.dll
• icuin30.dll
• icuuc30.dll
• libicudecnumber.dll
• libsapucum.dll

Note that the dll names may be different depending on the version of the SAP RFC SDK installed. The examples above are for version 3.0.

Set SapConnectionType to ctNetWeaver (0) to use this connection type.

Using Classic RFC SDK

The non-unicode library does not require anything other than the librfc32.dll. Place the librfc32.dll in a location where it will be accessible at runtime. Please note that these libraries are provided in both x86 and x64, so your project must use the same platform that the DLL you are referencing was built on. You do not need to set anything special in the component when using the x86 or x64 libraries.

Set SapConnectionType to ctClassic (1) to use this connection type.

Using Classic RFC SDK with Unicode support

The following libraries from the SAP RFC SDK must be available at runtime:

• librfc32u.dll
• icudt30.dll
• icuin30.dll
• icuuc30.dll

Note that the dll names may be different depending on the version of the SAP RFC SDK installed. The examples above are for version 3.0.

Please note that these libraries are provided in both x86 and x64, so your project must use the same platform that the DLL you are referencing was built on. You do not need to set anything special in the component when using the x86 or x64 libraries.

Set SapConnectionType to ctClassicUnicode (2) to use this connection type.

Using SOAP

In order to use SOAP, you must set the SapConnectionType to ctSOAP (3) and set the SapConnectionSoapURL to the SOAP URL for your SAP system. While using SOAP, it is not necessary to call OpenConnection, as a connection will be established when you call a function. However if you do call OpenConnection, the component will call RFC_PING to check if the SapConnectionSoapURL is available.

Note that this requires enabling SOAP on the SAP system.

Using the Java Connector

In order to use the Java Connector, the sapjco3.jar must be added to your project. Please note that these libraries are provided in both x86 and x64, so your project must use the same platform that the DLL you are referencing was built on. You do not need to set anything special in the component when using the x86 or x64 libraries.

Set SapConnectionType to ctJavaConnector (4) to use this connection type. Note that this connection type is only available in Java.