General

Import of Transport Requests

Please import the SAP Transport Request provided to you after reaching out to Cross ALM - Support and Helpdesk.

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. “ServiceNowSYNC”. This user will be used for communication from ServiceNow 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.

Register/Refresh HTTPS certificate - Download in ServiceNow

Create RFC Destination to ServiceNow

• Open transaction SM59 and Edit → Create.

• Name: <Whatever you want> (Proposal: ServiceNow)

• Type: G HTTP Connection to external server

• Technical Settings

  • Host: <Host of ServiceNow Instance>
    (You can find host and port of your ServiceNow instance in your URL address bar of your internet browser when logging into or working with ServiceNow)

  • Port: 443
    (For HTTPS or 80 for HTTP or whatever is used in your landscape.)

  • Path: Empty

• Logon & Security

  • Authentication: Basic

  • Username: ServiceNow-technical user with admin roles (or similiar authorizations) and cc4-roles

    • (see also CC4 / ServiceNow - ServiceNow Side - Set Up Prerequisites in ServiceNow | 1. Create a technical user or choose an existing user )

  • Password: <the user's password>

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

Test Connection

If you receive an HTTP status code 200 the connection is working. If you receive an error message, please verify host, port, username and password. Please ensure that a valid certificate is uploaded to STRUST.

Create and maintain a configuration profile (by template)

CC4 Cloud connects to cloud-based external Systems, such as ServiceNow or Jira Cloud. See side CC4 - Set Up - SAP Side - Cloud for details.