SAP TM Integration Framework.

Owned by Maria Hald
Last updated: Apr 21, 2022
2 min read

The ITSM systems are configured and activated in the configurations cockpit. The configuration cockpit of TM Integration Framework is called via the transaction /RTC/TM_IF_CONFIG. The section “ITSM System configuration” contains the configuration for the communication from SAP to Jira.

The assignment between transport requests and Jira issues are done by SAP attributes and, after the transport request has been moved to the Transport Manager, by the TM attributes.
The following two informations are stored in the SAP/TM attributes:

  1. ITSM name (configured in the configuration cockpit)

  2. Jira Issue ID

To be able to continue the communication from SAP to Jira and to be able to execute defined actions, it is important to ensure that the Jira issue ID's do not change after the migration and that the ITSM configuration has been adapted from the server to the cloud in the configuration cockpit.

 

Preparation BEFORE migration

ITSM System configuration

  1. Make a copy of current migration (e.g. with Server ID SERVER_COPY)

  2. Create a new entry from the template for Jira Cloud (e.g. with Server ID CUST_CLOUD_TEMPLATE)

  3. Adapt configuration in the new entry

    • Server Path

    • RFC Destination

    • Automation Path

    • Automation RFC

    • Work items - If customer attributes is used to save Jira issue ID, then the attribute name must be changed

    • Automation - Add automation items

    • Development system - Add development systems

    • Optional settings - check optional settings

  4. Set deaktivate flag for the new entry (CUST_CLOUD_TEMPLATE)

TM Workflow step configuration

  1. Make a copy for all item types of current migration (using same Server ID e.g. SERVER_COPY)

  2. Copy all entries to the newly created Jira Cloud Server ID (e.g. Server ID CUST_CLOUD_TEMPLATE

  3. Adapt filter query for the GET item from Server filter to Cloud filter:

    • Filters to take into account the development systems defined in the Jira project

      • Jira Server: project in projectsForProperty( devSystems, "~", {SYSID}_{MANDT} )

      • Jira Cloud: project.property[devSystems].content ~ "{SYSID}_{MANDT}"

    •  

  4. Optional action can be copied also from Jira Server entry to the newly created Jira Cloud template (CUST_CLOUD_TEMPLTE). That allows a test for the template configuration.

Steps AFTER migration

ITSM System configuration

  1. Note used ITSM ID for Jira Server

  2. Delete ITSM ID entry for Jira Server (a copy was made as preparation)

  3. Copy in the preparation created Jira Cloud entry and save it with previously noted ITSM ID

The created ITSM ID for Jira Cloud settings must be created with the same name as used for Jira Server.

 

TM Workflow step configuration

  1. Inactivate entry for item type GET, that was used for server

  2. Activate entry for item type GET, that was prepared for cloud