test

Sun Java Enterprise System 5 Installation Guide for Microsoft Windows

Chapter 6 Verifying Installed Java ES Components

This chapter provides instructions for starting and stopping Sun Java Enterprise System (Java ES) components that have been installed and configured. You can use the procedures in this section to verify that the components are operational.

Before using the procedures in this chapter, you should have completed all the postinstallation configuration tasks specified in Chapter 5, Completing Postinstallation Configuration.

Note –

If you used the Configure automatically during installation option, see the summary.txt file in the installation root location for information regarding each component.

This chapter includes the following sections:

Startup Sequence for Java ES

The startup sequence for Java ES 5 depends on the web container. If Web Server is the web container then the startup sequence is:

  1. Common Agent Container

  2. Directory Server

  3. Web Server

    If Application Server is the web container then the startup sequence is:

  1. Common Agent Container

  2. Directory Server

  3. HADB

  4. Message Queue

  5. Application Server

Portal Server and Access Manager run inside the web container, you access them only when you start the web container.

Starting and Stopping Access Manager

Access Manager depends on Directory Server and a web container to function as expected. Access Manager can be deployed into the following web containers:

By default, the web containers are not running after installation. You need to start the web container. For more information on starting and stopping the Web Server and Application Server, see Starting and Stopping Web Server and Starting and Stopping Application Server respectively. Directory Server must also be running for Access Manager to function. For more information about starting theDirectory Server, see Starting and Stopping Directory Server.

Access Manager does not include any start or stop entries in the Services page.

Starting and Stopping Application Server

Application Server depends on Message Queue to function. If you have selected the start servers option in the Finish page of Java ES installer, the Application Server is started automatically after installation.

You can also start and stop the Application Server by accessing the .bat file in the bin folder of the Application Server installation directory.

ProcedureTo Start an Application Server Domain

  1. Change to the ApplicationServer-base\bin directory.

  2. Start the Application Server Domain.

    asadmin.bat start-domain --user admin-user-ID --passwordfile passwordFileName domain-name

    For example, type the following command to start domain1 with admin-user-ID admin and passwordFileName passfile:

    asadmin.bat start-domain --user admin --passwordfile passfile domain1

ProcedureTo Stop an Application Server Domain

  1. Change to the ApplicationServer-base\bin directory.

  2. Stop the Application Server Domain:

    asadmin.bat stop-domain domainName

ProcedureTo Start an Application Server Agent

  1. Change to the ApplicationServer-base\bin directory.

  2. Start the Application Server Agent:

    asadmin.bat start-node-agent --port admin-Port --user admin-user-ID --password admin-password node-agent--name

ProcedureTo Stop an Application Server Agent

  1. Change to the ApplicationServer-base\bin directory.

  2. Start the Application Server Agent:

    asadmin.bat stop-node-agent node-agent-name

Starting and Stopping Directory Server

By default, the Directory Serveris started when you complete your installation.

You can also start and stop the Directory Server by accessing the dsadm.exe file in the bin folder of the Directory Server installation directory.

ProcedureTo Start the Directory Server

  1. Change to the DirectoryServer-base\ds6\bin directory.

    cd DirectoryServer-base\ds6\bin

  2. Start the Directory Server instance.

    dsadm.exe start instance-path

    For example, type the following command to start the Directory Server instance.

    dsadm.exe start C:\Program Files\Sun\JavaES5\DSEE\var\DSInstance

ProcedureTo Stop the Directory Server

  1. Change to the DirectoryServer-base\ds6\bin directory.

    cd DirectoryServer-base\ds6\bin

  2. Stop the Directory Server instance.

    dsadm.exe stop instance-path

Starting and Stopping Directory Proxy Server

By default, the Directory Proxy Server is started when you complete your installation.

You can also start and stop the Directory Proxy Server by accessing the dsadm.exe file in the Directory Proxy Server folder of the Directory Proxy Server installation directory.

ProcedureTo Start the Directory Proxy Server

  1. Change to the DirectoryServer-base\dps6\bin directory.

    cd DirectoryServer-base\dps6\bin

  2. Start the Directory Proxy Server instance.

    dpadm.exe start instance-path

    For example, type the following command to start the Directory Proxy Server instance.

    dpadm.exe start C:\Program Files\Sun\JavaES5\DSEE\var\DPSInstance

ProcedureTo Stop the Directory Proxy Server

  1. Change to the DirectoryServer-base\dps6\bin directory.

    cd DirectoryServer-base\dps6\bin

  2. Stop the Directory Proxy Server instance.

    dpadm.exe stop instance-path

Starting and Stopping the HADB Management Agent

the HADB management agent is registered as Windows Server. The HABD service starts automatically as the start type

After a successful Java ES installation, the HADBMgmtAgent service is registered as Windows services. This services starts automatically because the start up type for HADB is set as Automatic. Follow the next procedure to stop the HADB management agent.

ProcedureTo Stop HADB From Services

  1. Choose Start > Settings > Control Panel.

  2. Select Administrative Tools.

  3. Select Services.

  4. Select the HADBMgmtAgent service you want to stop from the Services list.

    You can use one of the following methods to stop the service:

    • Click mouse button 2 and select Stop.

    • Click the Stop service icon.

    • Select Stop from the Action Menu.

Starting and Stopping Message Queue

Message Queue has no dependencies. By default, the Java ES installer installs Message Queue for automatic startup on Windows. At times, you might want to start or stop the Message Queue service on Windows.

ProcedureTo Start the Message Queue From the Windows Start Menu

  1. Choose Start > Programs > Sun Java Enterprise System 5 > Message Queue 3.7 UR1> Message Broker.

ProcedureTo Start the Message Queue Using Windows Services

  1. Choose Start > Settings > Control Panel.

  2. Select Administrative Tools.

  3. Select Services.

  4. Select Message Queue Broker from the Services list.

    You can use one of the following methods to start the service:

    • Click mouse button 2 and select Start.

    • Click the Start Service icon.

    • Select Start from the Action Menu.

ProcedureTo Stop the Message Queue Using Windows Services

  1. Choose Start > Settings > Control Panel.

  2. Select Administrative Tools.

  3. Select Services.

  4. Select Message Queue Broker from the Services list.

    You can use one of the following methods to stop the service:

    • Click mouse button 2 and select Stop.

    • Click the Stop Service icon.

    • Select Stop from the Action Menu.

Starting and Stopping Monitoring Console

Monitoring Console cannot be run from the same host where any of the Java ES components are installed. For information about how to use Monitoring Console, see the Starting the Monitoring Console in Sun Java Enterprise System 5 Monitoring Guide.

Starting the Web Container to Access the Portal Server Desktop

The Portal Server startup and shutdown mechanisms are part of the startup and shutdown mechanisms for the web container on which the Sun Java Systems web container runs. Portal Server also depends on Directory Server, Access Manager, and the Access Manager SDK. The following sections describe how to start your Sun web container, Access Manager, and Portal Server after installation and configuration:

Portal Server administration is managed by using the Access Manager Administration Console. See Starting and Stopping Access Manager for information about how to open the Access Manager Administration Console.

ProcedureTo Access the Portal Server Desktop From a Sun Web Container

The web protocol for Portal Server can be either HTTP or HTTPS. By default, the host is hostname.domain.

  1. In a browser window, use the following URL format to display the sample Desktop.

    The default Portal Access URL and default deployment URI are /portal.

    http://hostname.domain:port/portal

    When you enter the URL, the welcome page is displayed, including a short description of Portal Server and links to sample portals that you selected for installation. Click one of the links to access the anonymous portal desktop for the sample portal. If the sample desktop displays without any exception, your Portal Server installation was successful.

  2. Type the following in the browser URL field:

    http://hostname.domain:port/psconsole

  3. Verify that the gateway is running on the specified port.

    netstat -a

    The default port is 443.

    • If the gateway is not running, start the gateway.

      C:\Sun\JavaES5\portal\bin\gateway.bat

  4. View the log files to verify that no problems have been logged.

  5. Run Portal Server in secure mode by typing the following in the browser URL field:

    https://gateway-hostname:port

    If you have chosen the default port (443) during installation, you do not need to specify the port number.

Starting and Stopping Portal Server

The Portal Serverstartup and shutdown mechanisms are part of the startup and shutdown mechanisms for the web container, either Web Server or an application server. Portal Server depends on Directory Server, Access Manager or Access Manager SDK, and a web container.

