Setting up an outgoing connection in SAP Solution Manager

The outgoing connection from SAP Solution Manager to Apache Tomcat must be configured in SAP transaction /nsm59. Add a new or change an existing HTTP RFC destination with type G.

  1. In SAP transaction /nsm59 configure the HTTPS port of the Tomcat Server. A redirect from the HTTP port to the HTTPS port of Apache Tomcat will not work with the SAP WEB AS. The HTTPS port is defined in the server.xml configuration file of the Tomcat Server.
  2. The SSL configuration of Apache Tomcat is switched off by default. Enable the configuration.
  3. In the settings for the SSL HTTP connector, set the Tomcat default port for SSL communication to 8443.
  4. The diagram below shows the example configuration of the RFC Destination (in the Target Host field enter the server name (case sensitive) instead of the IP address).

  5. In the Logon&Security tab of the RFC configuration define the logon procedure and the security protocol. Basic authorization with SSL communication and certificates is not supported by Apache Tomcat. Set the Logon Procedure to No Logon.
  6. In the security protocol status enable SSL and select a PSE from the certification list. SAP provides PSE “ANONYM SSL Client” and “DFAULT SSL Client (Standard)”.

  7. Check with the SAP Basis Administrator what client PSE should be used. In most cases this will be the PSE “SAP Client (Standard)”.
  8. After assigning a client Certificate to the RFC destination, save the settings. The RFC destination is configured for using SSL with Apache Tomcat. A connection test will fail if the Server certificate in Apache Tomcat is not trusted against a CA.
  9. Create a logical port (see Create a logical port).
  10. Configure the interface between SAP Solution Manager Service Desk and Service Manager for the SSL outgoing connection (see Configure interface to SAP Solution Manager Service Desk).