Tag Archives: javaee7

Java EE, Docker and Maven (Tech Tip #89)

May 20, 2015containers, javaee, techtipdocker, javaee7, maven, wildflyarungupta

Java EE applications are typically built and packaged using Maven. For example, github.com/javaee-samples/javaee7-docker-maven is a trivial Java EE 7 application and shows the Java EE 7 dependency:

<dependencies>
    <dependency>
        <groupId>javax</groupId>
        <artifactId>javaee-api</artifactId>
        <version>7.0</version>
        <scope>provided</scope>
    </dependency>
</dependencies>

<groupId>javax</groupId>

<artifactId>javaee-api</artifactId>

<scope>provided</scope>

</dependency>

</dependencies>

And the two Maven plugins that compiles the source and builds the WAR file:

<plugin>
    <artifactId>maven-compiler-plugin</artifactId>
    <version>3.1</version>
    <configuration>
        <source>1.7</source>
        <target>1.7</target>
    </configuration>
</plugin>
<plugin>
    <artifactId>maven-war-plugin</artifactId>
    <version>2.3</version>
    <configuration>
        <failOnMissingWebXml>false</failOnMissingWebXml>
    </configuration>
</plugin>

<artifactId>maven-compiler-plugin</artifactId>

</configuration>

</plugin>

<artifactId>maven-war-plugin</artifactId>

<failOnMissingWebXml>false</failOnMissingWebXml>

</configuration>

</plugin>

This application can then be deployed to a Java EE 7 container, such as WildFly, using the wildfly-maven-plugin:

<plugin>
    <groupId>org.wildfly.plugins</groupId>
    <artifactId>wildfly-maven-plugin</artifactId>
    <version>1.0.2.Final</version>
</plugin>

<groupId>org.wildfly.plugins</groupId>

<artifactId>wildfly-maven-plugin</artifactId>

<version>1.0.2.Final</version>

</plugin>

Tests can be invoked using Arquillian, again using Maven. So if you were to package this application as a Docker image and run it inside a Docker container, there should be a mechanism to seamlessly integrate in the Maven workflow.

Docker Maven Plugin

Meet docker-maven-plugin!

This plugin allows you to manage Docker images and containers from your pom.xml. It comes with predefined goals:

Goal	Description
`docker:start`	Create and start containers
`docker:stop`	Stop and destroy containers
`docker:build`	Build images
`docker:push`	Push images to a registry
`docker:remove`	Remove images from local docker host
`docker:logs`	Show container logs

Introduction provides a high level introduction to the plugin including building images, running containers and configuration.

Run Java EE 7 Application as Docker Container using Maven

TLDR;

Create and Configure a Docker Machine as explained in Docker Machine to Setup Docker Host
Clone the workspace as: git clone https://github.com/javaee-samples/javaee7-docker-maven.git
Build the Docker image as: mvn package -Pdocker
Run the Docker container as: mvn install -Pdocker
Find out IP address of the Docker Machine as: docker-machine ip mydocker

Access your application

javaee7-docker-maven> curl http://192.168.99.100:8080/javaee7-docker-maven/resources/persons
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><collection><person><name>Penny</name></person><person><name>Leonard</name></person><person><name>Sheldon</name></person><person><name>Amy</name></person><person><name>Howard</name></person><person><name>Bernadette</name></person><person><name>Raj</name></person><person><name>Priya</name></person></collection>

javaee7-docker-maven> curl http://192.168.99.100:8080/javaee7-docker-maven/resources/persons

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><collection><person><name>Penny</name></person><person><name>Leonard</name></person><person><name>Sheldon</name></person><person><name>Amy</name></person><person><name>Howard</name></person><person><name>Bernadette</name></person><person><name>Raj</name></person><person><name>Priya</name></person></collection>

Docker Maven Plugin Configuration

Lets look little deeper in our sample application.

pom.xml is updated to include docker-maven-plugin as:

<plugin>
    <groupId>org.jolokia</groupId>
    <artifactId>docker-maven-plugin</artifactId>
    <version>0.11.5</version>
    <configuration>
        <images>
            <image>
                <alias>user</alias>
                <name>arungupta/javaee7-docker-maven</name>
                <build>
                    <from>arungupta/wildfly:8.2</from>
                    <assembly>
                        <descriptor>assembly.xml</descriptor>
                        <basedir>/</basedir>
                    </assembly>
                    <ports>
                        <port>8080</port>
                    </ports>
                </build>
                <run>
                    <ports>
                        <port>8080:8080</port>
                    </ports>
                </run>
            </image>
        </images>
    </configuration>
    <executions>
        <execution>
            <id>docker:build</id>
            <phase>package</phase>
            <goals>
                <goal>build</goal>
            </goals>
        </execution>
        <execution>
            <id>docker:start</id>
            <phase>install</phase>
            <goals>
                <goal>start</goal>
            </goals>
        </execution>
    </executions>
</plugin>

<groupId>org.jolokia</groupId>

<artifactId>docker-maven-plugin</artifactId>

<image>

<name>arungupta/javaee7-docker-maven</name>

<build>

<from>arungupta/wildfly:8.2</from>

<descriptor>assembly.xml</descriptor>

</assembly>

<ports>

</ports>

</build>

<run>

<ports>

</ports>

</run>

</image>

</images>

</configuration>

<id>docker:build</id>

<phase>package</phase>

<goals>

<goal>build</goal>

</goals>

</execution>

<id>docker:start</id>

<phase>install</phase>

<goals>

<goal>start</goal>

</goals>

</execution>

</executions>

</plugin>

Each image configuration has three parts:

Image name and alias

<build> that defines how the image is created. Base image, build artifacts and their dependencies, ports to be exposed, etc to be included in the image are specified here.Assembly descriptor format is used to specify the artifacts to be included and is defined in src/main/docker directory. assembly.xml in our case looks like:

<assembly . . .>
  <id>javaee7-docker-maven</id>
  <dependencySets>
    <dependencySet>
      <includes>
        <include>org.javaee7.sample:javaee7-docker-maven</include>
      </includes>
      <outputDirectory>/opt/jboss/wildfly/standalone/deployments/</outputDirectory>
      <outputFileNameMapping>javaee7-docker-maven.war</outputFileNameMapping>
    </dependencySet>
  </dependencySets>
</assembly>

<id>javaee7-docker-maven</id>

<include>org.javaee7.sample:javaee7-docker-maven</include>

</includes>

<outputDirectory>/opt/jboss/wildfly/standalone/deployments/</outputDirectory>

<outputFileNameMapping>javaee7-docker-maven.war</outputFileNameMapping>

</dependencySet>

</dependencySets>

</assembly>

<run> that defines how the container is run. Ports that need to be exposed are specified here.

In addition, package phase is tied to docker:build goal and install phase is tied to docker:start goal.

There are four docker-maven-plugin and you can read more details in the shootout on what serves your purpose the best.

How are you creating your Docker images from existing applications?

Enjoy!

WildFly Swarm: Building Microservices with Java EE

May 6, 2015microservices, wildflyjavaee7, microservices, swarm, wildflyarungupta

Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away

Antoine de Saint-Exupery

This quote by the French writer Antoine de Saint-Exupery was made to substantiate that often less is more. This is true for architect, artist, designer, writer, running, software developer, or in any other profession. Simplicity, minimalism, cutting down the cruft always goes a long way and has several advantages as opposed to something bloated.

What is WildFly Swarm?

WildFly is a light weight, flexible, feature rich, Java EE 7 compliant application server. WildFly 9 even introduced a 27MB Servlet-only distribution. These are very well suited for your enterprise and web applications.

WildFly Swarm takes the notch a bit higher. From the announcement:

WildFly Swarm is a new sidecar project supporting WildFly 9.x to enable deconstructing the WildFly AS and pasting just enough of it back together with your application to create a self-contained executable jar.

WildFly Swarm

The typical application development model for a Java EE application is to create an EAR or WAR archive and deploy it in an application server. All the dependencies, such as Java EE implementations are packaged in the application server and provide the functionality required by the application classes. Multiple archives can be deployed and they all share the same libraries. This is a well understood model and have been used over the past several years.

WildFly Swarm turns the table where it creates a “fat jar” that has all the dependencies packaged in a JAR file. This includes a minimalist version of WildFly, any required dependencies, and of course, the application code itself. The application can simply be run using java -jar.

Each fat jar could possibly be a microservice which can then independently upgrade, replace, or scale. Each fat jar would typically follow single responsibility principle and thus will have only the required dependencies packaged. Each JAR can use polyglot persistence, and use only the persistence mechanism that is required.

Show me the code!

A Java EE application can be packaged as WildFly Swarm fat jar by adding a Maven dependency and a plugin. Complete source code for a simple JAX-RS sample is available at github.com/arun-gupta/wildfly-samples/tree/master/swarm.

WildFly Swarm Maven Dependency

Add the following Maven dependency in pom.xml:

<dependency>
    <groupId>org.wildfly.swarm</groupId>
    <artifactId>wildfly-swarm-jaxrs</artifactId>
    <version>${version.wildfly-swarm}</version>
    <scope>provided</scope>
</dependency>

<groupId>org.wildfly.swarm</groupId>

<artifactId>wildfly-swarm-jaxrs</artifactId>

<version>${version.wildfly-swarm}</version>

<scope>provided</scope>

</dependency>

WildFly Swarm Maven Plugin

Add the following Maven plugin in pom.xml:

<plugin>
    <groupId>org.wildfly.swarm</groupId>
    <artifactId>wildfly-swarm-plugin</artifactId>
    <version>${version.wildfly-swarm}</version>
    <executions>
        <execution>
            <phase>package</phase>
            <goals>
                <goal>create</goal>
            </goals>
        </execution>
    </executions>
</plugin>

<groupId>org.wildfly.swarm</groupId>

<artifactId>wildfly-swarm-plugin</artifactId>

<version>${version.wildfly-swarm}</version>

<phase>package</phase>

<goals>

<goal>create</goal>

</goals>

</execution>

</executions>

</plugin>

Create WildFly Swarm Fat Jar

The fat jar can be easily created by invoking the standard Maven target:

mvn package

mvn package

This generates a JAR file using the usual Maven conventions, and appends -swarm at the end. The generated WAR file name in our sample is swarm-1.0-SNAPSHOT-swarm.jar.

The generated WAR file is ~30MB, has 134 JARs (all in m2repo directory), and 211 classes. The application code is bundled in app/swarm-1.0-SNAPSHOT.war.

Run WildFly Swarm Fat Jar

This far jar can be run as:

swarm> java -jar target/swarm-1.0-SNAPSHOT-swarm.jar 
12:27:10,622 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final
12:27:10,739 INFO  [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Core 1.0.0.CR1 "Kenny" starting
2015-05-06 12:27:11,185 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 11) WFLYSEC0002: Activating Security Subsystem
2015-05-06 12:27:11,189 INFO  [org.jboss.as.security] (MSC service thread 1-10) WFLYSEC0001: Current PicketBox version=4.9.0.Beta2
2015-05-06 12:27:11,194 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 13) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
2015-05-06 12:27:11,199 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 12) WFLYNAM0001: Activating Naming Subsystem
2015-05-06 12:27:11,246 INFO  [org.jboss.as.naming] (MSC service thread 1-12) WFLYNAM0003: Starting Naming Service
2015-05-06 12:27:11,319 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 1.2.4.Final starting
2015-05-06 12:27:11,319 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 14) WFLYUT0003: Undertow 1.2.4.Final starting
2015-05-06 12:27:11,337 INFO  [org.xnio] (MSC service thread 1-7) XNIO version 3.3.1.Final
2015-05-06 12:27:11,343 INFO  [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.3.1.Final
2015-05-06 12:27:11,369 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-13) WFLYUT0012: Started server default-server.
2015-05-06 12:27:11,409 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080
2015-05-06 12:27:11,543 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 1.0.0.CR1 "Kenny" started in 855ms - Started 64 of 70 services (13 services are lazy, passive or on-demand)
2015-05-06 12:27:11,570 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "swarm-1.0-SNAPSHOT.war" (runtime-name: "swarm-1.0-SNAPSHOT.war")
2015-05-06 12:27:11,724 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
2015-05-06 12:27:11,906 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-14) Deploying javax.ws.rs.core.Application: class org.wildfly.samples.swarm.MyApplication
2015-05-06 12:27:11,923 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-14) WFLYUT0021: Registered web context: /
2015-05-06 12:27:11,944 INFO  [org.jboss.as.server] (main) WFLYSRV0010: Deployed "swarm-1.0-SNAPSHOT.war" (runtime-name : "swarm-1.0-SNAPSHOT.war")

swarm> java -jar target/swarm-1.0-SNAPSHOT-swarm.jar

12:27:10,622 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final

12:27:10,739 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Core 1.0.0.CR1 "Kenny" starting

2015-05-06 12:27:11,185 INFO [org.jboss.as.security] (ServerService Thread Pool -- 11) WFLYSEC0002: Activating Security Subsystem

2015-05-06 12:27:11,189 INFO [org.jboss.as.security] (MSC service thread 1-10) WFLYSEC0001: Current PicketBox version=4.9.0.Beta2

2015-05-06 12:27:11,194 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 13) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors

2015-05-06 12:27:11,199 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 12) WFLYNAM0001: Activating Naming Subsystem

2015-05-06 12:27:11,246 INFO [org.jboss.as.naming] (MSC service thread 1-12) WFLYNAM0003: Starting Naming Service

2015-05-06 12:27:11,319 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 1.2.4.Final starting

2015-05-06 12:27:11,319 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 14) WFLYUT0003: Undertow 1.2.4.Final starting

2015-05-06 12:27:11,337 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.3.1.Final

2015-05-06 12:27:11,343 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.3.1.Final

2015-05-06 12:27:11,369 INFO [org.wildfly.extension.undertow] (MSC service thread 1-13) WFLYUT0012: Started server default-server.

2015-05-06 12:27:11,409 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080

2015-05-06 12:27:11,543 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core 1.0.0.CR1 "Kenny" started in 855ms - Started 64 of 70 services (13 services are lazy, passive or on-demand)

2015-05-06 12:27:11,570 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "swarm-1.0-SNAPSHOT.war" (runtime-name: "swarm-1.0-SNAPSHOT.war")

2015-05-06 12:27:11,724 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting

2015-05-06 12:27:11,906 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-14) Deploying javax.ws.rs.core.Application: class org.wildfly.samples.swarm.MyApplication

2015-05-06 12:27:11,923 INFO [org.wildfly.extension.undertow] (MSC service thread 1-14) WFLYUT0021: Registered web context: /

2015-05-06 12:27:11,944 INFO [org.jboss.as.server] (main) WFLYSRV0010: Deployed "swarm-1.0-SNAPSHOT.war" (runtime-name : "swarm-1.0-SNAPSHOT.war")

The response can be verified as:

target> curl -v http://127.0.0.1:8080/resources/resource
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> GET /resources/resource HTTP/1.1
> User-Agent: curl/7.37.1
> Host: 127.0.0.1:8080
> Accept: */*
> 
< HTTP/1.1 200 OK
< Connection: keep-alive
< Content-Type: application/octet-stream
< Content-Length: 12
< Date: Wed, 06 May 2015 19:29:10 GMT
< 
* Connection #0 to host 127.0.0.1 left intact
hello swarm!

target> curl -v http://127.0.0.1:8080/resources/resource

* Hostname was NOT found in DNS cache

* Trying 127.0.0.1...

* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)

> GET /resources/resource HTTP/1.1

> User-Agent: curl/7.37.1

> Host: 127.0.0.1:8080

> Accept: */*

< HTTP/1.1 200 OK

< Connection: keep-alive

< Content-Type: application/octet-stream

< Content-Length: 12

< Date: Wed, 06 May 2015 19:29:10 GMT

* Connection #0 to host 127.0.0.1 left intact

hello swarm!

WildFly Swarm Release blog refers to lots of blogs about Servlet, JAX-RS with ShrinkWrap, DataSource via Deployment, Messaging and JAX-RS, and much more.

WildFly Swarm Next Steps

This is only 1.0.0.Alpha1 release so feel free to try out samples and give us feedback by filing an issue.

You have the power of all WildFly subsystems, and can even create embeddable Java EE container as shown in the release blog:

public class Main {

    public static void main(String[] args) throws Exception {
        Container container = new Container();

        container.subsystem(new MessagingFraction()
                        .server(
                                new MessagingServer()
                                        .enableInVmConnector()
                                        .topic("my-topic")
                                        .queue("my-queue")
                        )
        );

        // Start the container
        container.start();

        JaxRsDeployment appDeployment = new JaxRsDeployment();
        appDeployment.addResource(MyResource.class);

        // Deploy your JAX-RS app
        container.deploy(appDeployment);

        // Create an MSC deployment
        ServiceDeployment deployment = new ServiceDeployment();
        deployment.addService(new MyService("/jms/topic/my-topic" ) );

        // Deploy the services
        container.deploy( deployment );
    }
}

public class Main {

public static void main(String[] args) throws Exception {

Container container = new Container();

container.subsystem(new MessagingFraction()

.server(

new MessagingServer()

.enableInVmConnector()

.topic("my-topic")

.queue("my-queue")

)

);

// Start the container

container.start();

JaxRsDeployment appDeployment = new JaxRsDeployment();

appDeployment.addResource(MyResource.class);

// Deploy your JAX-RS app

container.deploy(appDeployment);

// Create an MSC deployment

ServiceDeployment deployment = new ServiceDeployment();

deployment.addService(new MyService("/jms/topic/my-topic" ) );

// Deploy the services

container.deploy( deployment );

}

Subsequent blogs will show how a microservice can be easily created using WildFly Swarm.

WildFly Swarm Stay Connected

You can keep up with the project through the WildFly HipChat room, @wildflyswarm on Twitter, or through GitHub Issues.

WildFly 9.0 CR1 is Released – HTTP/2, Intelligent Load Balancing, Graceful shutdown, Offline CLI, more

May 2, 2015wildflyjavaee7, wildflyarungupta

WildFly 9.0 CR1 is now released, download from wildfly.org/downloads (zip)!

It builds upon the Java EE 7 compliance already achieved in earlier versions and adds the following features:

Intelligent load balancing
HTTP/2 and SPDY support
A new offline CLI mode
Server suspend, resume, and graceful shutdown
A new Servlet-only distribution

Release Notes provide complete details. 86 issues were fixed since 9.0.0 Beta 2.

How do you get started?

Download zip and unzip

Start as:

tools> ./wildfly-9.0.0.CR1/bin/standalone.sh 
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /Users/arungupta/tools/wildfly-9.0.0.CR1

  JAVA: /Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/bin/java

  JAVA_OPTS:  -server -XX:+UseCompressedOops  -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
14:33:43,229 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final
14:33:44,014 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final
14:33:44,075 INFO  [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 9.0.0.CR1 (WildFly Core 1.0.0.CR1) starting
14:33:44,857 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 10) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version!
14:33:44,875 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:33:44,890 INFO  [org.xnio] (MSC service thread 1-10) XNIO version 3.3.1.Final
14:33:44,897 INFO  [org.xnio.nio] (MSC service thread 1-10) XNIO NIO Implementation Version 3.3.1.Final
14:33:44,930 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
14:33:44,932 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
14:33:44,933 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
14:33:44,939 INFO  [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=4.9.0.Beta2
14:33:44,944 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
14:33:44,949 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
14:33:44,968 INFO  [org.jboss.remoting] (MSC service thread 1-10) JBoss Remoting version 4.0.9.Final
14:33:44,975 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
14:33:44,986 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
14:33:44,995 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:33:45,004 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.4.Final starting
14:33:45,004 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.2.4.Final starting
14:33:45,006 INFO  [org.jboss.as.connector] (MSC service thread 1-9) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final)
14:33:45,014 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2
14:33:45,110 INFO  [org.jboss.as.naming] (MSC service thread 1-14) WFLYNAM0003: Starting Naming Service
14:33:45,110 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
14:33:45,171 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path /Users/arungupta/tools/wildfly-9.0.0.CR1/welcome-content
14:33:45,183 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
14:33:45,198 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-15) WFLYUT0018: Host default-host starting
14:33:45,252 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080
14:33:45,342 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
14:33:45,393 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-15) WFLYDS0013: Started FileSystemDeploymentService for directory /Users/arungupta/tools/wildfly-9.0.0.CR1/standalone/deployments
14:33:45,471 INFO  [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final
14:33:45,556 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
14:33:45,557 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
14:33:45,557 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.0.CR1 (WildFly Core 1.0.0.CR1) started in 2579ms - Started 202 of 379 services (210 services are lazy, passive or on-demand)

tools> ./wildfly-9.0.0.CR1/bin/standalone.sh

=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /Users/arungupta/tools/wildfly-9.0.0.CR1

JAVA: /Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/bin/java

JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

14:33:43,229 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final

14:33:44,014 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final

14:33:44,075 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 9.0.0.CR1 (WildFly Core 1.0.0.CR1) starting

14:33:44,857 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 10) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version!

14:33:44,875 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)

14:33:44,890 INFO [org.xnio] (MSC service thread 1-10) XNIO version 3.3.1.Final

14:33:44,897 INFO [org.xnio.nio] (MSC service thread 1-10) XNIO NIO Implementation Version 3.3.1.Final

14:33:44,930 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors

14:33:44,932 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem

14:33:44,933 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.

14:33:44,939 INFO [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=4.9.0.Beta2

14:33:44,944 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.

14:33:44,949 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]

14:33:44,968 INFO [org.jboss.remoting] (MSC service thread 1-10) JBoss Remoting version 4.0.9.Final

14:33:44,975 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem

14:33:44,986 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension

14:33:44,995 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

14:33:45,004 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.4.Final starting

14:33:45,004 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.2.4.Final starting

14:33:45,006 INFO [org.jboss.as.connector] (MSC service thread 1-9) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final)

14:33:45,014 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2

14:33:45,110 INFO [org.jboss.as.naming] (MSC service thread 1-14) WFLYNAM0003: Starting Naming Service

14:33:45,110 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]

14:33:45,171 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path /Users/arungupta/tools/wildfly-9.0.0.CR1/welcome-content

14:33:45,183 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.

14:33:45,198 INFO [org.wildfly.extension.undertow] (MSC service thread 1-15) WFLYUT0018: Host default-host starting

14:33:45,252 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080

14:33:45,342 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]

14:33:45,393 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-15) WFLYDS0013: Started FileSystemDeploymentService for directory /Users/arungupta/tools/wildfly-9.0.0.CR1/standalone/deployments

14:33:45,471 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final

14:33:45,556 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management

14:33:45,557 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

14:33:45,557 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.0.CR1 (WildFly Core 1.0.0.CR1) started in 2579ms - Started 202 of 379 services (210 services are lazy, passive or on-demand)

