Cleaning up old JBoss model deployments

In order to support multiple models on a single server, a unique suffix is added to the .ear deployment file, for example nexj-crm.ear. The older deployment file, nexj.ear, is not removed automatically. To remove the older deployment file, delete it from the JBoss deploy directory (or the farm directory for distributed server profiles such as "all").

In addition, for each deployment with a unique environment name, the server has a set of configuration data. Keeping this data will not cause errors, but if you want to keep your server clean of unused data, it must be removed manually as well. Old values will use "nexj" while newer values use the environment name as a suffix. Ensure that you do not remove any unrelated properties.

To clean up a JBoss instance, perform the following actions in the following files:

deploy\nexj.ear or farm\nexj.ear

Delete the old nexj.ear file as it will be redeployed with a different name.

conf\login-config.xml

Remove all <application-policy> blocks that have nexj in their names.

conf\jbossts-properties.xml

Remove all <property> tags that have XAResourceRecovery.nexj in their names.

deploy\nexj-ds.xml

Delete the nexj-ds.xml file as it is no longer required. When performing upgrades from an earlier to a later version of 5.1, instead of deleting the file, update it by removing all data sources that have nexj or nexj-<model> in the JNDI name, leaving all other entries intact.

deploy\messaging\jms-ds.xml

Remove all <[no]tx-connection-factory> blocks that have nexj in their JNDI names.

deploy\messaging\nexj-mq-service.xml

Delete the nexj-mq-service.xml file as it is no longer required. When performing upgrades from an earlier to a later version of 5.1, instead of deleting the file, update it by removing all data sources that have nexj or nexj-<model> in the JNDI name, leaving all other entries intact.