Sun Java Studio Enterprise 7 Installation Guide

After installation, you can use the procedures in this chapter to validate correct installation and configuration of your Java Studio Enterprise servers. This chapter describes:

• Overview of the Validation Process
• Validating Server Installation
• Stopping Servers
• Finding Additional Documentation
• Troubleshooting During Server Validation

---

Overview of the Validation Process

This section contains an overview of the general validation process, the use of the start server scripts and information on how to find configuration data.

To start and stop the root-owned component product servers, you must have root privileges. If you created a non-root instance of Application Server or Web Server, you can start and stop those instances while logged in as the non-root user account that was specified during installation.

The basic process for starting most Java Studio Enterprise servers has three steps:

1. Start the admin server process.

2. Log in to the administrative tool.

Most of the servers have browser-based interfaces to the administrative tool.

3. Start your server instance using the administrative interface.

Most of the servers also have command-line interfaces. See the documentation for the component products for additional information.

Sun Java System Application Server Standard Edition 7 2004Q2 and Sun Java System Web Server 6 2004Q1 Update 1, Service Pack 2 can also be started and stopped from the Java Studio Enterprise IDE via their respective plug-ins.

Finding Configuration Data

To perform the server validation procedures you need to know the port numbers, instance names, and other configuration data for the servers that you installed. You can review the configuration data for each server in the following ways:

• View the configuration data from your web browser. The file Configuration_Data.html is saved in the java-studio-install-dir.
• View the Summary Report created by the installer. This report is saved at /var/sadm/install/logs/Summary_Report.timestamp

---

Validating Server Installation

To start all the servers, the exact procedures depend on which servers you have installed and which installation options you have selected. You may need to run the start servers script once while logged in as root and again while logged in with your normal, non-root account login. See Product Usage by Non-root User for a description of this option and the resulting server instances.

TABLE 14-1 lists the procedures to use for validating your server installation.

1. Log in as root.

2. Change to the directory containing the start servers script. For example, if you used the default installation directory:

# cd /opt/SUNWjstudio04q4/bin

3. Run the script.

# ./startservers

If you installed all the server runtimes, you see output like the following:

Following server product(s) can be started:

[1] Sun Java [tm] System Administration Server 5 2004Q2

[2] Sun Java [tm] System Directory Server 5 2004Q2

[3] Sun Java [tm] System Web Server 6 2004Q1 Update 1 SP2

[4] Sun Java [tm] System Application Server Standard Edition 7 2004Q2

[5] Sun Java [tm] System Access Manager 2004Q2

Servers to be started [1,2...,all,q] ?:

4. Type all to start all installed root-owned servers.

You see messages indicating the progress of the script.

1. Exit from root privileges and log in with your normal non-root user account information.

2. In a terminal window, change to the directory containing the start servers script and execute the script as the non-root user.

% ./startservers

You see output similar to the following:

Following server product(s) can be started:

[1] Sun Java [tm] System Web Server 6 2004Q1 Update 1 SP2

[4] Sun Java [tm] System Application Server Standard Edition 7 2004Q2

Servers to be started [1,2...,all,q] ?:

3. Type all to start all your non-root owned servers.

Now you can access the admin consoles and verify the server status and do other admin tasks. Completing this additional step for each installed server verifies that the server runtimes were installed and configured properly.

Accessing Server Admin Consoles

Complete this step to verify proper connectivity and access to the admin console for each installed server after you have run the start servers script.

1. Start your web browser.

2. If you access the web using a proxy server, verify that your proxy server settings will enable you to access the server URLS on your local machine.

3. In your web browser, open the Configuration_Data.html file.

This file is created by the installer and stored in the default install directory. The report looks similar to FIGURE 14-1:

FIGURE 14-1 Configuration_Data.html Report

4. Find the entry labeled Application Server Admin URL and click on the link.

You are prompted for your username and password for Application Server.

5. Type the Application Server Admin User Id and Password and click OK.

The Application Server Admin Console displays in your browser.

1. Verify that Web Server processes are running.

# ps -ef | grep webservd

2. Repeat steps 1 and 2 of the prior procedure to open the Configuration_Data.html file or use the back button of your browser to return to the file.

3. Find the entry labeled Web Server Admin URL and click the link.

You are prompted for the username and password for Web Server Administration.

4. Type the admin user ID and password selected during installation and click OK.

The Web Server Administration Console is displayed in your browser.

1. (Optional) If you installed Access Manager, return to the Configuration Data report in your browser and in the section for Sun Java System Access Manager 2004Q2, in the name column find the row labeled Access Manager Console URL.

2. Click the link.

You see the Sun Java System Identity Server Login page.

3. Type your User Name (amadmin) and Password and click Log In.

The Access Manager admin console displays in your browser window.

[ D ]

1. Verify that the Directory Server process is running.

% ps -ef | grep slapd

2. Grep for the process appservd when Application Server is the container and for the process webservd when Web Server is the container.

3. Log out from Access Manager Console and start a new browser instance.

4. Open the Configuration_Data.html file and find the section for Sun Java System Portal Server 2004Q2.

In the name column find the row labeled Portal Server Console URL.

5. Click the link.

The Sun Java System Portal Server 2004Q2 sample desktop displays in your browser.

[ D ]

Congratulations, your servers were installed and configured correctly. You are ready to begin development.

---

Stopping Servers

The easiest way to stop all the installed servers is to run the stop server script once as root and once as non-root. You can also stop the servers individually from the command line.

1. Become root user.

2. Change to the directory containing the script. For example, if you accepted the default installation directory, type:

# cd /opt/SUNWjstudio04q4/bin

3. Invoke the stop server script.

# ./stopservers

Run the stop server script as the non-root user if you need to stop the server instances owned by the non-root user.

1. Log in as root.

2. Change to java-studio-install-dir/AppServer7/bin. For example, type:

# cd /opt/SUNWappserver/bin

3. Stop the Application Server instances.

# ./asadmin stop-domain --domain domain1

You see output similar to the following:

Instance domain1:admin-server stopped

Instance domain1:server1 stopped

Domain domain1 stopped

4. (Optional) Verify that Application Server is no longer running.

# ps -ef | grep appservd

1. Log in as root.

2. Change to the installation directory for Web Server Admin Server. For example:

# cd /opt/SUNWwbsvr/https-admserv

3. Stop the Web Server admin process.

# ./stop

4. Change to the installation directory for your Web Server instance. For example:

# cd /opt/SUNWwbsvr/https-machinename.domainname

5. Stop the Web Server instance.

# ./stop

6. Verify that Web Server is no longer running.

# ps -ef | grep webservd

1. Log in as root.

2. Change to the directory containing the stop script for your server instance. The directory name is of the form slapd-instancename, where instancename is usually the host name of the machine. For example, if host1 is your machine name. For example:

#cd /opt/SUNWdirserver/slapd-host1

3. Stop Directory Server.

# ./stop-slapd

4. Stop Directory Server admin server.

# ./stop-admin

5. Verify that Directory Server instances are no longer running.

# ps -ef | grep slapd

---

Finding Additional Documentation

You can find documentation at docs.sun.com. The following tables lists links to some of the available documentation titles.

---

Troubleshooting During Server Validation

The Java Studio Enterprise servers have specific dependencies and need to be started in the proper startup sequence. If you are using only Application Server or Web Server, then there is no startup sequence requirement. If you are starting the server runtimes manually, then observe the proper startup sequence. The Start Menu script takes care of these dependencies automatically.

The startup sequence is important when using Access Manager and Portal Server. Access Manager and Portal Server are deployed as web applications running on either Application Server (default) or Web Server (selection available throught the Product Selection panel of the installer, see Container Selection). Access Manager and Portal Server also rely on Directory Server. Therefore, before attempting to access either Access Manager or Portal Server, you must start both Directory Server and the appropriate web container. To shut down the servers, reverse the sequence.

If you experience any difficulties starting the admin consoles for Access Manager and Portal Server, confirm the following:

• Web browser has the correct proxy settings, use the procedure: To Verify Web Browser Proxy Settings
• Servers have been started in the correct sequence, use the procedure: To Start Servers in the Correct Sequence
• Directory Server connectivity, use the procedure: To Verify Directory Server Connectivity

If you see Page Not Found Errors while trying to access the admin console for Access Manager or while trying to display the Portal Server Desktop, check your web browser proxy settings. To access the servers that you have installed, the web browser should not be trying to resolve the URLs using a proxy server. For example, on Mozilla1.4, use these steps to change the proxy settings:

1. In the web browser window, click Edit Preferences.

2. Expand the Advanced node and select Proxies.

The Proxies dialog box is displayed. If you are using a proxy server, the option Manual Proxy Configuration is selected.

3. Verify that your server domains are listed in the text box labeled "No Proxy for:".

1. Start Directory Server.

Start both the admin server and the server instance.

2. Start the web container, either Application Server (default) or Web Server.

Start both the admin server and the server instance.

3. Now, try accessing Access Manager or the Portal Server desktop.

1. Log in as root.

2. Change to the directory containing the start script for your server instance. The directory name is of the form slapd-machinename, where machinename is the name of the machine. For example, if host1 is your machine name:

# cd /opt/SUNWdirserver/slapd-host1

3. Start Directory Server.

# ./start-slapd

4. Verify that Directory Server is running.

ps -ef | grep slapd

You see output similar to the following:

# root  1297     1  0   Jul 01 ?        2:27 ./ns-slapd -D /opt/SUNWdirserver/slapd-host1 -i /opt/SUNWdirserver/slapd-host1

5. Start the Directory Server Admin Server.

# cd /opt/SUNWdirserver

# ./start-admin

6. Start the Sun Java System Server Console.

# ./startconsole

The Java System Console login dialog appears.

7. Type your User ID and Password and click OK.

Your login to Sun Java System Server Console confirms successful installation.

8. (Optional) On the Servers and Applications tab, expand your server host node, then expand the Server Group node.

You see an entry for the Administration Server and an entry for your server of form Directory Server (machinename).

9. Double-click on the Directory Server (host-name) node.

The Sun Java System Directory Server console for your server instance appears. From this console, you can start, stop, and restart your server instance.

Diagnosing Common Errors

This section lists some of the more common errors you might see.

1. Trying to access Access Manager Console from your web browser results in the following error:

Server Error

This server has encountered an internal error which prevents it from fulfilling your request. The most likely cause is a misconfiguration. Please ask the administrator to look for messages in the server's error log.

Reason: Access Manager relies on other Java Studio Enterprise servers, such as Directory Server and Application Server or Web Server. The servers may not all be running.

Solution: Start the servers in the proper sequence. See To Start Servers in the Correct Sequence for details.

2. Trying to start Access Manager from the command line, you see the following error:

Reason: Access Manager relies on other Java Studio Enterprise servers, such as Directory Server and Web Server. The servers may not all be running.

Solution: Start the servers in the proper sequence. See To Start Servers in the Correct Sequence for details.

3. After starting all the servers, trying to access the amserver by using an URL of the form http://localhost/amserver gives you a Page Not Found error.

Reason: You may have an incorrect proxy server setting specified in your web browser settings. Your browser may be trying to resolve the URL by using the proxy server if one is set.

Solution: Set the Web browser proxy setting to direct connection or to not use a proxy server for the server domain name you are using.

4. Installing Java Studio Enterprise results in either a failed installation or failed configuration of Access Manager:

Reason. Your system DNS Suffix may not be set correctly.

Solution. See Verifying the DNS Suffix.

5. Trying to access Portal Server Desktop, you see this error in the browser window:

Reason: You have not logged out of Access Manager Console before trying to access Portal Server Desktop.

Solution: Logout of Access Manager Console and start a new instance of your browser and try again.

Sun Java Studio Enterprise 7 Installation Guide

817-7971-10

Copyright © 2004, Sun Microsystems, Inc. All Rights Reserved.