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 (this article)
• 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 2: Setup of the SAP PSE file on Boomi Runtime

At the completion of this section, you will have successfully created the SAP SNC Personal Security Environment (PSE) file required to communicate via SAP SNC between Boomi and your SAP system.  The tasks are: 

• Create the SAP PSE file in your Boomi runtime 
• Import the SAP SNC certificate associated with the SAP system which you plan to communicate via SAP SNC
• Export your certificate to be imported by SAP Administrator in the SAP system
• Set up the user which will be used to access the SAP PSE file

Steps

1. Setup your SECUDIR Environment Variable based on example directory “/shared/boomi/sec” for Linux and “C:\Shared\Boomi\sec” for Windows
   • Note: Confirm the SECUDIR environment variable is pointing to the directory which contains the SAP SNC executables.
     • Linux Environment Variable example: $ export SECUDIR=”/shared/boomi/sec”
     • Windows System Environment Variable example: C:\Windows\system32> setx SECUDIR “C:\Shared\Boomi\sec” -M
2. Create a new PSE file with a specific PIN and associated Distinguished Name (DN). Example shown below:

   $ cd /shared/boomi/sec  
   $ sapgenpse gen_pse -v -p <PSE file name.pse> -x <PIN> “<DN>”

   • Note:
     • Unix and Windows syntax are identical
     • “<DN>” is the agreed Distinguished Name of the Boomi runtime and must be specified in double quotes 
     • Store the <PIN> as it will be necessary to access the PSE file
3. Import the SAP certificate which you have received from your SAP Administrator

   $ sapgenpse maintain_pk -v -p <PSE filename> -a <SAP certificate> -x <PIN>

4. (Optional) List the import of the SAP certificate into PSE.

   $ sapgenpse maintain_pk -p <PSE filename> -l -v -x <PIN>

5. Export your own certificate from the PSE file. This certificate will be imported by the SAP Administrator so that SAP will the recognize Boomi runtime

   $ sapgenpse export_own_cert -v -p <PSE filename> -o <your_certificate.crt> -x <PIN>j

   • Note: Send your exported certificate to your SAP Administrator to be imported via SAP Transaction STRUST
6. Specify the user which will access the PSE file – this user should be the same user executing the Boomi runtime 
   • Linux: $ sapgenpse seclogin -p <PSE filename> -O <user> 
   • Windows (Local System Account): C:\Shared\Boomi\sec> sapgenpse seclogin -p <PSE filename> -O SYSTEM
   • Windows User (DOMAIN\User): C:\Shared\Boomi\sec> sapgenpse seclogin -p <PSE filename> -O <user>
     • In this case, the <user> should be the DOMAIN\User
7. Capture the following information for handover to your SAP Administrator:
   • Boomi Runtime Distinguished Name (Note: The Distinguished Name is case sensitive!)

 

Note: Once this is complete please proceed to Step 3 here