How to activate the SmartChange OData services

The TM web services are REST services created with ODATA API under the name of ‘/RTC/TM_GW_SRV’.
This article describes the activation of the SmartChang Odata services.

Instructions

The ODATA services /RTC/TM_GW_SRV are used by
- SmartChange Apps
+ SmartChange Approval
- SmartChange Integrations
+ SAP Transport Integration for JIRA
+ SAP Transport Integration for ServiceNow

System prerequisites

Service activation

Step: Activate HTTP service using transaction SMICM
Step: Configure SAP Gateway (transaction SPRO)
- Activate SAP Gateway
  Activate or Deactivate SAP NetWeaver Gateway
- Create SAP System Alias
  Manage SAP System Aliases
  
  Not using a central hub please check if system alias LOCAL is created:
Activate ICF node OPU (transaction SICF)
- Select service /default_host/sap/opu
- Activate Service OPU
- Confirm activation
Import Transport Request SmartChange (OData Hub_Registration v5.4.0.0).
Service Registration (transaction /IWFND/MAINT_SERVICE)
Go to /IWFND/MAINT_SERVICE to activate the Service Registration. The SICF node is delivered by default as inactive for security reasons.
The technical service name is /RTC/TM_GW_SRV - TransportManager OData Service.
1. Click on the service name in the Service Catalog.
  In the Systems Aliases window - add the system alias created before.
  In the ICF nodes window - Activate the ODATA ICF node.

SmartChange (OData Hub_Registration v5.4.0.0)

Service name: /RTC/TM_GW_SRV

General information

The TM web services are REST services created with ODATA API under the name of ‘/RTC/TM_GW_SRV’.

These calls are secured by the generated token ‘X-CSRF-Token’ which is fetched via a request of type ‘GET’ and sent to the other types of calls that require changes to the entities (‘POST’/’PUT’/DELETE’) when the session is created from the external.

Each entity is mapped to a structure from the ABAP Dictionary and its fields are used as input and also as output parameters. The ‘PUT’ and the ‘DELETE’ request types will not return any of the fields.

The service has navigations from an entity to another when both entities have linked keys.

E.g. of navigation from a transport request to its attributes for a ‘GET’ request:

‘sap/opu/odata/sap/RTC/TM_GW_SRV/Transport_RequestSet(<KEY>)/TR_AttributesSet’.

Next steps are ONLY relevant when using the SmartChange Integration
Additional configuration is required to Create TR and Release TR.
If you want to use these functions with the SmartChange Integration, please continue.

Additional configuration

Create trusted RFC connection between Development system(s) and TM Server.
- Use the naming convention: ZRTC4_TM_<targetSID>_<targetClient>_TRUST, where <targetSID> is the SID of the development system, and <targetClient> is the working client of the development system.
- Make sure that the RFC destination is set up as trusted: SM59>Logon and Security tab>Trust relationship = "Yes".
- Check if Systems are already Trusted Systems: TM Server must be a Trusted System of Development System (Transaction SMT1 on DEV).
  If NO, continue with following steps on DEV system:
Transaction SM59: Create an ABAP type RFC named 'TMS' (where TMS is SID of TM Server) to TM Server.
Transaction SMT1: Create a new trusted connection and follow the steps in the wizard to create it. Add 'TMS' as RFC there.
- on TMS system, a new RFC will be created called TRUSTING@"DEVsid"_"DEV_installationnumber"
- Test the connection. If not successfully connected:
  - error message is "Service 'sapmsDEV' unknown - in TMS Operation System check in the service file (/etc/service) if the service exists and create it.
    sapmsDEV 3601/tcp # SAP System Message Server Port
Assign the role /RTC/SC_INTEGRATION (authorization for using trusted RFC connections - object S_RFCACL) to all user using Odata Services (e.g. with SmartChange Approval, SAP Transport Integration for Jira).

REALTECH Connect