+

Search Tips   |   Advanced Search

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:

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.


Change the settings of an application or module

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


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