Containerizing microservices

duration 20 minutes

Prerequisites:

Learn how to containerize and run your microservices with Open Liberty using Docker.

What you’ll learn

From development to production, and across your DevOps environments, you can deploy your microservices in a lightweight and portable manner by using containers. You can run a container from a container image. Each container image is a package of what you need to run your microservice or application, from the code to its dependencies and configuration. If you’re new to the development of applications in containers, you might want to start with the Using Docker containers to develop microservices guide before you work through this guide.

You’ll learn how to build container images and run containers using Docker for your microservices. You’ll learn about the Open Liberty container images and how to use them for your containerized applications. You’ll construct Dockerfile files, create Docker images by using the docker build command, and run the image as Docker containers by using docker run command.

The two microservices that you’ll be working with are called system and inventory. The system microservice returns the JVM system properties of the running container. The inventory microservice adds the properties from the system microservice to the inventory. This guide demonstrates how both microservices can run and communicate with each other in different Docker containers.

Additional prerequisites

Before you begin, Docker needs to be installed. For installation instructions, refer to the official Docker documentation. You will build and run the microservices in Docker containers.

Make sure to start your Docker daemon before you proceed.

Getting started

The fastest way to work through this guide is to clone the Git repository and use the projects that are provided inside:

git clone https://github.com/openliberty/guide-containerize.git
cd guide-containerize

The start directory contains the starting project that you will build upon.

The finish directory contains the finished project that you will build.

Before you begin, make sure you have all the necessary prerequisites.

Packaging your microservices

Navigate to the start directory to begin.

You can find the starting Java project in the start directory. This project is a multi-module Maven project that is made up of the system and inventory microservices. Each microservice is located in its own corresponding directory, system and inventory.

To try out the microservices by using Maven, run the following Maven goal to build the system microservice and run it inside Open Liberty:

mvn -pl system liberty:run

Open another command-line session and run the following Maven goal to build the inventory microservice and run it inside Open Liberty:

mvn -pl inventory liberty:run

After you see the following message in both command-line sessions, both of your services are ready:

The defaultServer server is ready to run a smarter planet.

To access the inventory service, which displays the current contents of the inventory, see http://localhost:9081/inventory/systems.

To access the system service, which shows the system properties of the running JVM, see http://localhost:9080/system/properties.

You can add the system properties of your localhost to the inventory service at http://localhost:9081/inventory/systems/localhost.

After you are finished checking out the microservices, stop the Liberty instances by pressing CTRL+C in the command-line sessions where you ran the system and inventory services. Alternatively, you can run the liberty:stop goal in another command-line session:

mvn -pl system liberty:stop
mvn -pl inventory liberty:stop

To package your microservices, run the Maven package goal to build the application .war files from the start directory so that the .war files are in the system/target and inventory/target directories.

mvn package

To learn more about RESTful web services and how to build them, see Creating a RESTful web service for details about how to build the system service. The inventory service is built in a similar way.

Building your Docker images

A Docker image is a binary file. It is made up of multiple layers and is used to run code in a Docker container. Images are built from instructions in Dockerfiles to create a containerized version of the application.

A Dockerfile is a collection of instructions for building a Docker image that can then be run as a container. As each instruction is run in a Dockerfile, a new Docker layer is created. These layers, which are known as intermediate images, are created when a change is made to your Docker image.

Every Dockerfile begins with a parent or base image over which various commands are run. For example, you can start your image from scratch and run commands that download and install a Java runtime, or you can start from an image that already contains a Java installation.

Learn more about Docker on the official Docker page.

Creating your Dockerfiles

You will be creating two Docker images to run the inventory service and system service. The first step is to create Dockerfiles for both services.

In this guide, you’re using an official image from the IBM Container Registry (ICR), icr.io/appcafe/open-liberty:full-java11-openj9-ubi, as your parent image. This image is tagged with the word full, meaning it includes all Liberty features. full images are recommended for development only because they significantly expand the image size with features that are not required by the application.

To minimize your image footprint in production, you can use one of the kernel-slim images, such as icr.io/appcafe/open-liberty:kernel-slim-java11-openj9-ubi. This image installs the basic Liberty runtime. You can then add all the necessary features for your application with the usage pattern that is detailed in the Open Liberty container image documentation. To use the default image that comes with the Open Liberty runtime, define the FROM instruction as FROM icr.io/appcafe/open-liberty. You can find all official images on the Open Liberty container image repository.

Create the Dockerfile for the inventory service.
inventory/Dockerfile

inventory/Dockerfile

 1# tag::from[]
 2FROM icr.io/appcafe/open-liberty:full-java11-openj9-ubi
 3# end::from[]
 4
 5ARG VERSION=1.0
 6ARG REVISION=SNAPSHOT
 7
 8# tag::label[]
 9LABEL \
10  org.opencontainers.image.authors="Your Name" \
11  org.opencontainers.image.vendor="Open Liberty" \
12  org.opencontainers.image.url="local" \
13  org.opencontainers.image.source="https://github.com/OpenLiberty/guide-containerize" \
14  org.opencontainers.image.version="$VERSION" \
15  org.opencontainers.image.revision="$REVISION" \
16  vendor="Open Liberty" \
17  name="inventory" \
18  version="$VERSION-$REVISION" \
19  summary="The inventory microservice from the Containerizing microservices guide" \
20  description="This image contains the inventory microservice running with the Open Liberty runtime."
21# end::label[]
22
23# tag::copy-config[]
24# tag::config-userID[]
25COPY --chown=1001:0 \
26# end::config-userID[]
27    # tag::inventory-config[]
28    src/main/liberty/config \
29    # end::inventory-config[]
30    # tag::config[]
31    /config/
32    # end::config[]
33# end::copy-config[]
34
35# tag::copy-war[]
36# tag::war-userID[]
37COPY --chown=1001:0 \
38# end::war-userID[]
39    # tag::inventory-war[]
40    target/guide-containerize-inventory.war \
41    # end::inventory-war[]
42    # tag::config-apps[]
43    /config/apps
44    # end::config-apps[]
45# end::copy-war[]
46
47# tag::configure-sh[]
48RUN configure.sh
49# end::configure-sh[]

The FROM instruction initializes a new build stage, which indicates the parent image of the built image. If you don’t need a parent image, then you can use FROM scratch, which makes your image a base image.

It is also recommended to label your Docker images with the LABEL command, as the label information can help you manage your images. For more information, see Best practices for writing Dockerfiles.

The COPY instructions are structured as COPY [--chown=<user>:<group>] <source> <destination>. They copy local files into the specified destination within your Docker image. In this case, the inventory Liberty configuration files that are located at src/main/liberty/config are copied to the /config/ destination directory. The inventory application WAR file inventory.war, which was created from running mvn package, is copied to the /config/apps destination directory.

The COPY instructions use the 1001 user ID and 0 group because the icr.io/appcafe/open-liberty:full-java11-openj9-ubi image runs by default with the USER 1001 (non-root) user for security purposes. Otherwise, the files and directories that are copied over are owned by the root user.

Place the RUN configure.sh command at the end to get a pre-warmed Docker image. It improves the startup time of running your Docker container.

The Dockerfile for the system service follows the same instructions as the inventory service, except that some labels are updated, and the system.war archive is copied into /config/apps.

Create the Dockerfile for the system service.
system/Dockerfile

system/Dockerfile

 1FROM icr.io/appcafe/open-liberty:full-java11-openj9-ubi
 2
 3ARG VERSION=1.0
 4ARG REVISION=SNAPSHOT
 5
 6LABEL \
 7  org.opencontainers.image.authors="Your Name" \
 8  org.opencontainers.image.vendor="Open Liberty" \
 9  org.opencontainers.image.url="local" \
10  org.opencontainers.image.source="https://github.com/OpenLiberty/guide-containerize" \
11  org.opencontainers.image.version="$VERSION" \
12  org.opencontainers.image.revision="$REVISION" \
13  vendor="Open Liberty" \
14# tag::name[]
15  name="system" \
16# end::name[]
17  version="$VERSION-$REVISION" \
18# tag::summary[]
19  summary="The system microservice from the Containerizing microservices guide" \
20  description="This image contains the system microservice running with the Open Liberty runtime."
21# end::summary[]
22
23COPY --chown=1001:0 src/main/liberty/config /config/
24
25# tag::copy-war[]
26COPY --chown=1001:0 target/guide-containerize-system.war /config/apps
27# end::copy-war[]
28
29RUN configure.sh

Building your Docker image

Now that your microservices are packaged and you have written your Dockerfiles, you will build your Docker images by using the docker build command.

Run the following commands to build container images for your application:

docker build -t system:1.0-SNAPSHOT system/.
docker build -t inventory:1.0-SNAPSHOT inventory/.

The -t flag in the docker build command allows the Docker image to be labeled (tagged) in the name[:tag] format. The tag for an image describes the specific image version. If the optional [:tag] tag is not specified, the latest tag is created by default.

To verify that the images are built, run the docker images command to list all local Docker images:

docker images

Or, run the docker images command with --filter option to list your images:

docker images -f "label=org.opencontainers.image.authors=Your Name"

Your inventory and system images appear in the list of all Docker images:

REPOSITORY    TAG             IMAGE ID        CREATED          SIZE
inventory     1.0-SNAPSHOT    08fef024e986    4 minutes ago    1GB
system        1.0-SNAPSHOT    1dff6d0b4f31    5 minutes ago    977MB

Running your microservices in Docker containers

Now that your two images are built, you will run your microservices in Docker containers:

docker run -d --name system -p 9080:9080 system:1.0-SNAPSHOT
docker run -d --name inventory -p 9081:9081 inventory:1.0-SNAPSHOT

The following table describes the flags in these commands:

Flag Description

-d

Runs the container in the background.

--name

Specifies a name for the container.

-p

Maps the host ports to the container ports. For example: -p <HOST_PORT>:<CONTAINER_PORT>

Next, run the docker ps command to verify that your containers are started:

docker ps

Make sure that your containers are running and show Up as their status:

CONTAINER ID    IMAGE                   COMMAND                  CREATED          STATUS          PORTS                                        NAMES
2b584282e0f5    inventory:1.0-SNAPSHOT  "/opt/ol/helpers/run…"   2 seconds ago    Up 1 second     9080/tcp, 9443/tcp, 0.0.0.0:9081->9081/tcp   inventory
99a98313705f    system:1.0-SNAPSHOT     "/opt/ol/helpers/run…"   3 seconds ago    Up 2 seconds    0.0.0.0:9080->9080/tcp, 9443/tcp             system

If a problem occurs and your containers exit prematurely, the containers don’t appear in the container list that the docker ps command displays. Instead, your containers appear with an Exited status when they run the docker ps -a command. Run the docker logs system and docker logs inventory commands to view the container logs for any potential problems. Run the docker stats system and docker stats inventory commands to display a live stream of usage statistics for your containers. You can also double-check that your Dockerfiles are correct. When you find the cause of the issues, remove the faulty containers with the docker rm system and docker rm inventory commands. Rebuild your images, and start the containers again.

To access the application, go to the http://localhost:9081/inventory/systems URL. An empty list is expected because no system properties are stored in the inventory yet.

Next, retrieve the system container’s IP address by running the following:

docker inspect -f "{{.NetworkSettings.IPAddress }}" system

The command returns the system container IP address:

172.17.0.2

In this case, the IP address for the system service is 172.17.0.2. Take note of this IP address to construct the URL to view the system properties.

Go to the http://localhost:9081/inventory/systems/[system-ip-address] URL by replacing [system-ip-address] with the IP address that you obtained earlier. You see a result in JSON format with the system properties of your local JVM. When you go to this URL, these system properties are automatically stored in the inventory. Go back to the http://localhost:9081/inventory/systems URL and you see a new entry for [system-ip-address].

Externalizing Liberty’s configuration

inventory/server.xml

 1<server description="Sample Liberty server">
 2
 3  <featureManager>
 4    <feature>restfulWS-3.1</feature>
 5    <feature>jsonb-3.0</feature>
 6    <feature>jsonp-2.1</feature>
 7    <feature>cdi-4.0</feature>
 8    <feature>mpConfig-3.0</feature>
 9  </featureManager>
10
11  <!-- tag::httpPort[] -->
12  <variable name="default.http.port" defaultValue="9081" />
13  <!-- end::httpPort[] -->
14  <variable name="default.https.port" defaultValue="9444" />
15
16  <!-- tag::httpEndpoint[] -->
17  <httpEndpoint httpPort="${default.http.port}" httpsPort="${default.https.port}"
18      id="defaultHttpEndpoint" host="*" />
19  <!-- end::httpEndpoint[] -->
20
21  <webApplication location="guide-containerize-inventory.war" contextRoot="/">
22
23  </webApplication>
24
25</server>

As mentioned at the beginning of this guide, one of the advantages of using containers is that they are portable and can be moved and deployed efficiently across all of your DevOps environments. Configuration often changes across different environments, and by externalizing your Liberty’s configuration, you can simplify the development process.

Imagine a scenario where you are developing an Open Liberty application on port 9081 but to deploy it to production, it must be available on port 9091. To manage this scenario, you can keep two different versions of the server.xml file; one for production and one for development. However, trying to maintain two different versions of a file might lead to mistakes. A better solution would be to externalize the configuration of the port number and use the value of an environment variable that is stored in each environment.

In this example, you will use an environment variable to externally configure the HTTP port number of the inventory service.

In the inventory/server.xml file, the default.http.port variable is declared and is used in the httpEndpoint element to define the service endpoint. The default value of the default.http.port variable is 9081. However, this value is only used if no other value is specified. You can replace this value in the container by using the -e flag for the podman run command.

Run the following commands to stop and remove the inventory container and rerun it with the default.http.port environment variable set:

docker stop inventory
docker rm inventory
docker run -d --name inventory -e default.http.port=9091 -p 9091:9091 inventory:1.0-SNAPSHOT

The -e flag can be used to create and set the values of environment variables in a Docker container. In this case, you are setting the default.http.port environment variable to 9091 for the inventory container.

Now, when the service is starting up, Open Liberty finds the default.http.port environment variable and uses it to set the value of the default.http.port variable to be used in the HTTP endpoint.

The inventory service is now available on the new port number that you specified. You can see the contents of the inventory at the http://localhost:9091/inventory/systems URL. You can add your local system properties at http://localhost:9091/inventory/systems/[system-ip-address] by replacing [system-ip-address] with the IP address that you obtained in the previous section. The system service remains unchanged and is available at the http://localhost:9080/system/properties URL.

You can externalize the configuration of more than just the port numbers. To learn more about Open Liberty configuration, check out the Server Configuration Overview docs.

Optimizing the image size

As mentioned previously, the parent image that is used in each Dockerfile contains the full tag, which includes all of the Liberty features. This parent image with the full tag is recommended for development, but while deploying to production it is recommended to use a parent image with the kernel-slim tag. The kernel-slim tag provides a bare minimum Liberty runtime with the ability to add the features required by the application.

Replace the Dockerfile for the inventory service.
inventory/Dockerfile

inventory/Dockerfile

 1# tag::kernel-slim[]
 2FROM icr.io/appcafe/open-liberty:kernel-slim-java11-openj9-ubi
 3# end::kernel-slim[]
 4
 5ARG VERSION=1.0
 6ARG REVISION=SNAPSHOT
 7
 8# tag::label[]
 9LABEL \
10  org.opencontainers.image.authors="Your Name" \
11  org.opencontainers.image.vendor="Open Liberty" \
12  org.opencontainers.image.url="local" \
13  org.opencontainers.image.source="https://github.com/OpenLiberty/guide-containerize" \
14  org.opencontainers.image.version="$VERSION" \
15  org.opencontainers.image.revision="$REVISION" \
16  vendor="Open Liberty" \
17  name="inventory" \
18  version="$VERSION-$REVISION" \
19  summary="The inventory microservice from the Containerizing microservices guide" \
20  description="This image contains the inventory microservice running with the Open Liberty runtime."
21# end::label[]
22
23# tag::copy-config[]
24# tag::config-userID[]
25COPY --chown=1001:0 \
26# end::config-userID[]
27    # tag::inventory-config[]
28    src/main/liberty/config \
29    # end::inventory-config[]
30    # tag::config[]
31    /config/
32    # end::config[]
33# end::copy-config[]
34
35# tag::features[]
36RUN features.sh
37# end::features[]
38
39# tag::copy-war[]
40# tag::war-userID[]
41COPY --chown=1001:0 \
42# end::war-userID[]
43    # tag::inventory-war[]
44    target/guide-containerize-inventory.war \
45    # end::inventory-war[]
46    # tag::config-apps[]
47    /config/apps
48    # end::config-apps[]
49# end::copy-war[]
50
51# tag::configure-sh[]
52RUN configure.sh
53# end::configure-sh[]

Replace the parent image with icr.io/appcafe/open-liberty:kernel-slim-java11-openj9-ubi at the top of your Dockerfile. This image contains the kernel-slim tag that is recommended when deploying to production.

Place RUN features.sh command after the COPY command that copies the local /config/ directory into the Docker image. The features.sh script adds the Liberty features that your application is required to operate.

Ensure that you repeat these instructions for the system service.

Replace the Dockerfile for the system service.
system/Dockerfile

system/Dockerfile

 1# tag::kernel-slim[]
 2FROM icr.io/appcafe/open-liberty:kernel-slim-java11-openj9-ubi
 3# end::kernel-slim[]
 4
 5ARG VERSION=1.0
 6ARG REVISION=SNAPSHOT
 7
 8LABEL \
 9  org.opencontainers.image.authors="Your Name" \
10  org.opencontainers.image.vendor="Open Liberty" \
11  org.opencontainers.image.url="local" \
12  org.opencontainers.image.source="https://github.com/OpenLiberty/guide-containerize" \
13  org.opencontainers.image.version="$VERSION" \
14  org.opencontainers.image.revision="$REVISION" \
15  vendor="Open Liberty" \
16# tag::name[]
17  name="system" \
18# end::name[]
19  version="$VERSION-$REVISION" \
20# tag::summary[]
21  summary="The system microservice from the Containerizing microservices guide" \
22  description="This image contains the system microservice running with the Open Liberty runtime."
23# end::summary[]
24
25COPY --chown=1001:0 src/main/liberty/config /config/
26
27# tag::features[]
28RUN features.sh
29# end::features[]
30
31# tag::copy-war[]
32COPY --chown=1001:0 target/guide-containerize-system.war /config/apps
33# end::copy-war[]
34
35RUN configure.sh

Continue by running the following commands to stop and remove your current Docker containers that are using the full parent image:

docker stop inventory system
docker rm inventory system

Next, build your new Docker images with the kernel-slim parent image:

docker build -t system:1.0-SNAPSHOT system/.
docker build -t inventory:1.0-SNAPSHOT inventory/.

Verify that the images have been built by executing the following command to list all the local Docker images:

docker images

Notice that the images for the inventory and system services now have a reduced image size.

REPOSITORY      TAG             IMAGE ID        CREATED         SIZE
inventory       1.0-SNAPSHOT	d5a3d1b2c20e    4 minutes ago	682MB
system          1.0-SNAPSHOT	6346cf87eae0	5 minutes ago	694MB

After confirming that the images have been built, run the following commands to start the Docker containers:

docker run -d --name system -p 9080:9080 system:1.0-SNAPSHOT
docker run -d --name inventory -p 9081:9081 inventory:1.0-SNAPSHOT

Once your Docker containers are running, run the following command to see the list of required features installed by features.sh:

docker exec -it inventory /opt/ol/wlp/bin/productInfo featureInfo

Your list of Liberty features should be similar to the following:

jndi-1.0
servlet-5.0
cdi-3.0
concurrent-2.0
jsonb-2.0
jsonp-2.0
mpConfig-3.0
restfulWS-3.0
restfulWSClient-3.0

