Versions Compared

Old Version 13

changes.mady.by.user Kalpana Malladi

Saved on

compared with

New Version Current

changes.mady.by.user Kalpana Malladi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this article

Table of Contents
minLevel1
maxLevel7

...

You must install the SAP Java Connection (JCO) library for the SAP Snap Pack to work. You can download the shared library (Windows-sapjco3.dll) (Linux-libsapjco3.so)from theSAP portal.

Limitation

SAP configuration does not support the configuration of MSHOST (Message Server Host) on the Cloudplex.

Windows

  1. In all nodes of the Snaplex, install Copy the updated native library sapjco3.dll in %SL_ROOT%\ldlib (usually, c:\opt\Snaplogic\ldlib) .Set the Windows PATH variable to point to c:\opt\Snaplogic\ldlib. Restart the Snaplexon every node in the Snaplex. For Snaplexes with multiple nodes, make sure to install the library on every node.
    Note: For Snaplexes with multiple nodes, make sure to install the library on every node.

  2. Restart all the nodes ithe Snaplex.

Info

If you are upgrading to Jco 3.1.4 for Windows Snaplex, you must install the Visual Studio 2013 C/C++ runtime libraries. Learn more, https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=551387831

...

  1. Copy the updated native library libsapjco3.so file in  $SL_ROOT/ldlib (usually usually, /opt/snaplogic/ldlib) folder on every node in the Snaplex.
    Note: For Snaplexes with multiple nodes, make sure to install the library on every node.

  2. Restart all the nodes in the SanplexSnaplex.

Note

Update the following native library files under $SL_ROOT/ldlib/:

  • libsapjco3.so for Linux-based JCC nodes.

  • sapjco3.dll for Windows-based JCC nodes.

This is due to the parameter change in JCo (Java Connector) from 3.0 to 3.1. According to the JCo documentation, parameter jco.use_repository_roundtrip_optimization is used to optimize the metadata lookups.

In JCo 3.0.6, the default value of the parameter is 0, whereas, in JCo 3.1.10, the default value of the parameter is 1.
In the 3.0 driver, if the function module is not remote-enabled, the driver still calls the function module and the SAP server informs you regarding the failure. However, in the latest driver, if the function module is not remote-enabled, the JCo would detect it in advance, and the Snap fails.

Important: If you want to revert to the previous behavior, the JCo properties could be set through the jvm_options:

jcc.jvm_options=Djco.use_repository_roundtrip_optimization=0

...

  1. Register the external program in the SAP gateway by editing the reginfo file. For additional information, see Gateway Security Files secinfo and reginfo.

    1. Import reginfo in Gateway using the transaction code SMGW.

    2. Create RFC Destination of Type = 'T' (TCP/IP). For additional information, see SAP JCo Server Programming.

    3. Check the gateway monitor to ensure that the connection is registered correctly.

  2. Create a port using transaction code WE21.

...

Related content: