Name: SAP BTP DevOps: SAP Cloud Transport Management Pt 2
Uploaded: 2023-9-6
Duration: 518 s

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div>In this video tutorial, Philip Mugglestone continues to cover SAP Cloud Transport Management service. SAP BTP destinations are created before configuring the transport landscape with nodes and routes. Finally Philip triggers a CI/CD build job that will upload the Multitarget Application (MTA) archive to the QA node.<br><br>0:00 - Introduction<br>1:00 - Documentation<br>2:00 - Create new Destination; clone for GA and PROD<br>3:50 - SAP Cloud Transport Management, Landscape visualization: Create QA and PROD node with route<br>5:50 - SAP Business Application Studio: Update config.yml <br>7:00 - Stage, commit and push<br><br>Please be aware that the structure in SAP Help Portal has been updated since the time of recording. For example, the documentation for creating a destination for MTA deployment on Cloud Foundry can now be found at: <a href="https://help.sap.com/docs/cloud-transport-management/sap-cloud-transport-management/creating-destinations-for-mta-deployment-on-cloud-foundry" rel="nofollow noopener noreferrer" target="_blank">https://help.sap.com/docs/cloud-transport-management/sap-cloud-transport-management/creating-destina...</a><br><br>DevOps with SAP BTP: <a href="https://help.sap.com/viewer/product/DEVOPS_OVERVIEW" rel="nofollow noopener noreferrer" target="_blank">https://help.sap.com/viewer/product/DEVOPS_OVERVIEW</a><br><br>Please note:<br>                     This video was originally published on the SAP HANA Academy YouTube Channel                      and therefore may contain references to SAP HANA Academy and YouTube.                      The tech world is always evolving and the SAP HANA Academy YouTube channel                      is set to close on December 31, 2023.                      At that time, references will no longer be valid                      and will gradually be removed when the videos are updated.<br>Also, this video includes automatically generated captions and therefore might misrepresent the spoken content or display incorrect product names<br><br></div></div></div>

SAP BTP DevOps: SAP Cloud Transport Management Pt 2

