Tag Archives: jbosstools

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?

JBoss Tools Community Acceptance Testing (JBoss Tools CAT)

June 24, 2014jbosscommunity, eclipse, jbosstoolsarungupta

JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exists for JBoss and related technologies in the default Eclipse distribution.

Until now, early builds of JBoss Tools were released at a regular cadence leading up to the release of a particular version. Anybody could download, integrate the plugins in Eclipse, test, and provide feedback. JBoss Tools Community Acceptance Testing (CAT) seeks to obtain feedback from the community on early builds of JBoss Tools.

So what’s different ?

Allows JBoss Tools team to engage with individuals who can look at the release schedule and features coming in a particular release, test them, and provide feedback
JBoss Tools team will be paying close attention to the bugs filed by CAT members and ensuring they are responded/reacted to
Your name will be included in the JBoss Tools release notes
Help us decide if JBoss Tools is ready for release

Any feedback is relevant ? Stability, performance, usability, regression, RFE, anything literally.

Ready to get started ?

The simple process and other details are available at tools.jboss.org/cat/.

Learn more about the motivation behind all of this in a short interview with Max Andersen:

You might also wonder the name looks very familiar! Having actively participated in NetCAT and driven FishCAT, this was a very natural choice. All the more relevant because Red Hat truly believes in community powered innovation.

Max also blogged about it here.

And in case you are wondering, JBoss Developer Studio (JBDS) is a fully bundled Eclipse distribution which not only includes the majority of JBoss Tools but also all its needed dependencies and 3rd party plugins allowing for an easy one-click and no-fuss installation. JBDS is released along with the GA version of JBoss Tools. So if you are participating in JBoss Tools CAT, you are helping us test JBoss Developer Studio as well.

Tech Tip #5 shows how to get started with JBoss Tools and WildFly!

Getting Started with JBoss Tools and WildFly (Tech Tip #5)

December 17, 2013techtip, wildflyeclipse, jbosstools, wildflyarungupta

JBoss Tools 4.1.1 and JBoss Developer Studio 7.1 were released 2 days ago. This release is built on top of Eclipse Kepler 4.3.1, came in less than 6 months from the previous one, has 500+ bug fixes and some nice features.

Improved hybrid mobile tooling with support for Apache Cordova using Aerogear
More support for OpenShift 2.0
Content assist on Angular.js attributes and resource content

What is the difference between JBoss Tools and JBoss Developer Studio ?

JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exists for JBoss and related technologies in the default Eclipse distribution.

JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes the majority of JBoss Tools but also all its needed dependencies and 3rd party plugins allowing for an easy one-click and no-fuss installation.

If you are into doing your own bleeding edge Eclipse plugin assembly, JBoss Tools is for you; if you are more into having something that “Just Works” then JBoss Developer Studio is the way to go.

I took JBoss Tools for a ride and tried Java EE samples on WildFly. Here are the steps for the same:

Downloaded Eclipse IDE for Java EE Developers. Ignore this step if you already have Eclipse Kepler 4.3.1 for Java EE.
Drag and Drop the button in Eclipse to install the tools . There are other usual methods to install as well but I found this extremely convenient.Dropping the button shows the following screen:
Follow the instructions to complete the installation. Restarting the Eclipse shows the following screen:

And that shows a successful installation.
Click on the “Servers” tab, click on “Click this link to create a new server…”Select “WildFly” and click on “Next>”. Use Tech Tip #1 to install WildFly locally on your machine. Specify the WildFly location on next screen:

Click on the second “Browse…” button to select an appropriate profile. Click on “Finish” to complete WildFly installation.
Right-click on the selected server and click on “Start” to start WildFly.
Check out Java EE samples and import them in Eclipse. Select any project, right-click on it and select “Run on Server”. Choose the WildFly server to see the output as: