Cleaning up old WebSphere 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, use the Integrated Solutions Console to uninstall the old nexj application.
In addition, for each deployment with a unique environment name, the server has a set of configuration data. Keeping the old 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.
- the old
nexj
application - connection factories with
nexj
in the name - queues with
nexj
ornexj-<model>
in the name - JDBC providers with
nexj
ornexj-<model>
in the name - thread pools with
nexj
ornexj-<model>
in the name