Sun logo      Previous      Contents      Index      Next     

Sun Java Enterprise System 2003Q4 Installation Guide

Chapter 8
Postinstallation Configuration and Startup

This chapter provides instructions for configuring the component products that have been installed and verifying that they are operational.

This chapter has the following sections:

Overview of Postinstallation Configuration

When the Java Enterprise System installer finishes installation, several component products require that you perform some additional configuration tasks. The extent of the tasks depends on what configuration type you selected (custom or minimal), and whether or not your component products will be configured with the Sun Cluster software.

A number of component products come with configuration tools for completing a minimal installation. After running the configuration tools, you can make any additional changes by following the instructions in this guide and in the product documentation for each component product.

The following topics are addressed in this section:

Custom Configuration Mode

When you select the custom configuration mode, you are asked to specify configuration values for component products during installation. At the end of the installation process, a summary report containing the values that were set during installation is available. You can view this file from the directory where it is saved, /var/sadm/install/logs.

Note

All Java Enterprise System component products support custom configuration except the Calendar Server, Instant Messaging, Messaging Server, and Sun Cluster components. Configuration for these products can only be done after installation.

Minimal Configuration Mode

When you select the minimal configuration mode during installation, the Java Enterprise System installer places the component product package files in their respective directories. No parameter setting is done, and most component products are not operational because runtime services are not available.

You must do additional configuration for most of the component products before the Java Enterprise System environment is operational.

Note

If you performed a minimal configuration installation and selected Identity Server as a component, the installer required you to perform configuration for Identity Server and associated components during installation. In this case, many of the component products are also configured during installation (such as Application Server, Directory Server, Directory Proxy Server, Server Console and Administration Server, or Web Server).

Verification of Installation and Configuration

Even if you have already done much of the configuration, check the sections in this chapter to see whether any additional configuration is required for your component products. If no additional configuration is required, proceed to "Starting and Stopping Component Products" to verify that the component products are operational.

Sun Cluster Configuration Tasks

The following component products can be specified for use with the Sun Cluster software:

For a description of a Sun Cluster installation sequence, refer to "High Availability Using Sun Cluster Software".

The Java Enterprise System installer performs a simple pkgadd installation on Sun Cluster packages. You can use the pkginfo command to verify that the Sun Cluster packages have been installed. A list of the packages associated with the Sun Cluster component can be found in "Sun Cluster Software and Agents".

During installation, the Java Enterprise System installer installs the Sun Cluster packages and sets up the /usr/cluster/bin directory. No configuration is done. After package installation, you must establish the cluster, but before establishing the cluster, the following component products must be configured:

    To Configure the Sun Cluster Software After Installation
  1. Establish the cluster by starting the Sun Cluster installation utility, /usr/cluster/bin/scinstall. Do this on each machine that you are installing as a cluster node.
  2. After the scinstall utility starts, complete the Sun Cluster configuration tasks. For information, refer to the Sun Cluster 3.1 Software Installation Guide (http://docs.sun.com/doc/816-3388).

    3. During this phase, the scinstall utility verifies the Sun Cluster packages. If packages are missing, an error message indicates that packages on the CD are not available. If this happens, you must verify that the correct Sun Cluster packages were installed by the Java Enterprise System installer.

    To Configure Data Services for the Component Products

After the cluster has been configured, you are ready to configure data services.

Note

You must establish the cluster and install both the Sun Cluster Core and Sun Cluster Agents software components before you can configure data services for the component products.

Instructions on configuring data services for component products is available at the following locations:

Until you have fully configured the data services and all the supporting layers (volume manager, cluster file system, resource group information), Sun Cluster installation for Java Enterprise System is not complete.

Configuring Component Products

This section contains the following procedures:

Administration Server Configuration

    To Configure Administration Server After a Custom Installation

Note

Before you can configure Administration Server, Directory Server must already be configured. Refer to "To Configure Directory Server After a Minimal Installation".

After a custom configuration installation, Administration Server is fully configured and ready to use, with one exception. If Administration Server will be used with the Sun Cluster software, refer to "Sun Cluster Configuration Tasks" for instructions on how to complete this configuration.

    To Configure Administration Server After a Minimal Installation

After a minimal configuration installation, the packages are installed and you are ready to perform the configuration tasks for the Sun ONE Administration Server component product.

Note

If Administration Server was installed with Identity Server, most of the configuration in Step 3 was completed during installation.

  1. Create an initial configuration for Administration Server by following the instructions in the “Configuring Administration Server” section of the “Installing Sun ONE Directory Server” chapter in the Sun ONE Directory Server 5.2 Installation and Tuning Guide, http://docs.sun.com/doc/816-6697-10.
  2. Perform the steps in the “Completing the Installation Process” section of the “Installing Sun ONE Directory Server” chapter in the Sun ONE Directory Server 5.2 Installation and Tuning Guide, http://docs.sun.com/doc/816-6697-10.
  3. Verify the common server settings as described in "Common Server Settings" and the Administration Server settings as described in the tables in "Administration Server Configuration".

    4. Update the settings as needed. Information on these setting can be found in the Sun ONE Server Console Server Management Guide, http://docs.sun.com/doc/816-6704-10.

  4. If applicable, configure Administration Server for use with the Sun Cluster software. Refer to "Sun Cluster Configuration Tasks".
  5. To verify configuration, proceed to "Starting and Stopping Administration Server".

Application Server Configuration

    To Configure Application Server After a Custom Installation
  1. Add as_svr_base/bin to your PATH environment variable. To verify the setting, type the following:

    2. which asadmin

  2. Add as_svr_base/man to your MANPATH environment variable. To verify the setting, type the following:

    3. man asadmin

    The asadmin man page should be displayed.

  3. Create an initial domain for Application Server using the following asadmin command:

    4. asadmin create-domain --path domain_path --sysuser sys_user --passwordfile file_name --adminport port_number --adminuser admin_user --adminpassword password domain_name asadmin

    For example:

    asadmin create-domain --adminport 4848 --adminuser MyAdmin --adminpassword MyPassword MyDomain

    For additional information on administering Application Server, refer to the Sun ONE Application Server Administrator’s Guide, http://docs.sun.com/doc/817-1953-10.

  4. If you are configuring Application Server with Identity Server and Portal Server, you must reconfigure Application Server so that it can use the configuration information specified during the installation process.

    5. To reconfigure Application Server, run the following command:

    asadmin -reconfig instance-name

    For example:

    asadmin -reconfig server1

  5. If Application Server will be used with the Sun Cluster software, refer to "Sun Cluster Configuration Tasks" for instructions on how to complete this configuration.
  6. To verify configuration, proceed to "Starting and Stopping Application Server".
    To Configure Application Server After a Minimal Installation

After a minimal configuration installation, the Application Server packages are installed and you are ready to begin configuration.

  1. Add as_svr_base/bin to your PATH environment variable. To verify, type the following:

    2. which asadmin

  2. Add as_svr_base/man to your MANPATH environment variable. To verify this is working, type the following:

    3. man asadmin

    The asadmin man page should be displayed.

  3. Create an initial domain for Application Server using the following asadmin command:

    4. asadmin create-domain --path domain_path --sysuser sys_user --passwordfile file_name --adminport port_number --adminuser admin_user --adminpassword password domain_name asadmin

    For example:

    asadmin create-domain --adminport 4848 --adminuser MyAdmin --adminpassword MyPassword MyDomain

    For additional information on administering the Application Server, refer to the Sun ONE Application Server Administrator’s Guide, http://docs.sun.com/doc/817-1953-10.

  4. If applicable, configure Application Server for use with the Sun Cluster software. Refer to "Sun Cluster Configuration Tasks".
  5. To verify configuration, proceed to "Starting and Stopping Application Server".

Calendar Server Configuration

    To Configure Calendar Server After Installation

The Calendar Server component product cannot be configured by the Java Enterprise System installer.

  1. If this step was not done during Messaging Server configuration, configure Sun ONE Directory Server 5.x on Directory Server for Calendar Server by running the Directory Server Setup script, /opt/SUNWics5/cal/sbin/comm_dssetup.pl.

    2. Note

    Before you run the User Management Utility in Step 3, Identity Server must be installed and configured.

    1. Verify that Directory Server is running. Refer to "To Start Directory Server" if needed.
    2. Prepare Directory Server by running this command:

      3. server-root/cal/sbin/comm_dssetup.pl

    3. Select the Schema 2 schema type when running the script.

      4. Note

      Run the comm_dssetup.pl script once if Messaging Server, Calendar Server, and the User Management Utility are connected to the same directory server.

      If each product is using a different LDAP directory server, run the script on each LDAP directory.

  2. Verify that the second column in the /etc/hosts file contains the fully-qualified domain name (FQDN) rather than a simple host name. For example:

    3. 192.18.99.999   mycomputer.company.com   loghost

  3. Perform this step only if your installation includes Identity Server 6.1 and LDAP Schema 2 and if this step was not done during Messaging Server configuration: Configure for Calendar Server provisioning by running the User Management Utility, /opt/SUNWcomm/sbin/config-iscli.

    4. Instructions for running the utility are contained in the Sun ONE Messaging and Collaboration User Management Utility Installation and Reference Guide, http://docs.sun.com/doc/817-4216-10.

  4. Configure Calendar Server by running the Calendar Server configuration program, /opt/SUNWics5/cal/sbin/csconfigurator.sh.

    5. For information on configuring Calendar Server, refer to the Sun ONE Calendar Server Installation Guide for Solaris Operating Systems, http://docs.sun.com/doc/816-6707-10.

  5. If applicable, configure Calendar Server for use with the Sun Cluster software. Refer to "Sun Cluster Configuration Tasks" for information on completing this configuration.
  6. To verify configuration, proceed to "Starting and Stopping Calendar Server".

Directory Server Configuration

    To Configure Directory Server After a Custom Installation
  1. Run the idsktune command to obtain a list of recommendations for using Directory Server.
  2. If applicable, configure Directory Server for use with the Sun Cluster software. Refer to "Sun Cluster Configuration Tasks".
  3. To verify configuration, proceed to "Starting and Stopping Directory Server" and "Starting and Stopping Administration Server".
    To Configure Directory Server After a Minimal Installation

After a minimal configuration installation, you are ready to perform the configuration tasks for the Sun ONE Directory Server component product.

Note

If Directory Server was installed with Identity Server, most of the configuration in Step 3 was completed during installation.

  1. Create an initial configuration for Directory Server by performing the instructions in the “Configuring Directory Server” section of the “Installing Sun ONE Directory Server” chapter in the Sun ONE Directory Server 5.2 Installation and Tuning Guide, http://docs.sun.com/doc/816-6697-10.
  2. Perform the steps in the “Completing the Installation Process” section of the “Installing Sun ONE Directory Server” chapter in the Sun ONE Directory Server 5.2 Installation and Tuning Guide, http://docs.sun.com/doc/816-6697-10.
  3. Verify the common server settings as described in "Common Server Settings" and the Directory Server settings as described in the tables in "Directory Server Configuration".

    4. Update the settings as needed.

  4. Run the idsktune command to obtain a list of recommendations for using Directory Server.
  5. If applicable, configure Directory Server for use with the Sun Cluster software. Refer to "Sun Cluster Configuration Tasks".
  6. To verify configuration, proceed to "Starting and Stopping Directory Server" and "Starting and Stopping Administration Server".

Directory Proxy Server Configuration

    To Configure Directory Proxy Server After Installation

After a minimal configuration installation, you are ready to perform the following configuration tasks for the Sun ONE Directory Proxy Server component product.

Note

If Directory Proxy Server was installed along with Identity Server in the same session of installation, most of the configuration in Step 2 was completed during installation.

  1. Create an initial configuration for Directory Proxy Server by performing the instructions in the “Configuring the Directory Proxy Server Instance” section of the “Installation” chapter of the Sun ONE Directory Proxy Server Installation Guide, http://docs.sun.com/doc/816-6390-10.
  2. Verify the common server settings as described in "Common Server Settings" and the Directory Proxy Server settings as described in the tables in "Directory Proxy Server Configuration".
  3. To verify configuration, proceed to "Starting and Stopping Directory Proxy Server".

Identity Server Configuration

    To Configure Identity Server After Installation

Identity Server requires that you perform full configuration during installation rather than after installation. Installation-time configuration is required for both the Custom Configuration option and the Minimal Configuration option. In addition, component products that are automatically associated with Identity Server require configuration during installation.

Note

Component products that are automatically associated with Identity Server include Application Server, Directory Server, Directory Proxy Server, Server Console and Administration Server, and Web Server.

Although you can start Identity Server and log into its console immediately after running the Java Enterprise System installer, you cannot perform basic user management operations until you complete some final configuration steps. These steps differ depending on whether or not Identity Server is using a Directory Server instance that is already provisioned with user data.

The next sections explain what to do in the following cases:

When Directory Server Is Provisioned With User Data

When Directory Server is already provisioned with user data, refer to “Configuring a Provisioned Directory Server” in the Sun ONE Identity Server Migration Guide, http://docs.sun.com/doc/816-6771-10, for a description of the final configuration steps.

To verify configuration, proceed to "Starting and Stopping Identity Server".

When Directory Server Is Not Yet Provisioned With User Data

When Directory Server is not yet provisioned with user data, perform the steps in the following two procedures:

    To Enable the Referential Integrity Plug-in

When the referential integrity plug-in is enabled, it performs integrity updates on specified attributes immediately after a delete or rename operation. This ensures that relationships between related entries are maintained throughout the database.

  1. In Directory Server Console, click Configuration.
  2. In the navigation tree, double-click Plug-ins to expand the list of Plug-ins.
  3. In the Plug-ins list, click Referential integrity postoperation.
  4. In the properties area, check the Enable plug-in box.
  5. Click Save.
  6. Restart Directory Server to enable the plug-in.
    To Add Identity Server Indexes

Database indexes enhance the search performance in Directory Server.

  1. In Directory Server Console, click Configuration.
  2. Add the nsroledn index.
    1. In the navigation tree, double-click the Data icon, then click the root suffix that contains the directory entries you want to use in Identity Server.
    2. Click the Indexes tab.
    3. Under Additional Indexes, for the nsroledn attribute, check the following checkboxes: Equality, Presence, and Substring.
    4. Click Save.
    5. In the Indexes window, after the index is successfully created, click Close.
  3. Add the memberof index.
    1. In the Indexes tab, click Add attribute...
    2. In the Select Attributes window, select the attribute memberof, then click OK.
    3. In the Indexes tab, for the memberof attribute, check the following checkboxes: Equality and Presence.
    4. Click Save.
    5. In the Indexes window, after the index is successfully created, click Close.
  4. Add the iplanet-am-static-group index.
    1. In the Indexes tab, click Add attribute...
    2. In the Select Attributes window, select the attribute iplanet-am-static-group, and then click OK.
    3. In the Indexes tab, for the iplanet-am-static-group attribute, check the following checkbox: Equality.
    4. Click Save.
    5. In the Indexes window, after the index is successfully created, click Close.
  5. Add the iplanet-am-modifiable-by index.
    1. In the Indexes tab, click Add attribute...
    2. In the Select Attributes window, select the attribute iplanet-am-modifiable-by, and then click OK.
    3. In the Indexes tab, for the iplanet-am-modifiable-by attribute, check the following checkbox: Equality.
    4. Click Save.
    5. In the Indexes window, after the index is successfully created, click Close.
  6. Add the iplanet-am-user-federation-info-key index.
    1. In the Indexes tab, click Add attribute...
    2. In the Select Attributes window, select the attribute iplanet-am-user-federation-info-key, then click OK.
    3. In the Indexes tab, for the iplanet-am-user-federation-info-key attribute, check the following checkbox: Equality.
    4. Click Save.
    5. In the Indexes window, after the index is successfully created, click Close.
  7. Restart Directory Server.
  8. To verify configuration, proceed to "Starting and Stopping Identity Server".

Instant Messaging Configuration

    To Configure Instant Messaging After Installation

The Instant Messaging component product cannot be configured by the Java Enterprise System installer.

Instructions for using the Instant Messaging configurator, /opt/SUNWiim/configure, are contained in the “Configuring Sun ONE Instant Messenger” chapter in the Sun ONE Instant Messaging Installation Guide, http://docs.sun.com/doc/816-6676-10.

To verify configuration, proceed to "Starting and Stopping Instant Messaging".

    To Configure Message Queue After Installation

The Message Queue component product requires no additional configuration unless it is being configured for use with the Sun Cluster software. In this case, refer to "Sun Cluster Configuration Tasks".

Additional configuration for Message Queue is discussed in the Sun ONE Message Queue Administrator’s Guide, http://docs.sun.com/doc/817-0354-10. For example, you may want to change the default administration password.

To verify configuration, proceed to "Starting and Stopping Instant Messaging".

Messaging Server Configuration

    To Configure Messaging Server After Installation

The Messaging Server component product cannot be configured by the Java Enterprise System installer.

  1. If this step was not done during Calendar Server configuration, configure Sun ONE Directory Server 5.x for Messaging Server on Directory Server by running the Directory Server Setup script, /opt/SUNWmsgsr/lib/comm_dssetup.pl.
    1. Verify that Directory Server is running. Refer to "To Start Directory Server" for instructions.
    2. Prepare the Directory Server by running server-root/cal/sbin/comm_dssetup.pl.
    3. Select Schema 2 schema type when running the script.

      4. Note

      Run the comm_dssetup.pl script once if Messaging Server, Calendar Server, and the User Management Utility are connected to the same directory server.

      If each product is using a different LDAP directory server, run the script on each LDAP directory.

  2. Verify that the second column in the /etc/hosts file contains the fully-qualified domain name (FQDN) rather than a simple host name. For example:

    3. 192.18.99.1   mycomputer.company.com   loghost

  3. Perform this step only if your installation includes Identity Server 6.1 and LDAP Schema 2 and if this step was not done during Calendar Server configuration: Configure for Messaging Server provisioning by running the User Management Utility, /opt/SUNWcomm/sbin/config-iscli. Instructions are contained in the Sun ONE Messaging and Collaboration User Management Utility Installation and Reference Guide, http://docs.sun.com/doc/817-4216-10.
  4. Configure Messaging Server by running the Messaging Server configuration program, /msg_svr_base/sbin/configure.

    5. For information on configuring Messaging Server, refer to the Sun ONE Messaging Server Installation Guide for Solaris Operating Systems, http://docs.sun.com/doc/816-6735-10

  5. If applicable, configure for use with the Sun Cluster software. Refer to "Sun Cluster Configuration Tasks".
  6. To verify configuration, proceed to "Starting and Stopping Messaging Server".

Portal Server Configuration

    To Configure Portal Server After a Custom Installation

If you are using Web Server or the Application Server as the web container for Portal Server, you must apply changes to the instance. Use the instructions in the “Post Installation Tasks” section in Chapter 2 of the Sun ONE Portal Server 6.2 Installation Guide, http://docs.sun.com/doc/816-6754-10.

To verify configuration, proceed to "Starting and Stopping Portal Server".

    To Configure Portal Server After a Minimal Installation

The Sun ONE Portal Server component product provides a common configurator that can be used to configure all Portal Server subcomponents, including the Portal Server Secure Remote Access component.

  1. Create a runtime configuration for Portal Server by running the Port Server configurator, portal-server-install-dir/lib/configurator.

    2. Instructions for running the configurator as well as descriptions of the settings used by the configurator are contained in the “Installing Sun ONE Portal Server” chapter of the Sun ONE Portal Server 6.2 Installation Guide, http://docs.sun.com/doc/816-6754-10. You can also refer to the tables in "Portal Server Configuration".

  2. Apply changes to the Web Server or Application Server instance. Use the instructions in the “Post Installation Tasks” section in Chapter 2 of the Sun ONE Portal Server 6.2 Installation Guide, http://docs.sun.com/doc/816-6754-10.
  3. To verify configuration, proceed to "Starting and Stopping Portal Server" and "Starting and Stopping Portal, Server Secure Remote Access".

To verify configuration, proceed to "Starting and Stopping Portal Server" and "Starting and Stopping Portal, Server Secure Remote Access".

Web Server Configuration

    To Configure Web Server After a Custom Installation

After a custom configuration installation, Web Server is fully configured and ready to use, with one exception. If Web Server will be used with the Sun Cluster software, refer to "Sun Cluster Configuration Tasks" for instructions on how to complete this configuration.

To verify configuration, proceed to "Starting and Stopping Web Server".

    To Configure Web Server After a Minimal Installation

After a minimal configuration installation, you are ready to perform the configuration tasks for the Sun ONE Web Server component product.

Note

If Web Server was installed along with Identity Server in the same session of installation, most of the configuration in Step 2 was completed during installation.

  1. Configure Web Server by running the Web Server configuration program, ws_svr_base/setup/configure. The configuration program creates a runtime configuration, including an admin server and a default instance.
  2. Verify the common server settings as described in "Common Server Settings" and the Web Server settings as described in the tables in "Web Server Configuration".

    3. Update the settings as needed. Additional information on these settings can be found in the Sun ONE Web Server Installation and Migration Guide, http://docs.sun.com/doc/817-1830-10.

  3. If applicable, configure for use with the Sun Cluster software. Refer to "Sun Cluster Configuration Tasks".
  4. To verify configuration, proceed to "Starting and Stopping Web Server".

Starting and Stopping Component Products

Note

Default installation directories and port numbers for the component products are listed in "Installation Directories" and Appendix C, "Component Port Numbers". In many cases, the starting and stopping examples in the following sections are based on this default information, so if you do not remember what you specified for your component product, you can try the example.

Perform the procedures in this section to verify that component products are operational:

Suggested Startup Sequence

Note

To start and stop a component product server, you must log in as a user who has administrative rights to the system.

The general sequence for bringing up the entire Java Enterprise System component set is shown in the following table. The left column lists the order in which you should perform the startup, the middle column lists the task action and any comments on that action, and the right column lists the location of the instructions for performing the task.

Table 8-1  Startup Sequence Recommended for Java Enterprise System 

Order

Task

Location of Instructions

1

Start Directory Server.

"To Start Directory Server"

 

Start Administration Server.

"To Start Administration Server"

Start Server Console.

"To Start Server Console"

2

Start your web container. Starts Identity Server and Portal Server if they are installed.

 

Start Application Server (also starts Message Queue).

"To Start Application Server"

"To Verify Identity Server and Portal Server on Application Server"

"To Start Message Queue"

Start BEA Weblogic Server (only with Portal Server).

"To Verify Identity Server and Portal Server on BEA WebLogic"

Start IBM WebSphere Server (only with Portal Server).

"To Verify Identity Server and Portal Server on IBM WebSphere"

Start Web Server.

"To Start Web Server"

"To Verify Identity Server and Portal Server on Web Server"

3

Start Portal Server, Secure Remote Access.

"To Start Portal Server, Secure Remote Access"

4

Start Instant Messaging.

"To Start Instant Messaging"

5

Start Messaging Server.

"To Start Messaging Server"

6

Start Calendar Server.

"To Start Calendar Server"

To shut down the entire component set, it is typically appropriate to reverse the sequence.

Starting and Stopping Administration Server

To verify Administration Server, you start the Administration Server and the Console Server. Administration Server depends on Directory Server.

    To Start Administration Server
  1. Change to ds_svr_base. For example:

    2. cd /var/opt/mps/serverroot

  2. Start the Administration Server processes.

    3. ./start-admin

  3. Verify that Administration Server is running.

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

    root 2556 2554 0 13:19:07 ? 0:01 ns-httpd -d /var/opt/mps/serverroot/admin-serv/config

    root 2553 1 0 13:19:05 ? 0:00 ./uxwdog -e -d /var/opt/mps/serverroot/admin-serv/config

    root 2570 429 0 13:20:20 pts/1 0:00 grep admin-serv/config

    root 2554 2553 0 13:19:05 ? 0:01 ns-httpd -d /var/opt/mps/serverroot/admin-serv/config

    To Stop Administration Server
  1. Change to ds_svr_base For example:

    2. cd /var/opt/mps/serverroot

  2. Stop the Administration Server processes.

    3. ./stop-admin

  3. Verify that Application Server is no longer running.

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

    To Start Server Console
  1. If necessary, configure the $DISPLAY variable to display the Console Server on your machine.
  2. Verify that the Administration Server is running.

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

  3. Change to ds_svr_base. For example:

    4. cd /var/opt/mps/serverroot

  4. Start Server Console.

    5. ./startconsole

    To Stop Server Console
  1. To stop Server Console, exit the graphical interface.
  2. Verify that Console Server is no longer running.

    3. /usr/bin/ps -ef | grep console

Starting and Stopping Application Server

To verify Application Server, you need to start the Application Server instance, then invoke the graphical Administration interface and log in. Application Server depends on Message Queue.

    To Start Application Server
  1. Change to as_svr_base/bin/asadmin. For example:

    2. cd /opt/SUNWappserver7/bin

  2. Start the Application Server instances. For example:

    3. asadmin start-domain --domain domain1

    Note

    If you receive a message indicating failure to start, configuration changes might not be applied yet. In this case, run the asadmin -reconfig instance-name command. For example:

    asadmin -reconfig server1

  3. Verify that Application Server is running.

    4. /usr/bin/ps -ef | grep appservd

    root 4814 1 0 10:42:22 ? 0:00 ./appservd-wdog -r /SUNWappserver7 -d

    /var/opt/SUNWappserver7/domains/domain1/a root 4815 4814 0 10:42:22 ? 0:00 appservd -r /SUNWappserver7 -d

    /var/opt/SUNWappserver7/domains/domain1/admin-se root 4816 4815 0 10:42:23 ? 1:37 appservd -r /SUNWappserver7 -d

    /var/opt/SUNWappserver7/domains/domain1/admin-se root 4819 4816 0 10:42:25 ? 0:00

    /SUNWappserver7/lib/Cgistub -f /tmp/admin-server-4f378e6f/.cgistub_4816 root 4820 4819 0 10:42:25 ? 0:00

    /SUNWappserver7/lib/Cgistub -f /tmp/admin-server-4f378e6f/.cgistub_4816 root 4821 4819 0 10:42:25 ? 0:00

    /SUNWappserver7/lib/Cgistub -f /tmp/admin-server-4f378e6f/.cgistub_4816 root 4828 1 0 10:43:09 ? 0:00 ./appservd-wdog -r /SUNWappserver7 -d

    /var/opt/SUNWappserver7/domains/domain1/s root 4829 4828 0 10:43:09 ? 0:00 appservd -r /SUNWappserver7 -d

    /var/opt/SUNWappserver7/domains/domain1/server1/ root 4830 4829 0 10:43:09 ? 0:17 appservd -r /SUNWappserver7 -d

    /var/opt/SUNWappserver7/domains/domain1/server1/

    To Access the Application Server Graphical Interface

In your browser, use the http://hostname.domain:adminport format to access the Application Server Administration interface. For example:

http://mycomputer.example.com:4848

Your login to Application Server confirms successful installation.

    To Stop Application Server
  1. Change to as_svr_base/bin. For example:

    2. cd /opt/SUNWappserver7/bin

  2. Stop the Application Server instances.

    3. asadmin stop-domain --domain domain1

  3. Verify that Application Server is no longer running.

    4. /usr/bin/ps -ef | grep appservd

Starting and Stopping Calendar Server

Calendar Server depends on Directory Server.

    To Start Calendar Server
  1. Change to cal_svr_base/SUNWics5/cal/sbin. For example:

    2. cd /opt/SUNWics5/cal/sbin

  2. Start Calendar Server.

    3. ./start-cal

  3. The following processes should appear in the process list.

    4. enpd

    csnotifyd

    csadmind

    cshttpd

    To Access the Calendar Server Graphical Interface

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 following format to access Calendar Server:

http://hostname.domain[:port]

For example:

http://mycomputer.example.com

If this is an initial login, Calendar Server creates a default calendar for you. Your login to Calendar Server confirms successful installation.

    To Stop Calendar Server
  1. Change to cal_svr_base/SUNWics5/cal/sbin. For example:

    2. cd /opt/SUNWics5/cal/sbin

  2. Stop Calendar Server.

    3. ./stop-cal

Starting and Stopping Directory Server

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

    To Start Directory Server
  1. Change to ds_svr_base/slapd-instance-name (instance-name is usually machine name). For example:

    2. cd /var/opt/mps/serverroot/slapd-host1

  2. Start Directory Server.

    3. ./start-slapd

  3. Verify that Directory Server is running.

    4. /usr/bin/ps -ef | grep slapd

    root 1297 1 0 Jul 01 ? 2:27 ./ns-slapd -D /var/opt/mps/serverroot/slapd-host1 -i /var/opt/mps/serverroot/slapd-host1

    To Stop Directory Server
  1. Change to ds_svr_base/slapd-instance-name. For example:

    2. cd /var/opt/mps/serverroot/slapd-host1

  2. Stop Directory Server.

    3. ./stop-slapd

  3. Verify that Directory Server is no longer running.

    4. /usr/bin/ps -ef | grep slapd

Starting and Stopping Directory Proxy Server

Log in as root if the server runs on ports less than 1024; otherwise, log in either as root or with the server's user account. (By default, if Directory Proxy Server is run by root, it changes its user ID to nobody.)

    To Start Directory Proxy Server
  1. Change to dps_svr_base/dps-hostID. For example:

    2. cd /dps-host1

  2. Start the Directory Proxy Server process.

    3. ./start-dps

  3. Verify that Directory Proxy Server is running.

    4. /usr/bin/ps -ef | grep dps

    root 13769 1 0 Oct 24 ? 29:40 ./ldapfwd -t

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

    To Stop Directory Proxy Server
  1. Change to dps_svr_base/dps-hostID. For example:

    2. cd /dps-host1

  2. Stop the Directory Proxy Server processes.

    3. ./stop-dps

  3. Verify that Directory Proxy Server is no longer running.

    4. # ps -ef | grep SUNWdps

Starting and Stopping Identity Server

To verify Identity Server, you access your specific deployment configurations of Identity Server on the possible web containers:

Identity Server depends on Directory Server and a web container.

This section contains the following procedures:

    To Start Identity Server
  1. Change to the is_svr_base/SUNWam/bin directory. For example:

    2. cd /opt/SUNWam/bin

  2. Start the Identity Server processes.

    3. ./amserver start

    Note

    If Identity Server is hosted on Application Server, start the Application Server instance separately.

  3. Verify that Identity Server processes are running.

    4. /usr/bin/ps -ef | grep SUNWam

    root[sh]@icebox25# ps -ef | grep SUNWam

    root 13893 1 0 Oct 24 ? 0:00 /opt/SUNWam/share/bin/amsecuridd -c 58943

    root 13894 1 0 Oct 24 ? 0:00 /opt/SUNWam/share/bin/amunixd -c 58946

    To Verify Identity Server and Portal Server on Application Server
  1. Use the following URL to access the default page:

    2. http://appserver-host:port/amconsole

    The Identity Server login page appears.

  2. Log in.

    3. Your login to Identity Server confirms successful deployment of Identity Server on Application Server.

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

    4. http://server:port/portal

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

    To Verify Identity Server and Portal Server on Web Server
  1. Use the following URL to access the default page:

    2. http://webserver-host:port/amconsole

    The Identity Server login page appears.

  2. Log in.

    3. Your login to Identity Server confirms successful deployment of Identity Server on Web Server.

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

    4. http://server:port/portal

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

    To Verify Identity Server and Portal Server on BEA WebLogic
  1. Use the following URL to access the default page:

    2. http://beaweblogic-host:port/amconsole

    The Identity Server login page appears.

  2. Log in.

    3. Your login to Identity Server confirms successful deployment of Identity Server on BEA WebLogic.

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

    4. http://server:port/portal

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

    To Verify Identity Server and Portal Server on IBM WebSphere
  1. Use the following URL to access the default page:

    2. http://ibmwebsphere-host:port/amconsole

    The Identity Server login page appears.

  2. Log in.

    3. Your login to Identity Server confirms successful deployment of Identity Server on IBM WebSphere.

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

    4. http://ibmwebsphere-host:port/amconsole

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

    To Stop Identity Server
  1. Change to is_svr_base/bin. For example:

    2. cd /etc/init.d

  2. Stop the Identity Server processes.

    3. ./amserver stop

  3. Verify that Identity Server processes are no longer running.

    4. # ps -ef | grep SUNWam

Starting and Stopping Instant Messaging

Instant Messaging depends on Directory Server and the Identity Server SDK.

    To Start Instant Messaging
  1. Determine whether you selected automatic startup on reboot.
    • If no, go to Step 2.
    • If yes, proceed.
    • Change to /etc/init.d.
    • Start the Instant Messaging process:

      • ./sunwiim start

  2. For nonautomatic startup on reboot:
    1. Change to ims_svr_base/sbin. For example:

      2. cd /opt/SUNWiim/html/sbin

    2. Start Instant Messaging.

      3. ./imadmin start

  3. The following processes should appear in the process list.

    4. /../lib/multiplexor -c ./../config/iim.conf

    ...

    /usr/j2se/bin/java -server -Xmx256m -cp ./../classes/imserv.jar:./../classes/im

    To Stop Instant Messaging
  1. Change to ims_svr_base/sbin. For example:

    2. cd /opt/SUNWiim/sbin

  2. Stop Instant Messaging.

    3. ./imadmin stop

  3. The processes above should not appear in the process list.

Starting Message Queue

    To Start Message Queue
  1. Change to the mq_svr_base/bin directory. For example:

    2. cd /usr/bin

  2. Start the Message Queue broker.

    3. ./imqbrokerd

  3. Verify that the Message Queue processes are running.

    4. /usr/bin/ps -ef | grep imqbrokerd

    root 4833 4830 0 10:43:13 ? 0:00 /bin/sh /usr/bin/imqbrokerd -javahome /usr/j2se -name domain1_server1 -port 328

Starting and Stopping Messaging Server

Messaging Server depends on Directory Server.

    To Start Messaging Server
  1. Disable the Sendmail program.

    2. /etc/init.d/sendmail stop

  2. Move the Sendmail startup script, /etc/rc2.d/S88sendmail, to an archive directory.
  3. Change to ms_svr_base/sbin. For example:

    4. cd /opt/SUNWmsgsr/sbin

  4. Start the Messaging Server processes.

    5. ./start-msg

  5. Verify that the Messaging Server processes are running:

    6. /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

    To Stop Messaging Server
  1. Change to ms_svr_base/sbin. For example:

    2. cd /opt/SUNWmsgsr/sbin

  2. Stop the Messaging Server processes.

    3. ./stop-msg

  3. Verify that the Messaging Server processes are no longer running.

    4. /usr/bin/ps -ef | grep SUNWmsgsr

Starting and Stopping Portal Server

The Portal Server startup 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, Identity Server, and a web container.

To verify Portal Server, go to the following sections:

Starting and Stopping Portal, Server Secure Remote Access

    To Start Portal Server, Secure Remote Access
  1. Change to /etc/init.d.
  2. Start the Portal Server gateway.

    3. ./gateway start

  3. Verify that the Portal Server, Secure Remote Access processes are running:

    4. /usr/bin/ps -ef | grep entsys

    /usr/jdk/entsys-j2se/bin/java -ms64m -mx128m -classpath

    /opt/SUNWam/lib:/opt

    To Stop Portal Server, Secure Remote Access
  1. Change to /etc/init.d.
  2. Stop the Portal Server gateway.

    3. ./gateway stop

  3. Verify that the Portal Server Secure Remote Access processes are no longer running.

    4. /usr/bin/ps -ef | grep <tbd>

Starting and Stopping Web Server

Web Server has no dependencies.

    To Start Web Server
  1. Change to ws_svr_base/https-instance-name. For example:

    2. cd /opt/SUNWwbsvr/https-admserv

  2. Start the Web Server admin process.

    3. ./start

  3. Change to ws_svr_base/https-hostname.domain. For example:

    4. cd /opt/SUNWwbsvr/https-host1.example.com

  4. Start the Web Server instance.

    5. ./start

  5. Verify that Web Server processes are running.

    6. /usr/bin/ps -ef | grep SUNWwbsvr

    root 334 1 0 Jul 01 ? 0:00 ./webservd-wdog -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-admserv/config -n http

    root 352 1 0 Jul 01 ? 0:00 ./webservd-wdog -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-host1.example.com

    root 335 334 0 Jul 01 ? 0:01 webservd -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-admserv/config -n https-admserv

    root 336 335 0 Jul 01 ? 0:14 webservd -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-admserv/config -n https-admserv

    root 689 352 0 Jul 01 ? 0:00 webservd -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-host1.example.com/config

    root 690 689 0 Jul 01 ? 64:34 webservd -r /opt/SUNWwbsvr -d /opt/SUNWwbsvr/https-host1.example.com/config

    To Access the Web Server Graphical Interface
  1. In your browser, use the http://hostname.domain:port format to access the Web Server Administration interface. For example:

    2. http://host1.example.com:80

  2. Use the http://hostname.domain:adminport format to access the administration server. For example:

    3. http://host1.example.com:8888

Your login to Web Server confirms successful installation.

    To Stop Web Server
  1. Change to ws_svr_base/https-instance-name. For example:

    2. cd /opt/SUNWwbsvr/https-admserv

  2. Stop the Web Server admin process.

    3. ./stop

  3. Change to ws_svr_base/https-hostname.domain. For example:

    4. cd /opt/SUNWwbsvr/https-host1.example.com

  4. Stop the Web Server instance.

    5. ./stop

  5. Verify that Web Server is no longer running.

    6. # ps -ef | grep SUNWwbsvr

Next Steps

If you have completed this chapter, you have completed configuration of your component products and verified that they are functional. The Java Enterprise System installation is now complete.

You can now proceed to any of the following:

Entry points for the component product documentation can be found in Table 2 in the Java Enterprise System Roadmap (http://docs.sun.com/doc/817-4715).



Previous      Contents      Index      Next     

Copyright 2003 Sun Microsystems, Inc. All rights reserved.