SAP Solution Manager Interface Set-up Documentation

This document contains information on how to set up SAP Solution Manager service and configure Celonis Process Management to use it.

SAP Solution Manager Requirements

Features

  • The Document Versioning feature must be disabled to prevent errors during document updates.

1. Service set up

  1. Create a SQL Server database to be used by the service as a configStore.
  2. In the new database, create a table named dbo.settings with columns: Key(nvarchar(1024), null) and Value(nvarchar(max), null) .
  3. In the appsettings.json file, set the following configuration:
    Copy
    Copied
    {
    "ConfigStoreConnection": "Server=[SERVERNAME];Database=[DATABASENAME];Trusted_Connection=True;",
    "ConfigStoreTableName": "settings",
    "Serilog": {
        "MinimumLevel": "Verbose",
        "WriteTo": [
            {
                "Name": "File",
                "Args": {
                "path": "Logs\\log.txt",
                "rollingInterval": "Day"
                }
            }]
    },
    "AllowedHosts": "*"
}
  4. (Optional) Set sensitive data in user secrets (In development "ConfigStoreConnection").
  5. (Optional) Change Serilog settings in appsetting.json if needed.

2. Setting SAP Solution Manager run on premise

NOTE: This step is only needed if the SAP Solution Manager microservice is installed on premise.

This section explains how to set up the SAP Solution Manager microservice on IIS to run on an on premise solution.

Prerequisites for setting up SAP Solution Manager interface on premise:

  1. Running Celonis Process Management instance (1904 or higher).
  2. Valid relational database connection string for a database the microservice can use. An empty database has to be created manually.
  3. Accessible SAP Solution Manager instance https://{ip}:{port}/sap/opu/odata/sap/processmanagement/ with provided valid certificate.
  4. Provided valid certificate for SAP Solution Manager interface. Who is responsible for this?
  5. For the machine where the microservice will run, you need to have .Net Core Hosting bundle (for .Net core 3.1 applications) installed.
  6. Powershell version 5 or higher (to can run the install script).

2.1 Get zip file of a microservice build

You can get this file on the Celonis Process Management FTP server.

2.2 Configure the json parameters to create application site

Download the parameters.json file here. This file is used by the powershell script called Install.ps1.

Open the parameters.json file and change the parameters as shown below:

Copy
Copied
"SourcePath": - path to your zip file of the microservice 
"BaseTargetPath": - path to where the script will be unzipped
"InstanceName" : - should be Symbio-Service-SolMan
"IISSettings":
        "SiteName": - should be Symbio-Service-SolMan
        "ApplicationPoolName": - should be Symbio-Service-SolMan
        "ApplicationPoolUser": - should be the current user example (INT\username)
        "ApplicationPoolPassword": - should be the user password
        "Bindings": 
            "Protocol": "https"
            "Port": - use available port
            "HostName": - give it a wanted hostname
            "CertificateHash": - provide the certificate hash you want to use ( found in the iis -Server Certificates. It should be in local machine , personal or trusted root )
            "CertificateCN" : - provide name of certificate (found in the iis -Server Certificates)
            
"AppSettings":-
    "ConfigStoreConnection": - give right connection string to the database( you have to create the database yourself)

2.3 Run the script

  1. Turn on Powershell.
  2. Navigate to the folder where your script is located.
  3. Run the command : Set-ExecutionPolicy
  4. Provide the parameter Execution policy : unrestricted .
  5. Run the following line: ./Install.ps1 -ParametersFile symbio-service-solman.parameters.json

This will create the application pool and site for the microservice.

To check if the site is working, call this request from your browser: https://{domain}:{port}/api/values

This will return a simple response to show it is working.

2.4 Set the SAP Solution Manager certificate to be trusted

The client should provide the valid certificates for the SAP Solution Manager microservice and for the SAP Solution Manager API.

If for some reason the client cannot provide the certificates, in order for the microservice to work, they have to communicate with the SAP Solution Manager API.

The SAP Solution Manager API may have a certificate that is not trusted, so you may have to export it to your computer and then put it into MMC -> Certificates-> Trusted Root Certification Authorities. This will ensure that the connection is safe.