Before creating a new server instance, perform the following checks:
Check whether you have created a configuration. Creating a new server instance needs an existing instance configuration to be specified.
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:
Click Configuration tab and click the configuration link that you want to create an instance.
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 instanceand click Next button.
Select the nodes on which instances of the selected configuration [Step 2] should exist. Click Next button.
View the summary of your selection. Click Next button to view the result of the operation.
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).
Click Nodes tab to view the list of nodes configured in the server.
Select the node by selecting the node name checkbox.
Click Start Instances button to open a page window, listing all the instances controlled by that node.
Select the instance and click Start Instances button to start the instance.
Check if the status of the instance is Running and close the window.
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).
Click Nodes tab to view the list of nodes configured in the server.
Select the node by selecting the node name checkbox
Click Stop Instances button to open a page window, listing all the instances controlled by that node.
Select the instance and click Stop Instances button to stop the instance.
Check if the status of the instance is Not Running and close the window.
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).
Click Nodes tab to view the list of nodes configured in the server.
Select the node by selecting the node name checkbox
Click Restart Instances button to open a page window, listing all the instances controlled by that node.
Select the instance and click Restart Instances button to restart the instance.
Check if the status of the instance is Running and close the window.
Using CLI
wadm> restart-instance --user=admin --password-file=admin.pwd --host=serverhost --port=8989 --config=config1 nodehost1 |
See CLI Reference, restart-instance(1).
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.
For more information on reconfig command see, Dynamic Reconfiguration in Sun Java System Web Server 7.0 Update 2 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 Nodes tab to view the list of nodes configured in the server.
Select the node by selecting the node name checkbox
Click Reconfig Instances button to open a page window, listing all the instances deployed on that node.
Select the instance and click Reconfig Instances button to reconfigure the instance.
Check if the status of the instance is Running and close the window.
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).
The server instance should not be running for it to be deleted.
Click Configuration tab to view the list of available configurations.
Select the configuration from the configurations list.
Click Instances sub tab.
Select the instance from the list of deployed instances under the Nodes section.
Select Delete Instances from the action drop-down list to delete the selected instance.
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).