Access the main page as localhost:8080 as shown:

Shutting down the server now shows the following log:

^C14:34:00,815 INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
14:34:00,826 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
14:34:00,827 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0019: Host default-host stopping
14:34:00,830 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-9) WFLYJCA0019: Stopped Driver service with driver-name = h2
14:34:00,832 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0008: Undertow HTTP listener default suspending
14:34:00,832 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0007: Undertow HTTP listener default stopped, was bound to /127.0.0.1:8080
14:34:00,835 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.2.4.Final stopping
14:34:00,845 INFO  [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: WildFly Full 9.0.0.CR1 (WildFly Core 1.0.0.CR1) stopped in 16ms

^C14:34:00,815 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.

14:34:00,826 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]

14:34:00,827 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0019: Host default-host stopping

14:34:00,830 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-9) WFLYJCA0019: Stopped Driver service with driver-name = h2

14:34:00,832 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0008: Undertow HTTP listener default suspending

14:34:00,832 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0007: Undertow HTTP listener default stopped, was bound to /127.0.0.1:8080

14:34:00,835 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 1.2.4.Final stopping

14:34:00,845 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: WildFly Full 9.0.0.CR1 (WildFly Core 1.0.0.CR1) stopped in 16ms

You can already configure this in JBoss Tools Alpha 2. Its currently not supported in NetBeans and has been filed as #252197.

Configure JRebel with Docker containers – Tech Tip #81

March 18, 2015containers, javaee, techtip, wildflyeclipse, javaee7, jbosstools, jrebel, wildflyarungupta

JRebel allows you to skip build and redeploy process by instantly deploying your application to the application server of your choice. It is supported in all the major IDEs such as NetBeans, Eclipse, and IntelliJ. It is also supported in a wide variety of application servers such as JBoss EAP, WildFly, WebLogic, WebsFear (err, WebSphere), Tomcat, and many others.

You can easily get started with JRebel in JBoss Developer Studio or Integrate JRebel with JBoss on your local desktop. It can also be easily used with JBoss Developer Studio and Ticket Monster on OpenShift.

This Tech Tip will explain how do you set up JRebel with Docker containers. Specifically, we’ll use the sample application provided by Java EE 7 Hands-on Lab (jrebel branch), JBoss Tools with Eclipse Mars M5, and running the sample application in WildFly Docker container.

Many thanks to Adam Koblentz (@akoblentz) for helping me through the steps!

Lets get started!

Install JRebel in Eclipse

JRebel runs in three modes:

Local: App server is running from inside the IDE
External: App server is running from outside the IDE, such as using CLI, but on the same machine
Remote: App server is running on a different machine, VM, container, or cloud

Docker containers need to be configured using the “remote” mode.

Install JBoss Tools as explained at tools.jboss.org/downloads/. JRebel’s remote mode can only be enabled using the IDE. Install JRebel plugin from Eclipse Marketplace.

Package rebel.xml and rebel-remote.xml with the WAR

These files define the location of classes and resources in your archive.

Clone the Java EE 7 HOL repo:

git clone https://github.com/javaee-samples/javaee7-hol.git

git clone https://github.com/javaee-samples/javaee7-hol.git

Import the Maven project (from the solution directory) in the IDE, right-click on the project, select JRebel menu, and click on “Enable JRebel Nature”. This will generate rebel.xml in src/main/resources directory and would look something like:

<?xml version="1.0" encoding="UTF-8"?>
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.zeroturnaround.com" xsi:schemaLocation="http://www.zeroturnaround.com http://www.zeroturnaround.com/alderaan/rebel-2_0.xsd">

        <classpath>
                <dir name="/Users/arungupta/workspaces/javaee7-hol/solution/movieplex7/target/classes">
                </dir>
        </classpath>

        <web>
                <link target="/">
                        <dir name="/Users/arungupta/workspaces/javaee7-hol/solution/movieplex7/target/m2e-wtp/web-resources">
                                <exclude name="/"/>
                        </dir>
                </link>
                <link target="/">
                        <dir name="/Users/arungupta/workspaces/javaee7-hol/solution/movieplex7/src/main/webapp">
                        </dir>
                </link>
        </web>

</application>

<?xml version="1.0" encoding="UTF-8"?>

</dir>

</classpath>

<web>

</dir>

</link>

</dir>

</link>

</web>

</application>

Right-click on the project again, and select “Enable Remoting”. This generates rebel-remote.xml, in src/main/resources directory again, and will look like:

<?xml version="1.0" encoding="UTF-8"?>
<rebel-remote>
    <id>movieplex7</id>
    <publicKey>XXXXXXX</publicKey>
</rebel-remote>

<?xml version="1.0" encoding="UTF-8"?>

<rebel-remote>

<id>movieplex7</id>

<publicKey>XXXXXXX</publicKey>

</rebel-remote>

This needs to be done on the machine where JRebel will be used in the IDE. This will ensure that the public key is generated appropriately.

Package your application as

mvn package

mvn package

This will package rebel.xml and rebel-remote.xml in the WAR file.

Configure and Run the Application Server

Application server needs to know about JRebel agent and platform-specific library. Both of these files are available from Eclipse if JRebel was installed earlier. On Mac these files are available in eclipse/mars/m5/eclipse/plugins/org.zeroturnaround.eclipse.embedder_6.1.1.RELEASE-201503121801/jr6/jrebel/ directory. The exact name would very likely differ in your case.

Build the image using the Dockerfile:

FROM jboss/wildfly

COPY jrebel.jar $JBOSS_HOME/jrebel.jar
COPY libjrebel64.so $JBOSS_HOME/libjrebel64.so

RUN echo "JAVA_OPTS=\"\$JAVA_OPTS -Drebel.remoting_plugin=true -agentpath:\$JBOSS_HOME/libjrebel64.so\"" >> $JBOSS_HOME/bin/standalone.conf

CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone-full.xml", "-b", "0.0.0.0"]

RUN curl -L https://github.com/javaee-samples/javaee7-hol/blob/jrebel/solution/movieplex7-1.0-SNAPSHOT.war?raw=true -o /opt/jboss/wildfly/standalone/deployments/movieplex7-1.0-SNAPSHOT.war

FROM jboss/wildfly

COPY jrebel.jar $JBOSS_HOME/jrebel.jar

COPY libjrebel64.so $JBOSS_HOME/libjrebel64.so

RUN echo "JAVA_OPTS=\"\$JAVA_OPTS -Drebel.remoting_plugin=true -agentpath:\$JBOSS_HOME/libjrebel64.so\"" >> $JBOSS_HOME/bin/standalone.conf

CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone-full.xml", "-b", "0.0.0.0"]

RUN curl -L https://github.com/javaee-samples/javaee7-hol/blob/jrebel/solution/movieplex7-1.0-SNAPSHOT.war?raw=true -o /opt/jboss/wildfly/standalone/deployments/movieplex7-1.0-SNAPSHOT.war

The key parts in this image are:

Using the official jboss/wildfly Docker image
Copying the JRebel agent and platform-specific library to the image
Configuring application server such that it knows about the “remote” mode and platform-specific library
Start WildFly

Downloads the pre-built WAR file from GitHub. This will not work for you, and you’ll need to replace it with something like:

COPY movieplex7-1.0-SNAPSHOT.war $JBOSS_HOME/standalone/deployments/moviexplex7-1.0-SNAPSHOT.war

COPY movieplex7-1.0-SNAPSHOT.war $JBOSS_HOME/standalone/deployments/moviexplex7-1.0-SNAPSHOT.war

This WAR file is the same that was generated earlier.

Actually build the image as:

docker build -t javaee7-hol .

docker build -t javaee7-hol .

Run the container as:

docker run -it -p 8080:8080 javaee7-hol

docker run -it -p 8080:8080 javaee7-hol

and this should show something like:

JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Drebel.remoting_plugin=true -agentpath:/opt/jboss/wildfly/libjrebel64.so

=========================================================================

Mar 18, 2015 8:37:30 PM java.util.prefs.FileSystemPreferences$1 run
INFO: Created user preferences directory.
2015-03-18 20:37:40 JRebel:  
2015-03-18 20:37:40 JRebel:  #############################################################
2015-03-18 20:37:40 JRebel:  
2015-03-18 20:37:40 JRebel:  JRebel Agent 6.1.1 (201503111716)
2015-03-18 20:37:40 JRebel:  (c) Copyright ZeroTurnaround AS, Estonia, Tartu.
2015-03-18 20:37:40 JRebel:  
2015-03-18 20:37:40 JRebel:  Over the last 1 days JRebel prevented
2015-03-18 20:37:40 JRebel:  at least 0 redeploys/restarts saving you about 0 hours.
2015-03-18 20:37:40 JRebel:  
2015-03-18 20:37:40 JRebel:  Server is running with JRebel Remoting.
2015-03-18 20:37:40 JRebel:  
2015-03-18 20:37:40 JRebel:  
2015-03-18 20:37:40 JRebel:  #############################################################
2015-03-18 20:37:40 JRebel:  
20:37:46,219 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
20:37:47,340 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final

JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Drebel.remoting_plugin=true -agentpath:/opt/jboss/wildfly/libjrebel64.so

=========================================================================

Mar 18, 2015 8:37:30 PM java.util.prefs.FileSystemPreferences$1 run

INFO: Created user preferences directory.

2015-03-18 20:37:40 JRebel:

2015-03-18 20:37:40 JRebel: #############################################################

2015-03-18 20:37:40 JRebel:

2015-03-18 20:37:40 JRebel: JRebel Agent 6.1.1 (201503111716)

2015-03-18 20:37:40 JRebel: (c) Copyright ZeroTurnaround AS, Estonia, Tartu.

2015-03-18 20:37:40 JRebel:

2015-03-18 20:37:40 JRebel: Over the last 1 days JRebel prevented

2015-03-18 20:37:40 JRebel: at least 0 redeploys/restarts saving you about 0 hours.

2015-03-18 20:37:40 JRebel:

2015-03-18 20:37:40 JRebel: Server is running with JRebel Remoting.

2015-03-18 20:37:40 JRebel:

2015-03-18 20:37:40 JRebel: #############################################################

2015-03-18 20:37:40 JRebel:

20:37:46,219 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final

20:37:47,340 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final

JRebel license information is a good sign that everything is configured properly.

If you used Docker Machine to Setup Docker Host then the application should now be accessible at 192.168.99.100:8080/movieplex7/.

Configure Eclipse

Last step is to configure Eclipse so that it knows where the application is deployed.

In Eclipse, right-click on the project, select JRebel, Advanced Properties
Click on “Edit” on next to “Deployment URLs”
Click on Add and specify the URL of the application, 192.168.99.100:8080/movieplex7/ in our case.
Click on Continue, Apply, OK.

Voila, the configuration is now complete.

Now changing any class, adding any method, updating any entity or HTML or JSF page will push the changes to the Docker container instantly. No need to redeploy the application.

Enjoy!

Deploy to WildFly and Docker from Eclipse – Tech Tip #79

March 10, 2015containers, javaee, wildflydocker, eclipse, javaee7, jbosstools, wildflyarungupta

Docker and WildFly Part 1 – Deployment via Volumes and Docker and WildFly Part 2 – Deployment over Management API shows two approaches of how JBoss Tools can be configured to run any application on WildFly server running as a Docker container.

The blogs provide detailed setup and the underlying background. This Tech Tip will provide a quick summary of how to deploy a Java EE 7 application to WildFly and Docker from Eclipse.

