You can change the configuration of an application or module deployed
on a server.
Before you begin
You can change the contents of and deployment descriptors for 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:
This topic describes how to change the settings of an application
or module using the administrative console.
Attention: 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.
Procedure
- View current settings of the application or module.
Click Applications > Enterprise Applications >application_name to
access the settings page
for the enterprise application.
Many application or module settings
are available on other console pages that you 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
your application to a target server.
Specify the application
servers, clusters of
application servers, or Web servers onto which to install modules of
your application.
- Change
how quickly your application starts compared to other applications
or to the server.
- Configure the use of binary files.
- Change
how your application or Web modules use class loaders.
- Map a virtual
host for each Web module of your application. Configuring virtual hosts provides information on virtual
hosts.
- Change application
bindings or other settings of the application or module.
- Click Applications > Enterprise Applications
> application_name > property_or_item_name in the
console navigation tree. From the application settings page, you can access console
pages for further configuring of the application or module.
- 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. You 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 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.
Results
The application or module configuration is changed. The application
or standalone Web module is restarted so the changes take effect.
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.
In the Network Deployment
product, 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.