test

Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX

Chapter 6 Completing Postinstallation Configuration

This chapter contains instructions for completing initial configuration of the Sun JavaTM Enterprise System (Java ES) product components after installation. If a product component is not listed in this chapter, there is no postinstallation configuration required for that component. However, that component might still require postinstallation tasks relating to monitoring or Sun Cluster data service if you are installing these product components.

This chapter contains the following sections:

How to Use This Chapter

When the Java ES installer finishes installation, most product components require additional configuration before the Java ES environment is operational. The extent of this work depends on the configuration type you selected (Configure Now or Configure Later), and whether or not your product components will be configured for monitoring or high availability with Sun Cluster software.

If you selected the Configure Later type during installation, the installer placed the product component package files in their respective directories. No parameter setting was done, and most product components are not operational because runtime services are not available. A number of product components include configuration tools for completing a Configure Later installation. When running the configuration tools, you can make any additional changes by following the instructions located in this guide and the instructions in the product documentation for each product component.

Before acting on the information in this chapter, you should have installed the Java ES components. You can examine the product registry or use the Solaris OS pkginfo command, the Linux rpm command to verify that the component packages have been installed. A list of packages associated with the components is contained in Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Update 1 Installation Reference for UNIX.

A summary report containing the configuration values that were set during installation is available here:

Solaris OS: /var/sadm/install/logs

Linux: /var/opt/sun/install/logs

After completing installation, look through the procedures in this chapter for the product components you installed. If you determine that no additional configuration is required for your product components, you can start your product components by following the instructions in Chapter 7, Verifying Installed Product Components.

Note –

The default installation locations of Java ES product components might be different on the various platforms. Due to this, the procedures in this chapter often use variables to represent these locations. For example, ApplicationServer-base represents the directory where Application Server is installed, regardless of platform.

Verifying Man Pages

If your components have man pages, you will need to verify that your MANPATH environmental variable is set correctly. After installation, the man pages for the Java ES components are located in default directories. In some cases, the correct location for the component man pages is already set in your MANPATH environment variable. If the location of your man pages is not present, add this location to your MANPATH environment variable.

The following table indicates the default locations for the man pages of the Java ES components. If a component is not listed, the component does not have man pages.

Table 6–1 Man Pages Default Locations

Component 

Location of Man Pages 

Application Server

Solaris OS: /opt/SUNWappserver/share/man

Linux: /opt/sun/appserver/share/man

Common agent container

Common Agent Container V1.1 

Solaris OS: /opt/SUNWcacao/man

Common Agent Container V2.x 

Solaris OS: /usr/share/man

Linux: /opt/sun/man

Note –

Common Agent Container V1.1 does not co-exist on same Linux platform with V2.0 or V2.1.

Directory Server (and Directory Proxy Server)

Solaris OS: /opt/SUNWdsee/dsee6/man

Linux: /opt/sun/dsee6/man

Monitoring

Solaris OS: /opt/SUNWmfwk/man

Linux: /opt/sun/man

Sun Cluster

Solaris OS: /usr/cluster/man/

ProcedureTo Update Your MANPATH Variable

The following example procedure shows how to ensure that the Application Server man pages are available using the C shell.

  1. Check your MANPATH environment variable to see if the correct path is already there.

    env | grep MANPATH

  2. If the correct path is not there, add the location of your Java ES component man pages to your MANPATH environment variable.

    • On Solaris OS, the following example command sets your MANPATH environment variable for the session:


      setenv MANPATH {$MANPATH}:/usr/dt/man:/usr/man:/opt/SUNWappserver/share/man

      To configure this environment variable to apply each time you log in, add the setenv command contents to your .login or .cshrc file.

    • On Linux, update the /etc/man.config file with the required MANPATH. For example, add this line to the /etc/man.config file:


      MANPATH /opt/sun/man

      The new man pages will be fully accessible, regardless of path.

      Note –

      For Linux, if users have MANPATH settings in their own shells, the procedure for Solaris OS should be used. This allows their personal settings to override the /etc/man.config file. You must also set the MANSECT variable.

  3. On Linux, you might need to set the MANSECT environment variable.

    Edit the MANSECT line in the /etc/man.config file. For example:


    # and the MANSECT environment variablle is not set.
MANSECT     1:8:2:3:4:5:6:7:9:tcl:n:l:p:o

    Change the second line to read this:


    MANSECT     1:8:2:3:4:5:6:7:9:tcl:n:l:p:o:5:dsconf:5dpconf:5dssd:5dsat:5dsoc

  4. Verify that the man pages are accessible.

    For example, the following command should display the asadmin man page for Application Server:


    man asadmin

Monitoring Console Postinstallation Configuration

If the product components you have installed will use Java ES monitoring, a number of the components require postinstallation configuration before they are enabled for the monitoring framework. For configuration instructions, refer to Chapter 3, Installing and Using Monitoring Console, in Sun Java Enterprise System 5 Update 1 Monitoring Guide.

Sun Cluster Postinstallation Configuration

On Solaris OS, theSun Cluster software provides a high availability platform for managing applications such as databases, application servers and web servers. Before you install or configure Sun Cluster software, ensure that the combination of hardware and software that you choose for your cluster is currently a supported Sun Cluster configuration.

Sun Cluster software can be used to manage the following Java ES product components:

If the Java ES product components you installed will be included in a Sun Cluster environment, you must first configure the Sun Cluster framework before configuring the product components. then configure the Java ES product components you have selected. To install components from the Communications suite, refer to the Sun Java Communications Suite 5 Installation Guide. Finally, depending on the product components installed, you might need to configure Sun Cluster data services.

Phase I. Sun Cluster Framework

The Java ES installer performs a simple pkgadd installation of the core Sun Cluster packages and sets up the /usr/cluster/bin directory. No configuration is done during installation, so your first postinstallation task is to configure the cluster framework as described in the Sun Cluster Software Installation Guide for Solaris OS.

During this phase, the scinstall utility verifies the Sun Cluster packages. If packages are missing, an error message is displayed. If this happens, you must verify that the correct Sun Cluster packages were installed. Refer to Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Update 1 Installation Reference for UNIX.

Phase II. Product Component Data Services

After you have installed and configured the Sun Cluster framework and the other Java ES and non-Java ES components, you are ready to configure the Sun Cluster data services using the Sun Cluster agents software.

Note –

To configure Sun Cluster data services, you must have chosen the associated Sun Cluster agents during installation. To see an example Sun Cluster installation sequence, refer to Sun Cluster Software Example.

For guidelines on configuring the Sun Cluster data services, refer to Sun Cluster Data Services Configuration.

Access Manager Postinstallation Configuration

For all Access Manager installations, the web container needs to be restarted. If a full installation is being performed on Web Server or Application Server, the installer will stop the web container instance so only the instance needed to be started. For instructions on restarting Access Manager, see Starting and Stopping Access Manager.

Configuring Access Manager After a Configure Now Installation

After a Configure Now installation, you can start Access Manager and log into the Access Manager console. However, you cannot perform basic user management operations until you complete some final configuration steps. These steps differ depending on whether or not Access Manager is using a Directory Server instance that is already provisioned with user data. There are additional configuration tasks that you might want to perform for your deployment.

For instructions on performing these tasks, refer to the Sun Java System Access Manager 7.1 Postinstallation Guide.

Configuring Access Manager After a Configure Later Installation

After a Configure Later installation, the packages are installed and you are ready to configure Access Manager using the Access Manager configuration script, AccessManager-base/bin/amconfig. Instructions for using this program are contained in the Sun Java System Access Manager 7.1 Postinstallation Guide.

For instructions on configuring Access Manager for a third-party web container on Solaris OS (BEA WebLogic or IBM WebSphere Application Server), refer to Sun Java System Access Manager 7.1 Postinstallation Guide.

Application Server Postinstallation Configuration

After a Configure Now installation, Application Server requires no postinstallation configuration.

To configure Application Server for load balancing, refer to the “Configuring Web Servers for HTTP Load Balancing” section in the Chapter 5, Configuring HTTP Load Balancing, in Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide.

If needed, configure Application Server for use with the Sun Cluster software. Refer to Sun Cluster Postinstallation Configuration.

ProcedureTo Configure Application Server After a Configure Later Installation

After a Configure Later installation, you will need to run a post installation script to set the Application Server environment. The scripts configure and create the AppplicationsServer8–base/bin/* shell scripts and a config/asenv file from templates that are installed during installation. (For a Configure Now installation, they are created during installation.)

  1. Navigate to the following directory of the Java ES 5U1 distribution. For example:

    cd /os_arch/Product/application_server/Tools

  2. Open the postInstall README file and follow instructions to do the following:

    1. Run the postInstall script:

      ./postInstall Application8Server-base  ApplicationServer8Config-base

    2. Create a new domain.

      When using the asadmin create-domain command to create a new domain, you specify values for two parameters: adminPort and instancePort. The adminPort value can be the same as that used by the server instance. However, the instancePort value should not be the same as that used by any of the server instances.

  3. If needed, modify the environment variables in the ApplicationServer-base/samples/common.properties file.

    If you do not know some paths, you can copy them from the ApplicationServer-base /config/asenv.conf file. For example:

    Solaris Properties 

    com.sun.aas.derbyRoot=/opt/SUNWjavadb

    com.sun.aas.webServicesLib=/opt/SUNWappserver/appserver/lib

    com.sun.aas.imqHome=/var/opt/SUNWappserver/domains/domain1/imq

    com.sun.aas.imqBinDir=/usr/bin

    com.sun.aas.imqUserMgr=/usr/bin/imqusermgr

    com.sun.aas.imqLib=/usr/share/lib

    com.sun.aas.installRoot=/opt/SUNWappserver/appserver

    com.sun.aas.javaRoot=/usr/jdk/entsys-j2se

    com.sun.aas.domains.dir=/var/opt/SUNWappserver/domains

    #admin.password= The admin password will not be saved as default. User can enter it and save it manually.

    admin.host=jws-v210-4

    appserver.instance=server

    appserver.instance.port=8080

    admin.user=admin

    admin.port=4849

    derby.port=1527

    domain.name=domain1

    server.cert.alias=s1as

    keystore=${com.sun.aas.domains.dir}/${domain.name}/config/keystore.jks

    keystore.password=changeit

    trustStore=${com.sun.aas.domains.dir}/${domain.name}/config/cacerts.jks

    Linux Properties 

    #admin.password= The admin password will not be saved as default. User can enter it and save it manually.

    server.cert.alias=s1as

    keystore=${com.sun.aas.domains.dir}/${domain.name}/config/keystore.jks

    domain.name=domain1

    com.sun.aas.imqHome=/var/opt/sun/appserver/domains/domain1/imq

    com.sun.aas.imqUserMgr=/opt/sun/mq/bin/imqusermgr

    com.sun.aas.domains.dir=/var/opt/sun/appserver/domains

    admin.user=admin

    appserver.instance=server

    com.sun.aas.imqBinDir=/opt/sun/mq/bin

    trustStore=${cbom.sun.aas.domains.dir}/${domain.name}/config/cacerts.jks

    com.sun.aas.imqLib=/opt/sun/mq/share/lib

    keystore.password=changeit

    com.sun.aas.derbyRoot=/opt/sun/javadb

    admin.port=4849

    derby.port=1527

    com.sun.aas.webServicesLib=/opt/sun/appserver/lib

    admin.host=jws-linuxpc-2

    com.sun.aas.javaRoot=/usr/jdk/entsys-j2se

    com.sun.aas.installRoot=/opt/sun/appserver

    appserver.instance.port=8080

  4. If needed, configure Application Server for load balancing.

    Follow the instructions in the Chapter 4, Configuring Web Servers for Load Balancing, in Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide.

  5. If needed, configure Application Server for use with the Sun Cluster software.

Directory Server Postinstallation Configuration

After a Configure Now installation, no additional configuration is necessary for Directory Server or its subcomponents.

Configuring Directory Server and Directory Proxy Server After a Configure Later Installation

After you perform a Configure Later installation of Directory Server or Directory Proxy Server, you must create instances before you can use the components. For instructions, refer to Part I, Installing Directory Service Control Center, Directory Proxy Server, Directory Server, and Directory Server Resource Kit, in Sun Java System Directory Server Enterprise Edition 6.2 Installation Guide.

Configuring Directory Service Control Center After a Configure Later Installation

After you perform a Configure Later installation of Directory Service Control Center, you must complete initialization, and optionally enable Directory Service Control Center to restart when the system reboots. For instructions, refer to the Part I, Installing Directory Service Control Center, Directory Proxy Server, Directory Server, and Directory Server Resource Kit, in Sun Java System Directory Server Enterprise Edition 6.2 Installation Guide.

HADB Postinstallation Configuration

After a Configure Now installation, no additional configuration is necessary.

Configuring HADB After a Configure Later Installation

After a Configure Later installation, the packages are installed and you are ready to perform the configuration tasks for HADB. Postinstallation configuration instructions for HADB and additional information can be found in the Sun Java System Application Server Enterprise Edition 8.2 High Availability Administration Guide.

If needed configure HADB for use with the Sun Cluster software. Refer to Sun Cluster Data Services Configuration.

Java ES Reporter Postinstallation Configuration

After Java ES Reporter has been installed, you can disable Reporter and stop it from sending reports to Sun, or re-enable Reporter after it has been disabled.

ProcedureTo Enable or Disable Java ES Reporter

  1. Locate the Reporter configuration file.

    Solaris OS: /etc/opt/SUNWmfwk/config/reporter/config.properties

    Linux: /etc/opt/sun/mfwk/config/reporter/config.properties

  2. Edit the file to set the enabled property to true or false.


    enabled=true # Reporter is enabled
enabled=false # Reporter is disabled

  3. Restart the common agent container:


    cacaoadm restart

Message Queue Postinstallation Configuration

After installation, Message Queue requires no additional configuration.

If Message Queue will be included in a Sun Cluster configuration, proceed to Sun Cluster Postinstallation Configuration.

A common optional task is to configure Message Queue for automatic startup. To do this, become superuser and edit the following properties in the imqbrokerd.conf configuration file located in /etc/imq on Solaris OS and in /etc/opt/sun/mq on Linux .

Additional configuration for Message Queue is discussed in the Sun Java System Message Queue 3 2005Q4 Administration Guide. For example, you might want to change the default administration password.

Portal Server and Portal Server Secure Remote Access Postinstallation Configuration

After a Configure Now or a Configure Later installation, the packages are installed and you are ready to perform the configuration tasks for Portal Server using instructions in the Sun Java System Portal Server 7.1 Configuration Guide.

Guidelines for configuring Portal Server to use a third-party web container are also included in Sun Java System Portal Server 7.1 Configuration Guide.

Service Registry Postinstallation Configuration

Service Registry cannot be configured during installation (Configure Now).

After a Configure Later installation, the packages are installed and you are ready to perform the configuration tasks for Service Registry. It is recommended that you configure Service Registry as a non-root user. For details, refer toConfiguring Service Registry in Service Registry 3.1 Update 1 Administration Guide and in particular the task To Configure Service Registry as a Non-Root User Using Custom Properties After a Configure Later Installation in Service Registry 3.1 Update 1 Administration Guide.

Web Proxy Server Postinstallation Configuration

After a Configure Now installation, no additional configuration is needed.

After a Configure Later installation, the packages are installed and you are ready to configure Web Proxy Server using the following procedure.

ProcedureTo Configure Web Proxy Server After a Configure Later Installation

  1. Create a properties file with your settings.

    For example, the wps.properties file might contain the following:


    WPS_JDK_HOME=/usr/jdk/entsys-j2se/jre
WPS_SERVER_ROOT=/opt/SUNWproxy
WPS_ADMIN_NAME=admin
WPS_ADMIN_PWD=admin123
WPS_ADMIN_PORT=8889
WPS_START_ON_BOOT=N
WPS_ADMIN_SERVER_USER=root
WPS_SERVER_NAME=jws-v60x-4.red.iplanet.com
WPS_SERVER_PORT=8081
WPS_SERVER_ID=proxy-server1
WPS_ADMIN_SERVER_ID=proxy-admserv
WPS_SERVER_USER=root

  2. After you have created the file, run the following command:


    WebProxyServer-base/bin/proxy/bin/configureServer -l logfile -f path/wps.properties

Web Server Postinstallation Configuration

After a Configure Now installation, no additional configuration is needed unless you are using Sun Cluster or a 64–bit configuration.

ProcedureTo Configure Web Server After a Configure Later Installation

After a Configure Later installation, the packages are installed and you are ready to configure Web Server using the following procedure.

  1. Create a runtime configuration for Web Server.

    Run the Web Server configurator following instructions in the Configure Later Mode (Java ES Only) in Sun Java System Web Server 7.0 Update 1 Installation and Migration Guide.

  2. Verify the common server settings and update settings as needed.

    Refer to the tables in Web Server Configuration Information in Sun Java Enterprise System 5 Update 1 Installation Reference for UNIX.

Sun Cluster Data Services Configuration

After the cluster has been established and the product components have been configured, you are ready to configure Sun Cluster data services for the various Java ES product components. The installed Sun Cluster agents are software programs that enable applications to take advantage of clusters. Agent software and additional configuration files comprise data services that enable you to run an application (such as Web Server or an Oracle database) on a cluster instead of on a single server. Combined with the Sun Cluster framework software and multihost disks, data services enable applications to become highly available and scalable.

Until you have fully configured the data services and all the supporting layers (volume manager, cluster file system, resource group information), Sun Cluster installation is not complete. More information on data services can be found in the Sun Cluster Overview for Solaris OS .

Note –

You can deploy Access Manager and Portal Server in a highly available web container. However, they, like any web application deployed in a web container, are subject to failure. In this case, the web container will not fail over.

For Java ES product components, run the Java ES installer on each node installing the product components, then install the corresponding HA Sun Java System subcomponent of the Sun Cluster Agents for Sun Java System product components. In the Java ES installer, select the Configure Later type. When specifying installation directories, use the location on the node's local file system for product component, and use locations on a cluster file system for the component Configuration and Product Location.

The following table lists the agents that are provided in the Sun Cluster Agents component of the Java ES installer. Some additional links to documentation are provided.

Table 6–2 Sun Cluster Agents (Data Services)

Agent Name 

Special Instructions 

Platform 

HA Application Server  

Chapter 1, Sun Cluster HA for Sun Java System Application Server EE (Supporting HADB Versions as of 4.4), in Sun Cluster Data Service for Sun Java System Application Server EE (HADB) Guide for Solaris OS

SPARC, x86 

HA Application Server EE (HADB) 

Sun Cluster Data Service for Sun Java System Application Server EE (HADB) Guide for Solaris OS

SPARC, x86 

HA Directory Server 

 

SPARC. x86 

HA Message Queue 

Use Sun Cluster Data Service for Sun Java System Message Queue Guide for Solaris OS as a guide to installing and configuring for failover.

SPARC, x86 

HA/Scalable Web Server 

Use the Sun Cluster Data Service for Sun Java System Web Server Guide for Solaris OS as a guide to installing and configuring for failover or for scalability.

SPARC, x86 

HA Agfa IMPAX 

 

SPARC 

HA Apache Tomcat 

 

SPARC, x86 

HA Apache 

 

SPARC 

HA Broadvision One-to-One Enterprise 

 

SPARC 

HA Calendar Server 

Use Chapter 6, Configuring Calendar Server 6.3 Software for High Availability (Failover Service), in Sun Java System Calendar Server 6.3 Administration Guide as a guide to installing and configuring for failover.

SPARC 

HA DHCP 

 

SPARC, x86 

HA DNS 

 

SPARC, x86 

HA Instant Messaging 

Use the Sun Java System Instant Messaging 7.2 Administration Guide for instructions on installing and configuring for high availability.

SPARC 

HA Messaging Server 

Use Chapter 3, Configuring High Availability, in Sun Java System Messaging Server 6.3 Administration Guide as a guide to installing and configuring for failover

SPARC 

HA MySQL 

 

SPARC, x86 

HA NetBackup 

 

SPARC 

HA Sun N1 Service Provisioning 

 

SPARC 

HA NFS 

 

SPARC, x86 

HA Oracle 

 

SPARC 

HA Oracle Application Server 

 

SPARC 

HA Oracle E-Business Suite 

 

SPARC 

HA Oracle Real Application Clusters 

 

SPARC 

HA Samba 

 

SPARC, x86 

HA SAP  

 

SPARC 

HA SAP DB 

 

SPARC 

HA SAP liveCache 

 

SPARC 

HA Siebel 

 

SPARC 

HA Solaris Containers 

 

SPARC, x86 

HA Sun N1 Grid Engine 

 

SPARC 

HA Sun N1 Service Provisioning 

 

SPARC 

HA SWIFT Alliance Gateway 

 

SPARC 

HA Sybase ASE 

 

SPARC 

HA WebLogic Server 

 

SPARC 

HA WebSphere MQ 

 

SPARC 

HA WebSphere MQ Integrator 

 

SPARC 

ProcedureTo Implement High Availability With a Non-Java ES Product

If your installation plan calls for high availability for non-Java ES products, follow the instructions here.

  1. Install and configure the non-Java ES product.

    For example, install Instant Messaging using the Sun Java Communications Suite 5 Installation Guide.

  2. In the Choose Software Components page of the Java ES installer, select the Sun Cluster agent that supports that product.

    For example, select the HA Instant Messaging subcomponent of the Java ES Sun Cluster Agents component.

  3. Install the Sun Cluster agent using the Java ES installer.

  4. Configure the agent following the instructions in the appropriate Sun Cluster data service guide here:

Configuring the Java Virtual Machine (JVM)

After you have finished the required postinstallation configuration for your Java ES product components, some product components might require that you tune the Java Virtual Machine (JVM). The JVM consists of several entities, the most significant being the compiler, which turns Java byte code into machine instructions. In the version of the Java Developer's Kit (JDK) that is included with Java ES, there are several choices which can be made for the JVM.

The –server option is a good tuning option for a JVM running in server mode. (You can obtain the list of options by using the java –? command.)

For garbage collection, the default algorithm is a good place to start.

Another significant tuning option that might need to be configured is the Java heap memory. For example:

A good starting point for a heavily used system would be to set the maximum heap size to 1.2 GB.

Configuring Product Components With Non-root Identifiers

You must be root to run the Java ES installer. Because of this, all files placed on the machine by the installer are owned by root. However, when performing configuration after installation, you can assign a non-root runtime user or group to some product components. For example, you might be deploying Access Manager in an instance of Application Server that is not owned by root. For purposes of installation or administration, there are many reasons to configure a product component with a non-root identifier. Generally, the non-root user must already exist on the system, but this can vary by product component.

The following table provide links to information on configuring the applicable product components with non-root identifiers.

Table 6–3 Configuring Non-root Identifiers for Product Components

Product Component 

Where to Find Instructions 

Application Server 

Set up an entire administrative domain owned and operated by a non-root user. For instructions, refer to Sun Java System Application Server Enterprise Edition 8.2 Administration Guide.

Directory Server 

Create the server instance as a regular user, or specify the user when creating the instance. For instructions, refer to the Sun Java System Directory Server Enterprise Edition 6.2 Administration Guide.

Portal Server 

Use the Portal Server configurator to configure for non-root. Instructions for running the configurator as well as descriptions of the settings used are contained in the Postinstallation Configuration chapter of the Sun Java System Portal Server 7.1 Administration Guide.

Web Server 

By default, Web Server is configured with webservd as the runtime user. When using the Web Server configurator, you can specify any runtime user ID. For additional information, refer to Installing Portal Server 7.1 on Web Server 7.0 in Sun Java System Portal Server 7.1 Configuration Guide, then scroll down to the section called Installing Portal Server 7.1 as a Non-root User.

Next Steps

After you have completed the configuration tasks in this chapter, verify postinstallation configuration by starting the product components as described in Verifying After Postinstallation Configuration.