WAS v8.5 > Administer applications and their environment > Deploy enterprise applications

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 the module is already deployed on a server. Changing 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.
• Updating 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 you save the change. On multiple-server products, the application restarts after you 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.

• You must use either the dmgr console or wsadmin scripting to synchronization a node. Of these two options, using the dmgr console is the best way to perform this operation. The Nodes panel in the dmgr console includes the Synchronize operation.

  If you need 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, 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 dmgr console.

• View current settings of the application or module.

  Click Applications > Application Types > WebSphere enterprise applications > application_name to access the enterprise application settings page.

  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 you installed the application or module, you specified most of the settings values.

• Map each module of the application to a target server.

  Specify the 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.

  1. Click Applications > Application Types > WebSphere enterprise applications > application_name > property_or_item_name. From the enterprise application settings page, we can access console pages for further configuring of the application or module.

  2. Change the values for settings as needed, and click OK.

• 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, you must then start it manually.

• If the installed application or module uses a resource adapter archive (RAR file), ensure 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.

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.

Save changes to your administrative configuration.

Subtopics

• Application bindings
  Before an application that is installed on an application server can start, all EJB references and resource references defined in the application must be bound to the actual artifacts (enterprise beans or resources) defined in the application server.
• Configure application startup
  We can configure the startup behavior of an application. The values set affect how quickly an application starts and what occurs when an application starts.
• Configure binary location and use
  We can designate where binary files (binaries) used by the application reside, whether the product distributes binaries for you automatically, and otherwise configure the use of binaries.
• Configure the use of class loaders by an application
  We can configure whether the application and web modules use their own class loaders to load classes or use different class loaders, as well as configure the reloading of classes when application files are updated. Class loaders enable an application to access repositories of available classes and resources.
• Manage modules settings
  Use this page to specify deployment targets where to install the modules that are contained in the application. Modules can be installed on the same deployment target or dispersed among several deployment targets.
• Map modules to servers
  Each module of a deployed application must be mapped to one or more target servers. The target server can be an application server or web server.
• Map virtual hosts for web modules
  A virtual host must be mapped to each web module of a deployed application. Web modules can be installed on the same virtual host or dispersed among several virtual hosts.
• Map properties for a custom login or trusted connection configuration
  Use this page to view and manage the mapping properties for a custom login configuration or a trusted connection configuration.
• Application bindings
  Before an application that is installed on an application server can start, all EJB references and resource references defined in the application must be bound to the actual artifacts (enterprise beans or resources) defined in the application server.
• Enterprise application page
  Use this page to view and manage enterprise applications.
• Configure application startup
  We can configure the startup behavior of an application. The values set affect how quickly an application starts and what occurs when an application starts.
• Configure binary location and use
  We can designate where binary files (binaries) used by the application reside, whether the product distributes binaries for you automatically, and otherwise configure the use of binaries.
• Configure the use of class loaders by an application
  We can configure whether the application and web modules use their own class loaders to load classes or use different class loaders, as well as configure the reloading of classes when application files are updated. Class loaders enable an application to access repositories of available classes and resources.
• Manage modules settings
  Use this page to specify deployment targets where to install the modules that are contained in the application. Modules can be installed on the same deployment target or dispersed among several deployment targets.
• Map modules to servers
  Each module of a deployed application must be mapped to one or more target servers. The target server can be an application server or web server.
• Map virtual hosts for web modules
  A virtual host must be mapped to each web module of a deployed application. Web modules can be installed on the same virtual host or dispersed among several virtual hosts.
• Map properties for a custom login or trusted connection configuration
  Use this page to view and manage the mapping properties for a custom login configuration or a trusted connection configuration.

Related concepts:

Development and assembly tools

Related

Install enterprise application files
Remove enterprise files
Update enterprise application files
Deploy enterprise applications
View deployment descriptors

Reference:

Enterprise application page
Enterprise application settings
Display module build ID settings
Metadata for module settings
Target specific application status
Application profile page
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
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 page
Service clients collection at the application level
Service client policy set and bindings page
SQLJ profiles and pureQuery bind files settings

+

Search Tips   |   Advanced Search