Connecting your On-Premise Source System

In this section, step 4 is considered in the interaction of administrators.

Documentation

This section of the course is relevant for: SAP Source System Administrators

In this chapter, we look at how to connect an SAP source system to SAP Signavio Process Insights. Understanding the flow of information between your SAP on-premise source system and SAP Signavio Process Insights should help you set up your connection, which then triggers data collection.

What data is collected and imported depends on the data collection settings made in SAP Signavio Process Insights by the application administrator. The source system regularly requests the data collection settings from SAP Signavio Process Insights. Based on the settings, the source system then sends a subset of its data to SAP Signavio Process Insights in predefined intervals. If you change any data in SAP Signavio Process Insights, such as delete the data for a specific performance indicator, these changes don't affect the data in your source system.

The following diagram outlines the data flow between your SAP on-premise source system and SAP Signavio Process Insights for a „direct system connection".

The following diagram outlines the data flow between your SAP on-premise source system and SAP Signavio Process Insights for a „intermediate system connection".

Watch this video to better understand the setup activities. The setup starts at min 2:46.

You are using one of the two transactions in your SAP on-premise source system, to maintain the HTTPS destination of your SAP Signavio Process Insights cloud tenant and set up the outbound mechanism to transfer data for your performance indicators to your cloud tenant. Depending on the ST-PI plug-in version installed in your system, this transactions are available:

• For ST-PI 7.40 SP25 and higher, you use transaction /n/SDF/PINS_SETUP (Set up integration with SAP Signavio Process Insights) Documentation.
• For ST-PI 7.40 SP24 and lower, you use transaction /n/SDF/ALM_SETUP (Set up integration with SAP Cloud ALM) Documentation.

Connection a source system via an intermediate system requires two steps:

1. Connecting your intermediate system with your source system (SM59)
2. Connecting your intermediate system with SAP Signavio Process Insights (/n/SDF/PINS_SETUP or /n/SDF/ALM_SETUP)

   This step is relevant for a direct system connection and an intermediate system connection.

You connect your intermediate system to your source system by creating an RFC connection and making additional configuration settings.

In your intermediate system, create an RFC connection to the source system.

1. Call transaction SM59 (Configuration of RFC Connections).
2. Create an RFC connection with connection type 3 (RF connection to ABAP system). Make sure you use only upper-case letters for the RFC connection name.
3. Add the details for your source system.
4. On the Logon & Security tab, enter the RFC user that has the required authorizations in the source system. You created the user and the need authorization before. 

Add the required entry in the /SDF/DCCCONFIG (Data Collection Controller: configuration) table.

This step is only required if you're using ST-PI 7.40 SP24 or lower in your intermediate system. If you're using ST-PI 7.40 SP25, the entry is automatically created once you connect the intermediate system to SAP Signavio Process Insights.

1. Call transaction SE11 (Generate Table View) and display table /SDF/DCCCONFIG.
2. Select Utilities - Table Contents - Create Entries. Add the following details:

   CALM_ID	(leave blank)
   PARAM_NAME	RFC_"system ID of intermediate system"
   PARAM_VALUE	„name of the RFC connection"

3. Save the entry.

You've now set up the data connection between your intermediate system and your source system. You can use transaction SM59 in the intermediate system to check that the connection is appearing under HTTP Connections to External Server.

If you are using an intermediate system

1. Set up an RFC connection to your source system by using transaction SM59.
2. If you're using ST-PI 7.40 SP24 or lower in your intermediate system you need to enter the connection in table /SDF/DCCCONFIG via transaction SE11.

Check the table below to get an overview of the needed steps in the Setup transactions.

ALM_SETUP	PINS_SETUP
For ST-PI 7.40 SP24 and lower, you use transaction /n/SDF/ALM_SETUP (Set up integration with SAP Cloud ALM)	For ST-PI 7.40 SP25 and higher, you use transaction /n/SDF/PINS_SETUP (Set up integration with SAP Signavio Process Insights)
(1.) Create your Target ALM Destination, which is the HTTPS destination of your SAP Signavio Process Insights cloud tenant, by choosing an existing destination using the F4 help or providing a new destination name and pressing Enter	(1.) Create your Integration by choosing an existing integration using the F4 help or providing a new integration name and pressing Enter
For intermediate system connection only:
You already updated the table /SDF/DCCCONFIG in the steps before when you created the RFC connection between the intermediate system and your source system	(2.) Add the RFC destination to the source system and press Enter. The RFC destination you created when you connected the source system to the intermediate system is now added to the /SDF/DCCCONFIG (Data Collection Controller: configuration) table.
With pasting the key all fields are filled. If you can not copy and paste the key you can also specify the details of your HTTPS destination manually as outlined in the following table: Token Endpoint https://"identifier".authentification."region ID".hana.ondemand.com/oauth/token Client ID Enter the clientid value from the service key. Secret Enter the clientsecret value from the service key. Proxy Host, Port, User, Password If your organization uses a proxy, enter the host name and port number specific to your proxy. If your proxy uses authentication, enter the user name and password specific to your proxy. Root URL Enter your registration target. https://bpi-pia-core-api.cfapps."region ID".hana.ondemand.com
(2.) Choose Create/Update Destination and copy and paste the service key details to specify the details for the HTTPS destination of your SAP Signavio Process Insights cloud tenant destination	(3.) Choose Create/Update Destination and copy and paste the service key details to specify the details for the HTTPS destination of your SAP Signavio Process Insights cloud tenant destination
	(4.) Connect the system to the SAP Signavio Process Insights tenant. If the system is successfully connected, an ID is retrieved and displayed.
(3.) Enter your user and register your system Enter the background user created in your source system to perform the data collection. Choose Register to call your SAP Signavio Process Insights cloud tenant and register the system. If the registration is successful, the system retrieves and displays an LMS ID.	(5.) Enter your background user and start data collection. Enter the background user created in your source system to perform the data collection. To start the data collection, schedule the jobs for collecting data and getting the data collection settings from SAP Signavio Process Insights.
(4.) Choose Activate Use Cases and select "Business Process Monitoring". Selecting this use case triggers several background jobs, two of which are relevant for SAP Signavio Process Insights.	(6.) Select Option "Get Settings Once" and „Test Data Collection": To fetch the data collection settings from SAP Signavio Process Insights once and to test the data collection. Next, you select a performance indicator ID and choose Test Data Collection. If the collection test was successful, a green checkmark is displayed. You can change the options to a regular data load. Documentation

Connecting the intermediate or direct system to SAP Signavio Process Insights sets up the push mechanism to push the data for your performance indicators from your SAP on-premise source system to your cloud tenant.

Create the connection to the SAP Signavio Process Insights Cloud Tenant.

Use the transaction /n/SDF/ALM_SETUP or /n/SDF/PINS_SETUP depending on the release status.

You have now established the connection between SAP Signavio Process Insights and the source system and created the basis for the continuous loading of data.

You've set up the direct connection between your SAP on-premise system and the cloud tenant for SAP Signavio Process Insights. You can use transaction SM59 in your SAP on-premise system to check that the connection is appearing under HTTP Connections to External Server.

Understand which background jobs are triggered in your SAP on-premise system after you've set up the data connection to SAP Signavio Process Insights.

Once you've set up data collection using the SAP Cloud ALM functionality that's included in the ST-PI plug-in, four background jobs are triggered in your SAP on-premise system when you set up a data connection. The "Heartbeat job" and the "Scheduler job" aren't relevant for SAP Signavio Process Insights. Only the following two jobs are relevant:

1. CRBPA:AUTODISCOVERY

   This job runs every hour by default. It requests the latest data collection settings from SAP Signavio Process Insights system. The data collection settings determine for which performance indicators data is to be collected and how often it is collected. The job also requests the descriptions for the master data that's collected with the process performance data for performance indicators. However, these descriptions are requested once every 30 days only.As an answer to the request from the CRBPA:AUTODISCOVERY job, the SAP Signavio Process Insights system sends a list of all performance indicators which are set to Active, together with the predefined data collection frequency for each performance indicator.

2. CRBPA:DC_CONTROLLER

   This job runs every minute. It checks the available work processes, triggers data collection, and sends the data collected to SAP Signavio Process Insights. The CRBPA:DC_CONTROLLER job only collects data for those performance indicators that are on the list the SAP on-premise system received from SAP Signavio Process Insights as a response to the latest request from the CRBPA:AUTODISCOVERY job. It also collects data based on the frequency defined for each performance indicator. To control resource consumption in your connected systems, this job only uses up to one background process and three dialog processes.

If the application administrator for SAP Signavio Process Insights changes the Activation Status for a performance indicator in the SAP Signavio Process Insights application, the changes will only take effect after the settings have been synchronized with your SAP on-premise system. The CRBPA:AUTODISCOVERY job needs to request the latest settings and SAP Signavio Process Insights needs to provide them. We recommend you keep the default job frequency and let it run hourly. Like this, you can avoid a delay between the data collection settings in SAP Signavio Process Insights and these settings taking effect when data is collected from your SAP on-premise system.

Check that both jobs (CRBPA:AUTODISCOVERY and CRBPA:DC_CONTROLLER) are scheduled correctly in your systems (Transaction SM37 Job Overview).