Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 5 Next »

System Requirements

Required Software components:

  • SAP_BASIS min 7.31 SP15

  • If the system runs on 7.31 as a prerequisite you have to deploy at least the following three add-ons IW_BEP, GW_CORE and IW_FND using transaction SAINT. When using SAP NetWeaver 7.40 or higher, this step is not necessary since the software component SAP_GWFND is already deployed as part of SAP Basis.

    Minimum requirement:

    • SAP Gateway Backend Framework:

      • IW_BEP 200 SP12

    • SAP Gateway Hub Framework:

      • IW_FND 250 SP12

      • GW_CORE 200 SP12

The compatibility matrix about SAP Gateway 2.0 support package stacks and the corresponding support package stacks for software component SAP_GWFND in SAP NetWeaver 7.40, 7.50 are to find in the SAP Note 1942072.

On this page

SAP System Prerequisites

This steps must be perfomed on the TM Controller

Step

Transaction

1

HTTPS Service

SMICM

Make sure that the HTTPS service is active (Transaction SMICM -> Services).

2

Profile parameters

To enable successfull SSL handshake with the Jira Cloud instance set the following profile parameters:

ssl/ciphersuites = 135:PFS:HIGH::EC_P256:EC_HIGH
ssl/client_ciphersuites = 150:PFS:HIGH::EC_P256:EC_HIGH
icm/HTTPS/client_sni_enabled = TRUE
ssl/client_sni_enabled = TRUE

3

Install ITSM SSL Cerficates

STRUST

In order to use the HTTPS protocol for the RFC connection, install the security certificate from ITSM system into the SAP system, transaction code STRUST, usually under the node ‘SSL client SLL Client Standard’.

4

Create RFC connection to ITSM

SM59

Communication with ITSM system always takes place via the RFC connection, where the information about the authentication and the service URI for the REST service is stored. Logon data, etc. is stored by transaction SM59 already in a secure manner and the REST client implementation can rely on this.

  • Create RFC destination with type 'G' (HTTP Connection to External Server)

  • Technical Settings

    • RFC Destination Name:
      Choose a meaningful name to identify the connection (e.g., SMARTITSM).

    • Connection Type: ‘G’ > HTTP Connection to External Server

    • Target Host: api.dot4.de

    • Port: 443

    • HTTP Proxy Options: If you use a proxy, please maintain the proxy

  • Logon & Security:

    • Authentication Method: Basic Authentication

    • User: <tennant>\<user>

    • Password: <Password>

    • SSL Certificate: Ensure the SmartITSM certificates are imported in STRUST and assigned here.

 Logon & Security Screenshots
image-20241218-163014.png

image-20241218-163051.png

  • Special Options:

    • HTTP Settings > HTTP Version: HTTP 1.1 (mostly required)

 Special Options Screenshots
image-20241218-163238.png

  • No labels