To ensure that your containers are working properly, try accessing the system service to show the system properties of the running JVM. See http://localhost:9080/system/properties

Next, replace [system-ip-address] with the IP address that you obtained earlier and add your localhost system properties to the inventory service by visiting: http://localhost:9081/inventory/systems/[system-ip-address]

Then, verify the addition of your localhost system properties to your inventory service. See http://localhost:9081/inventory/systems

Testing the microservices

You can test your microservices manually by hitting the endpoints or with automated tests that check your running Docker containers.

Create the SystemEndpointIT class.
system/src/test/java/it/io/openliberty/guides/system/SystemEndpointIT.java

SystemEndpointIT.java

 1// tag::copyright[]
 2/*******************************************************************************
 3 * Copyright (c) 2018, 2023 IBM Corporation and others.
 4 * All rights reserved. This program and the accompanying materials
 5 * are made available under the terms of the Eclipse Public License 2.0
 6 * which accompanies this distribution, and is available at
 7 * http://www.eclipse.org/legal/epl-2.0/
 8 *
 9 * SPDX-License-Identifier: EPL-2.0
10 *******************************************************************************/
11// end::copyright[]
12package it.io.openliberty.guides.system;
13
14import static org.junit.jupiter.api.Assertions.assertEquals;
15
16import javax.net.ssl.HostnameVerifier;
17import javax.net.ssl.SSLSession;
18import jakarta.ws.rs.client.Client;
19import jakarta.ws.rs.client.ClientBuilder;
20import jakarta.ws.rs.client.WebTarget;
21import jakarta.ws.rs.core.Response;
22
23import org.junit.jupiter.api.AfterEach;
24import org.junit.jupiter.api.BeforeAll;
25import org.junit.jupiter.api.BeforeEach;
26import org.junit.jupiter.api.Test;
27
28public class SystemEndpointIT {
29
30    private static String clusterUrl;
31
32    private Client client;
33
34    @BeforeAll
35    public static void oneTimeSetup() {
36        String nodePort = System.getProperty("system.http.port");
37        clusterUrl = "http://localhost:" + nodePort + "/system/properties/";
38    }
39
40    @BeforeEach
41    public void setup() {
42        client = ClientBuilder.newBuilder()
43                    .hostnameVerifier(new HostnameVerifier() {
44                        public boolean verify(String hostname, SSLSession session) {
45                            return true;
46                        }
47                    })
48                    .build();
49    }
50
51    @AfterEach
52    public void teardown() {
53        client.close();
54    }
55
56    // tag::testGetProperties[]
57    @Test
58    public void testGetProperties() {
59        Client client = ClientBuilder.newClient();
60
61        WebTarget target = client.target(clusterUrl);
62        Response response = target.request().get();
63
64        assertEquals(200, response.getStatus(),
65            "Incorrect response code from " + clusterUrl);
66        response.close();
67    }
68    // end::testGetProperties[]
69
70}

The testGetProperties() method checks for a 200 response code from the system service endpoint.

Create the InventoryEndpointIT class.
inventory/src/test/java/it/io/openliberty/guides/inventory/InventoryEndpointIT.java

InventoryEndpointIT.java

  1// tag::copyright[]
  2/*******************************************************************************
  3 * Copyright (c) 2018, 2023 IBM Corporation and others.
  4 * All rights reserved. This program and the accompanying materials
  5 * are made available under the terms of the Eclipse Public License 2.0
  6 * which accompanies this distribution, and is available at
  7 * http://www.eclipse.org/legal/epl-2.0/
  8 *
  9 * SPDX-License-Identifier: EPL-2.0
 10 *******************************************************************************/
 11// end::copyright[]
 12package it.io.openliberty.guides.inventory;
 13
 14import static org.junit.jupiter.api.Assertions.assertEquals;
 15import static org.junit.jupiter.api.Assertions.assertTrue;
 16
 17import jakarta.json.JsonObject;
 18import javax.net.ssl.HostnameVerifier;
 19import javax.net.ssl.SSLSession;
 20import jakarta.ws.rs.client.Client;
 21import jakarta.ws.rs.client.ClientBuilder;
 22import jakarta.ws.rs.core.MediaType;
 23import jakarta.ws.rs.core.Response;
 24
 25import org.junit.jupiter.api.AfterAll;
 26import org.junit.jupiter.api.BeforeAll;
 27import org.junit.jupiter.api.MethodOrderer.OrderAnnotation;
 28import org.junit.jupiter.api.Order;
 29import org.junit.jupiter.api.Test;
 30import org.junit.jupiter.api.TestMethodOrder;
 31
 32@TestMethodOrder(OrderAnnotation.class)
 33public class InventoryEndpointIT {
 34
 35    private static String invUrl;
 36    private static String sysUrl;
 37    private static String systemServiceIp;
 38
 39    private static Client client;
 40
 41    @BeforeAll
 42    public static void oneTimeSetup() {
 43
 44        String invServPort = System.getProperty("inventory.http.port");
 45        String sysServPort = System.getProperty("system.http.port");
 46
 47        // tag::systemServiceIp[]
 48        systemServiceIp = System.getProperty("system.ip");
 49        // end::systemServiceIp[]
 50
 51        invUrl = "http://localhost" + ":" + invServPort + "/inventory/systems/";
 52        sysUrl = "http://localhost" + ":" + sysServPort + "/system/properties/";
 53
 54        client = ClientBuilder.newBuilder().hostnameVerifier(new HostnameVerifier() {
 55            public boolean verify(String hostname, SSLSession session) {
 56                return true;
 57            }
 58        }).build();
 59
 60        client.target(invUrl + "reset").request().post(null);
 61    }
 62
 63    @AfterAll
 64    public static void teardown() {
 65        client.close();
 66    }
 67
 68    // tag::tests[]
 69    // tag::testEmptyInventory[]
 70    @Test
 71    @Order(1)
 72    public void testEmptyInventory() {
 73        Response response = this.getResponse(invUrl);
 74        this.assertResponse(invUrl, response);
 75
 76        JsonObject obj = response.readEntity(JsonObject.class);
 77
 78        int expected = 0;
 79        int actual = obj.getInt("total");
 80        assertEquals(expected, actual,
 81                    "The inventory should be empty on application start but it wasn't");
 82
 83        response.close();
 84    }
 85    // end::testEmptyInventory[]
 86
 87    // tag::testHostRegistration[]
 88    @Test
 89    @Order(2)
 90    public void testHostRegistration() {
 91        this.visitSystemService();
 92
 93        Response response = this.getResponse(invUrl);
 94        this.assertResponse(invUrl, response);
 95
 96        JsonObject obj = response.readEntity(JsonObject.class);
 97
 98        int expected = 1;
 99        int actual = obj.getInt("total");
100        assertEquals(expected, actual,
101                        "The inventory should have one entry for " + systemServiceIp);
102
103        boolean serviceExists = obj.getJsonArray("systems").getJsonObject(0)
104                        .get("hostname").toString().contains(systemServiceIp);
105        assertTrue(serviceExists,
106                        "A host was registered, but it was not " + systemServiceIp);
107
108        response.close();
109    }
110    // end::testHostRegistration[]
111
112    // tag::testSystemPropertiesMatch[]
113    @Test
114    @Order(3)
115    public void testSystemPropertiesMatch() {
116        Response invResponse = this.getResponse(invUrl);
117        Response sysResponse = this.getResponse(sysUrl);
118
119        this.assertResponse(invUrl, invResponse);
120        this.assertResponse(sysUrl, sysResponse);
121
122        JsonObject jsonFromInventory = (JsonObject) invResponse
123                        .readEntity(JsonObject.class).getJsonArray("systems")
124                        .getJsonObject(0).get("properties");
125
126        JsonObject jsonFromSystem = sysResponse.readEntity(JsonObject.class);
127
128        String osNameFromInventory = jsonFromInventory.getString("os.name");
129        String osNameFromSystem = jsonFromSystem.getString("os.name");
130        this.assertProperty("os.name", systemServiceIp, osNameFromSystem,
131                        osNameFromInventory);
132
133        String userNameFromInventory = jsonFromInventory.getString("user.name");
134        String userNameFromSystem = jsonFromSystem.getString("user.name");
135        this.assertProperty("user.name", systemServiceIp, userNameFromSystem,
136                        userNameFromInventory);
137
138        invResponse.close();
139        sysResponse.close();
140    }
141    // end::testSystemPropertiesMatch[]
142
143    // tag::testUnknownHost[]
144    @Test
145    @Order(4)
146    public void testUnknownHost() {
147        Response response = this.getResponse(invUrl);
148        this.assertResponse(invUrl, response);
149
150        Response badResponse = client.target(invUrl + "badhostname")
151                        .request(MediaType.APPLICATION_JSON).get();
152
153        String obj = badResponse.readEntity(String.class);
154
155        boolean isError = obj.contains("error");
156        assertTrue(isError,
157                        "badhostname is not a valid host but it didn't raise an error");
158
159        response.close();
160        badResponse.close();
161    }
162    // end::testUnknownHost[]
163    // end::tests[]
164
165    // Returns response information from the specified URL.
166    private Response getResponse(String url) {
167        return client.target(url).request().get();
168    }
169
170
171    // Asserts that the given URL has the correct response code of 200.
172    private void assertResponse(String url, Response response) {
173        assertEquals(200, response.getStatus(), "Incorrect response code from " + url);
174    }
175
176    // Asserts that the specified JVM system property is equivalent in both the
177    // system and inventory services.
178    private void assertProperty(String propertyName, String hostname, String expected,
179                    String actual) {
180        assertEquals(expected, actual, "JVM system property [" + propertyName + "] "
181                        + "in the system service does not match the one stored in "
182                        + "the inventory service for " + hostname);
183    }
184
185    // Makes a simple GET request to inventory/localhost.
186    private void visitSystemService() {
187        Response response = this.getResponse(sysUrl);
188        this.assertResponse(sysUrl, response);
189        response.close();
190
191        Response targetResponse = client.target(invUrl + systemServiceIp).request()
192                        .get();
193
194        targetResponse.close();
195    }
196}

  • The testEmptyInventory() method checks that the inventory service has a total of 0 systems before anything is added to it.

  • The testHostRegistration() method checks that the system service was added to inventory properly.

  • The testSystemPropertiesMatch() checks that the system properties match what was added into the inventory service.

  • The testUnknownHost() method checks that an error is raised if an unknown host name is being added into the inventory service.

  • The systemServiceIp variable has the same value as the IP address that you retrieved in the previous section when you manually added the system service into the inventory service. This value of the IP address is passed in when you run the tests.

