Use this page to modify settings on an existing on demand router (ODR).
To view this administrative console page, click . On the Configuration tab, you can edit ODR setting fields.
To change the ODR settings, you must have administrator or configurator administrative privileges.
To configure the ODR to perform advanced routing options, such as routing requests to a cell that is not running WebSphere® Application Server, and to perform caching, click On demand router properties.
Indicates a logical name for the ODR. ODR names must be unique within a node.
This is a read-only field.
Enabling this option can reduce the startup time of an ODR. This time can include Java Virtual Machine (JVM) settings, such as disabling bytecode verification and reducing just-in-time (JIT) compilation costs. Do not enable this setting on production servers.
Check the check box to reduce the startup time of an ODR. This time can include Java Virtual Machine (JVM) settings, such as disabling bytecode verification and reducing just-in-time (JIT) compilation costs. Do not enable this setting on production servers.
Enable this option if you want to use the -Xverify and -Xquickstart JVM settings on startup. After checking the check box, save the configuration and restart the ODR to activate development mode.
Select this field to start the ODR on multiple threads. This option might shorten the startup time.
Check the check box if you want the ODR components, services, and applications to start in parallel, rather than sequentially.
The order in which the applications start depends on the weights that you assigned to each of them. Applications that have the same weight start in parallel. Set the weight of an application with the Starting weight option on the page of the administrative console.
Select this property if you want the server components started as they are needed by an application that is running on this server.
When this property is selected, server components are dynamically started as they are needed. When this property is not selected, all of the server components are started during the server startup process. Therefore, selecting this option can improve startup time, and reduce the memory footprint of the server, because fewer components are started during the startup process.
Starting components as they are needed is most effective if all of the applications, that are deployed on the server, are of the same type. For example, using this option works better if all of your applications are web applications that use servlets, and JavaServer Pages (JSP). This option works less effectively if your applications use servlets, JSPs and Enterprise JavaBeans (EJB).
If the ODR is a part of a cluster, information about the cluster displays.