Page Comparison

HTTPS Service

SMICM

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

Profile parameters

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

Create RFC connection to ITSM

SM59

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

Expand
title Logon & Security Screenshots
Image Added Image Added

• Special Options:

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

Expand
title Special Options Screenshots
Image Added

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

Import transport requests

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

Expand
title Screenshot WEBGUI > Handler List tab
Image Added

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}

Expand
title 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 Added

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.  

Create Trusted RFC connection

Create trusted RFC connections between all development systems and TM Server

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

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.

• Create an HTTPS entry for host:
  REALTECH-SMARTITSM-INTEGRATION.AZUREWEBSITES.NET