test

Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

Chapter 7 Verifying Installed Components

This chapter provides instructions for verifying that the Sun JavaTM Enterprise System (Java ES) components have been installed and configured successfully. The procedures here do not address more complex interactions among components that might occur after configuring such functionality as single sign-on.

This chapter includes the following sections:

The default installation locations of Java ES components are different on the Solaris OS and the Linux operating system. Due to this difference, the procedures in this chapter use placeholders to represent these locations. For example, AccessManager-base represents the base installation directory for Access Manager.

Tip –

In most cases, the examples in this chapter are based on default information. If you do not remember the installation or configuration values specified for your component, try the example.

Verifying After Installation

This section provides instructions for verifying that installation of the Java ES component packages was successful. If you performed a Configure Now installation, some of the components are configured and ready to run. However, the purpose of the guidelines in this section is simply to verify that the packages are installed correctly, with no partial packages or missing components.

A good way to verify that packages were installed successfully is to examine the product registry. After installation, the Java ES installer updated the product registry to contain the components that were installed. During uninstallation, this same file is read by the Java ES uninstaller to determine which components are present and can be uninstalled.

Looking at the installation logs is also helpful, as is checking a few of the components to see if the correct version is contained in the appropriate directory.

Finally, you can try to start components that were part of a Configure Now installation, such as Web Server or Directory Server.

Use some or all of the following steps to verify installation.

ProcedureTo Verify That Installation Succeeded

Steps

  1. Verify that no partial packages were installed. On Solaris OS:


    pkginfo -p

  2. Verify that the correct version of a component is present.

    To see the correct versions for this release, refer to Appendix A, Java ES Components for This Release. For example, the J2SE version for Solaris should be 1.5.0_03. 


    cd /usr/jdk
ls -l

  3. Verify that the installed components are reflected in the product registry.

    1. On Solaris, use the prodreg tool to view installed packages:


      prodreg &

    2. Expand the Java Enterprise System Node to view the packages installed by the Java ES installer.

    3. You can also use the following command to view the productregistry file directly.


      view /var/sadm/install/productregistry

      To exit, press the Esc key, then :q.

  4. Review the configuration data you provided during installation by opening the summary log:


    cd /var/sadm/install/logs
view Java_Enterprise_System_Summary_Report_install.*

  5. For a Configure Now installation, start Portal Server and its related services.

    1. Start Directory Server:


      /var/opt/mps/serverroot/slapd-hostname/start-slapd

    2. Start Web Server:


      /opt/SUNWwbsvr/https-hostname.domainname/start

      Starting Web Server automatically starts Portal Server and Access Manager.

    3. Access the Web Server URL:


      http://hostname

    4. Access the administration URL for Web Server:


      http://hostname:8888

  6. For a Configure Now installation, stop Portal Server and its related services.

    1. Stop the Web Server administration server:


      /opt/SUNWwbsvr/https-admserv/stop

    2. Stop Web Server:


      /opt/SUNWwbsvr/https-hostname.domainname/stop

    3. Stop Directory Server:


      /var/opt/mps/serverroot/slapd-hostname/stop-slapd

  7. For a Configure Now installation, start Portal Server and Access Manager services


    /var/opt/mps/serverroot/slapd-hostname/start-slapd
/opt/SUNWwbsvr/https-hostname/domainname/start

  8. For a Configure Now installation, access the Access Manager console

    For login, User ID is amadmin, password is password.


    http://hostname/amconsole

  9. For a Configure Now installation, access Portal Server:

    For login, User ID is amadmin, password is password.


    http://hostname/portal

  10. If errors occur, restart Web Server and repeat the steps.

Verifying After Post-Installation Configuration

This section provides guidelines for verifying that the Java ES components are working after you have finished post-installation configuration.

To start Java ES, you start the components one after another, in a specific sequence. You start with the basic services provided by Directory Server and your web container (Web Server or an application server). Java ES creates runnable instances of these services during installation. Because Portal Server and Access Manager run inside the web container, they start when you start the web container.

