When you make changes to the Configuration, you do not always need to restart the instance. The Administration Server supports re-configuring the server instances to pull changes made to the configuration store. In this Configuration changes are reflected on instances without a server restart. Only dynamically re-configurable changes in the configuration will be affected.
For more information on reconfig command see, Dynamic Reconfiguration in Sun Java System Web Server 7.0 Update 4 Administrator’s Configuration File Reference.
Changes in the user, temp-path, log, thread-pool, pkcs11, statistics, CGI, DNS, DNS-cache, file-cache, ACL-cache, SSL-session-cache, access-log-buffer, and JVM (except log-level ) settings will not come in to effect after a reconfiguration. Any such changes that require restart will be logged when a reconfiguration is performed. Reconfiguring the file cache requires a server restart.
Click the Nodes tab to view the list of nodes configured in the server.
Select the node by selecting the node name checkbox.
Click theReconfig Instances button to open a page window, listing all the instances deployed on that node.
Select the instance and click the Reconfig Instances button to reconfigure the instance.
Check if the status of the instance is Running and close the window.
To re-configure the server instance through CLI, execute the following command:
wadm> reconfig-instance --user=admin --password-file=admin.pwd --host=serverhost --port=8989 --config=config1 serverhost
See CLI Reference, reconfig-instance(1).