Generating the Service Wrapper in Red Hat JBoss Fuse

Introduction:

The Red Hat JBoss Fuse console's wrapper feature generates a wrapper around the JBoss Fuse runtime that allows you to install a message broker as a system service. The wrapper feature does not come preinstalled in the console, so before you can generate the service wrapper you must install the wrapper feature.

Once the feature is installed the console gains a wrapper:install command. Running this command generates a generic service wrapper in the JBoss Fuse installation.

Overview:

To generate the service wrapper:

1.      Start JBoss Fuse in console mode using the fuse command.

 

2.      Once the console is started and the command prompt appears, enter features:install wrapper.

 

The features:install command will locate the required libraries to provision the wrapper feature and deploy it into the run time.

3.      Generate the wrapper by entering wrapper:install -n serviceName -d displayName -D description.

The wrapper:install command has the options described in below table.

 

Table: Wrapper Install Options

Option	Default	Description
-s	AUTO_START	(Windows only) Specifies the mode in which the service is installed. Valid values are AUTO_START or DEMAND_START.
-n	karaf	Specifies the service name that will be used when installing the service.
-d		Specifies the display name of the service.
-D		Specifies the description of the service.

Generated files

The following files are generated and make up the service wrapper:

• bin\ServiceName-wrapper[.exe]—the executable file for the wrapper.
• bin\ServiceName-service[.bat]—the script used to install and remove the service.
• etc\ServiceName-wrapper.conf—the wrapper's configuration file.
• Three library files required by the service wrapper:
• lib\libwrapper.so
• lib\karaf-wrapper.jar
• lib\karaf-wrapper-main.jar

continue reading

Maven - Environment Setup

Introduction

Maven is Java based tool, so the very first requirement is to have JDK installed on your machine. We will discuss how to setup the Maven in windows operating system.

Overview

System Requirement

JDK	1.5 or above.
Memory	No minimum requirement.
Disk Space	No minimum requirement.
Operating System	No minimum requirement.

Verify Java installation on your machine

Now open console and execute the following java command.

Set JAVA environment

Set the JAVA_HOME environment variable to point to the base directory location where Java is installed on your machine. For example

Set the environment variable JAVA_HOME to C:\Program Files\Java\jdk1.8.0_51.

Set Maven environment variables

Add M2_HOME to environment variables.

Set the environment variables using system properties.

M2_HOME=C:\JBoss\Maven\apache-maven-3.3.3

Add Maven bin directory location to system path

Now append M2 variable to System Path

Set the environment variables using system properties.

Path=C:\Program Files\Java\jdk1.8.0_51\bin;C:\JBoss\Maven\apache-maven-3.3.3\bin

Verify Maven installation

Now open console, execute the following mvn command.

Open Command Console        c:\> mvn –version

Finally, verify the output of the above commands, which should be something as follows:

Conclusion

Congratulations! You are now all set to use Apache Maven for your projects. In this article we covered Apache Maven setup in Windows Operating system.

continue reading

JBoss Maven Configuration

Introduction

What is Maven

Maven was originally started as an attempt to simplify the build processes in the Jakarta Turbine project. There were several projects each with their own Ant build files that were all slightly different and JARs were checked into CVS. We wanted a standard way to build the projects, a clear definition of what the project consisted of, an easy way to publish project information and a way to share JARs across several projects.

Configuration

JAVA_HOME System Variable

Right click on My Computer à Select Advanced system settings à select Environment variables under advanced tab.

Under system variables click on New àgive variable name as JAVA_HOME and variable value as C:\Program Files\Java\jdk1.7.0_55(JDK  path). 

C:\Program Files\Java\jdk1.7.0_55(JDK  path).

Similarly create a system variable ‘M2_HOME’ and value as D:\Fuse ESB\apache-maven-3.3.1(Maven folder).

Similarly create a system variable ‘Path’ and value as D:\Fuse ESB\apache-maven-3.3.1(Maven folder).

Download and update the Maven configuration.

• Download maven from http://maven.apache.org/download.cgi
• Install maven to D:\Fuse ESB\apache-maven-3.3.1 
• Create maven repo folder e.g. D:\ Fuse ESB\Maven_Repo
• Edit the global and personal settings.xml file to add the config you want e.g. change personal repo location (TODO: understand whats common config looks like) 
• Add following repository tag to D:\Fuse ESB\apache-maven-3.3.1\conf\settings.xml:

<localRepository>D:\Fuse ESB\Maven_Repo</localRepository>This is for pointing Maven repository. All maven related jar’s will be downloaded into this folder.

Add profiles to Maven configuration.

Open JBoss Developer Studio, goto Window à Preferences à Expand Maven à select User Setting. Browse the user settings file as ‘D:\Fuse ESB\apache-maven-3.3.1\conf\settings.xml’

Then click on update settings, click on Apply and Ok.

Goto Window à Preferences à Expand JBoss Tools à select JBoss Maven Integration à Click on Configure Maven Repositories.

Click on Add Repository and enter the following details as shown below.

Profile ID: jboss-ga-repository
ID: jboss-ga-repository
Name: jboss-ga-repository
URL: http://maven.repository.redhat.com/techpreview/all/

Similarly add the following details too.Profile ID: jboss-earlyaccess-repository
ID: jboss-earlyaccess-repository
Name: jboss-earlyaccess-repository
URL: http://maven.repository.redhat.com/earlyaccess/all/

Now click on Ok and Click on Finish. There will be conformation pop up will be shown to update Settings.xml file and click on yes.

Create a Sample Fuse Project and and Right click on project select Run As à Maven Install.

Now Maven repository will be downloaded into repository folder and project will build successfully with Maven configuration, we can see the following logs in console.

continue reading