 Hi everybody, my name is Daniel Loh. In this demo, I'm going to showcase how to use SSH credentials to connect to remote the SSH repository using JVS-EAP740 better. Let's get started. In order to save my demo time, I actually already installed JVS-EAP740 better. As you see, there are a bunch of configurations on the standalone directory. For example, standalone-fullHA, standalone-HA, and standalone.hml. So we're going to start JVS-EAP instance using default standalone.xml. And once it started, you can find the right version. As you see, EAP740.better, version EAP just running on my local machine. When you go to admin console, you can find some kind of this message, because we don't have any management role or credential at the very beginning time. If you want to access the admin console, you have to create the management role and credential as well. We're going to do that actually a little bit later. I'm going to stop the running EAP. So next step, I'm going to run EAP once again with the SSH credential. To do that, I need to generate the key pair store and also a credential store. So luckily, JVS-EAP provides an electronic tool which allows us to create the credential store. For example, here is the credential name is cs-underscore, example cs-file, which is a credential store, which allows store key pair with a specific algorithm, for example, RSA algorithm. So let's try to create a new key pair to store in that credential store. So we're going to use an electron tool once again with the algorithm RHS and the specific size. And once we create the key pair, we can find our public key using an electron tool here. So just copy the public key and go to your developer project, for example, in my get report and go to setting. And then you can find the SHN GPG key menu and create a new SS key. You can just paste that your public key. Just create that from electron script tool. But I already created that for the demo ahead of time. So go back to our console. And the next step, we're going to create the wildfire compilation, which we need to refer that key pair we just created and store in greenage store. So here is the old default compilation. I just copied from cheat sheet. The one thing you have to do that, we need to actually use absolute or relative path, specifically under b-injectory. So once we create the wildfire compilation file, here is my compilation repository, which I wanted to share with my developer team. As you see, there was the sample text file, like a test.txt file. And also, I already printed my one of the credentials as a management property. So I'm going to use this compilation repository using SSS Git repository, based on SSS credential. So I just copied a ripple URL and the Git branch is main. And also, I'm going to add one more parameter, Git auth, with the wildfire configuration XML, we just created that. So you can actually use the Py protocol, but also the URL protocol as well. So when you run this command line to execute this EAP standard load server, you can find your old compilation will be pulling down from Git repository rather than use your local directory. So your EAP is running on well. And then let's go up to the logs. And then we can find that actually here. All right. Okay, here we go. So the compilation history managed through the Git, which means your compilation override from your Git compilation. So let's try to open another terminal window and try to go to a standalone compilation. As you see, the text file, just pulling down and just take a look at that inside the file. And then that's SSS authentication we just saw in my Git repository. Okay, pretty cool. And then when you go to admin console once again, and now we just log in based on my credential. This is one of some browser caching, but the Daniel low, I just added that credential on my management wall as you saw in my Git repository. All right. So one of the beauty of Jbos EAP 7.4, you can actually make a snapshot and also push that change to Git repository directly without using Git command line. So as you see, the there's no snapshot at this moment and try to make some change here, a compilation directory. So I just tried to remove standalone full hma.xml because I don't need to use that we in my developer team. And then I just deleted it and then go back to Jbos CLI terminal and try to take a snapshot with the name. Let's say the snapshot one and then comment, remove configuration. So you can actually take a multiple snapshot as well. Okay, I just created a new snapshot and the list the snapshot and we have a find the one snapshot here. If you try to make a multiple snapshot, you can you can actually publish that. So publish configuration with the location. You can have you can print the already Git repository with authenticate the SSH credential. We just outcome success here. And then go back to our configuration Git repository. You can find that the limit configuration, there's no ha compilation at this moment. Okay, so next step. So let's say we have a multiple developer on my team. And then I want to share this compilation with the different the other developers. So in order to do that, we're going to use the cloud name environment like a core ready workspace. Here's my sample application. As you see here, the dev file already defined in the git repository. When you run the core ready workspace with the parameter, give a proprietary project name and automatically spin up your project. So click on developer sandbox. This is hopefully for developer ready to provide. So you can actually run developer sandbox and go to core ready workspace from open container dev UI, but you can actually spin up the core ready workspace directly with your specific git repository. So in the meantime, you can find the core ready workspace. If found your dev file from your git repository, but also there is a bunch of stuff. In the meantime, let's try to go to dev file, take a look at that. So here is the project name, kitchen sink, one of the quick start example on the javas EAP. You can actually report to git repository for resources directly, or you can have a G file as to your source. And I'm going to use the Docker image component to run javas EAP 74 beta and the here is just some environmental value, such as maybe an option and Java option. And the one thing you have to do that you need to export and point to access application presentation layer, but also you need to pass down some specific javas option. For example, here, the git report, git branch, git also just like we did on my local machine. But one different thing is we're going to use the HTTPS protocol URI because previously we just file protocol, but you can actually use URI command line. And you can also add some command. This is one of the beauty of dev file. So we're going to take a look at that once core ready workspace is started. Okay, just call the ready workspace started. The left side in Explorer navigator, you can find exactly what kind of project from pull down from git repository. So here is a Java project just like your entire project application. So when you go a little bit drill down your project, there are a controller and a data and a model rest for your application, presentation layer and the services and you really just like the normal enterprise Java application architecture. And then when you open your tool and they just you can find the open a new terminal here. So first of all, just to make sure this application and the EAP already running inside the core ready workspace part. So take a look at that event valuable. And then with the javas searching and the javas EAP version here 740 dot beta. And then go to standalone computation directory. Just to make sure they share the combination already pull down as you see the test dot text file. And there's no standalone full hma xml. So now we have a same developer team, but one is from developer in local machine, the other one develop on cloud based ID tool. This is a more clouded way. And then let's try to build this application. Let's say I just create some application and bug fix, et cetera. And then before that, when you go to EAP endpoint, as you see the this is your admin console landing page, but unfortunately the javas EAP admin console is not available in a container platform, which is a developer sandbox running an open shift as well. So try to build this application. So let's try to hot deploy. This is one of the beauty of the javas EAP feature. So your EAP is actually running. But at a time, we can deploy the actual application. The first of all, this is a Maven project. That's why we build a Maven packaging. In the meantime, when you go back to open to developer console on developers and boss, you can find the EAP low, just like the EAP 740 beta is running. Okay, so our application build just complete. And I go to terminal window and try to make sure your wall file is deployed into your EAP. So as you see, root wall file is just deployed. And just go to endpoint here. So we have a new application just deployed in the meantime as part of the hot deploy behavior. So try to add a new name just for fun. So my name is Daniel and my email address and just my fake phone number and the register here. So new data is just stored and you click on REST for API. You can find the data based on JSON format and you can find all data here. Okay, so one thing maybe you can go to code radio space and dev file configuration. You can find all dev file detail just like we saw in the proprietary application. Thank you for watching. Have a good rest of the day.