Configure enterprise application files
We can change the configuration of a Java EE application or module deployed on a server.
We 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.
Change an application or module configuration consists of one or more of the following:
- Change the settings of the application or module.
- Removing a file from an application or module.
- Update the application or its modules.
If an application is running, changing an application setting causes the application to restart. On stand-alone servers, the application restarts after we save the change. On multiple-server products, the application restarts after we save the change and files synchronize on the node where the application is installed. To control when synchronization occurs on multiple-server products, deselect Synchronize changes with nodes on the Console preferences page.
- We 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.
To use wsadmin scripting to synchronize a node, use the NodeSync mbean's 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, initiated through the node agent, and affect the application servers, fail until the node agent has a chance to discover the application servers.
Change the settings of an application or module
- View current settings of the application or module.
Applications > Application Types > WebSphere enterprise applications > application_name
Many application or module settings are available on other console pages that we can access by clicking links on the settings page for the enterprise application. For detailed information on the settings and allowed values, examine the online help for the console pages. When we installed the application or module, we specified most of the settings values.
- Map each module of the application to a target server.
Specify the application servers, clusters of application servers, or web servers onto which to install modules of the application.
- Change how quickly the application starts compared to other applications or to the server.
- Configure the use of binary files.
- Change how the application or web modules use class loaders.
- Map a virtual host for each web module of the application.
- Change application bindings or other settings of the application or module.
Application Types > WebSphere enterprise applications > application_name > property_or_item_name
- Change the values for settings as needed, and click OK. . From the enterprise application settings page, we can access console pages for further configuring of the application or module.
- Optional: Configure the application so it does not start automatically when the server starts. By default, an installed application starts when the server on which the application resides starts. We can configure the target mapping for the application so the application does not start automatically when the server starts. To start the application, we must then start it manually.
- If the installed application or module uses a resource adapter archive (RAR file), ensure that the Classpath setting for the RAR file enables the RAR file to find the classes and resources that it needs. Examine the Classpath setting on the console Resource adapter settings page.
The application or module configuration is changed. The application or standalone web module is restarted so the changes take effect.
If we updated module metadata while the application was running, restarting the application might not be sufficient for the changes to take effect. For example, if we changed descriptors in running Java EE 6 applications that use annotations, we must reinstall the application. If we 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 we 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 the 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.
Subtopics
- Application bindings
- Enterprise application collection
- Enterprise application settings
- Configure application startup
- Configure binary location and use
- Configure the use of class loaders by an application
- Manage modules settings
- Mapping modules to servers
- Mapping virtual hosts for web modules
- Mapping properties for a custom login or trusted connection configuration
Related:
Development and assembly tools Install enterprise application files Remove enterprise files Update enterprise application files Deploy and administering enterprise applications View deployment descriptors Enterprise application settings Display module build ID settings Metadata for module settings Target specific application status Application profile collection Asynchronous request dispatching settings Context root for web modules settings Correct use of the system identity EJB JNDI names for beans EJB module settings EJB references Environment entries for client modules settings Environment entries for EJB modules settings Environment entries for web modules settings Remote dispatcher property settings Initial parameters for servlets settings JSP and JSF option settings Security role to user or group mapping Last participant support extension settings Application scoped resources Resource adapter settings Resource references Shared library reference and mapping settings Session management settings Virtual hosts settings Stateful session beans failover settings (applications) Stateful session beans failover settings (EJB modules) Map data sources for all 2.x CMP beans settings Map data sources for all 2.x CMP beans Provide JMS and EJB endpoint URL information Publish WSDL compressed files settings Provide HTTP endpoint URL information Web module deployment settings Service providers collection at the application level Service provider policy sets and bindings collection Service clients collection at the application level Service client policy set and bindings collection SQLJ profiles and pureQuery bind files settings