The general sequence for bringing up the entire Java ES component set is shown in the following table. The left column lists the order in which you should perform the startup, the middle column describes the task, and the right column lists the location of the instructions for performing the task.

Table 7–1 Preferred Startup Sequence for Java ES

Order 

Task 

Location of Instructions 

1 

Start your directory server. 

 

A. Start Directory Server. 

Starting and Stopping Directory Server

B. Start Administration Server. 

Starting and Stopping Administration Server and the Server Console

C. Start Server Console. 

Starting and Stopping Administration Server and the Server Console

2 

Start Directory Proxy Server. 

Starting and Stopping Directory Proxy Server

3 

Start your chosen web container. If installed, Access Manager and Portal Server are started. If installed and configured, Communications Express is also started. 

 

Start Application Server (also starts Message Queue). 

Starting and Stopping Application Server

Start Web Server. 

Starting and Stopping Web Server

Start IBM WebSphere Server. 

See the third-party documentation for the server. 

Start BEA WebLogic Server. 

See the third-party documentation for the server. 

4 

Start Access Manager 

Starting and Stopping Access Manager

5 

Start Portal Server Secure Remote Access. 

Starting and Stopping Portal Server Secure Remote Access

6 

Start Service Registry 

Starting and Stopping Service Registry

7 

Start Instant Messaging. 

Starting and Stopping Instant Messaging Server and Multiplexor

8 

Start Messaging Server. 

Starting and Stopping Messaging Server

9 

Start Calendar Server. 

Starting and Stopping Calendar Server

To shut down the entire Java ES component set, reverse the sequence.

Starting and Stopping Access Manager

To start and stop Access Manager, start and stop the web container in which it is running.

ProcedureTo Access the Access Manager Login Page

Accessing the login page depends on the type of installation you did for Access Manager:

Steps

  1. Use the following URL format to access the default page:


    http://web_container-host:port/amconsole

    The Access Manager login page appears.

  2. Log in.

    A successful login to Access Manager confirms successful deployment of the software. The default administrator account is amadmin.

Starting and Stopping Administration Server and the Server Console

Included here are instructions for starting and stopping Administration Server and the Server Console. For more information, see “Starting and Stopping Administration Server” in the Sun Java System Administration Server 5 2005Q1 Administration Guide. Administration Server depends on Directory Server.

ProcedureTo Start Administration Server

Steps

  1. Enter the following:

    On Solaris OS: /var/opt/mps/serverroot/start-admin On non-Solaris OS: Change to the server root directory and enter ./start-admin

  2. Verify that the Administration Server processes are running. For example, on Solaris OS:


    /usr/bin/ps -ef | grep admin-serv/config
    		 

    ./uxwdog -e -d /var/opt/mps/serverroot/admin-serv/config 
ns-httpd -d /var/opt/mps/serverroot/admin-serv/config ns-httpd -d 
/var/opt/mps/serverroot/admin-serv/config ns-httpd -d 
/var/opt/mps/serverroot/admin-serv/config ns-httpd -d 
/var/opt/mps/serverroot/admin-serv/config

ProcedureTo Start Server Console

Steps

  1. If necessary, configure the $DISPLAY variable to display the Server Console on your host.

  2. Verify that the Administration Server processes are running. For example, on Solaris OS:


    /usr/bin/ps -ef | grep admin-serv/config
    		 

    ./uxwdog -e -d /var/opt/mps/serverroot/admin-serv
/config ns-httpd -d /var/opt/mps/serverroot/admin-serv
/config ns-httpd -d /var/opt/mps/serverroot/admin-serv/config 
ns-httpd -d /var/opt/mps/serverroot/admin-serv/config 
ns-httpd -d /var/opt/mps/serverroot/admin-serv/config

  3. Enter the following:

    On Solaris OS: /usr/sbin/mpsadmserver startconsole

    On non-Solaris OS: Change to the server root directory and enter startconsole

  4. Verify that the Server Console process is running. For example, on Solaris OS:


    /usr/bin/ps -ef | grep console
    		 

    orion 4871 4812 0 17:46:03 pts/2 0:00 /bin/sh/usr/sbin/mpsconsole
orion 4990 4871 0 17:46:04 pts/2 0:00 /var/opt/mps/serverroot/startconsole
orion 4812 4418 0 17:46:02 pts/2 0:00 /bin/sh/usr/sbin/mpsadmserver startconsole

ProcedureTo Stop Server Console

Steps

  1. To stop Server Console, exit the graphical interface.

  2. Verify that Server Console is no longer running. For example:


    /usr/bin/ps -ef | grep console

ProcedureTo Stop Administration Server

Steps

  1. Enter the following:

    On Solaris OS: var/opt/mps/serverroot/stop-admin On non-Solaris OS: Change to the server root directory and enter ./stop-admin

  2. Verify that Administration Server is no longer running. For example:


    /usr/bin/ps -ef | grep admin-serv/config

Starting and Stopping Application Server

Application Server is configured as a domain. The installer creates the default administrative domain with the default port number 4849. The Admin Server instance name is “server.” To use Application Server, start the domain and access the graphical Admin console. More information can be found in the Chapter 2, Getting Started, in Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide.

Note –

Starting Application Server also starts Message Queue.

ProcedureTo Start the Application Server Domain

Steps

  1. On the command line, change to ApplicationServer-base/bin and enter:


    % asadmin start-domain --user admin-id --passwordfile \
path_to_admin-password_file domainname

    Enter the values that you provided during installation. A message is displayed telling you that the server is starting:


    Starting Domain domain1, please wait. Log redirected to install_dir...

    When the startup process has completed, an additional message is displayed:


    Domain domain1 started

  2. Verify that the Application Server processes are running. For example, on Solaris OS:


    /usr/bin/ps -ef | grep appserv
    		 

    /opt/SUNWappserver/appserver/lib/appservDAS domain1

ProcedureTo Access the Admin Console

Step

    To access the Admin Console, use the following URL format in your browser: https://localhost:port

    If the browser is running on the host on which the Application Server was installed, specify localhost for the host name. Replace localhost with the name of the system that the Application Server software is running on if the browser is on another system. Replace the port variable with the Admin port number assigned during installation. The default port number assigned during installation is 4849. For example:


    https://mycomputer.example.com:4849

    You should see the Admin Console Login screen.

    Note –

    More information on installing the Application Server, the Domain Administration Server, and its various port numbers and concepts can be found in the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Installation Guide.

ProcedureTo Stop Application Server

Steps

  1. On the command line, change to ApplicationServer-base/bin.

  2. Enter the following command to stop the Application Server instances.


    ./asadmin stop-domain --domain domain1

  3. Verify that Application Server is no longer running. For example:


    /usr/bin/ps -ef | grep appservd

Starting and Stopping Calendar Server

Calendar Server depends on Directory Server.

ProcedureTo Start Calendar Server

Steps

  1. Change to the sbin directory.

    On Solaris OS: /opt/SUNWics5/cal/sbinOn Linux: /opt/sun/calendar/cal/sbin

  2. Enter the following command to start Calendar Server.


    ./start-cal

  3. Verify that the Calendar Server processes are running. For example, on Solaris OS:


    /usr/bin/ps -ef | grep cal
    		 

    /opt/SUNWics5/cal/lib/cshttpd -d 3
/opt/SUNWics5/cal/lib/enpd -p 57997 -c config/ics.conf
/opt/SUNWics5/cal/lib/csadmind
/opt/SUNWics5/cal/lib/csnotifyd

ProcedureTo Access the Calendar Server Graphical Interface