Welcome to this series of hands-on tutorials from the SAP HANA Academy. I'm Philip Muggleston. In this series, we're covering DevOps for SAP Business Technology Platform Extension Applications. In this video, we're going to continue our configuration for SAP Cloud Transportation Management. I hope you've seen the previous Part 1, where we looked at how we do some of the initial setup. We created our sub-accounts. Today, we're going to talk about how to set up destinations in Cloud Transportation Management in our main sub-account. Where we're actually deploying Cloud Transportation Management that will allow us to access these different sub-accounts we're going to be deploying to what will be our nodes in Cloud Transportation Management. To understand that a bit more, what we can do is go to the Help Portal. We've seen previously how we can get the doc for cloud transportation management. Then we'll go to the admin section, so this section here for admin, and then choose the option which is configuring the landscape, and then create transportation destinations. Then we need to go to step five, which is where we're going to be working with the Cloud Foundry and we're going to be deploying a multi-target application. So, it's the MTA deployment on Cloud Foundry. Now, what you'll see here, there is actually a service URL and that's something that we're going to need. So, this is where you get the master kind of version of it. Basically, it's going to be how we actually connect to our org and space for QA and prod. So, I'm going to maybe copy this one because it's looking pretty close. It's already got EU 10, which happens to be the same thing I'm using. So, I'm going to copy that. We're going to use it in a moment. So, let's go to the cockpit for Business Technology Platform for the sub-account where you've actually subscribed to Cloud Transportation Management, which in my case is a dev one. I'm going to go to the connectivity section and choose destinations. I'm going to create a new destination, and I'm going to give it a name, doesn't matter what, I'm going to call it TMS, for example, QA. I'm going to put in a URL, and that's where I paste in that value, but I do need to just change that to make sure it's the org that I specify, which in our case is DPEQA, and then the space which we called QA. Remember, we've configured that in previous video tutorials. In your case, you put in what values make sense to you. And then in terms of authentication, we're not just going to get free access to it, it's secured. So we're going to need to specify basic auth, and then we're going to use our technical user. Notice it tells you don't put personal credentials in there. Make sure you have a technical user for doing this. That's what we've done in previous video tutorials, so we've got our technical user, so I'm going to paste the user and also the password value in there and hit save. Once you've done that, you should be able to do Check Connection, and we can see it returns 200 OK. Now we need to do the same for Prod. So the easy way to do that is just to clone the one we've already got, and then just change what's different. So it's going to be TMS Prod. In this case, the URL will change because it needs to be DPE Prod as the Cloud Foundry org, and then Prod as the Cloud Foundry space. Everything else is the same. Today I'm going to show you how to change the password in the same region data center. We'll go to basic authentication, again with the same technical user. Because we changed the URL, it's going to make us change the password. Make sure we put the password in again. So let's paste that value in for the password and hit save. And again, once that's done we can check connection. And should return 200 OK. So now we're ready to go ahead and build out our landscape using the cloud transportation application, the one we subscribe to. So what we're going to do is add some nodes first, and then we'll add the connections between the routes effectively. So let's use the plus sign to create a node. We'll create one for QA. So we can call this one QA, whatever you want. We're going to allow upload of a archive file that we'll use to deploy. So we're going to upload to this node. And then we need to say, what's the content type? For that, it's going to be a multi target application. That's what will be uploaded. And then we need to specify destination. Well, we just created some. So for QA, we're going to use the destination of QA so that when it imports, it knows where to import this multi target application, effectively where to deploy it to. And then you've got the deployment strategy. We're going to stick with default. Let's hit OK. We've created our first node. We're going to do basically the same thing now but for Prod. Prod's a little different. We're not going to allow upload to it directly because it's production. We're going to make sure we've gone through the QA first. So we're going to have actually a route. In terms of the content type, it will be the same. Today we're going to do the same multi-target application. The destination this time will be TMS Prod, that's the one we set up. And I've chosen for production, we're going to use a blue-green deployment strategy, which means we can minimize application downtime whenever we do an update. So for that one, we just select blue-green and hit OK. Now once we've done that, we need to create a route or route between the two. So we can now click this option here, create a route, give it a name. I'll call it QA2 Prod. Choose a source node, that will be QA. Choose a target node, that will be Prod in our case. Hit OK. And we can now visually see that we've got a route defined. Now it's completely up to you what nodes you want to have, how you configure them, what you connect to, what routes you want. This is just one example that fits what we saw in the initial introduction of this series, where we looked at an overall landscape. So we're basically ready to go, we're working this. What we want is we want this multi-target archive application to be sent to the QA node. In the last lecture, I spoke about three more things that we need to desired using Cloud Transportation Management System, CICD Service, and if you look further down, we've seen the steps, one of them is called TMS Upload, and here we can specify what the node name will be and what the ID of the credentials will be in our CICD system. So again, remember we called it TMS-SK. If you called it something different here, when you actually set up your credentials, then that's the name you need to make sure you specify here, actually in your configuration for the project. And the node name, we called it QA, that relates directly to this name of this node we've created here. So we're looking good. So what we need to do is actually make that happen. And so for that, well, we've made a change, we need to basically push to GitHub and it will then trigger with the webhook, the CICD to run and that will then eventually upload to Cloud Transportation Management. So let's go ahead and do it. So, we're going to stage all of our changes and then we'll create a message for our commit and commit it. And once we've committed, we can then go ahead and push it. And if we go to our CI CD and then have a look at the jobs, we've got our app job. Notice that based on this commit, a new job has been triggered. It's job number two. Look at the commit ID. You see dd36a2f. If we go to GitHub and we look at, we'll just refresh it. If you look, that is basically the ID of the latest push that we did to GitHub. So, we can actually see exactly which push it was that's now triggered this build. So, everything corresponds. And if we click on that, we actually see the full commit ID. That's something we're going to be able to reference in the future within the transportation management system to make sure we know which commit it is that we're actually working with. So, we now basically need just to sit back and wait for the CI CD process to complete. Now, we can click the build to see the details of how it's running. It's going to take a little while. So, why don't you meet me in the next video tutorial where we'll finish off. So, hopefully we'll be able to see the results and then we can go to the next step in the process. You can find more video tutorials on our YouTube channel. If you'd like to be informed as soon as new video tutorials are published, then please subscribe. Thanks for watching.