Set Up the SAP Integration Suite Source Subaccount

This step assumes that you’re running the tutorial in an SAP BTP Trial account. If you have an enterprise account, open SAP BTP Cockpit in your enterprise account.

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

   In your global trial account, you have the Central Services subaccount where SAP Cloud Transport Management service runs, if you’ve followed the Get Started with SAP Cloud Transport Management tutorial.

   You will use the default trial subaccount to set up SAP Integration Suite.

   

Set up an SAP Integration Suite trial as described in the tutorial 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 6 of the current tutorial, and you can skip step 7 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 to enable the transport in SAP Integration Suite and to run the test transport.

For the transport scenario, API access to SAP Content Agent is required. To enable API access, create a service instance.

1. In the SAP Integration Suite source subaccount trial, choose Services > Service Marketplace from the navigation on the left (1). In the search field, filter for Content Agent Service (2). On the Content Agent Service tile, select the three dots …, and choose Create (3).

   

2. Select the standard plan from the Plan dropdown menu of Content Agent Service (1). You can leave the values for Runtime Environment and Space unchanged. Enter an Instance Name, for example cpi_dev (2). Choose Create (3).

   

3. On the dialog box, choose View Instance to monitor the creation progress.

   

4. The progress bar indicates that the instance creation takes some time.

   

5. When the instance creation is completed, the instance gets the status 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 SAP Content Agent destination. The destination is required for the communication of SAP Integration Suite with SAP Content Agent.

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 name for the service key (1), here cas-on-cpi-dev, and choose Create (2):

   

3. The service key was created.

   

See also on SAP Help Portal: Create Service Key

The destination to SAP Content Agent defines which SAP Content Agent the SAP Integration Suite communicates with. The destination has the fixed name ContentAssemblyService. In the Destination editor, you can create it using the Service Key option. This approach eliminates the need to manually copy values from the service key to the destination.

1. In the SAP BTP Cockpit of your SAP Integration Suite source subaccount, choose Connectivity > Destinations (1), and choose Create (2).

   

2. In the Create New Destination dialog, choose Service Instance (1), and Create (2).

   

3. In the Choose Service Instance step, all service instances that exist in the subaccount are displayed. Here, the cpi_dev instance is the only one available. Select it (1), and choose Next (2).

   

4. In the Choose Service Key step, you can leave the Choose existing service key option selected. Select the cas-on-cpi-dev service key from the dropdown menu (1), and choose Next (2).

   

5. In the Destination Details step, enter the values for the following fields (1-2), and then scroll down (3):

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

   Field	Value
   Name	ContentAssemblyService
   Description	For example: Destination to SAP Content Agent Service

   

6. The other values relevant for the destination were already taken over from the service key of the instance. Choose Next.

   

7. In the Review step, verify all values of the destination, and choose Create to create it.

   

8. The destination was created. Click anywhere in the row to display the details.

   

9. In the details, choose Check Connection to test the connection.

   

10. The result should display HTTP request (without authentication) to ContentAssemblyService destination succeeded.

    

    This result means that the URL specified in the destination can be reached. However, such a successful check doesn’t guarantee successful deployment. We recommend that you run a test transport after completing the entire configuration of the transport scenario to know whether you actually have all necessary authorizations.

See also on SAP Help Portal: Create SAP Content Agent Service Destination

For the transport scenario, API access to SAP Process Integration Runtime is required. To enable API access, 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 Step 2: Set Up SAP Integration Suite.

   To check this, in the trial subaccount, choose Security > Users from the navigation on the left (1). To display the details of your user, click on it (2), and find the Integration_Provisioner role collection on the Roles Collections tab (3).

   

2. To create an instance for SAP Process Integration Runtime, choose Services > Service Marketplace from the navigation on the left (1). Filter for Process Integration 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-dev (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. This 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-on-cpi-dev (1), leave the other values unchanged, 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.

   

   You’ll need them in the next step when you create the SAP Cloud Integration destination. Unlike the SAP Content Agent destination, you must create the SAP Cloud Integration destination from scratch.

The SAP Cloud Integration destination serves as the endpoint where SAP Content Agent collects the content to be packed into an MTA and exported to SAP Cloud Transport Management service. The destination has the fixed name CloudIntegration.

1. In the SAP Integration Suite source subaccount, choose Connectivity > Destinations (1). The destination to SAP Content Agent is displayed. To create a new one, choose Create (2).

   

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

   

3. In the Destination Configuration window, enter details for the following fields (1), and then scroll down (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 details of the service key of the SAP Process Integration Runtime instance that you created in the previous step, and append /api/1.0/transportmodule/Transport to the URL. For example: https://12345678trial.it-cpitrial00.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://12345678trial.authentication.us10.hana.ondemand.com/oauth/token

   

4. Leave the Use default client trust store checkbox selected, and choose Create.

   

5. The SAP Cloud Integration destination was created.

   

   You can also perform a connection check to verify that the destination URL is reachable. This process is similar to the one described earlier for the SAP Content Agent destination.

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