SAP Cloud Platform Transport Magement (trial)
A few weeks ago SAP released the service to transport the code between environments for the cloud trial environment. This service allows us to define nodes and transport routes between these nodes.
As the previous image illustrates, we will move through 3 concepts:
- Nodes: It will be the definition of each of the environments.
- Transport routes: These will be the paths that our files will follow, for example MTAR, between nodes. That is, we will define that from sub-account A (space A) to sub-account B (space B)
- Destinations: They will help us navigate between environments since we will define the route of our subaccount and space and credentials
If you think about it, it will remind you of the transport system of an ECC, but instead of transport orders we have MTAR files. BUT… These files are more complex than a transport order.
Starting our service “Transportation Management”
We will access our SAP Cloud Foundry account in the Trial environment. We will be at the subaccount level:
Then click on “Activate”
Once finished, we will have our transport service ready. WELCOME DEVOPS TO OUR TRIAL!
Using the application
When we have our service activated we can access the “Go to Application” application.
First problem … we doesn’t access to the application
Do not panic, we lack the roles. The fastest way is to create a new role collection with the cockpit and once created assign it to our user:
Once this role collection has been added to our user. We can now add the roles of the new service:
For this test we will add all the roles to our user
If we enter again (we must go out and log in again) and we can access to the transport management
Creating the destination
At the subaccount level we create a destination like the following
Where the URL will be composed as follows:
- SPACE: Name of the space that we want to transport
As a user we will use the one we use to access our account
Creating our Landscape
We will use the Landscape Wizard option that will help us create a default transport scenario. In this case, we will only use 2 nodes.
We define the two nodes, and in each one we will add the destiantion that we have configured previously (TEST and PRO). As a type of transport we will indicate that we want to transport MTA’s (Multi target application)
Pressing “Next” if everything is well configured will create the transport environment.
Finally we have a summary of what was created:
Visualizing the transport
At this point, although we do not have transports made, we can already visualize our transports:
Clicking on each node, we can see the information related to the transport of that node.
With everything configured we can start the transport.
In this case we will use files of type mtar. (In case that you don’t know how to generate a mtar file You can check this post https://ecastella.com/deconstruccion-de-una-aplicacion-ui5-en-cloud-foundry/ (in spanish))
Once we have our MTAR, we can upload it to the origin node, in our case the node called test.
This will cause our applications to be deployed in the environment that we have configured through the destination. For this we go to the transport queue (to the classics this will sound to the STMS)
Once there we can load our MTAR file using the add button:
This step will start the process of loading the files to the repository, that is, we will queue to transport (it may take a while and it does not give feedback on how the process is). But once finished we will have it ready for transport.
Now we can transport, see the content that we will transport through the clip or see the transport detail.
We will click on “Import All” to start the transport and we will have our project ready.
Once finished we can see the detail by clicking on the magnifying glass.
Our project is already deployed in the “Test” node. We can only move between nodes through transport routes when we need it.
At this point I had to change the names of the nodes since my account expired
Once the transport to the origin node is started and it is validated as correct, the entry necessary to perform the import is created in the following environment. In the following image we see how in DEV there is the transport in running and in Test we already have the option “Initial / repeatable” pointed.
In this case, we go to the test environment (in the previous example it is PRO) and we can import the file loaded and deployed in the previous node.
Very useful blog post. Really helped me understand the service. Parallels drawn to ECC also helped. Thank you.