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.
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:
The startup sequence for Java ES 5 depends on the web container. If Web Server is the web container then the startup sequence is:
Common Agent Container
Directory Server
Web Server
If Application Server is the web container then the startup sequence is:
Common Agent Container
Directory Server
HADB
Message Queue
Application Server
Portal Server and Access Manager run inside the web container, you access them only when you start the web container.
Access Manager depends on Directory Server and a web container to function as expected. Access Manager can be deployed into the following web containers:
Web Server
Application Server
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.
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.
Change to the ApplicationServer-base\bin directory.
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
Change to the ApplicationServer-base\bin directory.
Stop the Application Server Domain:
asadmin.bat stop-domain domainName
Change to the ApplicationServer-base\bin directory.
Start the Application Server Agent:
asadmin.bat start-node-agent --port admin-Port --user admin-user-ID --password admin-password node-agent--name
Change to the ApplicationServer-base\bin directory.
Start the Application Server Agent:
asadmin.bat stop-node-agent node-agent-name
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.
Change to the DirectoryServer-base\ds6\bin directory.
cd DirectoryServer-base\ds6\bin
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
Change to the DirectoryServer-base\ds6\bin directory.
cd DirectoryServer-base\ds6\bin
Stop the Directory Server instance.
dsadm.exe stop instance-path
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.
Change to the DirectoryServer-base\dps6\bin directory.
cd DirectoryServer-base\dps6\bin
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
Change to the DirectoryServer-base\dps6\bin directory.
cd DirectoryServer-base\dps6\bin
Stop the Directory Proxy Server instance.
dpadm.exe stop instance-path
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.
Choose Start > Settings > Control Panel.
Select Administrative Tools.
Select Services.
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.
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.
Choose Start > Settings > Control Panel.
Select Administrative Tools.
Select Services.
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.
Choose Start > Settings > Control Panel.
Select Administrative Tools.
Select Services.
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.
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.
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.
The web protocol for Portal Server can be either HTTP or HTTPS. By default, the host is hostname.domain.
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.
Type the following in the browser URL field:
http://hostname.domain:port/psconsole
Verify that the gateway is running on the specified port.
netstat -a
The default port is 443.
View the log files to verify that no problems have been logged.
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.
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.
Start the Directory Server instance.
JavaES5-Install-Dir\DSEE\ds6\bin\dsadm.exe start DSInstancePath
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.
(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 |
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
If the Derby Server is not started then the Wiki and community samples will fail.
Start the web container, which can be Web Server or Application Server.
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.
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.
Change to the ServiceRegistry-base directory.
Start Service Registry.
JavaES-install-dir\share\ant\bin\ant.bat -f build-install.xml appserver.domain.start
A message is displayed telling you that the server is starting. When the startup process has been completed, an additional message is displayed.
To access theService Registry Web Console, use the following URL format in your browser:
https://hostname:port
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
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.
Change to the ServiceRegistry-base directory.
Stop Service Registry.
JavaES-install-dir\share\ant\bin\ant.bat -f build-install.xml appserver.domain.stop
Change to the ServiceRegistry-base\install directory.
Restart Service Registry.
JavaES-install-dir\share\ant\bin\ant.bat build-install.xml appserver.domain.bounce
Change to the WebProxyServer-base\admin-service-id\ directory.
Type startsvr.bat.
The default admin-service ID is proxy-admserv.
Change to the WebProxyServer-base\admin-service-id\ directory.
Type stopsvr.bat.
The default admin-service ID is proxy-admserv.
Change to the WebProxyServer-base\proxy-service-id\ directory.
Type startsvr.bat.
The default proxy-service ID is proxy-server1.
Change to the WebProxyServer-base\proxy-service-id\ directory.
Type stopsvr.bat.
The default proxy-service ID is proxy-server1.
Change to the JavaES-install-dir\proxy-service-id\ directory.
Type startsockd.bat.
The default proxy-service ID is proxy-server1.
Change to the JavaES-install-dir\proxy-service-id\ directory.
Type stopsockd.bat.
The default proxy-service ID is proxy-server1.
If you have selected the start servers option in the Finish page of Java ES installer, the Web Server is started automatically after installation.
Choose Start > Sun Java Enterprise System 5 > Web Server 7.0 > Start Web Server Administrator Server.
The cmd screen is displayed.
Choose Start > Sun Java Enterprise System 5 > Web Server 7.0 > Stop Web Server Administrator Server.
The cmd screen is displayed.
Choose Start > Sun Java Enterprise System 5 > Web Server 7.0 > Administration Console.
The Web Server 7.0 Administration Server Login page appears.
Type the User Name and Password, then click OK.
The Web Server 7.0 Administration Server page appears.
Select a Server from the drop down list, and click Manage.
The Server Manager page appears.
Click Server On.
The Web Server is started and a confirmation dialog box appears.
Choose Start > Sun Java Enterprise System 5 > Web Server 7.0 > Administration Console.
The Web Server 7.0 Administration Server Login page appears.
Type the User Name and Password, then click OK.
The Web Server 7.0 Administration Server page appears.
Select a Server from the drop down list, and click Manage.
The Server Manager page appears.
Click Server Off.
The Web Server stops and a confirmation dialog box appears.
Choose Start > Settings > Control Panel.
Select Administrative Tools.
Select Services.
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
Select Sun Java System Web Server 7.0 Administration Server and repeat step 4 to start the Web Server administration server.
Change to the WebServer-base\admin-server\bin directory.
Run the startserv.bat command to start the Web Server processes.
Change to the WebServer-base\https-[INSTANCE_NAME]\bin directory.
Run the startserv.bat command to start the Web Server processes.
Choose Start > Settings > Control Panel.
Select Administrative Tools.
Select Services.
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.
Select Sun Java System Web Server 7.0 Administration Server and repeat step 4 to stop the Web Server administrator server.
Change to WebServer-base\https-admserv.
Run the stopserv.bat command to stop the Web Server processes.
Change to WebServer-base\https-[INSTANCE_NAME].
Run the stopserv.bat command to stop the Web Server processes.
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.