Skip to Content
Technical Articles

Introducing SAP Cloud Platform Content Agent: Enhanced Transport Capabilities for SAP Cloud Platform Integration Suite Content

Overview

The SAP Cloud Platform Integration service helps you to connect cloud and on-premise applications with other SAP and non-SAP cloud and on-premise applications. This service has the capability to process messages in real-time scenarios spanning different companies, organizations, or departments within one organization. It is available in both Neo and Cloud Foundry (CF) environments.

Until now, the only way to transport integration content artifacts between integration tenants in the CF environment was to manually export and import them. This changes with the introduction of the SAP Cloud Platform Content Agent. Content Agent service is a Cloud Foundry based utility service. It acts like an agent that allows you to assemble the integration content and also export it to the transport queue using transport solutions like SAP Cloud Platform Transport Management or the Enhanced Change and Transport System (CTS+). This is equivalent to the assembly and export functionality provided by Solution Lifecycle Management Service in the Neo Environment.

Content%20Agent%20Schematic

Content Agent Schematic

In this blog, I will briefly show you how to set up this service along with the SAP Cloud Platform Transport Management option, and use it to transport integration content between your SAP Cloud Platform Integration tenants.

Setup

For the purpose of simplicity, I will take the example of setting up transports between two SAP Cloud Platform Integration tenants, e.g. the development tenant (DEV) and the test tenant (QAS). This is what is currently supported by the service as well. To manage transports in a three tenant landscape, you can use SAP Cloud Platform Transport Management, using different combinations of transport routes.

What you will need(Prerequisites):

  1. Two separate SAP Cloud Platform Integration tenants, attached to separate CF subaccounts. Let’s call them DEV(source) and QAS(target). These subaccounts should also have their respective CF spaces created with adequate resources assigned in their quota plans. For more information on entitlements, see here. For more information on configuring Quota plans for spaces, see here.
  2. Subscription and admin access to the SAP Cloud Platform Transport Management service.
  3. Sample integration content artifact that you can use to transport between the two integration tenants.

Setup Instructions:

  1. Create an instance and Service Key for the Content Agent service in the source CF space,  using the initial setup instructions found here.
  2. Create a destination in your source subaccount for the Content Agent service using the instructions found here in Step 3.
  3. Subscribe to the Cloud Platform Integration (CPI) Service Broker in the source CF space using the instructions here.
  4. Create a destination for the CPI Service Broker using instructions found here in Step 5.
  5. In your source subaccount, create a destination for deployment to your target CF space (QAS).  Let’s call it ‘TD’.
  6. Create a service instance and Service Key for the Transport Management service in your source CF space, using the instructions found here in Steps 6-10.
  7. In the Transport Management UI, create an empty transport node: In the node creation UI, only provide the name( value =DEV), description ( value =DEV), and check the checkbox for ‘Allow upload to node’. Leave everything else as empty (by default) and click ‘ok’. This will act as your source transport node. Instructions here.
  8. In the Transport Management UI, create a second node, called ‘QAS’ to point to your target CF space. Use the destination ‘TD’ created in step 4 for this node.
  9. In the Transport Management UI, using the nodes created in steps 7 & 8, create a Transport route. Instructions here.
  10. In your source subaccount, create a destination for the Transport Management service using the instructions found here. For the value of the additional property ‘sourceSystemId’, use the name of the node created in step 7.
  11. In the CPI source tenant, select the transport mode as ‘Transport Management Service’, using the instructions here.

Testing the Setup:

  1. In your source CPI tenant, go to the content packages view and select any content package by clicking on it.
  2. On the next screen, click the ‘Transport’ button and provide a description for the test transport, and click ‘Transport’ on the pop-up screen.
  3. In case of success, you should get a message such as “Transport Request <xxx> is created in the configured Transport Management Service system”.
  4. In the Transport Management web UI, go to the Import queue of the target node created in Step 8 above, called ‘QAS’. The transport request created in step 3 should be already added to this queue.
  5. Import this transport request into the target node ‘QAS’.
  6. Go to the content packages view of your target CPI tenant. The content package exported from the source CPI tenant in step 3 should have been imported and should be available here.

Important points to note

  1. Please note that step 1-4,6,10,11 need to be performed in your source subaccount or source CPI tenant ( as applicable)  from which you want to export content. For example, if you are exporting content from your Development tenant, you need to perform these steps only in the Development subaccount or Development CPI tenant ( as applicable).
  2. In step 11, Transport Settings will be available for you only if you have the role ‘AuthGroup.Administrator’ assigned to your account. Please assign this role to your user if you do not see the Transport Settings.
  3. The target CF subaccount should also have the requisite entitlements for the CPI service plan. If you’re not sure, please perform Steps 1-5, mentioned under ‘Subscribing to CPI Service Broker’ here.

I hope this article was clear enough to help you set up the Content Agent service, enhancing your transport experience for integration content in the CF environment.

Hope you enjoyed this article. If there are any questions, please let me know in the comments below.

Further information

 

What is SAP Cloud Platform Integration?

For the latest on SAP Cloud Platform Content Agent, please look here.

 

/
Content%20Agent%20Schematic
17 Comments
You must be Logged on to comment or reply to a post.
  • Hi Abhishek Nath,

    finally an automated solution to transport artifacts. This looks interesting.

    What about conflict resolution and dependencies? Are there override mechanisms and does it deploy artifacts? Do I need to cross-check versions in my tenants in case I start using this approach? I believe it would be a good practice to switch off editing of integration artifacts in stages other than DEV to avoid problems?

    Thanks for sharing.

    KR

    Martin

  • Hi Martin,

     

    Thanks for your feedback. Very valid points. The deployment will always be taken care of by the deploy service on CF. For the rest, we are looking to enhance this further in future versions.

     

    Thanks

    Abhi

  • Dear Abhishek,

    first of all thank you very much for this valuable blog entry.

    I am getting error message “Error in the http client” when clicking the check configuration button in the SCPI transport settings section.

    I believe the reason could be regarding the url in step 4 “setup instructions”. Can you please confirm that the url for CloudIntegration is the value of the CPI service broker?

    Or do I need add the “/api/1.0/transportmodule/Transport” to CPI Service Broker URL as well?

     

    Thank you in advance,

    Yasin

     

    • Hi Yasin,

       

      Thanks for taking the time to setup the service.

      You are right. Indeed, the value of the URL comes from the service key of the CPI service broker created in the previous step. As mentioned in the documentation the format is as below:

      URL Provide the URL of the system that you want a create a destination to.

      The format is: <oauth → url>/api/1.0/transportmodule/Transport

      Thanks

      Abhi

  • Hi Abhishek

    I am getting below error while doing a check configuration from CPI Settings –> Transport page

     

    {
    “results”:[{
    “status”:”ERROR”,”description”:”Configuration check for CloudIntegration”,”error”: {
    “errorCode”:”1042″,”parameters”: {
    “destinationName”:”CloudIntegration”
    }}}, {
    “status”:”SUCCESS”,”description”:”Configuration check for TransportManagementService”
    }]}

     

    Also , Destination CloudIntegration  : is throwing below error

    Failure reason: “An error of type SSLHandshake occurred during check connection!”

    I don’t understand why SSL Handshake error is coming. Please let me know if you have encountered this error. 

     

    Thanks 🙂

    • Hi Prachetas,

       

      Thanks for reaching out.

      It seems that your destination is not properly configured. You need to check all the values you have configured against the values from the CPI service broker and let me know.

       

      Thanks

      Abhi

  • Hi Abhishek

     

    Please have a look

     

    I have  created service instance Process Integration Runtime with role :

    WorkspacePackagesTransport

     

    Destination details :

     

    Name : CloudIntegration

    Type : HTTP

    url :  url/api/1.0/transportmodule/Transport

    Proxy : Internet

    Authentication : OAuth2ClientCredentials

    Client ID : from service key

    Client Secret: from service key

    Token Service URL: cpi url/oauth/token

     

    Destination seems correct ?

     

  • /
    • Hi Tim,

      Please check the configuration for below destinations once again.

      1. CloudIntegration and
      2. TransportManagementService  Or ChangeManagementSystem depending on which service you are using.

      You can verify the same in CPI Settings –> Transport–>Check Configuration

      If result for both the destination is successful then you can transport package.

       

      Regards,

      Nikhil

       

  • Hi,

    I am getting below error while deployment of TR in TMS.

    Exception during start of deployment for deploy type ‘SLP_CTS’: Error during deployment initialization: Not supported content type “text/html”

    I am using content type Multi-Target Application.

    Please let me know if anyone know cause for this error.

    Regards,

    Nikhil