C H A P T E R 13 - Using Java Studio Enterprise Servers (Microsoft Windows)

C H A P T E R 13

Using Java Studio Enterprise Servers (Microsoft Windows)

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

Overview of the Validation Process

Validating Server Installation

Finding Additional Documentation

Troubleshooting During Server Validation

Overview of the Validation Process

This section contains an overview of the general validation process and information on how to find configuration data.

To start and stop a component product server, you must have administrative rights. 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 on administration issues.

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.

TABLE 13-1 lists the procedures to use for validating each server installation.

TABLE 13-1 Procedures for Validating Java Studio Enterprise Servers (Windows)
Task	Windows Instructions
Validate Application Server	To Validate Application Server
Validate Web Server	To Validate Web Server
Validate Access Manager	To Validate Access Manager (formerly Identity Server)
Validate Portal Server	To Validate Portal Server

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.

The report is placed in the directory specified by the environment variable %TEMP%. For example C:\Documents and Settings\Administrator\Local Settings\Temp\Summary_Report.timestamp.

Validating Server Installation

On Microsoft Windows systems, you can start the servers from the Start Menu or the command line. For command line information, please see Appendix C. This section describes using the Start Menu entries for starting and stopping the servers.

The quickest way to verify the server installations is to use the Start Menu option to start all the servers and then verify access to the administrative tool for each one. These instructions assume that you are logged in as a user with administrative privileges.

To Start and Validate All Servers

1. Choose Start right arrow Programs Sun Microsystems Java Studio Enterprise 7 2004Q4 Start Servers All Servers.

This starts all the installed servers in the proper order.

2. (Optional) Access the Computer Management Services dialog to verify that the servers started properly by following these steps:

a. Open the Computer Management dialog.

(Microsoft Windows 2000 Pro) Right-click on the My Computer icon and select Manage from the contextual menu.

(Microsoft Windows XP Pro) Choose Start, right-click My Computer, and click Manage from the contextual menu.

b. Double-click Services and Applications.

c. Double-click Services.

d. Scroll down the list of services to see the following Java Studio Enterprise server entries. Verify that the Status column for each server entry shows the value Started:

Sun App Server 7 (domain1:server1)

Sun App Server 7 (jstudio-domain:jstudio-server)

Sun App Server 7 Admin Server (domain1:admin-server)

Sun App Server 7 Admin Server (jstudio-domain:admin-server)

Sun ONE Administration Server 5.2

Sun ONE Directory Server 5.2 (machinename)

Sun ONE Web Server 6.1 (https-machinename.domainname)

Sun ONE Web Server 6.1 Administration Server

3. Access the administrative console for the servers as follows:

a. For Application Server, follow steps 2-3 of the procedure To Validate Application Server.

b. For Web Server, follow steps 2-5 of the procedure To Validate Web Server.

c. For Access Manager, use the procedure To Validate Access Manager (formerly Identity Server).

d. For Portal Server, use the procedure To Validate Portal Server.

e. For Directory Server, follow steps 2-5 of the procedure To Validate Directory Server Installation.

To Validate Application Server

1. Choose Start right arrow Programs Sun Microsystems Java Studio Enterprise 7 2004Q4 Start Server Application Server.

This starts the Application Server admin process and the default instance.

2. Choose Start right arrow Programs Sun Microsystems > Java Studio Enterprise 7 2004Q4 > Administration Consoles > Application Server.

The Application Server Administration login prompt appears.

3. Type your User Name and Password and click OK.

Use the values specified during installation. Application Server Console appears.

Application Server Console showing server1 instance in right-hand side.

4. Click the server1 node in the left frame to check the status of the server instance.

Application Server Console showing server1 status.

Note - Starting Application Server from outside the IDE using the Start Menu entry starts all instances of Application Server created by the Java Studio Enterprise installer. Using the IDE to start the server enables you to start a specific instance.

To Validate Web Server

You can start Web Server from the Start Menu or from inside the Java Studio Enterprise IDE. This procedure describes using the Start Menu.

1. Choose Start right arrow Programs Sun Microsystems Java Studio Enterprise 7 2004Q4 Start Servers Web Server.

This starts the Web Server Administration service.

2. Choose Start right arrow Programs Sun Microsystems Java Studio Enterprise 7 2004Q4 Administration Consoles Web Server.

The Web Server Administration login prompt appears.

Web Server Administration log in prompt with no values for User Name and Password. Buttons are OK and Cancel.

If you see the following error:

The connection was refused when attempting to contact servername:portnumber

Check to be sure that the Web Server admin server is actually started. Do this by checking your Microsoft Windows Services and confirming that Sun One Web Server 6.1 Administration Console shows a status of started. Refer to Appendix C for details on how to start this service from the command line if needed.

Check that your proxy settings are set to use direct connection or not use a proxy server for your Web Server domain name.

Tip - If you see an error stating that the proxy server could not locate your web server, an incorrect proxy setting could be the cause. Check your web browser proxy settings and be sure that the domain used for your web server installation is set to "no proxy". Check the documentation for your browser for information on how to edit the proxy settings.

3. Type your User Name and Password and click OK.

These are the values you provided on the Configuration page during installation. The Web Server Console appears in your browser window.

Web Server Administration Console showing Servers tab. [ D ]

4. Select your server instance and click Manage.

Web Server Manager displays your server instance.

Web Server Manager showing server instance status.

If you see this JavaScript Application popup dialog:

Warning message popup dialog. Button is OK.

Click OK and use the `Apply' button as described to Apply Changes.

5. Confirm that your server instance is running by clicking Server On if your server instance is off.

To Validate Access Manager (formerly Identity Server)

To use the Access Manager Admin Console, Directory Server and your web container instance and admin server must be running. The default container is Application Server. If you started all servers using the Start Menu, this has been done.

1. Change to the java-studio-install-dir and open the Configuration_Data.html file in your web browser.

This file shows the URLs assigned for each server runtime that you installed.

2. Locate the section of this report for Sun Java System Access Manager 6.1.

Review the entries and find the row labeled Access Manager Server Console URL. This should be a live hypertext link of the form http://machinename.domainname:port-number/amconsole.

3. Click on this link.

The Access Manager Admin Console login dialog appears in the browser window.

Access Manager login prompt with empty data fields, User Name and Password.Access Manager Console login prompt with no values for User Name and Password. Button is Log In.

4. Type your User Name and Password and click Log In.

Access Manager's Console appears in your browser window.

Note - User Name is amadmin. Password is the value specified during installation.

Access Manager Console. [ D ]

Using Access Manager

Access Manager uses the amldapuser as the bind user to search for users in the directory during authentication. This user by default has read access to the directory. The bind password for this user is prereconfigured by the installer by appending a `1' to the Administrator Password that is used during installation. For example, if you type admin123 as the Administrator Password on the installer's Configuration page, the assigned amldapuser password is admin1231.

To Validate Portal Server

After successfully following all the prior procedures to validate Directory Server, the web container and Access Manager, perform these additional steps.

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

2. In your web browser open the java-studio-install-dir\Configuration_Data.html file .

This file shows the URLs assigned for each server runtime that you installed.

3. Locate the section of this report for Sun Java System Portal Server 6.2.

4. Review the entries and find the row labeled Portal Server Console URL. This is a live hypertext link of the form: http://webcontainerhost.domainname:port-number/portal.

For example, using the default values for the port number with Application Server as the web container, the URL might look like this: http://host1.my.company.com:8080/portal.

5. Click this link.

The Portal Server Desktop appears in the browser window. Display of the sample desktop confirms successful deployment of Portal Server on your web container instance.

Portal Server desktop. [ D ]

To Stop All Servers

Choose Start right arrow Programs Sun Microsystems Java Studio Enterprise 7 2004Q4 Stop Servers All Servers.

Finding Additional Documentation

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

TABLE 13-2 Server Runtime Documentation Links (Windows versions)
Component Product Server Runtime Version	Link
Sun Java System Application Server Standard Edition 7 2004Q2	`http://docs.sun.com/db/coll/ApplicationServer7_04q2`
Sun Java System Web Server 6 2004Q1 Update 1, Service Pack 2	`http://docs.sun.com/db/coll/S1_websvr61sp2_en`
Sun Java System Message Queue 3.5 SP 1	`http://docs.sun.com/db/coll/MessageQueue_35_SP2`
Sun Java System Directory Server 5.2	`http://docs.sun.com/db/coll/S1_DirectoryServer_52`
Sun Java System Access Manager 6.1	`http://docs.sun.com/db/coll/S1_IdServ_61`
Sun Java System Portal Server 6.2	`http://docs.sun.com/db/coll/S1_PortalServer_62`
Sun Java System Identity Server Policy Agent 2.1 for Sun Java System Application Server 7	`http://docs.sun.com/db/coll/S1_IdServPolicyAgent_21`

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 (formerly Identity Server) and Portal Server. Access Manager and Portal Server are deployed as web applications running on either Application Server (default) or Web Server (selection available through the Product Selection page 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.

Note - The script, startservers.bat, found at java-studio-install-dir\bin automatically starts all the servers in the proper order. You can run this script from the command line or you can use the Windows Start Menu.

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 Validate Directory Server Installation

To Verify Web Browser Proxy Settings

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 right arrow 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:".

To Start Servers in the Correct Sequence

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.

To Validate Directory Server Installation

1. Choose Start right arrow Programs Sun Microsystems Java Studio Enterprise 7 2004Q4 Start Servers Directory Server.

This starts Directory Server's admin process and Directory Server's server instance.

2. Choose Start right arrow Programs Sun Microsystems Java Studio Enterprise 7 2004Q4 Administration Consoles Directory Server.

The Server Console Login dialog appears. The User ID and Administration URL display the values used during installation and configuration.

Server Console login dialog with prepopulated values for User ID and Administration URL, no value for Password. Buttons are OK, Cancel and Help.

3. Type your Password and Click OK.

This is the password that you used on the Configuration page during installation. The Server Console appears.

Server Console showing installed server tab.Buttons are Edit and Help.

4. 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 entry for your server of the form Directory Server (machinename).

Server Console with expanded Server Group node showing Administration Server and Directory Server instance.

5. Double-click on the Directory Server node.

The Sun ONE Directory Server Console for your server instance appears.

From this console, you can perform administrative tasks.

Directory Server console for 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. 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. IS 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.

3. You see this error message in the console window trying to start Access Manager from the Start Menu:

C:\Sun\jstudio\IS6.1\bin>C:\Sun\jstudio\DirectoryServer5.2\slapd-localhost\start -slapd.bat

C:\Sun\jstudio\WebServer6.1\https-localhost.my.company.com\startsvr.bat

C:\Sun\jstudio\IS6.1\bin>net start slapd-localhost

The requested service has already been started.

More help is available by typing NET HELPMSG 2182

C:\Sun\jstudio\IS6.1\bin>

Reason: Directory Server is already started and can not be started again.

Solution: You can ignore this message. You should be able to access Access Manager as both Directory Server and Web Server are already running.

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:

A serious error has occurred in the Desktop. This may have been caused by a mis-configuration on the server.

Report this problem to you administrator.

Possible cause:

You do not have permission to access the dektop

Return to front page

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

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