Updating environment information for JBoss application servers

Using NexJ Studio, update the server or environment file for your deployment to include details about your JBoss application server installation.

Prior to updating the environment information for your deployment, install the JBoss application server, apply any necessary patches, then configure the JBoss application server to run either as an application or a service.

To update the clustering and location information for your deployment:

Open NexJ Studio.
On the Deployment layer, in the Environment tab, open the server or environment for this deployment.
In the Overview tab, ensure that Type is set to JBoss.
In the Overview tab, in the Deployment Location field, specify the shared folder directories for all the server nodes.
For example: \\projectdir\jboss-svr,\\projectdir2\jboss-svr or \\{projectdir,projectdir2}\jboss-svr.
If you are updating the environment information for a JBoss application server cluster, in the Clustering/Session subtab, ensure that the Distributed (Enable Clustering) option is selected.
Optional: If you plan to host the JMS tables in a database other than the default relational database or if the database user configured for the database that will host the JMS tables does not have DDL privileges, you need to configure additional parameters in the server or environment file.
See Configuring a different database for JMS tables and generating a script to create JMS tables for detailed instructions.
Save the updated server or environment file.

The environment information for your deployment has been updated.

You can now continue configuring your JBoss application server installation. After the configuration is complete, you can deploy your NexJ application on the JBoss application server instance or cluster.

If you included JMS parameters in the server or environment file, after the NexJ application is deployed, a script is generated in the location identified in the jms.sql.file attribute. You need to provide this script to your database administrator, who can run it against the database that should contain JMS tables.