Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 6 Next »

This steps must be perfomed on the TM Controller

Step

Transaction

Description

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., SNOW_CHG).

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

    • Target Host: <host>.service-now.com

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

  • Logon & Security:

    • Authentication Method: Basic Authentication

    • User: <ServiceNow Technical user>

    • Password: <Password>

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

 Logon & Security Screenshots
image-20250114-234859.png

image-20241218-163051.png

  • Special Options:

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

 Special Options Screenshots
image-20241218-163238.png
5

User Authorization

S_TCODE authorizations are needed for running the TM Integration Framework Transactions.

Relevant Transaction codes for the TM Integration:

  • · /RTC/TM_IF_CONFIG –TM IF Configuration cockpit
    the user needs authorization for transaction codes:

    • /RTC/TM_IF_CONFIG - TM Integration Framework: Config.

    • /RTC/TM_IF_ITSM - TM Integration Framework: ITSM Conf.

  • /RTC/TM_IF_MONITOR – TM IF Monitor and Recall

  • /RTC/TM_IF_LOG – TM IF Log

  • No labels