test

Sun Java System Web Server 7.0 Update 1 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 needs 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 Configuration tab and select New from the action list.

  2. In the New Instance Wizard page, select the configuration for which you need to create an instance and click Next button.

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

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

Note –

Using CLI

For creating 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 Nodes tab to view the list of nodes configured in the server.

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

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

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

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

Note –

Using CLI

For starting 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 Nodes tab to view the list of nodes configured in the server.

  2. Select the node by selecting the node name checkbox

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

  4. Select the instance and click 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

For stopping 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 Nodes tab to view the list of nodes configured in the server.

  2. Select the node by selecting the node name checkbox

  3. Click 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 need to restart the instance for some cases. 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.

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 Nodes tab to view the list of nodes configured in the server.

  2. Select the node by selecting the node name checkbox

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

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

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

Note –

Using CLI

For re-configuring 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 for it to be deleted.

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

  2. Select the configuration from the configurations list.

  3. Click 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

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