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 (discussed in this article)
• Creation of the SAP PSE (Personal Security Environment) file for you Boomi Runtime (shown here)
• Setup of your SAP JCo V2 Connector properties file in Boomi (shown here)
• 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 1 Prerequisites

SAP Administrator Support

• SAP Software Required
  • Download the latest SAP SNC (SAP CRYPTOLIB 8) from SAP Support Portal for your specific operating system 
    • Search keyword COMMONCRYPTOLIB 8 under Downloads and download the latest version/patch level 
  • Downloading the SAPCAR utility is required to extract the SAP SNC (COMMONCRYPTOLIB 8) once it is downloaded from SAP Support Portal
    • Search keyword SAPCAR under Downloads and download the appropriate version associated with your Operating System 
  • Alternatively, request your SAP administrator to download and extract the SAP SNC software and provide to you the software in a compressed file using non-proprietary tool zip, tar, etc. which you can extract into your Boomi server
• Establish “Distinguished Name” and configure SAP User
  • Your Boomi server is required to have a unique name called “Distinguished Name” (DN) in SAP SNC and an SAP user associated with is assigned to the SAP SNC
  • You should jointly establish the “Distinguished Name” with your SAP administrator based if a defined nomenclature is already established by your SAP administrator 
  • Unique DN is not required for Boomi runtime (basic runtime, runtime cluster, Cloud) for SAP SNC, however, you should align with your SAP team based on your proposed architecture (i.e., more than one basic runtime on a server)
    • DN can be used across multiple Boomi runtimes on the same infrastructure if necessary (e.g., CN=boomi_server_name, OU=organization_name, C=country_code) 
  • Define Unique SAP user which will be used with SAP SNC and Boomi 
    • SAP User, SAP Password, Client Number 
    • Unique SAP user will be linked to the “Distinguished Name” in SAP
  • Request SAP PSE certificate for SAP SNC from your SAP administrator for the SAP system
    • Your SAP administrator using transaction STRUST in SAP
  • SAP Administrator is knowledgeable on the steps required to import Boomi certificate generated from sapgenpse command in the Boomi runtime (i.e. SAP Transaction STRUST) 

Boomi Runtime Infrastructure

• SAP Java Connector libraries have already been installed in your Boomi runtime based on instructions in https://help.boomi.com/bundle/connectors/page/int-SAP_JCo_V2_additional_basic runtime_configuration.html
  • Boomi recommends that you use SAP JCO 3.1 based on SAP’s deprecation strategy for SAP JCO 3.0 as documented at https://support.sap.com/en/product/connectors/jco.html 
• SAP SNC Installation Directory “Best Practice” 
  • It is not recommended to install SAP SNC software in the same directory as SAP JCo V2 connector files (i.e., install in a separate directory outside Boomi installation in case you decide to delete and re-install Boomi runtime) 
  • The SAP PSE file which is created as part of the SAP SNC configuration in the Boomi runtime must be in the same directory as SAP SNC executables 
  • Once the SAP PSE file is created in the Boomi runtime, it is recommended to not move the file into a different directory
  • If using/creating a shared Connection, you can use one PSE file for your Boomi basic runtimes, runtime clusters, and Clouds.

Note: Once this is complete, please proceed to Step 2 here