 Hello, welcome back. In the last video, we learned how to install a CDK with the JPOS Developer Studio using the Red Hat Development Suite. Now we'll see how to deploy an application into this environment. On the welcome page in Red Hat Central, you'll see that there is an OpenShift application. Click on that. This will connect by default to the container development environment that we just installed. So if you look at the connection parameters, these are already set for you. So this is pointing to the master's URL for the CDK that got just installed. And the credentials are also set. The protocol is set to basic. All this configuration information for CDK is stored in .miniShift folder under your user home. So if you go to your user home, find a .miniShift folder, it's a hidden folder. Get inside, you'll find a file with the name CDK and that would have the setting that are used by this environment. So let's move forward. And now it connects to the OpenShift environment. Remember that in the last video, we saw that there was a project created there with the name MyProject. You can use the same project to deploy or you can create a new project by clicking this button. Now let's deploy a JPOS EAP application. So I'll filter by choosing EAP here. And let's choose JPOS EAP 6.4 as the version of the app server. In order to deploy an application, I'm now using an example. The code is on the GitHub and I'm just providing the URL for my code. I'm removing the rest of the stuff. There is no context directory or a GitHub reference. I'll leave the rest of the things as default. We are going to run one replica. If you have used OpenShift from a web console, all the parameters that you would try to set in the advanced options are all here. Just go with the defaults and use the default route and click Next and Finish. This will create all the objects that the OC new app would create. It is creating an image stream, a service, a build configuration, deployment configuration and a route. Let's give it a minute for the app to be created. At this point to clone the Git repository to your local machine. I'll leave it as clone to the default location which is slash user slash v slash git. I'll just leave it there and say Finish. It will also clone the source code to my local workstation. Right now it's doing a Git clone. Git clone is now complete. We have the application project here in the Project Explorer. In the OpenShift Explorer tab, you'll also see that there is a connection to OpenShift Master. I'm expanding that. Here is that project with the name MyProject. Inside that there is this service, the name. I left it as the default names and there is a build running. You can right click on this. Look at the build logs by and it shows me that it's clone the source code and it is initiating the S2I build. So we'll give it a minute for the build to be complete and we'll come back. The build is in progress. You can see that the main dependencies are being downloaded. The build is now complete. You can see that it created a war file, created a container out of it, pushed it into the registry and pushes successful. Now let's look at what's happening with the container. The pod is now running. So we can also look at the pod logs. So these are all JBoss EEP logs root.war is deployed and the application should now be running. Let's go back to the OpenShift Explorer. Click on this service and show in the browser. This is our running application. Now let's see how to make changes to this application and test it on the fly. Let's right click on this service. You can see that there is a server adapter here. Let's select that. Now we have to make sure that the pod where the application is running and the project Eclipse project where the code is on the local machine are in sync. So in order to do that, we'll be setting up the server adapter. The repository on my local machine is matching with what is listed here and clicking on finish. Now you'll see that in the server adapters, there is a new server adapter that got created and it is syncing the contents between the pod and this project. So the logs that you see here is a sync up between the pod and the project. So if you again go back to the server adapters, you can see that there is a new server adapter that got created. We'll make a small change to this app. Welcome to OpenShift container platform. I'll change this to welcome to JBDS integration with OpenShift. I'll save these changes and see what happens here. You can see that there are logs here that say that, hey, there is a root dot war deployed and a root dot war got do deploy got created and the index dot XHTML, which is the file that I changed, it got synced with the pod. So it has sent 54 bytes of data from my workstation where I made the code change into the pod which is running on OpenShift. There is a sync between the local repository and the pod. So let's go back and see what happened here. The pod is still running. I'll run this application again in browser and hey, you see the changes here. So this is a Java application. I'm making code changes and as soon as I save, the code changes are synced with the pod and looking at the pod logs, the logs show that the application got just redeployed. It shows the replacement of the war file. So in this video, we have learned how to deploy an application by using an IDE into the local OpenShift cluster running on CDK and how to make changes locally, not commit to a Git repo yet, but still test the code changes immediately by just saving, right? There is no compilation. There is no building. It's all done automatically for you by Javas Developer Studio and it is synced with the pod. I hope you enjoyed this video. Hang on. There is more to show in the next video.