Changing Application Server Configuration

When making any of these configuration changes, restart the server for the changes to take effect:

• Changing JVM options

• Changing port numbers

• Managing HTTP, IIOP, and JMS services

• Managing thread pools

• Modifying the following JDBC connection pool properties:

  • datasource-classname

  • JDBC-driver vendor specific properties

  • associate-with-thread

  • lazy-connection-association

  • lazy-connection-enlistment

• Modifying the following connector connection pool properties:

  • resource-adapter-name

  • connection-definition-name

  • transaction-support

  • vendor specific properties

  • associate-with-thread

  • lazy-connection-association

  • lazy-connection-enlistment

For instructions, see Restarting the Domain.

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

• Deploying and undeploying applications

• Adding or removing JDBC, JMS, and Connector resources and pools

• Changing logging levels

• Adding file realm users

• Changing monitoring levels

• Enabling and disabling resources and applications

Note that the asadmin reconfig command has been deprecated and is no longer necessary. Configuration changes are applied to the server dynamically.