How to Configure Progress Rollbase on JBOSS EAP

• “JBOSS_HOME/domain/configuration”
• Edit domain.xml and look for “<subsystem xmlns=”urn:jboss:domain:ee:1.2″>”
• Add the static module (mentioned above).Please note that there will be multiple occurrences of the subsystem tag and this text should be added to all. Finally, your subsystem configuration should look like this:

With these three simple steps we have configured all the required Rollbase libraries as a static module in JBOSS. These libraries can now be used by the deployed applications.

Setting up Rollbase Configuration Files in JBOSS EAP

In case of standalone mode, go to “JBOSS_HOME/standalone” and unzip the rollbase.zip archive. In case of a domain mode, do the same for each of the servers i.e. “JBOSS_HOME/domain/servers/<server_name>.” In case the “servers” folder is not available, please run the “domain.bat” from “JBOSS_HOME/bin.”

You will have to set defaults for properties in these configurations. Please refer to the Rollbase documentation below on how to do this:

• Configuring shared.properties
• Configuring components.xml
• Setting environment variables

Adding Libraries to the Static Module

JBOSS relies on the module.xml to load the required resources for the applications. There may be scenarios when you would need to add your own .jar resource as a dependency. We will look at how to do it in this section.

Let’s look at a use case where there is a need to add a mysql jdbc driver to the ROLLBASE_LIBSas dependency.

• Add mysql-connector.jar to the ROLLBASE_LIBS folder.
• Edit “ROLLBASE_LIBS/module.xml” and add an entry for this .jar as shown below:

Deploying Rollbase Applications on JBOSS EAP

Before proceeding with the deployment, please make sure a management user has been created in JBOSS EAP. This can be done by running the add-user.bat/sh from “JBOSS_HOME/bin.”

We are now all set to start the application deployment.

Now, run the appropriate .bat file to start the JBOSS application server:

• “JBOSS_HOME/bin/standalone.bat” for the Standalone operating mode (or)
• “JBOSS_HOME/bin/domain.bat” for the Domain operative mode.

Once the JBOSS application server has started, go to management console (usually <hostname>:9990). When prompted for credentials, enter the management user credentials.

On successful login:

• Go to Runtime tab and
• Click on “Manage Deployments”

Here you can start adding the wars. After the wars are uploaded, deploy them using “Assign” in domain mode & “En/Disable” in standalone mode.

Once the wars are deployed successfully, you are all set to start using Rollbase. Type in the url linked here in the browser and voila!

Conclusion

By now, we have learnt how to deploy Rollbase on JBOSS EAP. The setup has been carefully designed to be a fairly simple process. The same approach can be followed to setup Rollbase on Wildfly. Also known as JBOSS AS, it is a community version of JBOSS. Please note, however, that this is not yet officially supported by Rollbase.

Curious to try it for yourself? Learn more about Rollbase or start your free trial today.