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 »

System Requirements

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'System Requirements - SAP'.

Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'System Requirements - SAP'.

On this page

SAP System Prerequisites

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

SAP System Prerequisites > Bi-direction connectivity

If you use SmartChange Panel bi-directionally the following steps must be configured in SAP.

Example for Bi-directional activities

  • create transport requests

  • approve transport request

  • display TM attributes in SmartChange Panel

Step

Transaction

Description

1

Import transport requests

Import the transport request SmartChange (OData Hub_Registration v5.x.0.0).
The transport request is included in the latest Service Pack!

2

Activate web services

SICF

The following services are consumed and must be activated

  • /sap/bc/gui/sap/its/webgui
    SAP Login for WebGUI

  • /sap/public/bc/icf/logoff
    SAP Logoff for user logout

  • /sap/opu/*
    OData for SAP Products

  • /sap/opu/odata/RTC/TM_GW_SRV/*
    All Realtech OData Services are located under this path

  • /sap/opu/odata/RTC/TM_GW_NOTIFY_SRV/*
    SmartChange notification OData Services

Service WEBGUI

In the Handler List, add /RTC/CL_HTTP_HANDLE to the last position

 Screenshot WEBGUI > Handler List tab
image-20241218-165345.png

3

Configure SAP Gateway Routing

SPRO

  1. Activate SAP NetWeaver Gateway
    IMG Path: SAP NetWeaver > SAP Gateway > OData Channel > Configuration

  2. Create SAP System Alias
    IMG Path: SAP NetWeaver > SAP Gateway > OData Channel > Connect Settings > SAP NetWeaver Gateway to SAP System > Manage SAP System Aliases

 Screenshots Manage SAP System Aliases

  • Not using a central hub please check if system alias LOCAL is created

  • Using SAP Gateway Server as central hub, create a system alias with (trusted!) RFC Destination to your backend system (e.g. NT3_SC_INT)

image-20241218-170329.png


4

Activate and Maintain Services

/IWFND/MAINT_SERVICE

Technical Service Name:

  • /RTC/TM_GW_SRV

  • /RTC/TM_GW_NOTIFY_SRV

  1. Click on the service name in the Service Catalog. 

  2. In the Systems Aliases window - add the system alias created before. 

  3. In the ICF nodes window - Activate the ODATA ICF node.  

5

Create Trusted RFC connection

Create trusted RFC connections between all development systems and TM Server

Note:
The trusted RFC connection is needed for distributed landscapes (TM Controller is not on the Development system)
Development system should trust TM Controller. 

6

Authorization for using trusted RFC connections

Assign the role /RTC/SC_INTEGRATION (object S_RFCACL) to all user using Odata Services (e.g. with SmartChange Approval, SAP Transport Integration for Jira).

7

Managing HTTP Whitelist

UCONCOCKPIT

If you use an HTTP whitelist, only HTTP calls from URLs in this list are accepted by the system. You can call this function from the UCON Cockpit).

Before SAP NW Release 7.51 SP00, it was only possible to edit the HTTP whitelist using the database table HTTP_WHITELIST.

  • No labels