. Access the application at http://dockerhost:8080/employees/resources/employees/. This is shown in the browser as:

### Stop Services

<<JavaEE7_PreBuilt_WAR>> explained how to use an in-memory database with the application server. This gets you started rather quickly but becomes a bottleneck soon as the database is only in-memory. This means that any changes made to your schema and data are lost when the application server shuts down. In this case, you need to use a database server that resides outside the application server. For example, MySQL as the database server and WildFly as the application server.

This section will show how https://docs.docker.com/userguide/dockerlinks/[Docker Container Linking] can be used to connect to a service running inside a Docker container via a network port.

In our particular case, the https://github.com/jboss-dockerfiles/wildfly/blob/master/Dockerfile[jboss/wildfly] image extends the https://github.com/jboss-dockerfiles/base/blob/master/Dockerfile[jboss/base-jdk:7] image which adds the OpenJDK distribution on top of the https://github.com/jboss-dockerfiles/base/blob/master/Dockerfile[jboss/base] image.

Now we're ready to test http://dockerhost:8080 again. This works with the exposed port, as expected.

### Enabling WildFly Administration

This shows the admin console as:

##### Additional Ways To Find Port Mapping

. Select '`Servers`' tab, create a new server adapter

+

+

. Assign an existing or create a new WildFly 9.0.0 runtime (changed properties are highlighted.)

+

+

. If a new runtime needs to be created, pick the directory for WildFly 9.0.0:

+

+

Click on '`Finish`'.

+

. Double-click on the newly selected server to configure server properties:

+

+

The host name is specified to '`dockerhost`'. Two properties on the left are automatically propagated from the previous dialog. Additional two properties on the right side are required to disable to keep deployment scanners in sync with the server.

+

. Specify a custom deployment folder on Deployment tab of Server Editor

+

+

. Right-click on the newly created server adapter and click '`Start`'.

+

### Deploy Application Using Shared Volumes

The project runs and displays the start page of the application.

Congratulations!

WildFly comes with a web-based administration console. It also relies on the same management APIs that are used by JBoss Developer Tools and the CLI. It provides a simple and easy to use web-based console to manage WildFly instance. For a Docker image, it needs to be explicitly enabled as explained in <<Enabling_WildFly_Administration>>. Once enabled, it can be accessed at http://dockerhost:9990.

Username and password credentials are shown in <<WildFly_Administration_Credentials>>.

. Go to '`Deployments`' tab.

+

+

. Click on '`Add`' button.

. On '`Add Deployment`' screen, take the default of '`Upload a new deployment`' and click '`Next>>`'.

. Select '`Enable`' checkbox.

+

+

. Click '`Finish`'.

+

This will complete the deployment of the Java EE 7 application using Web Console. The output can be seen out http://dockerhost:8080/javaee7-simple-sample and looks like:

### Deploy Application Using Management API

+

. Create a new server adapter in JBoss Developer Studio and name it "`WildFly 9.0.0-Management`". Specify the host name as '`dockerhost`'.

+

+

. Click on '`Next>`' and change the values as shown.

+

+

. Take the default values in '`Remote System Integration`' and click on '`Finish`'.

+

