Welcome back. In this video, we are going to understand about how to actually register an account with any point platform and how to use any point runtime manager for deploying applications onto a mule runtime on standalone. Right. So let's go and get started. So firstly, you need to have an account with any point platform. So I'll just go to any point that you will sub.com and I will sign up for a new account.

So I'll give some details. Register I'll give you the name as a civil. thousand 19. Last Word and then let me check. Okay, enter first and last name. Okay.

I'll give my full name. Now. It should create an account. The user name is Sai pro 2019. So I have an account in any point platform. I'll actually walk through various things on any point platform letter, but on the left menu here, I will right now directly go to runtime manager.

This As a manager for managing your mule runtimes so first time whenever you visit runtime manager, it'll ask you to select which environment I will select something called a sandbox environment. Okay. Now, here, there is a tab called a service on the left side. So here there are no servers registered. Now what I want is I want my standalone web server which is running here to get registered. Firstly, I stopped my standalone server by pressing Ctrl C, it's already running and press Ctrl C. It returns.

Now, what I will do is just for safety, I will delete all the apps running here. I will delete it, I will deploy it again and also I will delete the data Little folder which was containing alias. Earlier runtime specific information I want to refresh. So I deleted.mil folder also. Now, what I have to do is if I want to register the standalone server with runtime manager, what all I have to do is to click on Add server. If I click on Add server it is asking me to execute this command.

I'll copy this command. To add a server into this environment. Go to slash bin directory and execute the following command. I'll have to go to the bin directory. So let me go to bin directory I'll open CMD Yeah, I'm in the bin directory. So I'll try to execute that command.

But since mine is a Windows Windows, it is I just removed the dot slash and the file is exactly AMC setup dot bat. Either AMC setup dot bat available here in the vendor tree. Yes, I'm executing game setup dot bat, hyphen, some randomly generated identifier. And lastly it is server name. So I want to name my server as Siva that server my name. So if I execute this command, let us see what is going to happen Hmm, so it's unpacking some libraries.

Let's wait. Yep. so here we can see the message mule Agent unpacker. Actually, if I go to the top, I can see that mule agent is getting installed. Right for this mule home. So basically by executing a MC setup dot bat, a MC stands for any point Management Center.

So by actually In a PC setup not bad actually it is installing new agent onto my Enterprise Server. So, there are some jars it got extracted and installed. And finally, if you see at the end, what is it saying communication between any point Management Center and mule agent is authorized by two way SSL verification. So, mule agent got started right now, mule agent did a handshake with something called us any point Management Center and the handshake is authorized before two way SSL. So, they have done handset basically I can say whenever they are doing an SSL handshake they will exchange certificates, right. So, actually I want you to observe that here in standalone runtime In standalone runtime, inside cons there is a file called as mule dash agent dot j Ks which got generated mule agent yml file.

So, this first got generated right now if you can see the timestamp is 1233 right now, the time on my machine is 1235 that just got generated softer first successful handshake mule agent dot j k s j k stands for Java keystore contains certificate information, these two files are generated and mule agent squats successfully installed. Now, if you see the endpoint Management Center if I close this you can see that my service river is listed here. So, actually what when I executed this command, the mule agent started and it communicated with any point Management Center And then and then it has done a hand shake, they have exchanged their certificates. That means now my mule runtime knows about my SQL Server, then this is just saying created, it's not running as it. So what I'll do is I'll go to bin directory and then execute mule dot bat right now, the mule server starts when the mule server is starting right now, the mule agent also starts inside the same JVM mule agent will open communication with the runtime manager and send it status.

So once it starts, I should see that this turns to green and it should be running. Yep, see now it's saying connected. That means actually what the mule agent which is running on my mission, started communicating with the runtime manager and he's sending the heartbeat information Okay, now it is saying running. The version is four dot one dot five. So the runtime manager They're registered my server and my server is running. Now if I want to deploy my application in this server, what I will do is I'll go to applications, click on deploy application.

Choose the file, and select Upload. on my desktop it is. This is mule basic start. So what the target, if I select here there is server server. I'll give a name to my deployment, my first deployment. So what are the target right now?

CI server. That's all. Now the application will be deployed on to standalone runtime. We just have to wait here for some time. And here to show you that the mule server stuck at the application appear you can see the status starting up here also you can see my first deployment or jar is received and take some time. Yep.

My first deployment it started. Now if you see here, it started. Now let me test locally aids right once less code. I should get 200 response. Yep, it is working now. So if you want to deploy it again, you can select this here.

And you can select, stop or restart or delete application. You can click on Manage application and if you want to arrange in the future You can choose a file, and then delete it, and then redeploy it if you want. Okay. So that's how I have introduced you to deployments using runtime manager. Don't worry, we will work more on runtime manager when I show you cloud hub deployments. As of now, I didn't introduce you to cloud hub, we'll see it.

Okay. So there are two ways to deploy an application manually by copying your jar file under apps folder, or now registering your server and deploying it through any point runtime manager. All right. Now, what I can do is I can, I can actually start one more server also on my local machine by clicking on Add server. Again. If I execute this command, I'll be able to register a number of servers on runtime manager through runtime manager To be able to manage a number of service.

Okay, we'll do one thing. Now what I'll do is I'll just rename this to noon around time for dot one dot five, just for now, a runtime I gave us for linguistic. Okay, let's crack to this another folder, simply extracting this to another folder. Now, if I want to run another instance of node server on my same mission, I would just have to go here CMD I'm in this folder. Now if I want to register another server, I just have to Copy this simple again, I'll click on Add server one more server, copy this and then paste it I'll go to server server two. And since mine is a Windows machine interfacing dot slash empty setup, I use AMC setup dot bat.

So it's again installing agent in the in the existing folder. And again, one more agent will communicate with runtime manager. Done. Now if you see in runtime manager, there are two servers one server server and server server two. And this is in running state this got created. I can of course go here and say mule dot bat.

The second server also Get started on my same mission. Normally in production, why do we start two servers on same machine. But just here I wanted to show a demo, we can run. And we can register a number of servers on runtime manager and we can deploy applications to any of this service, which so now you understand what runtime manager deployments. We'll see you next video. And before that, you have an exercise right now, before we proceed to the next video, please follow this video start servers and registered them with runtime manager as I have shown in the video.

There is no document provided to you for this but just see the video and follow the steps as it is. See you next week.