General

Import of Transport Requests

Please import the SAP Transport Request provided to you after reaching out to https://crossalm2.atlassian.net/servicedesk/customer/portal/6.

This Transport Request delivers oData Services, customizing tables and technical functionalities needed by this product. The import of this Transport Request is necessary to continue with the configuration steps described below.

Configuration Guide

This documentation is guiding you through all configuration steps. Additionally or alternatively you can use the configuration guide provided in SAP Solution Manager by transaction code /XALM/CC4_CUST or via “SPRO → SAP Solution Manager Implementation Guide → SAP Solution Manager → Cross Connector”.

Open

Create a technical service user or choose an existing user

Go to SU01 to create your technical user e.g. “JIRASYNC”. This user will be used for communication from Jira to SAP Solution Manager.

It needs authorities to read, create and change all transaction types that should be synchronized in your SAP Solution Manager. Web UI authorities are not needed, but authorities for transaction types, texts, status, appointments, ppf action etc are needed. Therefore we recommend to use working end-user authorities. Additionally, the user needs authorization object S_SERVICE with the following values. These are needed to call the custom OData service in SolMan.

Open

For testing the user should be a dialog user (which can be analyzed using debugging). For production use, you should switch to a service or system user. This will guarantee that nobody can logon using this user, even he/she knows the password. This also will guarantee, that the password will never expire.

Activation of oData-Service

Open transaction /n/IWFND/MAINT_SERVICE and search for the oData-Service /XALM/CC4_EXT_INTEG_CREATE_SRV_01 and activate the Standard ICF Node

Add LOCAL_SM as System Alias.

In case the system alias LOCAL_SM is not existing, you have to generate it automatically or manually. Please have a look at 1786290 - Solman Setup:System alias could not be created successfully and 2550286 - Unable to register service in SEGW Transaction.

Maintain https certificate in STRUST

CC4 Cloud - Set up - Jira Side

• Please access your Jira Cloud Instance e.g. by using the URL https://<host>:port/.

• Open certificate e.g. in Chrome by clicking the lock next to the URL and select “Connection is secure“ and “Certificate is valid”.

   

   

• In the “Details”-tab of the certificate-viewer you can export the certificate.

You have already downloaded your certificate from Jira, now you have to import it in your SAP System.

• Goto your SAP system and perform logon.

• Call transaction STRUST.

  • Select node “SSL Client DEFAULT”.

  • Execute menu action Certificate → Import.

     

  • Select certificate file previously saved.

  • Add imported certificate to certificate list by pressing the related button.

  • Perform save.

Create RFC destination to external tool

The example configuration is shown for Jira Cloud, but other external tools are configured analogously.

• Open transaction SM59 and edit → create.

• Name: <Whatever you want> (Proposal: JIRA or JIRA_CLOUD)

• Type: G HTTP Connection to external server

• Technical Settings

  • Host: <Host of Jira Cloud Instance>
    (You can find host and port of your Jira instance in your URL address bar of your internet browser when loging in or working with Jira.)

  • Port: 443
    (for https or 80 for http or whatever is used in your landscape.)

  • Path: Empty

• Logon & Security

  • Authentication: Basic

  • Username: <Username of Jira synchronization user previously created on Jira side>
    (Usually it is an e-mail address. As workaround in a test environment you can use your own e-mail address.)

  • Password: <Token previously generated>

  • Security: SSL with Certificate stored in DEFAULT SSL Client secure store

• Please test your connection.

Configuration by template

Depending on the CC4 version -Server or Cloud- the configuration processes can differ from different templates.

CC4 Cloud connects to cloud-based external Systems, such as Jira Cloud. See side https://crossalm2.atlassian.net/wiki/spaces/JXFB/pages/6574244351 for Configuration Guide.

CC4 Server is used to connect to server based tools such as Jira (Server) Jira Datacenter. There are multiple templates avaiable. See for more information side https://crossalm2.atlassian.net/wiki/spaces/JXFB/pages/6574244075 for Configuration Guide.