Chapter 4
Post-installation Tasks

This chapter discusses some tasks you may need to perform during or after installing the Sun ONE Application Server 7, Enterprise Edition software.

The following topics are addressed here:

Starting and Stopping the Server
Creating Domains and Instances
Web Services Client Implementation
Stopping and Starting the HADB

---

Starting and Stopping the Server

Because the Sun ONE Application Server is not automatically started during installation, you will need to start the application server environment yourself using either of the following methods:

Using the Command-line Interface
Using the Administration Interface

Using the Command-line Interface

You can use the asadmin command-line interface to start and stop:

The entire application server
A specific administrative domain
An individual application server instance

The subcommands of asadmin listed in Table 4-1 are relevant to start and stop operations.

Table 4-1  Start/Stop Subcommands of asadmin 

Subcommand	Description
start-appserv	Starts the entire Application Server.
stop-appserv	Stops the Application Server.
start-domain	Starts the administrative server and application server instances of the specified administrative domain
stop-domain	Stops the administrative server and the application server instances of the specified administrative domain.
start-instance	Starts the specified application server instance. Can be run in either a local or remote mode. In local mode, running this subcommand does not require the administrative server to be running.
stop-instance	Stops the specified application server instance. Similar in operation to start-instance.

Using start-domain and stop-domain

If the Application Server is running, use the following command to stop both the Admin Server as well as the application server instance of the initially-configured domain:

asadmin stop-domain --domain domain1 --local

where domain1 is the default name of the administrative domain defined during installation of the Application Server.

As the command completes, you should observe the following results:

asadmin stop-domain --domain domain1 --local
Instance domain1:server1 stopped
Domain domain1 Stopped.

Likewise, you can start the initially-configured administrative domain by running the following command:

asadmin start-domain --domain domain1

As the command completes, you should observe the following results:

asadmin start-domain --domain domain1
Instance domain1:admin-server started
Instance domain1:server1 started
Domain domain1 Started.

Using start-instance and stop-instance

To stop a specific application server instance without relying on the presence of an Admin Server, you can use the following command:

asadmin stop-instance --local server1

where server1 is the default name of the application server instance. If your environment contains more than one administrative domain, then you need to specify the administrative domain name when invoking the stop-instance command. For example:

asadmin stop-instance --local --domain domain1 server1

To start a specific application server instance in local mode, you can use the following command:

asadmin start-instance --local server1

If you want to start or stop an instance on a remote system, you can specify the target Admin Server and administrative user name and password on the start-instance and stop-instance commands.

Getting Helpful Information

If you run either of these subcommands without parameters, usage information is displayed. For example:

asadmin start-instance

Invalid number of operands received
Command 'start-instance' not executed successfully

USAGE: start-instance [--user admin_user] [--password admin_password] [--host localhost] [--port 4848] [--local=false] [--domain domain_name] [--debug=false] [--secure | -s] instancename

Alternatively, you can issue the subcommands followed by the --help option to obtain complete usage information.

Using the Administration Interface

When the Admin Server is running, you can use the web-based Administration interface to start and stop application server instances.

To start the Administration interface (also called the Admin Console or the graphical interface):

Open a browser window and specify the location of your Admin Server’s console application.

During installation, the default port number for the Admin Server is set to 4848. If this port was already in use, or you selected another port number, specify that port number. For example:

http://localhost:4848

Sign into the Administration interface using the administrative user name and password specified during installation.

After you've been successfully authenticated, the initial screen of the Administration interface is displayed.

Select the server1 node to access the start and stop functions.

The application server instance is either in a Running or Not Running state.

Depending on the server instance state, click either Start or Stop to start or stop the application server instance.

---

Creating Domains and Instances

The installation program creates an initial domain called domain1 with a single instance called server1. Create any additional domains and server instances using following commands:

To create a new domain:

asadmin create-domain --adminport port_number --adminuser admin --adminpassword password domain_name [--path domain_path][--sysuser sys_user] [--passwordfile file_name]

To create a new instance:

asadmin create-instance --instanceport instanceportinstance_name [--user admin_user] [-password admin_password] [--host localhost] [--port 4848] [--sysuser sys_user] [--domain domain_name] [--local=false] [--passwordfile filename][--secure|-s]

Refer to the asadmin man pages for additional information on these commands.

---

Web Services Client Implementation

To install and configure the web services client, refer to the Sun ONE Application Server Developer's Guide to Clients.

---

Stopping and Starting the HADB

This section addresses the following topics:

Stopping the HADB
Starting the HADB After Stopping

Stopping the HADB

If you are uninstalling, you will need to stop the running HADB on the node where you are working. The hadbm stop command stops all HADM processes on each node. It also captures the role of each node and saves this information locally to the /etc/opt/SUNWhadb/dbdef/mydb/stopstate file. The hadbm start command references this file so it knows what role to give the nodes when it starts the database.

To stop a running HADB, perform these steps:

Log in as root on the system where the HADB is running.
Run the hadbm stop command using the following format:

hadbm stop hadb_name

This command stops the database.

Type yes or y to confirm, anything else to cancel. When the HADB is stopped, the following is displayed:

Database successfully stopped

Verify the HADB is stopped by running the following command:

hadbm status --nodes hadb_name

The state for all nodes should be Stopped.

Note	If the inetd process was still running, the clu_nsup_srv process would be running and the state for the nodes (NodeState) would be Starting.

Starting the HADB After Stopping

You must issue the hadbm start command from the host where you issued the hadbm stop command because the stopstate file is on that host and the stopstate file is needed for the hadbm start command.

To start all active nodes of an HADB after it has been stopped using the hadbm stop command, perform these steps:

Log in as root on the system where the HADB resides.
Run the hadbm start command from the host where you issued the hadbm stop command using the following format:

hadbm start hadb_name

After the HADB has started, the following is displayed:

Database successfully started

Previous      Contents      Index      Next

---

Copyright 2003 Sun Microsystems, Inc. All rights reserved.