The release 7.2 of JBoss AS introduces the capability to install a module using the Command Line Interface. In this tutorial we will show how you can install a data source as a module using a CLI script.

Jboss Global Module Slots
Jboss Global Module Slot Tool
Jboss Global Module Slot Installer

Step 5 - Update the JBoss server configuration – “urn:jboss:domain:ee” subsystem to specify the Solace Resource Adapter module as a Global Module: Note: the version of the subsystem, “V.V” depends on your JBoss EAP version. Global Modules Global modules is a set of JBoss Modules that will be added as dependencies to the JBoss Module of every Java EE deployment. Such dependencies allows Java EE deployments to see the classes exported by the global modules. Each global module is defined through the module resource, an example of its XML configuration.

Global Modules Global modules is a set of JBoss Modules that will be added as dependencies to the JBoss Module of every Java EE deployment. Such dependencies allows Java EE deployments to see the classes exported by the global modules. Each global module is defined through the module resource, an example of its XML configuration. A global module is a module that JBoss EAP provides as a dependency to every application. Any module can be made global by adding it to JBoss EAP’s list of global modules. It does not require changes to the module. You can set the list of global modules via this CLI. I have six applications in Jboss Instance jboss EAP 6.0.1 There is global module defined as below. Standalone.xml global-modules module name='oracle.jdbc' slot='m.

Modules are the heart of the new application server release. If you want to install a library as a module, in order to share with your applications, you have to create a directory structure for it and add the module.xml file descriptor and the JAR libraries. See this tutorial for more information about installing a module on your AS 7 file system.

This might be a little lenghty approach or simply it can be you don't have access to the JBoss AS file system. (e.g. a remote server installation). In order to install modules using the CLI, you have to download a JBoss AS 7.2 latest build from Jenkins https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/

As you can see, once you connect with the CLI (jboss-cli.cmd / jboss-cli.sh) some new commands are available, by pressing the tab key.

The command we will use is 'module' and you need to provide three arguments: the module name, the resources (JAR files) and the dependencies used. Optionally you can add a module slot, in case your module uses several different implementations.

Here's the script for creating a MySQL module (line 1) + driver (line 2) + data source (line 3).

The JBoss Application Server is configured using various XML configuration files. JBoss must be shut down before editing any of these configuration files. If JBoss is running and these files are changed, JBoss will probably crash. JBoss also has a few configuration files that are formatted as .property files. You must ensure that the .property files are saved as UNIX text files on Linux or Solaris if you edit these files on Windows environments at any time.

For single-server installations, you may use jboss profile located at [appserver root] standaloneconfiguration as a template. For cluster installations, use jboss profile located at [appserver root] domain as a template.

It is recommended that you make a copy of the profile (all or standard) and make changes to the copied profile.

Jboss Global Module Slots

12.4.1 Modify the JBoss configuration

Perform the following steps to modify the JBoss configuration to customize JBoss for AEM forms.

Modify domain.conf.bat file (windows)
Modify jboss.cli.bat (windows)
Modify domain.conf file (Linux and Solaris)
Modify domain.xml file (Windows and Unix Both)
Modify host.xml file

Modify EAR file class-loading isolation
Modify the standalone.conf.bat file (Windows)
Modify standalone.conf (Linux and Solaris)

12.4.1.1 Modify the domain.conf.bat file (Windows only)

Open the [appserver root] /bin/domain.conf.bat file in an editor.
Delete the text in bold in the following line and add the memory arguments for 64-bit JVM.
Add the following argument for 64-bit JVM:
(Optional) Modify JBoss Application Server to run in IPv6 mode as follows:
- Locate and modify -Djava.net.preferIPv4Stack=false
- Insert the string -Djava.net.preferIPv6Stack=true
Note: If the application server log contains the following error on startup, remove the value for the IPv6 stack and set the IPV4 value back to true :
“13:37:44,488 WARN [HANamingService] Failed to start AutomaticDiscovery java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound to any interface at java.net.PlainDatagramSocketImpl.socketSetOption(Native Method)at java.net.PlainDatagramSocketImpl.setOption(PlainDatagramSocketImpl.java:260)”
Save and close the file.

12.4.1.2 Modify the standalone.bat file (Windows only)

Open the [appserver root] /bin/standalone.bat file in an editor.
Modify the line immediately following rem Setup JBoss specific properties to set encoding to UTF-8:

Note: Ensure that no line breaks appear in this new line.

Note: These memory arguments are for both, domain controllers and process controllers, and should be set on each node of cluster.

(Optional) Modify JBoss Application Server to run in IPv6 mode as follows:
- Locate and modify -Djava.net.preferIPv4Stack=false
- Insert the string -Djava.net.preferIPv6Stack=true
Note: If the application server log contains the following error on startup, remove the value for the IPv6 stack and set the IPV4 value back to true :
“13:37:44,488 WARN [HANamingService] Failed to start AutomaticDiscovery java.net.SocketException: bad argument for IP_MULTICAST_IF: address not bound to any interface at java.net.PlainDatagramSocketImpl.socketSetOption(Native Method)at java.net.PlainDatagramSocketImpl.setOption(PlainDatagramSocketImpl.java:260)”
Save and close the file.

12.4.1.3 Modify jboss.cli.bat (windows)

Open the [JBoss_root]binjboss-cli.bat file for editing.
Add double-quotes (“ ”) to the text in bold in the following line:
Save and close the file.

12.4.1.4 Modify the domain.conf file (JBoss with Solaris 10, Red Hat 6.0, 64-bit only)

Solaris JDKs from Sun require an additional argument to use 64-bit features. Without this configuration change, the Sun JDK defaults to 32-bit support only.

Note: If you're running JBoss as a non-root user, use -Djava.io.tmpdir='location' to set the location of the temporary directory to a directory to which you have access.

Open the