Set Up the SAP Integration Suite Target Subaccount

This step assumes that you’re running the tutorial in an SAP BTP Trial target account. If you have an enterprise account, open SAP BTP Cockpit of the enterprise account that you want to use as the target account.

1. You or your colleague: To access the SAP BTP Cockpit of the target BTP Trial, go to the SAP BTP Trial landing page and choose Go To Your Trial Account. (The name of the button may vary.)

   The default trial subaccount can be used as the SAP Integration Suite target subaccount.

   

Set up SAP Integration Suite in the trial subaccount of the target SAP BTP account the same way as you’ve done in the course of the previous tutorial Set Up the SAP Integration Suite Source Subaccount. Proceed as described in Set Up Integration Suite Trial.

Keep these points in mind:

• Subscribe to SAP Integration Suite in the trial subaccount.

• Make sure that you assign the Integration_Provisioner role to your user as mentioned in Step 2: Subscribe to the service of that tutorial.

• Make sure you activate the capabilities of SAP Integration Suite.

• If you use the Enable Integration Suite booster to assign roles and create service instances for SAP Process Integration Runtime, you’ll only need to update the api instance in step 3 of the current tutorial, and you can skip step 4 since the service key was automatically created.

• If you don’t use the Enable Integration Suite booster to assign roles and create service instances, additionally assign the PI_Read_Only, PI_Integration_Developer, and PI_Administrator role collections to your user. You’ll need them towards the end of the tutorial group when you run the test transport.

For the transport scenario, API access to SAP Process Integration Runtime is required also on the target subaccount. First create a service instance.

Creating a new instance is only required, if you haven’t used the Enable Integration Suite booster to assign roles and create service instances. If you’ve used the booster, update the api instance that was created as part of the booster with the WorkspacePackagesTransport, WorkspacePackagesRead, and WorkspacePackagesEdit roles.

1. Make sure your user has the Integration_Provisioner role collection assigned as mentioned in the previous step.

   To check this, choose Security > Users from the navigation on the left. To display the details of your user, click on it, and find the Integration_Provisioner role collection.

2. To create an instance for SAP Process Integration Runtime, choose Services > Service Marketplace (1), and filter for Process Integration Runtime in the search field (2). On the SAP Process Integration Runtime tile, select the three dots …, and choose Create (3).

   

3. Select the api plan from the Plan dropdown menu of the SAP Process Integration Runtime service (1). You can leave the values for Runtime Environment and Space unchanged. Enter an Instance Name, for example pi-prod (2), and choose Next (3).

   

4. The following roles are required for the instance: WorkspacePackagesTransport, WorkspacePackagesRead, and WorkspacePackagesEdit. Select them from the Roles dropdown menu (1), and choose Create (2).

   

5. The SAP Process Integration Runtime instance was created.

   

See also on SAP Help Portal: Creating Service Instance and Service Key for Inbound Authentication

The details of the service key of the SAP Process Integration Runtime instance are required for the configuration of the SAP Cloud Integration destination. The destination is required for the communication of SAP Content Agent with SAP Process Integration Runtime.

If you’ve used the Enable Integration Suite booster to assign roles and create service instances, you can skip this step. A service key for the SAP Process Integration Runtime instance was already created.

1. To create a service key for the SAP Process Integration Runtime instance, in the service instance row, select the three dots …, and choose Create Service Key.

   

2. Enter a name for the service key, here PI-RT_SK1 (1), and choose Create (2).

   

3. The service key was created. Select the three dots … in the service key row, and choose View.

   

4. The service key looks as follows. Leave the service key open so that you copy the required values in the next step, or note down the values of url, clientid, clientsecret, and tokenurl.

   

See also on SAP Help Portal: Creating Service Instance and Service Key for Inbound Authentication

The SAP Cloud Integration destination serves as the endpoint where SAP Content Agent imports the integration content. The destination has the fixed name CloudIntegration. You need the values of the service key from the SAP Process Integration Runtime instance created in the target account during the previous step.

1. Choose Connectivity > Destinations (1). To create a new destination, and choose Create (2).

   

2. In the Create New Destination dialog, choose From Scratch (1), and Create (2).

   

3. In the Create Destination window, enter details for the following fields (1), and choose Create (2):

   Keep the values of fields not mentioned in the table unchanged.

   Field	Value
   Name	CloudIntegration
   Description	For example: Destination to SAP Cloud Integration
   URL	Enter the value of the url from the service key details and append /api/1.0/transportmodule/Transport to the URL. For example: https://87654321trial.it-cpitrial06.cfapps.us10-001.hana.ondemand.com/api/1.0/transportmodule/Transport
   Authentication	Select OAuth2ClientCredentials.
   Client ID	Enter the value of clientid from the service key details.
   Client Secret	Enter the value of the clientsecret from the service key details.
   Token Service URL	Enter the value of tokenurl from the service key details. For example: https://87654321trial.authentication.us10.hana.ondemand.com/oauth/token

   

4. The destination was created.

   

   You can test the destination by displaying its details, and choosing Check Connection. However, a successful check result doesn’t guarantee successful deployment. We recommend that you run a test transport after completing the entire configuration of the transport scenario. This helps ensure that you’ve correctly completed all configuration tasks and have all necessary authorizations.

See also on SAP Help Portal: Create SAP Cloud Integration Destination

For the transport scenario, API access to SAP Content Agent is required also on the target subaccount. First create a service instance.

1. Choose Services > Service Marketplace (1), and filter for Content Agent Service (2). On the Content Agent Service tile, select the three dots …, and choose Create (3).

   

2. Select the application instance plan (1). You can leave the values for Runtime Environment and Space unchanged. Enter an instance name, for example CAS-deploy (2), and choose Next (3).

   

3. Select the Import role (1), and choose Create (2).

   

   The SAP Content Agent instance CAS-deploy was created.

   

See also on SAP Help Portal: Create Instance

The details of the service key of the SAP Content Agent instance are required for the configuration of the destination to SAP Content Agent in the target subaccount that you’ll configure in the SAP BTP source account as part of the next tutorial Create a Transport Destination and Configure the SAP Integration Suite Transport Landscape.

1. To create a service key for the SAP Content Agent instance, in the service instance row, select the three dots …, and choose Create Service Key.

   

2. Enter a Service Key Name, here CAS-deploy-SK (1), and choose Create (2).

   

3. The service key was created. Select the three dots … in the service key row, and choose View.

   

   The credentials are displayed. Leave the service key open so that you copy the required values in the next tutorial, or note down the values of url, as well as clientid, clientsecret, and url from the uaa section.

   

   You’ll need them in the next tutorial Create a Transport Destination and Configure the SAP Integration Suite Transport Landscape to create the transport destination (called CAS_on_Target) in the central administrative subaccount that points to SAP Content Agent in the target subaccount.

See also on SAP Help Portal: Create Service Key