HTTPS Configuration for Messaging

When configuring HTTPS for message exchange, you must handle the ABAP and Java parts differently.

For the ABAP proxies, you use transaction SM59 to configure the destinations pointing to the Integration Server to use HTTPS.

For the J2EE-based Adapter Engines and the Java proxies, HTTPS communication is set generically using the following parameter in the exchange profile (see also HTTP and SSL). = messaging

To be able to send and receive messages using HTTPS/SSL:

·        The J2EE Engine must first be configured to support HTTPS/SSL.

This process includes downloading and deploying the SAP Crypto Toolkit (IAIK) SDA from SAP Service Marketplace, as well as creating a private key and public certificate for the server. This whole procedure is described in detail under Transport Layer Security on the SAP J2EE Engine.

·        The AS-ABAP Engine must first be configured to support HTTPS/SSL.

For more information, see Using the Secure Sockets Layer Protocol with SAP NetWeaver AS-ABAP.

With HTTPS, you can use basic authentication with username and password, as well as authentication using client certificates. If you want to use client certificate authentication, additional private keys and public certificates are required for each user.