/
CC4 - 1.1 Connection Profile

CC4 - 1.1 Connection Profile

Owned by CrossALM
Last updated: Jun 27, 2024 by Yannic Zinke

This configuration page describes how the connection to Solution Manager will be established.

Connection Profile

 

image-20240606-110424.png

Description

Simple Text descriptor for the configuration profile, freely definable.

Template

The configuration of all additional steps as well as the supported functionality depend on this value.

For a full explanation of the available templates please refer to Connection Templates

Jira Project

Select in which Jira project the integration will be available

 

SolMan Url

Define the protocol, domain and port that should be used for building the URL that will directly forward end users to the Solution Manager transaction when the link in the Jira ticket is clicked.

Middleware

In case a middleware is used between Jira → SolMan, the checkbox “Middleware” must be checked. It is then possible to enter an individual endpoint for every endpoint of the CC4 OData service. The CC4 OData service has three endpoints:

  • ISCREATESET: for creating and updating SolMan transactions

  • ISUPDATESTATUSSET: for changing the status of SolMan transactions

  • ISATTACHSET: endpoint that is used for synchronizing attachments. It is not directly addressed as an endpoint but is referenced in the ISCREATESET endpoint

How do the connection calls between Jira and SolMan work in general when no middleware is used?

  • Connection check: Jira sends a GET call to the OData service to get a token from SolMan. The call does not address any specified endpoint. If Jira receives a token back the connection check is successful. If no token is received the connection check is not successful.

  • ISCREATESET: At first, Jira sends a GET call to the OData service to receive a token from SolMan. If Jira receives a token back it sends a POST call to the OData end point ISCREATESET and performs the creation/update of the SolMan transaction.

  • ISUPDATESTATUSSET: Jira first sends a GET call to the OData service to get a token from SolMan. When Jira receives a token back, it sends a PUT call to the OData endpoint ISUPDATESTATUSSET and performs the status change of the SolMan transaction.

 If a middleware is used, the token handling is handed over to the middleware. Respective endpoints must be created in the middleware for the following OData end points:

  • ISCREATESET

  • ISUPDATESTATUSSET

Additionally, an own end point for the connection check must be created in the middleware. As token handling is handled by the middleware, a success message (Code 200) is expected by the app.

As ISATTACHSET is not directly addressed, no separate endpoint needs to be created in the middleware.

In the ‘SolMan Url’ field, the general URL to the middleware must be entered then. For the different endpoints and for the connection check, the endpoints must be entered as they were defined in the middleware:

image-20240606-125953.png

System ID

SID of your Solution Manager system.

SAP Client

Working client of your Solution Manager system.

SAP Language

Preferred language of your Solution Manager System, this is mainly used for error messages.

Configuration Profile

This field must contain the information created in SAP during the Outbound Customizing.

What value needs to be maintained here depends on the template selected above.

Please refer to Connection Templates

Please make sure that the value in this field corresponds exactly to the value entered as “External System” in the SAP CC4 view cluster. 

User

Maintain login information of the synchronization user that will be used in your SAP system.

All creation and update actions will be executed by this user. Authorization has to be adjusted accordingly on the SAP side.

Check the SAP Configuration page for the respective template you are using for further information.

Example

After saving the Connection Profile, you can check it to see if you can reach SAP Solution Manager without issues.

 

Related content