For the moment, we will use the templates provided by default from the platform, and in Chapter 8, Microservices Patterns, we will see how to create templates for our cloud-native application football manager—composed of three databases, three backend microservices, and two frontend Angular applications.

Let's try the WildFly template:

1. If you are not already logged in as developer, log in and from the catalog choose the WildFly icon.
2. You should read through the following wizard; just go through and rely on the defaults: 

3. Click on the Try Sample Repository link, as follows:

4. The template for the WildFly application will prepare the runtime environment in a few seconds, as follows:

5. If you click on the Continue to the project overview link, you will see your project with an overview of all deployments (in this case, only this one), as shown in the following screenshot:

As you can see in the preceding screenshot, the build is in place, downloading the source code and compiling the application. Once the build is complete, the OKD platform should deploy a pod with a container running our application in it. A properly running pod is shown with a blue ring, as follows:

The overview shows a lot of different information.

6. At the top right, there is the URL to access the application; if you click on http://openshift-jee-sample-myproject.127.0.0.1.nip.io, the following page should be displayed:

Getting back to the overview of our WildFly deployment example, you should also see the following Networking section, which is one of the most important aspects of any application.