Sun Java System Web Server 7.0 Update 7 Administrator's Guide

Managing Server Instances

Creating a Server Instance

Before creating a new server instance, perform the following checks:

  1. Check whether you have created a configuration. Creating a new server instance requires an existing instance configuration to be specified.

  2. Check if all the available nodes in the Server Farm already have an instance of the required configuration. You can not create duplicate instances.

Create a new server instance by performing the following tasks:

  1. Click the Configuration tab and click the configuration link that you want to create an instance.

  2. In the New Instance Wizard page, select the configuration for which you need to create an instance. Select the SMF Service if you want to create a service for this instance and click the Next button.

  3. Select the nodes on which instances of the selected configuration [Step 2] should exist. Click the Next button.

  4. View the summary of your selection. Click the Next button to view the result of the operation.


Note –

Using CLI

To create a server instance, execute the following command:


wadm> create-instance --user=admin --password-file=admin.pwd 
--host=serverhost --port=8989 --config=config1 serverhost

See CLI Reference, create-instance(1).

Starting Server Instances

  1. Click the Nodes tab to view the list of nodes configured in the server.

  2. Select the node by selecting the node name checkbox.

  3. Click the Start Instances button to open a page window, listing all the instances controlled by that node.

  4. Select the instance and click the Start Instances button to start the instance.

  5. Check if the status of the instance is Running and close the window.


Note –

Using CLI

To start a server instance through CLI, execute the following command:


wadm> start-instance --user=admin --password-file=admin.pwd --host=serverhost 
--port=8989 --config=config1 nodehost1

See CLI Reference, start-instance(1).

Stopping Server Instances

  1. Click the Nodes tab to view the list of nodes configured in the server.

  2. Select the node by selecting the node name checkbox

  3. Click the Stop Instances button to open a page window, listing all the instances controlled by that node.

  4. Select the instance and click the Stop Instances button to stop the instance.

  5. Check if the status of the instance is Not Running and close the window.


Note –

Using CLI

To stop a server instance through CLI, execute the following command:


wadm> stop-instance --user=admin --password-file=admin.pwd --host=serverhost 
--port=8989 --config=config1 nodehost1

See CLI Reference, stop-instance(1).


Restarting Server Instances

  1. Click the Nodes tab to view the list of nodes configured in the server.

  2. Select the node by selecting the node name checkbox.

  3. Click the Restart Instances button to open a page window, listing all the instances controlled by that node.

  4. Select the instance and click Restart Instances button to restart the instance.

  5. Check if the status of the instance is Running and close the window.


Note –

Using CLI


wadm> restart-instance --user=admin --password-file=admin.pwd 
--host=serverhost --port=8989 --config=config1 nodehost1

See CLI Reference, restart-instance(1).


Re-Configuring Server Instances

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 7 Administrator’s Configuration File Reference.


Note –

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.


  1. Click the Nodes tab to view the list of nodes configured in the server.

  2. Select the node by selecting the node name checkbox.

  3. Click the Reconfig Instances button to open a page window, listing all the instances deployed on that node.

  4. Select the instance and click the Reconfig Instances button to reconfigure the instance.

  5. Check if the status of the instance is Running and close the window.


Note –

Using CLI

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


Deleting Server Instances


Note –

The server instance should not be running in order for it to be deleted.


  1. Click the Configuration tab to view the list of available configurations.

  2. Select the configuration from the configurations list.

  3. Click the Instances sub tab.

  4. Select the instance from the list of deployed instances under the Nodes section.

  5. Select Delete Instances from the action drop-down list to delete the selected instance.


Note –

Using CLI

To delete a server instance through CLI, execute the following command:


wadm> delete-instance --user=admin --password-file=admin.pwd --host=serverhost 
--port=8989 --config=config1 serverhost

See CLI Reference, delete-instance(1).