Running the tests

Run the Maven package goal to compile the test classes. Run the Maven failsafe goal to test the services that are running in the Docker containers by replacing the [system-ip-address] with the IP address that you determined previously.

mvn package
mvn failsafe:integration-test -Dsystem.ip=[system-ip-address] -Dinventory.http.port=9081 -Dsystem.http.port=9080

If the tests pass, you see output similar to the following example:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running it.io.openliberty.guides.system.SystemEndpointIT
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.653 s - in it.io.openliberty.guides.system.SystemEndpointIT

Results:

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running it.io.openliberty.guides.inventory.InventoryEndpointIT
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.935 s - in it.io.openliberty.guides.inventory.InventoryEndpointIT

Results:

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

When you are finished with the services, run the following commands to stop and remove your containers:

docker stop inventory system
docker rm inventory system

Great work! You’re done!

You have just built Docker images and run two microservices on Open Liberty in containers.

Guide Attribution

Containerizing microservices by Open Liberty is licensed under CC BY-ND 4.0

Copy file contents
Copied to clipboard

Prerequisites:

Nice work! Where to next?

What did you think of this guide?

Extreme Dislike Dislike Like Extreme Like

What could make this guide better?

Raise an issue to share feedback

Create a pull request to contribute to this guide

Need help?

Ask a question on Stack Overflow

Like Open Liberty? Star our repo on GitHub.

Star