ProcedureTo Start the Portal Server

  1. Start the Directory Server instance.

    JavaES5-Install-Dir\DSEE\ds6\bin\dsadm.exe start DSInstancePath

  2. Start the Cacao Server instance.

    JavaES5-Install-Dir\share\cacao_2\bin\cacaoadm.bat start

    Wait for some time to ensure that the Cacao Server is started.

  3. (Optional) Verify the Cacao Server status.

    JavaES5-Install-Dir\share\cacao_2\bin\cacaoadm.bat status

    Cacao Server status is displayed in the following format:


    default instance is DISABLED at system startup.
Current retries count : 0/4
Processes:
3780
Uptime: 0 day(s), 0:8

  4. Start the Derby Server instance.

    JavaES5-Install-Dir\share\ant\bin\ant.bat -buildfile PortalServer-base\lib\derby.xml -propertyfile PortalServer-base\config\PSConfig.properties start-instance

    Note –

    If the Derby Server is not started then the Wiki and community samples will fail.

  5. Start the web container, which can be Web Server or Application Server.

    Note –

    If both Access Manager and Portal Server are deployed on the same web container, starting web container brings up both Access Manager and Portal Server by default.

    1. To Start the Application Server, type:

      JavaES5-Install-Dir\appserver\bin\asadmin.bat start-domain --user adminUserName --password adminPassword deployedDomain

Starting and Stopping the Service Registry

Service Registry installation creates an Application Server domain in ServiceRegistry-basedata\domains\registry directory.

The Application Server administrative console for this domain has port number 6489. Service Registry is automatically deployed as a web application in the registry domain at port 6480.

ProcedureTo Start Service Registry

  1. Change to the ServiceRegistry-base directory.

  2. Start Service Registry.

    JavaES-install-dir\share\ant\bin\ant.bat -f build-install.xml appserver.domain.start

Next Steps

A message is displayed telling you that the server is starting. When the startup process has been completed, an additional message is displayed.

ProcedureTo Access the Service Registry Web Console

  1. To access theService Registry Web Console, use the following URL format in your browser: 

    https://hostname:port

  2. Specify your local host as hostname if you are running your browser on the same system where Service Registry is installed.

    Otherwise, instead of specifying your local host as hostname, use the name of the system that Service Registry is running on.

    The default port number assigned during installation is 6480. For example:

    https://mycomputer.example.com:6480
Next Steps

You should see the Web Console welcome page. The default login name is admin. The password is set during installation.

Expand the Applications node, then the Web Applications node. Service Registry is deployed as a web application named soar.

ProcedureTo Stop Service Registry

  1. Change to the ServiceRegistry-base directory.

  2. Stop Service Registry.

    JavaES-install-dir\share\ant\bin\ant.bat -f build-install.xml appserver.domain.stop

ProcedureTo Restart Service Registry

  1. Change to the ServiceRegistry-base\install directory.

  2. Restart Service Registry.

    JavaES-install-dir\share\ant\bin\ant.bat build-install.xml appserver.domain.bounce

Starting and Stopping Web Proxy Server

ProcedureTo Start the Proxy Administration Server Service From the Command Prompt

  1. Change to the WebProxyServer-base\admin-service-id\ directory.

  2. Type startsvr.bat.

    The default admin-service ID is proxy-admserv.

ProcedureTo Stop the Proxy Admin Server Service From the Command Prompt

  1. Change to the WebProxyServer-base\admin-service-id\ directory.

  2. Type stopsvr.bat.

    The default admin-service ID is proxy-admserv.

ProcedureTo Start the Proxy Server Service From the Command Prompt

  1. Change to the WebProxyServer-base\proxy-service-id\ directory.

  2. Type startsvr.bat.

    The default proxy-service ID is proxy-server1.

ProcedureTo Stop the Proxy Server Service From the Command Prompt

  1. Change to the WebProxyServer-base\proxy-service-id\ directory.

  2. Type stopsvr.bat.

    The default proxy-service ID is proxy-server1.

ProcedureTo Start the Socks Server Service From the Command Prompt

  1. Change to the JavaES-install-dir\proxy-service-id\ directory.

  2. Type startsockd.bat.

    The default proxy-service ID is proxy-server1.

ProcedureTo Stop the Socks Server Service From the Command Prompt

  1. Change to the JavaES-install-dir\proxy-service-id\ directory.

  2. Type stopsockd.bat.

    The default proxy-service ID is proxy-server1.

ProcedureTo Start the Proxy Admin Server Service From the Start Menu

  1. Choose Start>Programs>Sun Java Enterprise System 5>Web Proxy Server 4.0.4>Start Admin Server.

ProcedureTo Start Proxy Server Service From the Start Menu

  1. Choose Start>Programs> Sun Java Enterprise System 5>Web Proxy Server 4.0.4>Start Proxy Server.

ProcedureTo Stop Proxy Server Service From the Start Menu

  1. Choose Start> Programs >Sun Java Enterprise System 5 >Web Proxy Server 4.0.4>Stop Proxy Server.

Starting and Stopping Web Server

If you have selected the start servers option in the Finish page of Java ES installer, the Web Server is started automatically after installation.

ProcedureTo Start the Web Server From the Windows Start Menu Console

  1. Choose Start > Sun Java Enterprise System 5 > Web Server 7.0 > Start Web Server Administrator Server.

    The cmd screen is displayed.

ProcedureTo Stop the Web Server From the Windows Start Menu Console

  1. Choose Start > Sun Java Enterprise System 5 > Web Server 7.0 > Stop Web Server Administrator Server.

    The cmd screen is displayed.

ProcedureTo Start the Web Server Using Web Server Administration Server

  1. Choose Start > Sun Java Enterprise System 5 > Web Server 7.0 > Administration Console.

    The Web Server 7.0 Administration Server Login page appears.

  2. Type the User Name and Password, then click OK.

    The Web Server 7.0 Administration Server page appears.

  3. Select a Server from the drop down list, and click Manage.

    The Server Manager page appears.

  4. Click Server On.

    The Web Server is started and a confirmation dialog box appears.

ProcedureTo Stop the Web Server Using Web Server Administration Server

  1. Choose Start > Sun Java Enterprise System 5 > Web Server 7.0 > Administration Console.

    The Web Server 7.0 Administration Server Login page appears.

  2. Type the User Name and Password, then click OK.

    The Web Server 7.0 Administration Server page appears.

  3. Select a Server from the drop down list, and click Manage.

    The Server Manager page appears.

  4. Click Server Off.

    The Web Server stops and a confirmation dialog box appears.

ProcedureTo Start the Web Server Using Windows Services

  1. Choose Start > Settings > Control Panel.

  2. Select Administrative Tools.

  3. Select Services.

  4. Select Web Server 7.0 from Services list.

    You can use one of the following methods to start the service:

    • Click mouse button 2 and select Start.

    • Click the Start service icon.

    • Click Action Menu and click Start option

  5. Select Sun Java System Web Server 7.0 Administration Server and repeat step 4 to start the Web Server administration server.

ProcedureTo Start the Web Server Usingstartserv.bat

  1. Change to the WebServer-base\admin-server\bin directory.

  2. Run the startserv.bat command to start the Web Server processes.

ProcedureTo Start the Web Server Instance Using startserv.bat

  1. Change to the WebServer-base\https-[INSTANCE_NAME]\bin directory.

  2. Run the startserv.bat command to start the Web Server processes.

ProcedureTo Stop the Web Server Using Windows Services

  1. Choose Start > Settings > Control Panel.

  2. Select Administrative Tools.

  3. Select Services.

  4. Select Web Server 7.0 from Services list.

    You can use one of the following methods to stop the service:

    • Click mouse button 2 and select Stop.

    • Click the Stop service icon.

    • Select Stop from the Action Menu.

  5. Select Sun Java System Web Server 7.0 Administration Server and repeat step 4 to stop the Web Server administrator server.

ProcedureTo Stop the Web Server Using stopserv.bat

  1. Change to WebServer-base\https-admserv.

  2. Run the stopserv.bat command to stop the Web Server processes.

ProcedureTo Stop the Web Server Instance Using stopserv.bat

  1. Change to WebServer-base\https-[INSTANCE_NAME].

  2. Run the stopserv.bat command to stop the Web Server processes.

Next Steps

If you have completed this chapter, you have verified that the Java ES components that you installed and configured are functional. You can now begin administering the Java ES components. For further information, see the Java ES component documentation at http://docs.sun.com/app/docs/prod/entsys.5.