Configuring enterprise application files
You can change the configuration of a Java™ Platform, Enterprise Edition (Java EE) application or module deployed on a server.
Before you begin
You can change the contents and deployment descriptors of an application or module before deployment, such as in an assembly tool. However, it is assumed that the module is already deployed on a server.
About this task
Changing an application or module configuration consists of one or more of the following:
- Changing the settings of the application or module.
- Removing a file from an application or module.
- Updating the application or its modules.
- You must use either the administrative console or wsadmin scripting to synchronization a node.
Of these two options, using the administrative console is the best way to perform this operation.
The Nodes panel in the administrative console includes the Synchronize
operation.
If you need to use wsadmin scripting to synchronize a node, use the NodeSync MBean sync() command.
- Do not restart the node agent as part of the synchronize node process. Administration operations, such as node synchronization for application deployment, or updates that take place while the node agent is starting, that are initiated through the node agent, and affect the application servers, fail until the node agent has a chance to discover the application servers.
Complete the following procedure to change the settings of an application or module using the administrative console.
Procedure
Results
The application or module configuration is changed. The application or standalone web module is restarted so the changes take effect.
If you updated module metadata while the application was running, restarting the application might not be sufficient for the changes to take effect. For example, if you changed descriptors in running Java EE 6 applications that use annotations, you must reinstall the application. If you changed classes that introduce, remove, or alter class hierarchies within an application, and those changes impact annotated classes, you also must reinstall the application.
What to do next
If the application or module is deployed on a cluster and you have no more configuration changes to make, click Rollout Update on the Enterprise applications page to propagate the changed configuration on all cluster members of the cluster on which the application or module is deployed. Rollout Update sequentially updates the configuration on the nodes that contain cluster members.
Save changes to your administrative configuration.
On multiple-server products, the application binaries are transferred to nodes when the configuration changes on the deployment manager synchronize with configurations for individual nodes on which the application will run.