You can use the Secure Sockets Layer (SSL) protocol to secure HTTP connections to and from the AS ABAP. When using SSL, the data being transferred between the two parties (client and server) is encrypted and the two partners can be authenticated. For example, if a user must transfer his or her account information, then you can use SSL to authenticate the user and encrypt the information during transfer.
Note
Users that access a service that is protected with SSL use the prefix https: in the URL instead of http:.
Use the following functions to maintain the server's SSL information:
Profile parameter maintenance (transaction RZ10)
Trust manager (transaction STRUST)
For more information, see Using the Trust Manager.
RFC destination maintenance (transaction SM59)
ICM Monitor (transaction SMICM)
For more information, see Monitoring the ICM with the ICM Monitor.
The server possesses a public and private key pair and public-key certificate.
The SSL protocol uses public-key technology to provide its protection. Therefore, the server must possess a public and private key pair and a corresponding public-key certificate. It must possess one key pair and certificate to identify itself as the server component and another key pair and certificate if it is to identify itself as a client component. These key pairs and certificates are stored in the server's own Personal Security Environments (PSEs), the SSL server PSE and the SSL client PSE, respectively. (For more information, see Public-Key Technology.)
You are authorized to receive the SAP Cryptographic Library.
Caution
The distribution of the SAP Cryptographic Library is subject to and controlled by German export regulations and is not available to all customers. In addition, the library may be subject to local regulations of your own country that may further restrict the import, use and (re)export of cryptographic software. If you have any further questions on this issue, contact your local SAP subsidiary.
For more information about public-key technology and SSL, see: