Verify if you have a proper setup of the Secure Network Communication to ensure secure
communication between the adapter and SAP NetWeaver AS ABAP
and to avoid possible configuration issues.
Procedure
-
Make sure the following files are in their corresponding folders in the client system, where
the IBM® Security Directory Integrator is running.
Folder |
Files |
\usr\sap |
- sapcrypto.dll
- sapgenpse.exe
- local certificate
- server certificate
|
\usr\sap\sec |
- adapter.pse
- cred_v2
- ticket
|
-
Make sure all the files used from the SAP cryptolibrary packages are unused.
-
Make sure the sapcrypto.dll file is a Win32 file. Otherwise, you are
prompted that the sapcrypto.dll file is not a valid Win32 application.
-
Use the following command to check the certificate entry in the sapgenpse
file:
sapgenpse maintain_pk -l -p <PSE_name> [-x <PIN>]
Where:
- -l
- Returns the list of existing certificates.
- -p <PSE_name>
- Specifies the path and file name for the server's PSE.
- -x <PIN>
- Specifies the PIN that protects the PSE
-
Make sure the entry to USRACLEXT (table) in SM30 (t-code) complies with the following
requirements:
- Starts with "p"
- Contains the details of the local certificate
- Does not have any space after a period "."
- Includes the canonical name
-
The server certificate name must be selected in STRUST (t-code) when you download it.
-
Make sure each parameter in the Optional RFC parameter complies with the following
requirements:
- Separated using a pipe "|"
- Does not have any space after a period "."