Overview
There are four parts to the setup of SAP SNC between Boomi and SAP. The steps are:- SAP SNC software download/SAP prerequisites including setting up a Distinguished Name and SAP User (shown here)
- Creation the SAP PSE (Personal Security Environment) file for you Boomi Runtime (shown here)
- Setup of your SAP JCo V2 Connector properties file in Boomi (this article)
- Setup in your SAP system to allow your Boomi Runtime to communicate via SAP SNC (shown here)
- (Optional) Validating your Connectivity between SAP and the Boomi runtime via SAP SNC as a Server ie: LISTEN (shown here)
Part 3: Configuring the SAP JCo Parameters in your Boomi SAP JCo V2 Connector
At the completion of this section, you will have successfully configured your SAP JCo V2 connection for SAP SNC support. The tasks are:- Configuration of SAP JCo Properties File to support SAP SNC as Client (SEND, EXECUTE) and Server (LISTEN) for IDocs
- Upload your SAP JCo Properties file to your Boomi Runtime
- Restart your Boomi Runtime
Prerequisites
The following information is required:- Your Distinguished Name from your SAP PSE setup
- SAP Distinguished Name from SAP PSE Import and confirmation from SAP Administrator
- Directory and File of SAP SNC executable (i.e., libsapcrypto.so for LINUX) in your Boomi runtime environment
- QoP (Quality of Protection) value, please consult with your SAP administrator on setting this value. This will be further discussed in Section 4 as well.
Steps
- Setup SAP JCO properties file for SAP SNC based on the prerequisites. Example shown below:
# Required SAP JCo Parameters to support SAP SNC for SEND IDocs and EXECUTE operations # SNC Mode is 0 – Inactive 1 – Active jco.client.snc_mode=1 # There is a p: in front of the Distinguished Name in the line below jco.client.snc_partnername=p:<SAP System Distinguished Name> jco.client.snc_myname=p:<Boomi Runtime Distinguished Name> # Options are 1, 2, 3, 8, 9 for snc_qop jco.client.snc_qop=8 jco.client.snc_lib=<location and filename of your SAP SNC executable> # Required SAP JCo Parameters to support SAP SNC for LISTEN Operation # SNC Mode is 0 – Inactive 1 – Active jco.server.snc_mode=1 # Options are 1, 2, 3, 8, 9 for snc_qop jco.server.snc_qop=8 jco.server.snc_lib=<location and filename of your SAP SNC executable> # There is a p: in front of the Distinguished Name in the line below jco.server.snc_myname= p:<Boomi Runtime Distinguished Name>j
- Upload your properties file to the Boomi Runtime. Instructions can be found here as per naming of the sample file, deployment, etc.
- Configure your SAP Connection
- Make sure to update the field 'JCo Properties Setting' with the properties file name (NOT the JAR file name). An example is shown below:
4. Restart your basic runtime/runtime cluster