| Table of Contents |
|---|
| Note |
|---|
UNDER CONSTRUCTION |
Create a technical user or choose an existing user
...
You need a technical user on SNOW side for communication from SAP Solution Manager to SNOW.
...
Logon to your SNOW Instance with the technical user
Please check the logon to your SNOW Instance with the technical user created in the step before.
Verify authorizations
...
Access to Incident Mangement & Change Management in SNOW
Verify that you can access the areas where you want to use CC4.
...
Create and edit tickets of type Change Request, Incident, Change Task and Incident Task.
Verify that you can create, edit and read tickets of type Change Request, Incident, Change Task and Incident Task.
...
Create API token
Go to your Jira Account Settings with the technical user→ Security → API Token
or use the link https://id.atlassian.com/manage-profile/security/api-tokens
...
→ Create an API token and remember it for RFC destination creation on SAP side.
...
Register/Refresh HTTPS certificate - Download in SNOW
...
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 need the certificate to upload it in your SAP system after you finished the set up on Jira side. You can find the documentation for these steps on the page https://crossalm2.atlassian.net/wiki/spaces/CC4C/pages/6444187663/CC4+Cloud+-+Set+up+-+SAP+Side#Register%2FRefresh-https-certificate.
Import Automations
You find a connection test automation attached below to make sure your connection is working. You get a file with templates for 3 further automations after reaching out https://crossalm2.atlassian.net/servicedesk/customer/portal/6.
Connection Test
| View file | ||
|---|---|---|
|
Create issue
Change status
Change fields
Please import these automations in your Jira project by going to the system settings and choosing “Global Automation”.
...
Afterwards choose the three dots in the right corner and “Import rules”
...
Configure Automations
After importing the automations you need to adapt some sections.
In every automation please change the following components if available:
...
“Initiator is not”
Insert your technical Jira user in “Criteria”
...
...
“Then: Create variable”
Insert the domain of your Solution Manager System including port e.g. “sap.solman.com:443”
...
...
The following pages will guide you through the configuration process on ServiceNow side:
Please make sure the following points are already set up on SAP Side before starting the ServiceNow configuration to assure an active connection:
https://crossalm2.atlassian.net/wiki/spaces/CC4CJXFB/pages/64441876636870663169/CC4+CloudServiceNow+-+Set+upUp+-+SAP+Side#CreateSAP#Create-a-technical-service-user-or-choose-an-existing-user
Please be aware that Basic Authentication is used here, this means the value of the header needs to be Base64 encrypted.
...
“And: Send web request POST”
Adapt the client in the “Web request URL” and fill in the password from above in the authorization field here too and exchange the “IVEXTSYSGUID” with the name of your configuration profile from SAP Solution Manager, find documentation on https://crossalm2.atlassian.net/wiki/spaces/CC4CJXFB/pages/64441876636870663169/CC4+CloudServiceNow+-+Set+upUp+-+SAP+Side#CreateSAP#Activation-aof-configuration-profile
Check connection
After you passed the steps https://crossalm2.atlassian.net/wiki/pages/resumedraft.action?draftId=6444548121 and /wiki/spaces/CC4C/pages/6444187663 please check your connection with the “Connection Test” Automation in Jira.
To run the rule go to your Jira Project Settings again and open the “Connection Test Automation”.
...
Then run the rule and check the results in the Audit log.
...