Let’s get started with building and deploying your application to the fuselab project.

We will be using OpenShift's Source 2 Image capability, also referred to as S2I . The OpenShift S2I tool injects application source code into a container image and the final product is a new and ready-to-run container image that incorporates the builder image and built source code.

To enable this S2I capability, you need to collect the following information and configure it in Red Hat Developer Studio.

Right click on your project in the sidebar menu, select Run As > Run Configuration

On the pop up sidebar menu under Maven Build, click on "Deploy projectname on OpenShift" to open the project's default run configuration. projectname will be replaced by your project name. Leave all of the default settings on the Main tab.

Select the JRE tab to access the VM arguments.

• Find the line that reads -Dkubernetes.namespace=test, and replace test with the project name you supplied when the project was created.

  -Dkubernetes.namespace=fuselab

• On the line that reads -Dkubernetes.master=https://xx.x.x.x:8443 change the url to your openshift instance below.

  https://[[HOST_SUBDOMAIN]]-8443-[[KATACODA_HOST]].environments.katacoda.com

• Get the authentication token by running the following command oc whoami -t

• Copy the result token

• Remove the the userid and password entries and add a new entry for your authentication token.

  -Dkubernetes.auth.token={{YOUR_TOKEN}}

Click Apply and then click Run.

Your application is now being built locally on your machine. The first build may take some time. You can keep track of the progress in the Console view.

WInterested in tracking progress of your deployment to OpenShift? Click Continue on to see how.

To view the status of our build, go back to the Dashboard, on the lefthand side menu, hover over Builds and click on Builds.

From this page, you can monitor the status of your build on the platform.

Click Overview on the lefthand side menu. This page will display the list of applications that are running in your project. You can find overall details about each application on this page. For instance, the number of pods running your application, container images used in the pod, source code (if available). etc..

For a more detailed view of your application, let’s go to the Fuse Hawtio console. This includes standard JVM resources such as memory and threads as well as JMX attributes and operations. The console also provides a full selection of tools used to drill into the Fuse integration.

To get there, click on the running pod on the overview page. You will be taken directly to the pod detail page. Below the Template section on the page you will find a link named "Open Java Console". Go ahead and click it.

The Fuse Hawtio console provides deep insight into your integration and its current status. Select Route Diagram to see detailed view of your implementation logic :

The Route Diagram tab provides a graphical review of all the routes currently deployed in our API application. After selecting this tab, you should see something similar to what is pictured below.

Once done, close the console by clicking the back link as shown below and then head back to our terminal:

Now let’s check on the output of our application in the log console. Click on the Logs tab on the top of the page.

You will be able to see the output of the application.

Congratulations! You have completed your first Fuse application on OpenShift.