Lets get started!

Configure Docker

Configure Docker on your machine using Docker Machine.

Find the IP address as:

docker-machine ip

docker-machine ip

and add an entry in /etc/hosts as:

192.168.99.101  dockerhost

192.168.99.101 dockerhost

Deployment to WildFly Container using Docker Volumes

Create a folder that will be mounted as volume in the WildFly Docker container. In this case, the folder is /Users/arungupta/tmp/deployments.WildFly Docker container can be started as:

docker run -it -p 8080:8080 -v /Users/arungupta/tmp/deployments:/opt/jboss/wildfly/standalone/deployments/:rw jboss/wildfly

docker run -it -p 8080:8080 -v /Users/arungupta/tmp/deployments:/opt/jboss/wildfly/standalone/deployments/:rw jboss/wildfly

rw ensures that the Docker container can write to it.

Create a new server adapter:
Assign or create a WildFly 8.x runtime:

Changed properties are highlighted.
Setup the server properties as:

Changed properties are highlighted. The 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”.

Status quickly changes to “Started, Synchronized” as shown.
Open up any Java EE 7 project (for example javaee7-simple-sample), right-click, Run on Server, and chose this server. The project runs and displays the page:

Deployment to WildFly Container using Management API

Run WildFly management image as:

docker run -it -p 8080:8080 -p 9990:9990 arungupta/wildfly-management

docker run -it -p 8080:8080 -p 9990:9990 arungupta/wildfly-management

This is only a convenience image to reduce the number of steps required to get started. Dockerfile for this image has more details, including admin credentials.

Volume mapping is not required in this case, instead additional management port is exposed.

Configure a remote server controlled by management operations:
Changed properties are highlighted.
Take the defaults:
Set up server properties by specifying the admin credentials (Admin#70365). 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, Synchronized” as shown.
Open up any Java EE 7 project (for example javaee7-simple-sample), right-click, Run on Server, and chose this server. The project runs and displays the page:

Enjoy!

This blog showed how how to deploy a Java EE 7 application to WildFly and Docker from Eclipse.

Is there any other way that you deploy to WildFly Docker container from Eclipse?

Docker Machine to Setup Docker Host – Tech Tip #78

March 9, 2015containers, techtip, wildflydocker, javaee7, wildflyarungupta

Running Docker containers typically involve three components:

Docker Client is a binary that accepts commands from the user and communicates back and forth with host
Docker Daemon runs on a host machine and does the heavy lifting of building, running, and distributing Docker containers
Docker Registry is SaaS platform for sharing and managing Docker images.Docker Hub is a public hub. Private registries can be easily setup as well, such as one by Artifactory. More on this in a subsequent blog.

Docker Client communicates with Daemon, either co-located on the same host, or on a different host. It requests the Daemon to pull an image from the repository using pull command. The Daemon then downloads the image from Docker Hub, or whatever registry is configured. Multiple images can be downloaded from the registry and installed on Daemon host.

In a typical development environment setup, Docker Client and Host/Daemon will be co-located on the same host machine. Even if they are on separate machines, it still require to login to the Host and setup Docker Daemon for that OS.

Docker Machine takes you from zero-to-Docker on a host with a single command. This host could be your laptop, in the cloud, or in your data center. It creates servers, installs Docker on them, then configures the Docker client to talk to them.

This downloads the boot2docker VM, setup ssh keys, generate certificates, start the VM. It basically takes care of all the boring work so that you can focus on all the fun things.

This Tech Tip will show you to get started with Docker Machine and use it to setup Docker Host on Mac. It does not work on Windows yet because of github.com/docker/machine/issues/742.

Lets get started!

Install Docker Machine

Download the appropriate binary from docs.docker.com/machine/#installation. Binary for Mac can be downloaded as:

~> curl -L https://github.com/docker/machine/releases/download/v0.1.0/docker-machine_darwin-amd64 > /usr/local/bin/docker-machine
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   403    0   403    0     0    725      0 --:--:-- --:--:-- --:--:--   726
100 15.5M  100 15.5M    0     0  2276k      0  0:00:06  0:00:06 --:--:-- 3362k
~> chmod +x /usr/local/bin/docker-machine

~> curl -L https://github.com/docker/machine/releases/download/v0.1.0/docker-machine_darwin-amd64 > /usr/local/bin/docker-machine

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 403 0 403 0 0 725 0 --:--:-- --:--:-- --:--:-- 726

100 15.5M 100 15.5M 0 0 2276k 0 0:00:06 0:00:06 --:--:-- 3362k

~> chmod +x /usr/local/bin/docker-machine

Verify the installation as:

~> docker-machine -v
docker-machine version 0.1.0

~> docker-machine -v

docker-machine version 0.1.0

Setup Mac Host using Docker Machine

Docker Machine can be configured to use with multiple drivers, such as Amazon Web Services, Google Compute Engine, Microsoft Azure, and Oracle VirtualBox. On a developer laptop, Virtual Box is a convenient option.Virtual Box 4.3.20 is the minimum requirement. So make sure you’ve the correct version installed.

Create a Docker Host using VirtualBox provider and call the machine as “mydocker”.Make sure ssh-keygen is in the PATH before invoking this command. On Mac, this is already in /usr/bin/ssh-keygen. On Windows, this can be installed as part of Git Bash.This can be done as:

~> docker-machine create --driver virtualbox mydocker
INFO[0000] Creating CA: /Users/arungupta/.docker/machine/certs/ca.pem 
INFO[0000] Creating client certificate: /Users/arungupta/.docker/machine/certs/cert.pem 
INFO[0002] Downloading boot2docker.iso to /Users/arungupta/.docker/machine/cache/boot2docker.iso... 
INFO[0006] Creating SSH key...                          
INFO[0007] Creating VirtualBox VM...                    
INFO[0018] Starting VirtualBox VM...                    
INFO[0018] Waiting for VM to start...                   
INFO[0051] "mydocker" has been created and is now the active machine. 
INFO[0051] To point your Docker client at it, run this in your shell: $(docker-machine env mydocker)

~> docker-machine create --driver virtualbox mydocker

INFO[0000] Creating CA: /Users/arungupta/.docker/machine/certs/ca.pem

INFO[0000] Creating client certificate: /Users/arungupta/.docker/machine/certs/cert.pem

INFO[0002] Downloading boot2docker.iso to /Users/arungupta/.docker/machine/cache/boot2docker.iso...

INFO[0006] Creating SSH key...

INFO[0007] Creating VirtualBox VM...

INFO[0018] Starting VirtualBox VM...

INFO[0018] Waiting for VM to start...

INFO[0051] "mydocker" has been created and is now the active machine.

INFO[0051] To point your Docker client at it, run this in your shell: $(docker-machine env mydocker)

This downloads boot2docker with the Docker daemon installed, and will create and start a VirtualBox VM with Docker running.

Find IP address of the machine as:

~> docker-machine ip
192.168.99.101

~> docker-machine ip

192.168.99.101

Note down this IP address, this will be used for accessing the application.

Check the status of running machine as:

~> docker-machine ls
NAME       ACTIVE   DRIVER       STATE     URL                         SWARM
mydocker   *        virtualbox   Running   tcp://192.168.99.101:2376

~> docker-machine ls

NAME ACTIVE DRIVER STATE URL SWARM

mydocker * virtualbox Running tcp://192.168.99.101:2376

The * in the ACTIVE column indicates this is an active host.

Check the environment of newly created machine as:

~> docker-machine env mydocker
export DOCKER_TLS_VERIFY=yes
export DOCKER_CERT_PATH=/Users/arungupta/.docker/machine/machines/mydocker
export DOCKER_HOST=tcp://192.168.99.101:2376

~> docker-machine env mydocker

export DOCKER_TLS_VERIFY=yes

export DOCKER_CERT_PATH=/Users/arungupta/.docker/machine/machines/mydocker

export DOCKER_HOST=tcp://192.168.99.101:2376

Setup Docker client to Communicate

Setup your client to talk to this host as:

$(docker-machine env mydocker)

$(docker-machine env mydocker)

Run Java Application on Host

Run Java EE 7 Application discussed in Java EE 7 Hands-on Lab on WildFly and Docker on this host as:

docker run -it -p 8080:8080 arungupta/javaee7-hol
Unable to find image 'arungupta/javaee7-hol' locally
Pulling repository arungupta/javaee7-hol
a068decaf892: Download complete 
511136ea3c5a: Download complete 
5b12ef8fd570: Download complete 
ae0c2d0bdc10: Download complete 

. . .

03:13:20,449 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-12) Adding provider class org.javaee7.movieplex7.json.MovieReader from Application class org.javaee7.movieplex7.rest.ApplicationConfig
03:13:20,554 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-12) JBAS017534: Registered web context: /movieplex7
03:13:20,596 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "movieplex7-1.0-SNAPSHOT.war" (runtime-name : "movieplex7-1.0-SNAPSHOT.war")
03:13:20,674 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
03:13:20,675 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
03:13:20,675 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 10513ms - Started 400 of 452 services (104 services are lazy, passive or on-demand)

docker run -it -p 8080:8080 arungupta/javaee7-hol

Unable to find image 'arungupta/javaee7-hol' locally

Pulling repository arungupta/javaee7-hol

a068decaf892: Download complete

511136ea3c5a: Download complete

5b12ef8fd570: Download complete

ae0c2d0bdc10: Download complete

. . .

03:13:20,449 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-12) Adding provider class org.javaee7.movieplex7.json.MovieReader from Application class org.javaee7.movieplex7.rest.ApplicationConfig

03:13:20,554 INFO [org.wildfly.extension.undertow] (MSC service thread 1-12) JBAS017534: Registered web context: /movieplex7

03:13:20,596 INFO [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "movieplex7-1.0-SNAPSHOT.war" (runtime-name : "movieplex7-1.0-SNAPSHOT.war")

03:13:20,674 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

03:13:20,675 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

03:13:20,675 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 10513ms - Started 400 of 452 services (104 services are lazy, passive or on-demand)

Access the application at 192.168.99.101:8080/movieplex7/ and looks like:

Docker Machine Commands

Complete list of Docker Machine commands can be seen as:

~> docker-machine 
NAME:
   docker-machine - Create and manage machines running Docker.

USAGE:
   docker-machine [global options] command [command options] [arguments...]

VERSION:
   0.1.0

AUTHOR:
  Docker Machine Contributors - <https://github.com/docker/machine>

COMMANDS:
   active          Get or set the active machine
   create       Create a machine
   config          Print the connection config for machine
   inspect        Inspect information about a machine
   ip                  Get the IP address of a machine
   kill              Kill a machine
   ls                  List machines
   restart        Restart a machine
   rm                  Remove a machine
   env                Display the commands to set up the environment for the Docker client
   ssh                Log into or run a command on a machine with SSH
   start            Start a machine
   stop              Stop a machine
   upgrade        Upgrade a machine to the latest version of Docker
   url                Get the URL of a machine
   help, h        Shows a list of commands or help for one command
   
GLOBAL OPTIONS:
   --debug, -D                                                          Enable debug mode
   --storage-path "/Users/arungupta/.docker/machine"                    Configures storage path [$MACHINE_STORAGE_PATH]
   --tls-ca-cert "/Users/arungupta/.docker/machine/certs/ca.pem"        CA to verify remotes against [$MACHINE_TLS_CA_CERT]
   --tls-ca-key "/Users/arungupta/.docker/machine/certs/ca-key.pem"     Private key to generate certificates [$MACHINE_TLS_CA_KEY]
   --tls-client-cert "/Users/arungupta/.docker/machine/certs/cert.pem"  Client cert to use for TLS [$MACHINE_TLS_CLIENT_CERT]
   --tls-client-key "/Users/arungupta/.docker/machine/certs/key.pem"    Private key used in client TLS auth [$MACHINE_TLS_CLIENT_KEY]
   --help, -h                                                           show help
   --version, -v                                                        print the version

~> docker-machine

NAME:

docker-machine - Create and manage machines running Docker.

USAGE:

docker-machine [global options] command [command options] [arguments...]

VERSION:

0.1.0

AUTHOR:

Docker Machine Contributors - <https://github.com/docker/machine>

COMMANDS:

active Get or set the active machine

create Create a machine

config Print the connection config for machine

inspect Inspect information about a machine

ip Get the IP address of a machine

kill Kill a machine

ls List machines

restart Restart a machine

rm Remove a machine

env Display the commands to set up the environment for the Docker client

ssh Log into or run a command on a machine with SSH

start Start a machine

stop Stop a machine

upgrade Upgrade a machine to the latest version of Docker

url Get the URL of a machine

help, h Shows a list of commands or help for one command

GLOBAL OPTIONS:

--debug, -D Enable debug mode

--storage-path "/Users/arungupta/.docker/machine" Configures storage path [$MACHINE_STORAGE_PATH]

--tls-ca-cert "/Users/arungupta/.docker/machine/certs/ca.pem" CA to verify remotes against [$MACHINE_TLS_CA_CERT]

--tls-ca-key "/Users/arungupta/.docker/machine/certs/ca-key.pem" Private key to generate certificates [$MACHINE_TLS_CA_KEY]

--tls-client-cert "/Users/arungupta/.docker/machine/certs/cert.pem" Client cert to use for TLS [$MACHINE_TLS_CLIENT_CERT]

--tls-client-key "/Users/arungupta/.docker/machine/certs/key.pem" Private key used in client TLS auth [$MACHINE_TLS_CLIENT_KEY]

--help, -h show help

--version, -v print the version

Learn more about Docker Machine, Swarm, and Compose in this video:

Why would you use anything else other than Docker Machine to setup Docker host? How do you setup Docker Host otherwise?

Some useful references …

Full documentation
GitHub Repo
Issues
#docker-machine on freenode

Enjoy!

Docker Compose to Orchestrate Containers – Tech Tip #77

March 6, 2015containers, javaeecompose, docker, javaee7, mysql, wildflyarungupta

Docker Orchestration using Fig showed how to defining and control a multi-container service using Fig. Since then, Fig has been renamed to Docker Compose, or Compose for short.

First release of Compose was announced recently

Announcing @docker compose https://t.co/jJNvzbYCyk by @aanand @bfirsh & community!

— Docker (@docker) February 26, 2015

From github.com/docker/compose

Compose is a tool for defining and running complex applications with Docker. With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.

Docker Compose uses the same API used by other Docker commands and tools.

This Tech Tip will rewrite Docker Orchestration using Fig blog to use Docker Compose. In other words, it will show how to run a Java EE 7 application that is deployed using MySQL and WildFly.

Lets get started!

Install Docker Compose

Install Compose as:

curl -L https://github.com/docker/compose/releases/download/1.1.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

curl -L https://github.com/docker/compose/releases/download/1.1.0/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose

chmod +x /usr/local/bin/docker-compose

Docker Compose Configuration File

Entry point to Compose is docker-compose.yml. To begin with, docker-compose tool also recognizes fig.yml file name but shows the following message:

fig.yml is deprecated and will not be supported in future. Please rename your config file to docker-compose.yml

fig.yml is deprecated and will not be supported in future. Please rename your config file to docker-compose.yml

And if both fig.yml and docker-compose.yml are available in the directory then the following message is shown:

Found multiple config files with supported names: docker-compose.yml, fig.yml
Using docker-compose.yml

Found multiple config files with supported names: docker-compose.yml, fig.yml

Using docker-compose.yml

Use the same configuration file from the previous blog and rename to docker-compose.yml:

mysqldb:
  image: mysql:latest
  environment:
    MYSQL_DATABASE: sample
    MYSQL_USER: mysql
    MYSQL_PASSWORD: mysql
    MYSQL_ROOT_PASSWORD: supersecret
mywildfly:
  image: arungupta/wildfly-mysql-javaee7
  links:
    - mysqldb:db
  ports:
    - 8080:8080

mysqldb:

image: mysql:latest

environment:

MYSQL_DATABASE: sample

MYSQL_USER: mysql

MYSQL_PASSWORD: mysql

MYSQL_ROOT_PASSWORD: supersecret

mywildfly:

image: arungupta/wildfly-mysql-javaee7

links:

- mysqldb:db

ports:

- 8080:8080

This YML-based configuration file has:

Two containers defined by the name “mysqldb” and “mywildfly”
Image names are defined using “image”
Environment variables for the MySQL container are defined in “environment”
MySQL container is linked with WildFly container using “links”
Port forwarding is achieved using “ports”

Start, Verify, Stop Docker Containers

All the containers can be started, in detached mode, by giving the command:

docker-compose up -d

docker-compose up -d

And that shows the output as:

Creating wildflymysqljavaee7_mysqldb_1...
Creating wildflymysqljavaee7_mywildfly_1...

Creating wildflymysqljavaee7_mysqldb_1...

Creating wildflymysqljavaee7_mywildfly_1...

Verify the containers as:

docker-compose ps
             Name                            Command               State                Ports               
-----------------------------------------------------------------------------------------------------------
wildflymysqljavaee7_mysqldb_1     /entrypoint.sh mysqld --da ...   Up      3306/tcp                         
wildflymysqljavaee7_mywildfly_1   /opt/jboss/wildfly/customi ...   Up      0.0.0.0:8080->8080/tcp, 9990/tcp

docker-compose ps

Name Command State Ports

-----------------------------------------------------------------------------------------------------------

wildflymysqljavaee7_mysqldb_1 /entrypoint.sh mysqld --da ... Up 3306/tcp

wildflymysqljavaee7_mywildfly_1 /opt/jboss/wildfly/customi ... Up 0.0.0.0:8080->8080/tcp, 9990/tcp

Logs for the containers can be seen as:

docker-compose logs

docker-compose logs

And shows the output as:

mywildfly_1 | => Starting WildFly server
mywildfly_1 | => Waiting for the server to boot
mywildfly_1 | =========================================================================
mywildfly_1 | 
mywildfly_1 |   JBoss Bootstrap Environment
mywildfly_1 | 
mywildfly_1 |   JBOSS_HOME: /opt/jboss/wildfly
mywildfly_1 | 
mywildfly_1 |   JAVA: /usr/lib/jvm/java/bin/java
mywildfly_1 | 
mywildfly_1 |   JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true


. . .


mywildfly_1 | 18:43:38,449 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (6, 'Raj')
mywildfly_1 | 18:43:38,452 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (7, 'Howard')
mywildfly_1 | 18:43:38,455 INFO  [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (8, 'Priya')
mywildfly_1 | 18:43:39,714 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-9) Deploying javax.ws.rs.core.Application: class org.javaee7.samples.employees.MyApplication
mywildfly_1 | 18:43:39,751 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017534: Registered web context: /employees
mywildfly_1 | 18:43:39,805 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "employees.war" (runtime-name : "employees.war")
mywildfly_1 | 18:43:39,828 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
mywildfly_1 | 18:43:39,828 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
mywildfly_1 | 18:43:39,829 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 8393ms - Started 280 of 334 services (92 services are lazy, passive or on-demand)

mywildfly_1 | => Starting WildFly server

mywildfly_1 | => Waiting for the server to boot

mywildfly_1 | =========================================================================

mywildfly_1 |

mywildfly_1 | JBoss Bootstrap Environment

mywildfly_1 |

mywildfly_1 | JBOSS_HOME: /opt/jboss/wildfly

mywildfly_1 |

mywildfly_1 | JAVA: /usr/lib/jvm/java/bin/java

mywildfly_1 |

mywildfly_1 | JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

. . .

mywildfly_1 | 18:43:38,449 INFO [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (6, 'Raj')

mywildfly_1 | 18:43:38,452 INFO [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (7, 'Howard')

mywildfly_1 | 18:43:38,455 INFO [stdout] (ServerService Thread Pool -- 50) Hibernate: INSERT INTO EMPLOYEE_SCHEMA(ID, NAME) VALUES (8, 'Priya')

mywildfly_1 | 18:43:39,714 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-9) Deploying javax.ws.rs.core.Application: class org.javaee7.samples.employees.MyApplication

mywildfly_1 | 18:43:39,751 INFO [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017534: Registered web context: /employees

mywildfly_1 | 18:43:39,805 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "employees.war" (runtime-name : "employees.war")

mywildfly_1 | 18:43:39,828 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

mywildfly_1 | 18:43:39,828 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

mywildfly_1 | 18:43:39,829 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 8393ms - Started 280 of 334 services (92 services are lazy, passive or on-demand)

Find the IP address of the host as:

boot2docker ip

boot2docker ip

And access the application as:

curl http://192.168.59.103:8080/employees/resources/employees/

curl http://192.168.59.103:8080/employees/resources/employees/

To see the output as:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><collection><employee><id>1</id><name>Penny</name></employee><employee><id>2</id><name>Sheldon</name></employee><employee><id>3</id><name>Amy</name></employee><employee><id>4</id><name>Leonard</name></employee><employee><id>5</id><name>Bernadette</name></employee><employee><id>6</id><name>Raj</name></employee><employee><id>7</id><name>Howard</name></employee><employee><id>8</id><name>Priya</name></employee></collection>

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><collection><employee><id>1</id><name>Penny</name></employee><employee><id>2</id><name>Sheldon</name></employee><employee><id>3</id><name>Amy</name></employee><employee><id>4</id><name>Leonard</name></employee><employee><id>5</id><name>Bernadette</name></employee><employee><id>6</id><name>Raj</name></employee><employee><id>7</id><name>Howard</name></employee><employee><id>8</id><name>Priya</name></employee></collection>

Or in the browser as:

Stop the containers as:

docker-compose stop

docker-compose stop

to see the output as:

Stopping wildflymysqljavaee7_mywildfly_1...
Stopping wildflymysqljavaee7_mysqldb_1...

Stopping wildflymysqljavaee7_mywildfly_1...

Stopping wildflymysqljavaee7_mysqldb_1...

Docker Compose Commands

Complete list of Docker Compose commands can be seen by typing docker-compose and shows the output as:

velopment environments using Docker.

Usage:
  docker-compose [options] [COMMAND] [ARGS...]
  docker-compose -h|--help

Options:
  --verbose                 Show more output
  --version                 Print version and exit
  -f, --file FILE           Specify an alternate compose file (default: docker-compose.yml)
  -p, --project-name NAME   Specify an alternate project name (default: directory name)

Commands:
  build     Build or rebuild services
  help      Get help on a command
  kill      Kill containers
  logs      View output from containers
  port      Print the public port for a port binding
  ps        List containers
  pull      Pulls service images
  rm        Remove stopped containers
  run       Run a one-off command
  scale     Set number of containers for a service
  start     Start services
  stop      Stop services
  restart   Restart services
  up        Create and start containers

velopment environments using Docker.

Usage:

docker-compose [options] [COMMAND] [ARGS...]

docker-compose -h|--help

Options:

--verbose Show more output

--version Print version and exit

-f, --file FILE Specify an alternate compose file (default: docker-compose.yml)

-p, --project-name NAME Specify an alternate project name (default: directory name)

Commands:

build Build or rebuild services

help Get help on a command

kill Kill containers

logs View output from containers

port Print the public port for a port binding

ps List containers

pull Pulls service images

rm Remove stopped containers

run Run a one-off command

scale Set number of containers for a service

start Start services

stop Stop services

restart Restart services

up Create and start containers

A subsequent blog will likely play with scale command.

Help for each command is shown by typing -h after the command name. For example, help for run command is shown as:

docker-compose run -h
Run a one-off command on a service.

For example:

    $ docker-compose run web python manage.py shell

By default, linked services will be started, unless they are already
running. If you do not want to start linked services, use
`docker-compose run --no-deps SERVICE COMMAND [ARGS...]`.

Usage: run [options] [-e KEY=VAL...] SERVICE [COMMAND] [ARGS...]

Options:
    --allow-insecure-ssl  Allow insecure connections to the docker
                          registry
    -d                    Detached mode: Run container in the background, print
                          new container name.
    --entrypoint CMD      Override the entrypoint of the image.
    -e KEY=VAL            Set an environment variable (can be used multiple times)
    --no-deps             Don't start linked services.
    --rm                  Remove container after run. Ignored in detached mode.
    --service-ports       Run command with the service's ports enabled and mapped
                          to the host.
    -T                    Disable pseudo-tty allocation. By default `docker-compose run`
                          allocates a TTY.

docker-compose run -h

Run a one-off command on a service.

For example:

$ docker-compose run web python manage.py shell

By default, linked services will be started, unless they are already

running. If you do not want to start linked services, use

`docker-compose run --no-deps SERVICE COMMAND [ARGS...]`.

Usage: run [options] [-e KEY=VAL...] SERVICE [COMMAND] [ARGS...]

Options:

--allow-insecure-ssl Allow insecure connections to the docker

registry

-d Detached mode: Run container in the background, print

new container name.

--entrypoint CMD Override the entrypoint of the image.

-e KEY=VAL Set an environment variable (can be used multiple times)

--no-deps Don't start linked services.

--rm Remove container after run. Ignored in detached mode.

--service-ports Run command with the service's ports enabled and mapped

to the host.

-T Disable pseudo-tty allocation. By default `docker-compose run`

allocates a TTY.

Enjoy!

Build Binaries Only Once for Continuous Deployment

February 25, 2015devopsdevops, javaee7, nexus, wildflyarungupta

What is Build Binaries Only Once?

One of the fundamental principle of Continuous Delivery is Build Binaries Only Once, or in short BBOO. This means that the binary artifacts should be build once, and only once. These artifacts should then be stored in a repository manager, such as a Nexus Repository. Subsequent deploy, test, and release cycles should never attempt to build this binary again and instead reuse this binary. This ensures that the exact same binary has gone through all different test cycles and delivered to the customer.

Several times binaries are rebuilt during each testing phase using a specific tag of the workspace, and considered the same. But that is still different! This might turn out to be the same but that’s more incidental. Its more likely not same because of different environment configurations. For example, development team might be using JDK 8 on their machine and the test/staging might be using JDK 7. There are a multitude reasons because of which the binary artifacts could differ. So it’s very essential to build binaries only once, store them in a repository, and make them go through different test, staging, and production cycle. This increases the overall confidence level of delivery to the customer.

This image shows how the binaries are built once during Build stage and stored on Nexus repository. There after, Deploy, Test, and Release stages are only reading the binary from Nexus.

The fact that dev, test, and staging environments differ is a different issue. And we’ll deal with that in a subsequent blog.

How do you setup Build Binaries Only Once?

For now, lets look at the setup:

A Java EE 7 application WAR file is built once
Store in a Nexus repository, or .m2 local repository
Same binary is used for smoke testing
Same binary is used for running full test suite

The smoke test in our case will be just a single test and full suite has four tests. Hopefully this is not your typical setup in terms of the number of tests, but at least you get to see how to setup everything.

Also only two stages of testing, smoke and full but the concept can be easily extended to add other stages. A subsequent blog will show a full blown deployment pipeline.

Lets get started!

Check out a trivial Java EE 7 sample application from github.com/javaee-samples/javaee7-simple-sample. This is a typical Java EE application with REST endpoints, CDI beans, JPA entities.

Setup a local Nexus Repository and deploy a SNAPSHOT of the application to it as:

mvn deploy

mvn deploy

By default, Nexus repository is configured on localhost:8081/nexus. Note down the host/port if you are using a different combination. Also note down the exact version number that is deployed to Nexus. By default, it will be 1.0-SNAPSHOT.

You can also deploy a RELEASE to this Nexus repository as:

mvn release:clean release:prepare release:perform

mvn release:clean release:prepare release:perform

Note down whether you deployed SNAPSHOT or RELEASE.

In either case, you can also specify -P release Maven profile and sources and javadocs will be attached with the deployment. So if RELEASE is deployed as:

mvn release:clean release:prepare release:perform -P release

mvn release:clean release:prepare release:perform -P release

Then sources and javadocs are also attached.

Check out the test workspace from github.com/javaee-samples/javaee7-simple-sample-test. Make the following changes in this project:
1. Change nexus-repo property to match the host/port of the Nexus repository. If you used the default installation of Nexus and deployed a RELEASE, then nothing needs to be changed.By default, Nexus has one repository for SNAPSHOTs and another for RELEASEs. The workspace is configured to use RELEASE repository. If you deployed a SNAPSHOT, then “releases” in nexus-repo needs to be changed to “snapshots”to point to the appopriate repository.
2. Change javaee7-sample-app-version property to match the version of the application deployed to Nexus.

Start WildFly and run smoke tests as:

mvn test -P smoketest

mvn test -P smoketest

This will run all files ending in “SmokeTest”. ShrinkWrap and Arquillian perform the heavy lifting of resolving the WAR file from Nexus and using it for running the tests:

return Maven.configureResolver()
       .withRemoteRepo("local-nexus", System.getProperty("nexus-repo"), "default")
       .resolve("org.javaee7.sample:javaee7-simple-sample:war:"
          + System.getProperty("javaee7-sample-app-version"))
       .withoutTransitivity()
       .asSingle(WebArchive.class);

return Maven.configureResolver()

.withRemoteRepo("local-nexus", System.getProperty("nexus-repo"), "default")

.resolve("org.javaee7.sample:javaee7-simple-sample:war:"

+ System.getProperty("javaee7-sample-app-version"))

.withoutTransitivity()

.asSingle(WebArchive.class);

Running the smoke tests will show the results as:

Running org.javaee7.sample.PersonResourceSmokeTest
Feb 25, 2015 2:00:39 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.2.0.Beta4
Feb 25, 2015 2:00:39 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.2.0.Beta4
Feb 25, 2015 2:00:40 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version (unknown)
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.895 sec - in org.javaee7.sample.PersonResourceSmokeTest

Results :

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

Running org.javaee7.sample.PersonResourceSmokeTest

Feb 25, 2015 2:00:39 PM org.xnio.Xnio <clinit>

INFO: XNIO version 3.2.0.Beta4

Feb 25, 2015 2:00:39 PM org.xnio.nio.NioXnio <clinit>

INFO: XNIO NIO Implementation Version 3.2.0.Beta4

Feb 25, 2015 2:00:40 PM org.jboss.remoting3.EndpointImpl <clinit>

INFO: JBoss Remoting version (unknown)

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.895 sec - in org.javaee7.sample.PersonResourceSmokeTest

Results :

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

Run the full tests as:

mvn test -P fulltest

mvn test -P fulltest

This will run all files included in your test suite and will show the results as:

Running org.javaee7.sample.PersonResourceSmokeTest
Feb 25, 2015 2:35:38 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.2.0.Beta4
Feb 25, 2015 2:35:38 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.2.0.Beta4
Feb 25, 2015 2:35:38 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version (unknown)
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.388 sec - in org.javaee7.sample.PersonResourceSmokeTest
Running org.javaee7.sample.PersonResourceTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec - in org.javaee7.sample.PersonResourceTest

Results :

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

Running org.javaee7.sample.PersonResourceSmokeTest

Feb 25, 2015 2:35:38 PM org.xnio.Xnio <clinit>

INFO: XNIO version 3.2.0.Beta4

Feb 25, 2015 2:35:38 PM org.xnio.nio.NioXnio <clinit>

INFO: XNIO NIO Implementation Version 3.2.0.Beta4

Feb 25, 2015 2:35:38 PM org.jboss.remoting3.EndpointImpl <clinit>

INFO: JBoss Remoting version (unknown)

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.388 sec - in org.javaee7.sample.PersonResourceSmokeTest

Running org.javaee7.sample.PersonResourceTest

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec - in org.javaee7.sample.PersonResourceTest

Results :

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

In both cases, smoke tests and full tests are using the binary that is deployed to Nexus.

Learn more about your toolset for creating this simple yet powerful setup:

Here are some other blogs coming in this series:

Use a CI server to deploy to Nexus
Run tests on WildFly running in a PaaS
Add static code coverage and code metrics in testing
Build a deployment pipeline

Enjoy!

OpenShift v3: Getting Started with Java EE 7 using WildFly and MySQL (Tech Tip #73)

February 13, 2015containers, javaee, techtip, wildflydevops, docker, javaee7, kubernetes, openshift, wildflyarungupta

OpenShift is Red Hat’s open source PaaS platform. OpenShift v3 (due to be released this year) will provide a holistic experience on running your microservices using Docker and Kubernetes. In a classic Red Hat way, all the work is done in the open source at OpenShift Origin. This will also drive the next major release of OpenShift Online and OpenShift Enterprise.

OpenShift v3 uses a new platform stack that is using plenty of community projects where Red Hat contributes such as Fedora, Centos, Docker, Project Atomic, Kubernetes, and OpenStack. OpenShift v3 Platform Combines Docker, Kubernetes, Atomic and More explain this platform stack in detail.

This tech tip will explain how to get started with OpenShift v3, lets get started!

Getting Started with OpenShift v3

Pre-built binaries for OpenShift v3 can be downloaded from Origin at GitHub. However the simplest way to get started is to run OpenShift Origin as a Docker container.

OpenShift Application Lifecycle provide complete details on what it takes to run a sample application from scratch. This blog will use those steps and adapt them to run using boot2docker VM on Mac. And in the process we’ll also deploy a Java EE 7 application on WildFly which will be accessing database on a separate MySQL container.

Here is our deployment diagram:

WildFly and MySQL are running on separate pods.
Each of them is wrapped in a Replication Controller to enable simplified scaling.
Each Replication Controller is published as a Service.
WildFly talks to the MySQL service, as opposed to directly to the pod. This is important as Pods, and IP addresses assigned to them, are ephemeral.

Lets get started!

Configure Docker Daemon

Configure the docker daemon on your host to trust the docker registry service you’ll be starting. This registry will be used to push images for build/test/deploy cycle.

Log into boot2docker VM as:

boot2docker ssh

boot2docker ssh

Edit the file

sudo vi /var/lib/boot2docker/profile

sudo vi /var/lib/boot2docker/profile

This will be an empty file.

Add the following name/value pair:

EXTRA_ARGS="--insecure-registry 172.30.17.0/24"

EXTRA_ARGS="--insecure-registry 172.30.17.0/24"

Save the file, and quit the editor.

This will instruct the docker daemon to trust any docker registry on the 172.30.17.0/24 subnet.

Check out OpenShift v3 and Java EE 7 Sample

Download and Install Go and setup GOPATH and PATH environment variable. Check out OpenShift origin directory:

openshift> git clone https://github.com/openshift/origin.git
Cloning into 'origin'...
remote: Counting objects: 21451, done.
remote: Compressing objects: 100% (76/76), done.
remote: Total 21451 (delta 26), reused 15 (delta 1)
Receiving objects: 100% (21451/21451), 35.11 MiB | 1.24 MiB/s, done.
Resolving deltas: 100% (11392/11392), done.
Checking connectivity... done.

openshift> git clone https://github.com/openshift/origin.git

Cloning into 'origin'...

remote: Counting objects: 21451, done.

remote: Compressing objects: 100% (76/76), done.

remote: Total 21451 (delta 26), reused 15 (delta 1)

Receiving objects: 100% (21451/21451), 35.11 MiB | 1.24 MiB/s, done.

Resolving deltas: 100% (11392/11392), done.

Checking connectivity... done.

Note the directory where its checked out. In this case, its ~/workspaces/openshift.

Build the workspace:

make release
origin> make release
rm -rf _output Godeps/_workspace/pkg
hack/build-release.sh
Unable to find image 'openshift/origin-release' locally
Pulling repository openshift/origin-release
c59f040a4054: Download complete 
511136ea3c5a: Download complete 
5b12ef8fd570: Download complete 
dade6cb4530a: Download complete 
bd195712b86c: Download complete 
4aae29c1c846: Download complete 
d8738da3ed4c: Download complete 
7f7491063665: Download complete 
b5cfa9eebdb5: Download complete 
2f6297477756: Download complete 
dc98bd93df2f: Download complete 
1be2a7550a3d: Download complete 
42fd088f8c55: Download complete 
b6f6ad4012df: Download complete 
Status: Downloaded newer image for openshift/origin-release:latest

make release

origin> make release

rm -rf _output Godeps/_workspace/pkg

hack/build-release.sh

Unable to find image 'openshift/origin-release' locally

Pulling repository openshift/origin-release

c59f040a4054: Download complete

511136ea3c5a: Download complete

5b12ef8fd570: Download complete

dade6cb4530a: Download complete

bd195712b86c: Download complete

4aae29c1c846: Download complete

d8738da3ed4c: Download complete

7f7491063665: Download complete

b5cfa9eebdb5: Download complete

2f6297477756: Download complete

dc98bd93df2f: Download complete

1be2a7550a3d: Download complete

42fd088f8c55: Download complete

b6f6ad4012df: Download complete

Status: Downloaded newer image for openshift/origin-release:latest

Check out javaee7-hol workspace that has been converted to a Kubernetes application:

origin> git clone https://github.com/bparees/javaee7-hol
Cloning into 'javaee7-hol'...
remote: Counting objects: 1159, done.
remote: Compressing objects: 100% (49/49), done.
remote: Total 1159 (delta 35), reused 37 (delta 21)
Receiving objects: 100% (1159/1159), 20.35 MiB | 1.78 MiB/s, done.
Resolving deltas: 100% (605/605), done.
Checking connectivity... done.

origin> git clone https://github.com/bparees/javaee7-hol

Cloning into 'javaee7-hol'...

remote: Counting objects: 1159, done.

remote: Compressing objects: 100% (49/49), done.

remote: Total 1159 (delta 35), reused 37 (delta 21)

Receiving objects: 100% (1159/1159), 20.35 MiB | 1.78 MiB/s, done.

Resolving deltas: 100% (605/605), done.

Checking connectivity... done.

This is also done in ~/workspaces/openshift directory.

Start OpenShift v3 Container

Start OpenShift Origin as Docker container:

~> docker run -d --name "openshift-origin" --net=host --privileged \
  -v /var/run/docker.sock:/var/run/docker.sock  \
  -v /Users/arungupta/workspaces/openshift:/workspaces/openshift \
  -v /usr/local/bin/docker:/usr/bin/docker \
  openshift/origin start --public-master=$(boot2docker ip)

The VM's Host only interface IP address is: 

0ae85091e7ad7e85697575369f008273a6673d112b49860f5557a61d9e82d908

~> docker run -d --name "openshift-origin" --net=host --privileged \

-v /var/run/docker.sock:/var/run/docker.sock \

-v /Users/arungupta/workspaces/openshift:/workspaces/openshift \

-v /usr/local/bin/docker:/usr/bin/docker \

openshift/origin start --public-master=$(boot2docker ip)

The VM's Host only interface IP address is:

0ae85091e7ad7e85697575369f008273a6673d112b49860f5557a61d9e82d908

Note ~/workspaces/openshift directory is mounted as /workspaces/openshift volume in the container. Some additional volumes are mounted as well.

Check that the container is running:

~> docker ps
CONTAINER ID        IMAGE                    COMMAND                CREATED             STATUS              PORTS               NAMES
0ae85091e7ad        openshift/origin:beta1   "/usr/bin/openshift    2 minutes ago       Up 2 minutes                            openshift-origin

~> docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

0ae85091e7ad openshift/origin:beta1 "/usr/bin/openshift 2 minutes ago Up 2 minutes openshift-origin

Log into the container as:

openshift> docker exec -it `docker ps | grep origin:beta1 | awk '{ print $1 }'` bash
[root@boot2docker openshift]#

openshift> docker exec -it `docker ps | grep origin:beta1 | awk '{ print $1 }'` bash

[root@boot2docker openshift]#

Install Docker registry in the container by giving the following command:

export CERT_DIR=/var/lib/openshift/openshift.local.certificates/openshift-client && \
export KUBECONFIG=/var/lib/openshift/openshift.local.certificates/admin/.kubeconfig && \
cd /workspaces/openshift/origin && hack/install-registry.sh

export CERT_DIR=/var/lib/openshift/openshift.local.certificates/openshift-client && \

export KUBECONFIG=/var/lib/openshift/openshift.local.certificates/admin/.kubeconfig && \

cd /workspaces/openshift/origin && hack/install-registry.sh

Confirm that the registry is running by getting the list of pods:

[root@boot2docker origin]# osc get pods
POD                       IP                  CONTAINER(S)         IMAGE(S)                    HOST                    LABELS                                                                                                             STATUS
docker-registry-1-gfkbz   172.17.0.14         registry-container   openshift/docker-registry   boot2docker/127.0.0.1   deployment=docker-registry-1,deploymentconfig=docker-registry,name=registrypod,template=docker-registry-template   Running

[root@boot2docker origin]# osc get pods

POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS

docker-registry-1-gfkbz 172.17.0.14 registry-container openshift/docker-registry boot2docker/127.0.0.1 deployment=docker-registry-1,deploymentconfig=docker-registry,name=registrypod,template=docker-registry-template Running

osc is OpenShift Client CLI and allows to create and manage OpenShift projects. Some of the kubectl commands can also be using this script.

Confirm the registry service is running. Note the actual IP address may vary:

[root@boot2docker origin]# osc get services
NAME                LABELS                                    SELECTOR            IP                  PORT
docker-registry     template=docker-registry-template         name=registrypod    172.30.17.142       5001
kubernetes          component=apiserver,provider=kubernetes   <none>              172.30.17.2         443
kubernetes-ro       component=apiserver,provider=kubernetes   <none>              172.30.17.1         80

[root@boot2docker origin]# osc get services

NAME LABELS SELECTOR IP PORT

docker-registry template=docker-registry-template name=registrypod 172.30.17.142 5001

kubernetes component=apiserver,provider=kubernetes <none> 172.30.17.2 443

kubernetes-ro component=apiserver,provider=kubernetes <none> 172.30.17.1 80

Confirm that the registry service is accessible:

curl `osc get services docker-registry -o template --template="{{ .portalIP}}:{{ .port }}"`

curl `osc get services docker-registry -o template --template="{{ .portalIP}}:{{ .port }}"`

And look for the output:

"docker-registry server (dev) (v0.9.0)"

"docker-registry server (dev) (v0.9.0)"

Access OpenShift v3 Web Console

OpenShift Origin server is now up and running. Find out the host’s IP address using boot2docker ip and open http://<IP addresss of boot2docker host>:8444 to view OpenShift Web Console in your browser.For example, the console is accessible at https://192.168.59.103:8444/ on this machine.

You will need to have the browser accept the certificate at https://<host>:8444 before the console can consult the OpenShift API. Of course this would not be necessary with a legitimate certificate.
OpenShift Origin login screen shows up. Enter the username/password as admin/admin:

and click on the “Log In” button. The default web console looks like:

Create OpenShift v3 Project

Use project.json from github.com/openshift/origin/blob/master/examples/sample-app/project.json in the OpenShift v3 container and create a test project as:

[root@boot2docker origin]# osc create -f /workspaces/openshift/origin/examples/sample-app/project.json 
test

[root@boot2docker origin]# osc create -f /workspaces/openshift/origin/examples/sample-app/project.json

test

Refreshing the web console now shows:

Clicking on “OpenShift 3 Sample” shows an empty project description:

Request creation of the application template:

[root@boot2docker openshift]# cd javaee7-hol/
[root@boot2docker javaee7-hol]# osc process -n test -f application-template-jeebuild.json | osc create -n test -f -
frontend
origin-jee-sample
wildfly-8-centos
jee-sample-build
frontend
mysql
database

[root@boot2docker openshift]# cd javaee7-hol/

[root@boot2docker javaee7-hol]# osc process -n test -f application-template-jeebuild.json | osc create -n test -f -

frontend

origin-jee-sample

wildfly-8-centos

jee-sample-build

frontend

mysql

database

Web Console automatically refreshes and shows:

The list of services running can be seen as:

Build the Project

Trigger an initial build of your project:

[root@boot2docker javaee7-hol]# osc start-build -n test jee-sample-build
cee73fbc-b32d-11e4-a0f2-5282784576db

[root@boot2docker javaee7-hol]# osc start-build -n test jee-sample-build

cee73fbc-b32d-11e4-a0f2-5282784576db

Monitor the builds and wait for the status to go to “complete” (this can take a few minutes):

[root@boot2docker javaee7-hol]#  osc get -n test builds
NAME                                   TYPE                STATUS              POD
cee73fbc-b32d-11e4-a0f2-5282784576db   STI                 Running             build-cee73fbc-b32d-11e4-a0f2-5282784576db

[root@boot2docker javaee7-hol]# osc get -n test builds

NAME TYPE STATUS POD

cee73fbc-b32d-11e4-a0f2-5282784576db STI Running build-cee73fbc-b32d-11e4-a0f2-5282784576db

You can add the –watch flag to wait for updates until the build completes:

[root@boot2docker javaee7-hol]#  osc get -n test builds --watch
NAME                                   TYPE                STATUS              POD
cee73fbc-b32d-11e4-a0f2-5282784576db   STI                 Running             build-cee73fbc-b32d-11e4-a0f2-5282784576db
NAME                                   TYPE                STATUS              POD
cee73fbc-b32d-11e4-a0f2-5282784576db   STI                 Complete            build-cee73fbc-b32d-11e4-a0f2-5282784576db

[root@boot2docker javaee7-hol]# osc get -n test builds --watch

NAME TYPE STATUS POD

cee73fbc-b32d-11e4-a0f2-5282784576db STI Running build-cee73fbc-b32d-11e4-a0f2-5282784576db

NAME TYPE STATUS POD

cee73fbc-b32d-11e4-a0f2-5282784576db STI Complete build-cee73fbc-b32d-11e4-a0f2-5282784576db

Wait for the STATUS column to show Complete. It will take a few minutes as all the components (WIldFly, MySQL, Java EE 7 application) are provisioned. Effectively, their new Docker images are created and pushed to the local registry that was started earlier.

Hit Ctrl+C to stop watching builds after the status changes to Complete.

Complete log of the build can be seen as:

[root@boot2docker javaee7-hol]# osc build-logs -n test cee73fbc-b32d-11e4-a0f2-5282784576db
2015-02-13T03:10:07.065718606Z Cloning into '/tmp/sti552730161/upload/src'...
2015-02-13T03:11:03.184576532Z I0213 03:11:03.184326       1 build.go:160] Successfully built 172.30.17.142:5001/test/origin-jee-sample
2015-02-13T03:11:07.261489310Z The push refers to a repository [172.30.17.142:5001/test/origin-jee-sample] (len: 1)
2015-02-13T03:11:07.261489310Z Sending image list
2015-02-13T03:11:07.275256699Z Pushing repository 172.30.17.142:5001/test/origin-jee-sample (1 tags)
2015-02-13T03:11:07.307836081Z Pushing
Buffering to disk07.314345045Z Buffering to disk 1.024 kB
2015-02-13T03:11:07.315452728Z Buffering to disk
Pushing-13T03:11:07.323973430Z Pushing [=========================>                         ]    512 B/1.024 kB 0

. . .

Pushing-13T03:13:05.932725921Z Pushing [================================================>  ]  6.56 MB/6.704 MB 0
Pushing-13T03:13:05.942989165Z Pushing [=================================================> ] 6.635 MB/6.704 MB 0
Pushing-13T03:13:05.943025109Z Pushing [=================================================> ] 6.702 MB/6.704 MB 0
Pushing-13T03:13:05.947665528Z Pushing [==================================================>] 6.704 MB/6.704 MB
2015-02-13T03:13:05.953476634Z Image successfully pushed
2015-02-13T03:13:05.953476634Z Pushing tag for rev [b0a7868377c1] on {http://172.30.17.142:5001/v1/repositories/test/origin-jee-sample/tags/latest}

[root@boot2docker javaee7-hol]# osc build-logs -n test cee73fbc-b32d-11e4-a0f2-5282784576db

2015-02-13T03:10:07.065718606Z Cloning into '/tmp/sti552730161/upload/src'...

2015-02-13T03:11:03.184576532Z I0213 03:11:03.184326 1 build.go:160] Successfully built 172.30.17.142:5001/test/origin-jee-sample

2015-02-13T03:11:07.261489310Z The push refers to a repository [172.30.17.142:5001/test/origin-jee-sample] (len: 1)

2015-02-13T03:11:07.261489310Z Sending image list

2015-02-13T03:11:07.275256699Z Pushing repository 172.30.17.142:5001/test/origin-jee-sample (1 tags)

2015-02-13T03:11:07.307836081Z Pushing

Buffering to disk07.314345045Z Buffering to disk 1.024 kB

2015-02-13T03:11:07.315452728Z Buffering to disk

Pushing-13T03:11:07.323973430Z Pushing [=========================> ] 512 B/1.024 kB 0

. . .

Pushing-13T03:13:05.932725921Z Pushing [================================================> ] 6.56 MB/6.704 MB 0

Pushing-13T03:13:05.942989165Z Pushing [=================================================> ] 6.635 MB/6.704 MB 0

Pushing-13T03:13:05.943025109Z Pushing [=================================================> ] 6.702 MB/6.704 MB 0

Pushing-13T03:13:05.947665528Z Pushing [==================================================>] 6.704 MB/6.704 MB

2015-02-13T03:13:05.953476634Z Image successfully pushed

2015-02-13T03:13:05.953476634Z Pushing tag for rev [b0a7868377c1] on {http://172.30.17.142:5001/v1/repositories/test/origin-jee-sample/tags/latest}

Check for the application pods to start:

[root@boot2docker javaee7-hol]# osc get -n test pods    
POD                                          IP                  CONTAINER(S)        IMAGE(S)                                                                                                     HOST                    LABELS                                                                              STATUS
build-cee73fbc-b32d-11e4-a0f2-5282784576db   172.17.0.17         sti-build           openshift/origin-sti-builder:v0.3                                                                            boot2docker/127.0.0.1   <none>                                                                              Succeeded
database-1-axe6d                             172.17.0.16         jee-database        mysql                                                                                                        boot2docker/127.0.0.1   deployment=database-1,deploymentconfig=database,name=database,template=jee-sample   Running
frontend-1-pkcia                             172.17.0.20         jee-sample          172.30.17.142:5001/test/origin-jee-sample:b0a7868377c10a50b40019be70e22d040b9a2bb2d87fa3932b700494e50a4de6   boot2docker/127.0.0.1   deployment=frontend-1,deploymentconfig=frontend,name=frontend,template=jee-sample   Running

[root@boot2docker javaee7-hol]# osc get -n test pods

POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS

build-cee73fbc-b32d-11e4-a0f2-5282784576db 172.17.0.17 sti-build openshift/origin-sti-builder:v0.3 boot2docker/127.0.0.1 <none> Succeeded

database-1-axe6d 172.17.0.16 jee-database mysql boot2docker/127.0.0.1 deployment=database-1,deploymentconfig=database,name=database,template=jee-sample Running

frontend-1-pkcia 172.17.0.20 jee-sample 172.30.17.142:5001/test/origin-jee-sample:b0a7868377c10a50b40019be70e22d040b9a2bb2d87fa3932b700494e50a4de6 boot2docker/127.0.0.1 deployment=frontend-1,deploymentconfig=frontend,name=frontend,template=jee-sample Running

Note, that the “frontend” and “database” pods are now running.

Determine IP of the “frontend” service:

[root@boot2docker javaee7-hol]# osc get -n test services
NAME                LABELS                SELECTOR            IP                  PORT
frontend            template=jee-sample   name=frontend       172.30.17.115       8080
mysql               template=jee-sample   name=database       172.30.17.75        3306

[root@boot2docker javaee7-hol]# osc get -n test services

NAME LABELS SELECTOR IP PORT

frontend template=jee-sample name=frontend 172.30.17.115 8080

mysql template=jee-sample name=database 172.30.17.75 3306

Access the application at http://<IP address of “frontend”>:8080/movieplex7-1.0-SNAPSHOT should work. Note the IP address may (most likely will) vary. In this case, it would be http://172.30.17.115:8080/moviexplex7-1.0-SNAPSHOT.The app would not be accessible yet, as some further debugging is required to configure firewall on Mac when OpenShift v3 is used as Docker container. Until we figure that out, you can do docker ps in your boot2docker VM to see the list of all the containers:

origin> docker ps
CONTAINER ID        IMAGE                                                                                                       COMMAND                CREATED             STATUS              PORTS               NAMES
c776cabb72f8        172.30.17.17:5001/test/origin-jee-sample:91d1b5a5ed58e1642aafbd652eba0b7eae3a0ac08c17729d205ae88204f64449   "/tmp/scripts/run"     2 hours ago         Up 2 hours                              k8s_jee-sample.7af25557_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_53f91f55                      
e7f87112c473        openshift/origin-pod:beta1                                                                                  "/pod"                 2 hours ago         Up 2 hours                              k8s_POD.9cbfdefa_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_64263b61                             
7e7579db5f82        openshift/origin-pod:beta1                                                                                  "/pod"                 2 hours ago         Up 2 hours                              k8s_POD.123cbdd6_build-e075047d-b3b4-11e4-81f6-5282784576db.test.api_e07bcdb2-b3b4-11e4-81f6-5282784576db_376c0e63   
74082d7791ec        openshift/origin-pod:beta1                                                                                  "/pod"                 2 hours ago         Up 2 hours                              k8s_POD.123cbdd6_build-76364bb6-b3b2-11e4-81f6-5282784576db.test.api_7639e3a5-b3b2-11e4-81f6-5282784576db_f653c7fd   
3e42dacb0da7        mysql:latest                                                                                                "/entrypoint.sh mysq   3 hours ago         Up 3 hours                              k8s_jee-database.f12628ae_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_193dddf7                    
cb551c8cf7bf        openshift/origin-pod:beta1                                                                                  "/pod"                 3 hours ago         Up 3 hours                              k8s_POD.95f2def6_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_295fc320                             
e8719152df42        openshift/docker-registry:latest                                                                            "\"sh -c 'echo \"$OP   3 hours ago         Up 3 hours                              k8s_registry-container.4e338487_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_a6f4f83b    
d3ecc5841c3b        openshift/origin-pod:beta1                                                                                  "/pod"                 3 hours ago         Up 3 hours                              k8s_POD.8a29deef_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_ba53d62b                   
a506222fae91        openshift/origin:beta1                                                                                      "/usr/bin/openshift    3 hours ago         Up 3 hours                              openshift-origin

origin> docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

c776cabb72f8 172.30.17.17:5001/test/origin-jee-sample:91d1b5a5ed58e1642aafbd652eba0b7eae3a0ac08c17729d205ae88204f64449 "/tmp/scripts/run" 2 hours ago Up 2 hours k8s_jee-sample.7af25557_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_53f91f55

e7f87112c473 openshift/origin-pod:beta1 "/pod" 2 hours ago Up 2 hours k8s_POD.9cbfdefa_frontend-2-9ciae.test.api_12a0d77e-b3b5-11e4-81f6-5282784576db_64263b61

7e7579db5f82 openshift/origin-pod:beta1 "/pod" 2 hours ago Up 2 hours k8s_POD.123cbdd6_build-e075047d-b3b4-11e4-81f6-5282784576db.test.api_e07bcdb2-b3b4-11e4-81f6-5282784576db_376c0e63

74082d7791ec openshift/origin-pod:beta1 "/pod" 2 hours ago Up 2 hours k8s_POD.123cbdd6_build-76364bb6-b3b2-11e4-81f6-5282784576db.test.api_7639e3a5-b3b2-11e4-81f6-5282784576db_f653c7fd

3e42dacb0da7 mysql:latest "/entrypoint.sh mysq 3 hours ago Up 3 hours k8s_jee-database.f12628ae_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_193dddf7

cb551c8cf7bf openshift/origin-pod:beta1 "/pod" 3 hours ago Up 3 hours k8s_POD.95f2def6_database-1-bqg8v.test.api_56093bac-b3b2-11e4-81f6-5282784576db_295fc320

e8719152df42 openshift/docker-registry:latest "\"sh -c 'echo \"$OP 3 hours ago Up 3 hours k8s_registry-container.4e338487_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_a6f4f83b

d3ecc5841c3b openshift/origin-pod:beta1 "/pod" 3 hours ago Up 3 hours k8s_POD.8a29deef_docker-registry-1-bt49s.default.api_177a691c-b3b0-11e4-81f6-5282784576db_ba53d62b

a506222fae91 openshift/origin:beta1 "/usr/bin/openshift 3 hours ago Up 3 hours openshift-origin

And then login to the container associated with frontend as:

docker exec -it `docker ps | grep origin-jee-sample | awk '{ print $1 }'` bash

docker exec -it `docker ps | grep origin-jee-sample | awk '{ print $1 }'` bash

This will log in to the Docker container where you can check that the application is deployed successfully by giving the following command: