
Hello everyone,
I’m excited to announce a new feature for SAP Mobile service users that allows you to transport Native/MDK mobile applications across different SAP BTP accounts.
If you're a developer working on Native or MDK mobile apps, this new capability will enable you to create transport requests to move your apps from the source SAP BTP account where you’ve tested and finalized your development changes to other SAP BTP accounts.
For example, if you have an MBK app that's ready to be transported from your development account, as depicted here:
To do this, we would use SAP Content Agent that acts as a local agent on the Cloud Foundry subaccount level offering content management operations. SAP Content Agent provides an easy integration with SAP Cloud Transport Management which provides a central cloud-based transport management solution to handle the propagation of your changes in the cloud. It is the recommended tool to transport all your application-specific content across your SAP BTP landscape. It can work with local services from different environments - like SAP BTP ABAP, Cloud Foundry & Neo.
Consider the following landscape DEV -> TEST -> PROD for moving your changes. Apart from this, you also need a central account form where you can configure and manage the transport routes defining how the changes should be moved.
Getting started to use SAP Content Agent:
Content Agent Admin | Contains the overall administration authorization for all Content Agent tasks. With this access the user can export and import the content and has access to Content Agent Viewer authorization. |
Content Agent Export Operator | Allows Export operation and access to read the operation details. |
Getting started with SAP Cloud Transport Management:
In the SAP BTP subaccount DEV where your source Mobile Service is hosted, create a destination pointing to SAP Cloud Transport Management created using service credentials from the service key of your SAP Cloud Transport Management instance.
Configure a landscape to create a route based on your landscape by creating nodes and destinations pointing to the target SAP BTP account. Create transport nodes as representations of the source and target endpoints of deployment processes in your landscape. Add configuration details as required. Create transport routes to connect transport nodes. For the configuration of simple landscapes, you can optionally use the landscape wizard offered by the service, as depicted here:
You can either import all transport requests in an import queue or selected transport requests only. To execute an import of all transport requests in the import queue, you need the ImportOperator authorization. To execute an import of selected transport requests in the import queue, you need the TransportOperator authorization. For more information, see Security.
You're in the import queue of the transport node where you want to execute imports. Select one of the options, either 'Import All' or 'Import Selected (this is only recommended, if there are no interdependencies to other (earlier) transport requests, as otherwise, out-of-order issues might come up).
Optional: Schedule imports of all transport requests to be executed at regular intervals. For more information, see Schedule Imports.
When the transport request is successfully imported in SAP Cloud Transport Management, the application becomes available in the TEST account for you to validate.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
15 | |
14 | |
13 | |
10 | |
9 | |
9 | |
8 | |
7 | |
7 | |
7 |