. Change server properties by double clicking on the newly created server adapter. Specify admin credentials (username: docker, password: docker#admin). Note, you need to delete the existing password and use this instead:

+

+

. Right-click on the newly created server adapter and click '`Start`'. Status quickly changes to '`Started`' as shown.

+

+

. Right-click on the javaee7-simple-sample project, select '`Run on Server`' and choose this server. The project runs and displays the start page of the application.

. Stop WildFly when you're done.

Specify the '`Name:`' as "`Docker Nightly`" and '`Location:`' as http://download.eclipse.org/linuxtools/updates-docker-nightly/.

+

.Add Docker Tooling To JBoss Developer Studio

+

. Expand Linux Tools, select '`Docker Client`' and '`Docker Tooling`'.

+

.Add Docker Tooling

+

. Click on '`Next >`', '`Next >`', accept the terms of the license agreement, and click on '`Finish`'. This will complete the installation of plugins.

+

. Use the menu '`Window`', '`Show View`', '`Other...`'. Type '`docker`' to see the output as:

+

+

. Select '`Docker Explorer`' to open Docker Explorer.

+

+

. Click on the link in this window to create a connection to Docker Host. Specify the settings as shown:

+

.Docker Explorer

+

Make sure to get IP address of the Docker Host as:

+

. Click on '`Test Connection`' to check the connection. This should show the output as:

+

.Docker Explorer

+

Click on '`OK`' and '`Finish`' to exit out of the wizard.

+

. Docker Explorer itself is a tree view that handles multiple connections and provides users with quick overview of the existing images and containers.

+

.Docker Explorer Tree View

+

. Customize the view by clicking on the arrow in toolbar:

+

.Docker Explorer Customize View

+

Built-in filters can show/hide intermediate and '`dangling`' images, as well as stopped containers.

+

.Docker Explorer Customize View Wizard

### Docker Images

. Use the menu '`Window`', '`Show View`', '`Other...`', select '`Docker Images`'. It shows the list of images on Docker Host:

+

.Docker Images View

+

. Right-click on the image ending with "`wildfly:latest`" and click on the green arrow in the toolbar. This will show the following wizard:

+

.Docker Run Container Wizard

+

By default, all exports ports from the image are mapped to random ports on the host interface. This setting can be changed by unselecting the first checkbox and specify exact port mapping.

+

. When the container is started, all logs are streamed into Eclipse Console:

+

.Docker Container Logs

### Docker Containers

. Use the menu '`Window`', '`Show View`', '`Other...`', select '`Docker Containers`'. It shows the list of running containers on Docker Host:

+

.Docker Containers View

+

. Pause the container by clicking on the "`pause`" button in the toolbar (https://bugs.eclipse.org/bugs/show_bug.cgi?id=469310[#469310]). Show the complete list of containers by clicking on the '`View Menu`', '`Show all containers`'.

+

.All Docker Containers

+

. Select the paused container, and click on the green arrow in the toolbar to restart the container.

. Right-click on any running container and select "`Display Log`" to view the log for this container.

+

.Eclipse Properties View

TODO: Users can also attach an Eclipse console to a running Docker container to follow the logs and use the STDIN to interact with it.

Info view is shown as:

+

.Docker Container Properties View Info

+

Inspect view is shown as:

+

.Docker Container Properties View Inspect

https://github.com/javaee-samples/javaee7-hol[Java EE 7 Movieplex] is a standard multi-tier enterprise application that shows design patterns and anti-patterns for a typical Java EE 7 application.

Pull the Docker image that contains WildFly and pre-built Java EE 7 application WAR file as shown:

See the application in action at http://dockerhost:8080/movieplex7/. The output is shown:

This uses an in-memory database with WildFly application server as shown in the image:

Only two changes are required to the standard `jboss/wildfly` image:

A picture is always worth a thousand words and so this is a high-level logical block diagram for Kubernetes:

After the 50,000 feet view, lets fly a little lower at 30,000 feet and take a look at how Kubernetes make all of this happen. There are a few key components at Master and Minion that make this happen.

NOTE: By default, only one minion is created. This can be manipulated by setting an environment variable NUM_MINIONS variable to an integer before invoking `kube-up.sh` script.

+

.Kubernetes Cluster using Vagrant

+

By default, each VM in the cluster is running Fedora, Kubelet is installed into ``systemd'', and all other Kubernetes services are running as containers on Master.

+

. Access https://10.245.1.2 (or whatever IP address is assigned to your kubernetes cluster start up log). This may present the warning as shown below:

+

+

Click on '`Advanced`' and then on '`Proceed to 10.245.1.2`' to see the output as:

+

.Kubernetes Output from Master

+

Use '`vagrant`' as the username and '`vagrant`' as the password.

+

Kubernetes services is an abstraction which defines a logical set of pods. A service is typically back-ended by one or more physical pods (associated using labels), and it has a permanent IP address that can be used by other pods/applications. For example, WildFly pod can not directly connect to a MySQL pod but can connect to MySQL service. In essence, Kubernetes service offers clients an IP and port pair which, when accessed, redirects to the appropriate backends.

NOTE: In this case, all the pods are running on a single minion. This is because, that is the default number for a Kubernetes cluster. The pod can very be on another minion if more number of minions are configured to start in the cluster.