CC4 - Set Up - Jira Side - Cloud - Connection Profile
This configuration page describes how the connection to Solution Manager will be established.
Connection Profile
Description
Simple text descriptor for the configuration profile, freely definable.
Jira Project
Select in which Jira project the integration will be available
SolMan URL
Define the protocol, domain and port via which Jira will communicate with your Solution Manager system.
Jump In 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:
If no explicit middleware endpoint is entered for the create and update status endpoint, the endpoints of the CC4 OData Service are automatically addressed. So /sap/opu/odata/XALM/CC4_EXT_INTEG_CREATE_SRV_01/ISCREATESET is set for the Create endpoint and /sap/opu/odata/XALM/CC4_EXT_INTEG_CREATE_SRV_01/ISUPDATESTATUSSET(IVEXTSYSGUID='',IVEXTID='',IVGUID='') for the Update Status endpoint
SAP Connection Settings
System ID
SID of your Solution Manager system.
SAP Client
Working client of your Solution Manager system.
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.
Please refer to this page on how to set it up: CC4 Create and maintain configuration profile
Please make sure that the value in this field corresponds exactly to the value entered as “External System” in the SAP CC4 view cluster.
Jira User used by SolMan
This field must contain the user that is maintained in the RFC of your solution manager system to act as the synchronization user on Jira side.
Please refer to this section to see how to set it up: CC4 - Set Up - SAP | Create RFC destination to external tool
Credentials
Basic Authentication
Maintain user information for the technical synchronization user on Solution Manager side.
Refer to this section for more info: CC4 - Set Up - SAP | Create a technical service user or choose an existing user
OAuth
If there is a middleware in place, e.g. CPI, OAuth authentication can be used as an alternative authentication method.