Step

    If you are already provisioned in the LDAP directory that Calendar Server points to, you can log into Calendar Server. In your browser, use the http:// hostname.domainname [:port] format to access Calendar Server. For example:

    http://mycomputer.example.com:89

    At initial login, Calendar Server creates a default calendar for you. Your login to Calendar Server confirms successful installation.

ProcedureTo Stop Calendar Server

Steps

  1. Change to the sbin directory.

    On Solaris OS: /opt/SUNWics5/cal/sbinOn Linux: /opt/sun/calendar/cal/sbin

  2. Enter the following command to stop Calendar Server.


    ./stop-cal

  3. Verify that Calendar Server is no longer running. For example:


    /usr/bin/ps -ef | grep cal

Starting and Stopping Communications Express

Communications Express is a web-based communications client that comprises an address book, a mail client and a calendar. It is accessed by typing the following URL into the address field of a web browser:

http://webcontainer-host:
webcontainer-port/URI path

where

Starting and Stopping Directory Proxy Server

For all UNIX-type systems, log in as root if the server runs on ports less than 1024. On ports greater than 1024, log in either as root or using the administrator account for the server. Directory Proxy Server depends on Administration Server.

ProcedureTo Start Directory Proxy Server

Steps

  1. Change to DirectoryProxyServer-base/dps-instancename where instancename is usually the host name. For example, the default is:


    cd /var/opt/mps/serverroot/dps-host1

  2. Enter the following command to start the Directory Proxy Server process.


    ./start-dps

  3. Verify that the Directory Proxy Server process is running. For example, on Solaris OS:


    /usr/bin/ps -ef | grep dps
    		 

    ./ldapfwd -t /var/opt/mps/serverroot/dps-or03/etc/tailor.txt

ProcedureTo Stop Directory Proxy Server

Steps

  1. Change to DirectoryProxyServer-base /dps-instancename where instancename is usually the host name. For example, the default is:


    cd /var/opt/mps/serverroot/dps-host1

  2. Enter the following command to stop the Directory Proxy Server process.


    ./stop-dps

  3. Verify that Directory Proxy Server is no longer running. For example:


    /usr/bin/ps -ef | grep dps

Starting and Stopping Directory Server

If Directory Server is part of a cluster, ensure that you are working on the active node for the logical host. Directory Server has no dependencies.

ProcedureTo Start Directory Server

Steps

  1. Start Directory Server using one of the following commands:

    • If Directory Server 5.2 is the default version:

      On Solaris OS: /usr/sbin/directoryserver startOn Linux: /opt/sun/sbin/directoryserver start

    • If Directory Server 5.2 is not the default version:

      On Solaris OS: /usr/sbin/directoryserver -useversion 5.2 start On Linux: /opt/sun/sbin/directoryserver -useversion 5.2 start

  2. Verify that the Directory Server process is running. For example, on Solaris OS:


    /usr/bin/ps -ef | grep slapd
    		 

    ./ns-slapd -D /var/opt/mps/serverroot/slapd-host1 -i /var/opt/mps/ \
serverroot/slapd-host1

ProcedureTo Stop Directory Server

Steps

  1. Stop Directory Server using one of the following commands:

    • If Directory Server 5.2 is the default version:

      On Solaris OS: /usr/sbin/directoryserver stopOn Linux: /opt/sun/sbin/directoryserver stop

    • If Directory Server 5.2 is not the default version:

      On Solaris OS: /usr/sbin/directoryserver -useversion 5.2 stopOn Linux: /opt/sun/sbin/directoryserver -useversion 5.2 stop

  2. Verify that Directory Server is no longer running. For example:


    /usr/bin/ps -ef | grep slapd

Starting and Stopping Instant Messaging Server and Multiplexor

Starting the Instant Messaging server enables Sun Java System Instant Messenger clients to connect to it. Stopping the Instant Messaging server closes all connections and disconnects all clients. The configuration of a given instance specifies whether only the multiplexor, only the server or both these components are enabled. Instant Messaging depends on Directory Server and Web Server.

Note –

For information on starting the Instant Messaging client (and the server on the Windows operating system), refer to theSun Java System Instant Messaging 7 2005Q1 Administration Guide.

ProcedureTo Start Instant Messaging Server and Multiplexor

Steps

  1. Change to the InstantMessaging-base/sbin/ directory. For example:

    On Solaris OS: cd /opt/SUNWiim/sbin On Linux: cd /opt/sun/im/sbin

  2. Enter the following command to start the Instant Messaging Server and Multiplexor process:


    ./imadmin start

  3. Verify that the Instant Messaging processes are running:


    ./imadmin status
    		 

    Server           [UP}
Multiplexor      [UP]
Agent:calendar   [DOWN]
Watchdog         [UP]

ProcedureTo Stop Instant Messaging

Steps

  1. Change to the InstantMessaging-base/sbin/ directory. For example:

    On Solaris OS: cd /opt/SUNWiim/sbin On Linux: cd /opt/sun/im/sbin

  2. Enter the following command to stop the Instant Messaging Server and Multiplexor process:


    ./imadmin stop

  3. Verify that the Instant Messaging processes are not running:


    ./imadmin check

Starting Message Queue

The heart of the Message Queue service is the Message Server. The Message Server performs message routing and delivery services using one or more brokers. The imqbrokerd command starts a broker.

ProcedureTo Start Message Queue Message Server Broker

Steps

  1. Change to the MessageQueue-base/bin directory.

  2. Enter the following command to start the Message Queue Message Server broker:


    ./imqbrokerd

  3. Verify that the broker process is running. For example:

    On Solaris OS: /usr/bin/ps -ef | grep imqbrokerd 


    /bin/sh /usr/bin/imqbrokerd

    On Linux: /bin/ps -ef | grep imqbrokerd 


    /bin/sh ./imqbrokerd

Starting and Stopping Messaging Server

The Messaging Server start-msg utility starts all of the messaging server processes, or optionally, one specified service. The services started can be controlled by enabling or disabling the configuration parameters. Messaging Server depends on Directory Server and Administration Server.

ProcedureTo Start Messaging Server

Steps

  1. Change to the MessagingServer-base/sbin directory.

  2. Enter the following command to start the Messaging Server:


    ./start-msg

  3. Verify that the Messaging Server processes are running.

    Notice that the list of processes varies according to the Messaging Server features you have configured to use.


    /usr/bin/ps -ef | grep SUNWmsgsr
    		 

    /opt/SUNWmsgsr/lib/enpd
/opt/SUNWmsgsr/lib/stored -d
/opt/SUNWmsgsr/lib/popd -d 5
/opt/SUNWmsgsr/lib/imapd -d 5 -D 6
/opt/SUNWmsgsr/lib/mshttpd -d 5 -D 6
/opt/SUNWmsgsr/lib/dispatcher
/opt/SUNWmsgsr/lib/job_controller
/opt/SUNWmsgsr/lib/tcp_lmtp_server
/opt/SUNWmsgsr/lib/tcp_smtp_server
/opt/SUNWmsgsr/lib/tcp_smtp_server
/opt/SUNWmsgsr/lib/imsched
/opt/SUNWmsgsr/lib/watcher

ProcedureTo Stop Messaging Server

Steps

  1. Change to the MessagingServer-base/sbin directory.

  2. Enter the following command to stop the Messaging Server:


    ./stop-msg

  3. Verify that the Messaging Server processes are not running. For example.


    /usr/bin/ps -ef | grep SUNWmsgsr

    Some Messaging Server processes might take several minutes to stop because they wait for their current transactions to complete.

ProcedureTo Access Messenger Express

Messenger Express is a web-based electronic mail program that enables end users to access their mailboxes using a browser.

