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.

- 您必須使用管理主控台或 wsadmin Scripting 來同步化節點。在這兩個選項中,使用管理主控台是執行這項作業的最佳方法。管理主控台中的「節點」畫面包括同步化作業。
如果您需要使用 wsadmin Scripting 來同步化節點,請使用 NodeSync MBean 的 sync() 指令。
- 在同步化節點過程中,請勿重新啟動節點代理程式。透過節點代理程式起始並會影響應用程式伺服器的管理作業(例如,用於應用程式部署的節點同步化,或節點代理程式啟動時進行的更新),在節點代理程式有機會探索應用程式伺服器之前會失敗。
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.