Impact of Configuration Changes

Configuration changes often require that you restart Enterprise Server for the changes to take effect. In other cases, changes are applied dynamically without requiring that Enterprise Server be restarted. The procedures in this guide indicate when you need to restart the server.

• Configuration Changes That Require Server Restart

• Dynamic Configuration Changes

Configuration Changes That Require Server Restart

When making any of the following configuration changes, you must restart the server for the changes to take effect:

• Changing JVM options

• Changing port numbers

• Changing log handler elements

• Configuring certificates

• Managing HTTP, JMS, IIOP, JNDI services

• Creating or deleting resources (Exception: Some JDBC, JMS, or connector resources do not require restart.)

• Modifying the following JDBC connection pool properties:

  • datasource-classname

  • associate-with-thread

  • lazy-connection-association

  • lazy-connection-enlistment

  • JDBC driver vendor-specific properties

• Modifying the following connector connection pool properties:

  • resource-adapter-name

  • connection-definition-name

  • transaction-support

  • associate-with-thread

  • lazy-connection-association

  • lazy-connection-enlistment

  • Vendor-specific properties

Dynamic Configuration Changes

With dynamic configuration, changes take effect while the server is running. To make the following configuration changes, you do not need to restart the server:

• Adding or deleting add-on components

• Adding or removing JDBC, JMS, and connector resources and pools (Exception: Some connection pool properties require restart.)

• Adding file realm users

• Changing logging levels

• Enabling and disabling monitoring

• Changing monitoring levels for modules

• Enabling and disabling resources and applications

• Deploying, undeploying, and redeploying applications