Steps

  1. If you are already provisioned in the LDAP directory to which Messaging Server points, you can log in using your browser. Use the http:// hostname.domainname[: port] format to access Messenger Express. For example:

    http://mycomputer.example.com:80

  2. If the LDAP directory is not yet provisioned, you can login as admin, specifying the password you entered during configuration.

Starting the Web Container to Access Portal Server Desktop

The Portal Server startup and shutdown mechanisms are part of the startup and shutdown mechanisms for the web container on which it runs (Sun Java Systems or third-party). It also depends on Directory Server, Access Manager and the Access Manager SDK. See the following sections to start your Sun web container, Access Manager, and Portal Server after installation and configuration:

Portal Server administration is managed using the Access Manager Administration Console. See Starting and Stopping Access Manager to open the Access Manager Administration Console.

The following procedures pertain to accessing the end-user Portal Server Desktop.

ProcedureTo Access the Portal Server Desktop from a Sun Web Container

Steps

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

    http://servername:port/portal

    Display of the sample Desktop confirms successful deployment of Portal Server.

  2. For a mobile device, use the following URL:

    http://servername:port/portal/dt

ProcedureTo Access the Portal Server Desktop from BEA WebLogic

Step

    In a new browser, use the following URL to display the sample Desktop:

    http://beaweblogic-host: port/portal

    Display of the sample Desktop confirms successful deployment of Portal Server on BEA WebLogic.

ProcedureTo Access the Portal Server Desktop from IBM WebSphere

Step

    In a new browser, use the following URL to display the sample Desktop:

    http://ibmwebsphere-hostname: port/portal

    Display of the sample Desktop confirms successful deployment of Portal Server on IBM WebSphere.

Starting and Stopping Portal Server Secure Remote Access

The Secure Remote Access components of Portal Server offers browser-based secure remote access to portal content and services from any remote device with a Java technology-enabled browser. The Gateway component presents the content securely from internal web servers and application servers through a single interface to a remote user. Portal Server Secure Remote Access depends on Portal Server and Access Manager or the Access Manager SDK.

ProcedureTo Start Portal Server Secure Remote Access Gateway

Steps

  1. After installing the Gateway component and creating the required profile, run the following command to start the Gateway:


    /gateway-install-root/SUNWps/bin/gateway -n default start

    default is the default gateway profile created during installation. You can create your own profiles later, and restart the Gateway with the new profile.

  2. Run the following command to check if the Gateway is running on the specified port:


    netstat -a | grep port-number

    The default Gateway port is 443.

ProcedureTo Stop Portal Server Secure Remote Access Gateway

Steps

  1. Use the following command to stop the Gateway:


    /gateway-install-root/SUNWps/bin/gateway stop

    This command stops all the Gateway instances that are running on that particular host.

  2. Run the following command to check that the Gateway processes are no longer running:


    /usr/bin/ps -ef | entsys

Starting and Stopping Service Registry

Service Registry installation creates an Application Server domain in the following location:

The administrative domain has port number 6489. Service Registry is automatically deployed as a web application in the registry domain.

ProcedureTo Start Service Registry

Steps

  1. Change to the Service Registry install directory.

    On Solaris OS: cd /opt/SUNWsoar/install

    On Linux: cd /opt/sun/SUNWsoar/install

  2. Run the following command:

    On Solaris OS:/usr/sfw/bin/ant -f ./build-install.xml appserver.domain.start

    On Linux: /opt/sun/bin/ant --noconfig -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 completed, an additional message is displayed.

ProcedureTo Access the Admin Console

Steps

  1. To access the Admin Console for the Service Registry domain, use the following URL format in your browser: 

    https://hostname:port

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

    Otherwise, instead of specifying your local host as hostname, use the name of the system that the Application Server software is running on.

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

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

You should see the Admin Console Login screen. The default login name and password are as follows: Login: admin Password: 12345678

ProcedureTo Stop Service Registry

Steps

  1. Change to the Service Registry install directory.

    On Solaris OS: cd /opt/SUNWsoar/install

    Linux: cd /opt/sun/SUNWsoar/install

  2. Run the following command:

    On Solaris OS: /usr/sfw/bin/ant -f ./build-install.xml appserver.domain.stop

    On Linux: /opt/sun/bin/ant --noconfig -f ./build-install.xml appserver.domain.stop

  3. If you want to stop the domain and then start it again immediately, use the Ant target appserver.domain.bounce.

Stopping and Rebooting Sun Cluster Software

Although Sun Cluster software is not started and stopped like other components, the software can be stopped by rebooting into noncluster mode. For instructions, refer to the Sun Cluster System Administration Guide for Solaris OS.

Starting and Stopping Web Server

When you install Web Server, two server instances are installed by default: an Administration Server instance and a Web Server instance. Web Server has no dependencies.

ProcedureTo Start Web Server Administration Server and Instance

Steps

  1. On the command line, change to WebServer-base/https-admserv.

  2. Enter the following command to start the Web Server administration process.


    ./start

  3. Change to WebServer-base/https- hostname.domainname.

  4. Enter the following command to start the Web Server instance.


    ./start

    You should receive the following message: startup: Server started successfully.

  5. Verify that the Web Server processes are running. For example, on Solaris OS:


    /usr/bin/ps -ef | grep SUNWwbsvr
    		 

    ./webservd-wdog -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-admserv/config -n http
./webservd-wdog -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-host1.example.com
webservd -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-admserv/config -n https-admserv
webservd -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-admserv/config -n https-admserv
webservd -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-host1.example.com/config
webservd -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-host1.example.com/config

  6. Access the Administration Server graphical interface.

    In the browser, enter the http://hostname .domainname:adminport format. For example:

    http://host1.example.com:8888

    Your login confirms successful installation.

ProcedureTo Stop Web Server Administration Server and Instance

Steps

  1. On the command line, change to WebServer-base/https-admserv.

  2. Enter the following command to stop the Web Server administration process.


    ./stop

  3. Change to WebServer-base/https- hostname.domainname.

  4. Enter the following command to stop the Web Server instance.


    ./stop

  5. Verify that the Web Server processes are no longer running. For example:


    ps -ef | grep SUNWwbsvr

Starting and Stopping Web Proxy Server

Instructions for starting and stopping Web Proxy Server are contained in this section.

ProcedureTo Start Web Proxy Server Admin Server and Instance

When you install Web ServerAdministration Server instance and a Web Proxy Server instance.

Steps

  1. On the command line, start the Admin Server by changing to WebProxyServer-base/proxy-admserv:

    • Solaris OS: /opt/SUNWproxy/proxy-admin start

    • Linux: /opt/sun/webproxyserver/proxy-admin start

  2. On the command line, start the Web Proxy Server instance by changing to the WebProsyServer-base/proxy-hostname.domainname :

    • Solaris OS: /opt/SUNWproxy/proxy-server1 start

    • Linux: /opt/sun/webproxyserver/proxy-server1 start

ProcedureTo Access the Administration Server Graphical Interface

Step

    Use the http://hostname.domainname:adminport format to access the Administration Server graphical interface. For example:

    http://host1/example.com:8888

    Your login confirms successful installation.

ProcedureTo Stop Web Proxy Server

Steps

  1. On the command line, stop the Admin Server by changing to WebProxyServer-base/proxy-admserv:

    • Solaris OS: /opt/SUNWproxy/proxy-admin stop

    • Linux: /opt/sun/webproxyserver/proxy-admin stop

  2. On the command line, stop the Web Proxy Server instance by changing to the WebProxyServer-base/proxy-hostname.domain :

    • Solaris OS: /opt/SUNWproxy/proxy-server1 stop

    • Linux: /opt/sun/webproxyserver/proxy-server1 stop

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 components. The following documentation can help you get started: