Configure an application

You can change the configuration of an application or module deployed on a server.

You can change the contents of and deployment descriptors for an application or module before deployment, such as in an assembly tool. However, this article assumes that the module is already deployed on a server.

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.

This article describes how to change the settings of an application or module using the administrative console.

(dependent on configuration)

• Change the settings of the application or module on the settings page for the enterprise application.

  1. Click Applications > Enterprise Applications > application_name in the console navigation tree.

  2. Change the values for settings as needed. The settings page help provides detailed information on the settings and allowed values. When you installed the application or module, you specified most, if not all, of the settings values. After installation, the settings on this page that you are likely to change include the following:

     Enable class reloading and Reloading interval	These settings control whether classes are reloaded when application files are updated. For enterprise bean (EJB) modules or any non-Web modules, enabling class reloading causes the application server run time to stop and start the application to reload application classes. For Web modules such as servlets and JavaServer page (JSP) files, a Web container reloads a Web module only when the IBM extension reloadingEnabled in the ibm-web-ext.xmi file is set to true. Refer to the settings page help for detailed information on enabling or disabling class reloading.
     Starting weight	If your application starts automatically when its server starts, this value controls how quickly the application starts. Starting weight specifies the order in which applications are started when the server starts. The application with the lowest starting weight is started first.
     Background application	If your application starts automatically when its server starts, Background application specifies whether the application must initialize fully before its server is considered started. Background applications can be initialized on an independent thread, thus allowing the server startup to complete without waiting for the application. This setting applies only if the application is run on a Version 6 (or later) application server.

  3. Click OK .

• 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.

• 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.

  1. 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.

     • Stateful session bean failover

     • Session management

     • Application profiles

     • Libraries or library references

     • Target mappings

     • Last participant support extension

     • Deployment descriptors

     • Publish WSDL files

     • Provide JMS and EJB endpoint URL information

     • Provide HTTP endpoint URL information

     • Map security roles to users/groups

     • Provide JNDI Names for Beans. For more information, refer to Task overview: Using enterprise beans in applications.

     • Map resource references to resources

     • Correct use of system identity

     • Map EJB references to beans. For more information, refer to Task overview: Using enterprise beans in applications.

     • Map data sources for all 2.x CMP beans

     • Provide default data source mapping for modules containing 2.x entity beans. For more information, refer to Creating and configuring a data source using the administrative console.

     • Map modules to servers

     • Map virtual hosts for Web modules

     • Web modules

     • EJB modules

     • Connector modules

  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. You can configure the target mapping for the application so the application does not start automatically when the server starts. To start the application, 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.

ResultThe 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.

Related tasks
Deploying and administering applications

Related reference
Enterprise application settings