test

Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

Chapter 6 Configuring Components After Installation

When the Sun JavaTM Enterprise System (Java ES) installer finishes installation, most 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 components will be configured with Sun Cluster software.

If you selected the Configure Later option during installation, the installer placed the component package files in their respective directories. No parameter setting was done, and most components are not operational because runtime services are not available. A number of 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 in the product documentation for each component.

This chapter contains the following sections:

How to Use This Chapter

Before acting on the information in this chapter, you should have completed the installation of the Java ES components. You can use the pkginfo command or the 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 2005Q4 Installation Reference. 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 included in this chapter for the components you installed. If you determine that no additional configuration is required for your components, you can start your components by following the instructions in Chapter 7, Verifying Installed Components.

Note –

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

MANPATH Setup

After installation, the man pages for the Java ES components are located in default directories. You need to 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 

Administration Server

For Solaris OS: /opt/SUNWasvmn/man

For Linux: /opt/sun/man

Application Server

For Solaris OS: /opt/SUNWappserver/share/man

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

Common agent container

For Solaris OS: /opt/SUNWcacao/man

For Linux: /opt/sun/man

Directory Server

For Solaris OS: /opt/SUNWdsvmn/man

For Linux: /opt/sun/man

Sun Cluster

For 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.

Steps

  1. 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.

  2. Verify that the man pages are accessible.

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


    man asadmin

Sun Cluster Postinstallation Configuration

Sun 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 components:

If the Java ES components you installed will be included in a Sun Cluster environment, you must first configure the Sun Cluster framework before configuring the components. then configure the Java ES components you have selected. Finally, depending on the 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 2005Q4 Installation Reference.

Phase II. Component Data Services

After you have installed and configured the Sun Cluster framework and the other 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

Whenever you use the Java ES installer to configure Access Manager on Web Server, you will need to perform the following steps:

  1. Start the Web Server administration instance.

  2. Log in as the Web Server administrator.

  3. Select the Web Server instance on which Access Manager and Portal Server were installed.

  4. Click Manage.

  5. Click Apply and Apply Changes. This will commit the changes made by Access Managerand Portal Server, and restart the Web Server instance.

Note –

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 it need only be started. For instructions on restarting Access Manager, see Starting and Stopping Access Manager.

Access Manager configuration is described in the following sections:

Configuring Access Manager After a Configure Now Installation

Although you can start Access Manager and log into the Access Manager console immediately after running the Java ES installer, 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.

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 Access Manager With an Existing Directory Server in the Sun Java System Access Manager 6 2005Q1 Migration Guide for a description of the final configuration steps.

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 sections:

Caution – Caution –

Before performing the tasks in this section, Directory Server must be configured and running. To verify that Directory Server, is running, refer to Starting and Stopping Directory Server.

Enabling the Directory Server Referential Integrity Plug-in

When the Directory Server 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. If the Referential Integrity Plug-in is not already enabled, perform the following procedure.

ProcedureTo Enable the Referential Integrity Plug-in

Steps

  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.

Adding Access Manager Indexes to Directory Server

Directory Server indexes improve the performance of searches of Directory Server data. The following table lists the recommended attributes that you should consider indexing for Access Manager (if they are not already indexed).

Table 6–2 Suggested Access Manager Indexes for Directory Server

Attribute 

Index Type 

nsroledn

Equality, Presence, and Substring 

memberof

Equality and Presence 

iplanet-am-static-group-dn

Equality 

iplanet-am-modifiable-by

Equality 

iplanet-am-user-federation-info-key

Equality 

sunxmlkeyvalue

Equality and Substring 

o

Equality 

ou

Equality, Presence, and Substring 

sunPreferredDomain

Equality, Presence, and Substring 

associatedDomain

Equality, Presence, and Substring 

sunOrganizationAlias

Equality, Presence, and Substring 

Add indexes using either the Directory ServerConsole or the ldapmodify command-line utility. Use ldapmodify to load the Access Managerindex.ldif file, which is available in the following directory:

For more information about both the Console and ldapmodify, see Chapter 10 of the Sun Java System Directory Server 5 2005Q1 Administration 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 2005Q4 Administration Guide.

For instructions on configuring Access Manager for a third-party web container (BEA WebLogic or IBM WebSphere Application Server), refer to Sun Java System Access Manager 7 2005Q4 Administration Guide.

Note –

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 it need only be started. For instructions on restarting Access Manager, see Starting and Stopping Access Manager.

Administration Server Postinstallation Configuration

After a Configure Now installation, Administration Server requires no additional configuration. If this component will be included in a Sun Cluster configuration, proceed to Sun Cluster Postinstallation Configuration.

After a Configure Later installation, packages are installed and you are ready to begin Administration Server configuration using the following procedure. Additional configuration details can be found in the Sun Java System Administration Server 5 2005Q1 Administration Guide.

Note –

Before configuring Administration Server, Directory Server must already be configured.

ProcedureTo Configure Administration Server After a Configure Later Installation

Steps

  1. Start the configuration utility.

    For example, on Solaris OS:

    /usr/sbin/mpsadmserver configure

    Follow the instructions on each screen.

  2. Ensure that access permissions for the files under server-root /alias have been set to prevent access by all user accounts other than those of the servers installed there.

  3. Verify the common server settings and the Administration Server settings.

    See the tables in Administration Server Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference.

    Note –

    If Administration Server was installed in the same installation session as Access Manager, most of the configuration was completed during installation.

  4. If needed, configure Administration Server for use with the Sun Cluster software.

    Refer to Administration Server Data Service.

Application Server Postinstallation Configuration

After a Configure Now installation, Application Server requires no postinstallation configuration unless you will be applying Web Server plug-in for load balancing.

Note –

To configure Application Server for load balancing, refer to the “Configuring Web Servers for HTTP Load Balancing” section in the Chapter 4, Configuring Load Balancing and Failover, in Sun Java System Application Server Enterprise Edition 8.1 2005Q2 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

Steps

  1. Locate the accessory CD for Application Server.

    Accessory contents can also be downloaded from the Sun Download Center at http://www.sun.com/download/index.jsp.

  2. Refer to the README file in the Addon folder on the CD and follow the procedures detailed there.

  3. Modify the ApplicationServer-base/samples/common.properties file.

    Modify the following properties in the common.properties file. If you do not know some paths, you can copy them from the ApplicationServer-base /config/asenv.conf file.

    Solaris Properties 

    com.sun.aas.pointbaseRoot=/opt/SUNWappserver/appserver/pointbase

    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

    pointbase.port=9092

    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=admin123

    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.pointbaseRoot=/opt/sun/appserver/pointbase

    admin.port=4849

    pointbase.port=9092

    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 use with the Sun Cluster software.

    Note –

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

Calendar Server Postinstallation Configuration

Calendar Server cannot be configured by the Java ES installer (Configure Now).

After a Configure Later installation, use the following procedure to configure Calendar Server.

Note –

Skip Step 1 if you have already run the Directory Preparation Tool on the same Directory Server during configuration of another communications component.

ProcedureTo Configure Calendar Server After a Configure Later Installation

Steps

  1. Configure Directory Server for communications services (Calendar Server, Messaging Server and Delegated Administrator) by running the Directory Preparation Tool, comm_dssetup.pl.

    1. Verify that Directory Server is running. Refer to Starting and Stopping Directory Server.

    2. On the host where Directory Server is installed, run the Directory Preparation Tool:

      perl comm_dssetup.pl

    3. When prompted by the script, select Schema 2 Native Mode as the schema type unless you need to retain compatibility with previous versions of Calendar Server, Messaging Server, or custom applications.

      For more information about making the appropriate choice, see the Sun Java System Communications Services 6 2005Q4 Schema Migration Guide.

  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:

    192.18.99.999 mycomputer.company.com mycomputer loghost

  3. If you intend to use Delegated Administrator to provision users for Calendar Server, you must perform additional steps to configure Delegated Administrator.

    Instructions for configuring the utility and provisioning users are contained in the Sun Java System Communications Services 6 2005Q4 Delegated Administrator Guide.

    Caution – Caution –

    This step only applies if your installation includes Access Manager and LDAP Schema 2, and if this step was not done during configuration of another communications component.

  4. Configure Calendar Server by running the Calendar Server configuration program, CalendarServer-base /cal/sbin/csconfigurator.sh .

    For more information on configuring Calendar Server, refer to the Sun Java System Calendar Server 6 2005Q4 Administration Guide.

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

    Refer to Calendar Server Data Service.

Communications Express Postinstallation Configuration

Communications Express cannot be configured during installation (Configure Now).

After a Configure Later configuration installation, the packages are installed and you are ready to configure Communications Express.

ProcedureTo Configure Communications Express After a Configure Later Installation

Note –

Skip Step 1 if you have already run the Directory Preparation Tool on the same Directory Server during configuration of another communications component.

Steps

  1. Configure Directory Server for communications services (Calendar Server, Messaging Server and Delegated Administrator) by running the Directory Preparation Tool (comm_dssetup.p1).

    See Calendar Server Postinstallation Configuration

    Tip –

    Before proceeding to Step 2, ensure that the components on which Communications Express is dependent are installed and running. For more information, see “Prerequisites for Configuring Communications Express” in the Sun Java System Communications Express 6 2005Q4 Administration Guide.

  2. Configure Communications Express using the configuration program, CommunicationsExpress-base /sbin/config-uwc.

    Instructions are in Chapter 3, Installing and Configuring Communications Express, in Sun Java System Communications Express 6 2005Q4 Administration Guide.

  3. Compete the additional post configuration tasks needed for Communications Express.

    See Chapter 3, Installing and Configuring Communications Express, in Sun Java System Communications Express 6 2005Q4 Administration Guide.

Directory Proxy Server Postinstallation Configuration

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

After a Configure Later installation, the packages are installed and you are ready to perform the configuration tasks for Directory Proxy Server.

ProcedureTo Configure Directory Proxy Server After a Configure Later Installation

Steps

  1. Configure the Directory Proxy Server instance using the quickstart.tcl script. For example:


    # cd /usr/sadm/mps/admin/v5.2/dps 


    # /usr/sadm/mps/admin/v5.2/bin/tcl8.2/tclsh quickstart.tcl
    		 

    -cid cid_path -listen 
port-number -password 
password


    -serverroot serverroot_path 
-userID dn

    The arguments of the quickstart.tcl script are as follows:

    Argument 

    Description 

    -cid

    Fully qualified path. Allows the script for verify that the following directory exists: 

    cid-path/bin/dps/install/script

    -serverroot

    A fully qualified path to an installed and configured Administration Server. The script validates that the following files exist: 

    serverroot-path/admin-serv/config/adm.conf serverroot_path/admin-serv/config/jvm12.conf

    -listen

    Directory Proxy Server port. 

    -userID

    The UID of the Administration Server administrator. 

    -password

    Password of the Administration Server administrator. 

  2. Verify the common server settings.

    Refer to Administration Server Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference.

  3. Update the common server settings for Directory Proxy Server.

    Refer to Common Server Settings in Sun Java Enterprise System 2005Q4 Installation Reference.

  4. Verify the configuration.

    Refer to Directory Proxy Server Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference.

Directory Server Postinstallation Configuration

After a Configure Now installation, no additional configuration is necessary unless you need to configure Directory Server in 32–bit mode on a 64–bit Solaris SPARC platform. If this is the case, refer to Step 6 in the following Configure Later procedure.

Note –

The Directory Serverthat is bundled with Solaris OS is not the same version as the current Java ES Directory Servercomponent. After you have installed Directory Server, you should consider running the following command to set the default Directory Server to 5.2: /usr/sbin/directorysoerver –d 5.2

You will then be able to use the various Directory Servercommands against the Java ES Directory Server5.2. If you are planning to use the version that is bundled with the Solaris OS (Directory Server 5.1), this action is not required.

After a Configure Later installation, the packages are installed and you are ready to perform the configuration tasks for Directory Server. Directory Server.

ProcedureTo Configure Directory Server After a Configure Later Installation

Steps

  1. Start the configuration utility. For example:

    directoryserver -u 5.2 configure

    Follow the instructions on each screen.

    Note –

    On Linux, two commands are available, but only one works correctly. Be sure to use /opt/sun/sbin/directoryserver.

  2. Update the system configuration to enable core file generation.

    For example:

    coreadm -e proc-setid

    Note –

    If you have installed Directory Server to run as a user other than superuser, Directory Server might not be able to generate a core file during a crash. It is important that you allot enough space for core files, and that you allow Directory Server to generate core files during a crash.

  3. (Optional) Many command-line scripts written in Perl can read the bind password interactively (-w option). To enable this functionality, do the following:

    1. Install the Term::ReadKey Perl module, available separately from CPAN (http://cpan.org).

    2. Edit each Perl script to read the bind password interactively by uncommenting the appropriate lines.

      All other Perl script functionality remains available without the Term::ReadKey module.

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

    Refer to Administration Server Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference.

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

    Refer to Directory Server Data Service.

  6. If needed, configure Directory Server in 32-bit mode on a 64-bit Solaris SPARC platform as follows:

    1. Use the pkgrm command to remove the following 64–bit Directory Server packages:

      SUNWdsvhx SUNWdsvx

    2. Edit the /var/sadm/install/productregistry file, removing references to the SUNWdsvhx and SUNWdsvx packages.

    3. Configure Directory Server.

HADB Postinstallation Configuration

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

After a Configure Later installation, the packages are installed and you are ready to perform the configuration tasks for HADB.

Configuring HADB After a Configure Later Installation

Postinstallation configuration instructions for HADB and additional information can be found in the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 High Availability Administration Guide.

If needed configure HADB for use with the Sun Cluster software. Refer to Application Server EE (HADB) Data Service.

Instant Messaging Postinstallation Configuration

Instant Messaging 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 Instant Messaging.

Configuring Instant Messaging After a Configure Later Installation

When you install the server, the multiplexor is also installed and enabled. If you want to support only a multiplexor on a host, you must disable the server installed on that host. For instructions, refer to the Sun Java System Instant Messaging 7 2005Q1 Administration Guide.

Instructions for using the Instant Messaging configure utility, InstantMessaging-base/configure, are contained in Chapter 1, Configuring Instant Messaging After Installation in the Sun Java System Instant Messaging 7 2005Q1 Administration Guide.

If needed configure Instant Messaging for use with the Sun Cluster software. Refer to Instant Messaging Data Service.

Message Queue Postinstallation Configuration

After installation, Message Queue requires no additional configuration.

If this component 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 (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.

Messaging Server Postinstallation Configuration

Messaging Server cannot be configured during installation (Configure Now).

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

ProcedureTo Configure Messaging Server After a Configure Later Installation

Note –

Skip Step 1 if you have already run the Directory Preparation Tool on the same Directory Server during configuration of another communications component.

Steps

  1. Configure Directory Server for communications services (Calendar Server, Messaging Server and the Delegated Administrator) by running the Directory Preparation Tool, comm_dssetup.pl.

    See Calendar Server Postinstallation Configuration

  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:

    192.18.99.999 mycomputer.company.com mycomputer loghost

  3. Configure Messaging Server by running the initial runtime configuration program for Messaging Server, MessagingServer-base /sbin/configure.

    For information on configuring Messaging Server, refer to the Sun Java System Messaging Server 6 2005Q4 Administration Guide.

  4. If you intend to use Delegated Administrator to provision users for Messaging Server, you must perform additional steps to configure it.

    Instructions for configuring Delegated Administratorand provisioning users are contained in the Sun Java System Communications Services 6 2005Q4 Delegated Administrator Guide.

    Caution – Caution –

    This step applies only if your installation includes Access Manager and LDAP Schema 2, and if this step was not done during configuration of another communications component.

  5. Configure for use with the Sun Cluster software, if applicable. Refer to Messaging Server Data Service.

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 the following procedures.

Configuring Portal Server and Portal Server Secure Remote Access After a Configure Now Installation

Final configuration steps for Portal Server and Portal Server Secure Remote Access differ depending on whether it is deployed in a Sun web container or a third-party web container. The following sections explain the details:

Configuring Portal After a Configure Now Installation on a Sun Web Container

If you are using Application Server or Web Server as the web container for Portal Server and Portal Server Secure Remote Access, you must apply changes to the instance. Follow the instructions in the Sun Java System Portal Server 6 2005Q4 Administration Guide and the Sun Java System Portal Server 6 2005Q4 Release Notes.

Configuring Portal After a Configure Now Installation on a Third-Party Web Container

If you are using BEA WebLogic Server or IBM WebSphere Application Server as the web container for Portal Server and Portal Server Secure Remote Access, use the following procedure.

ProcedureTo Configure Portal on a Third-Party Web Container

Note –

Deployment of Portal Server and Portal Server Secure Remote Access on third-party web containers is only supported on the Solaris OS.

Steps

  1. Stop all web container instances, including the admin instance and, in the case of BEA WebLogic Server, managed server instances.

  2. Start the web container’s admin server instance. If you have installed on a BEA WebLogic Server managed instance, start the managed instance too.

  3. Deploy Portal Server and Portal Server Secure Remote Access by running the deploy command:

    cd PortalServer-base /bin ./deploy

    When prompted, choose the default for the deploy URI and server instance name, and enter the web container admin password.

  4. Deploy the Portlet samples (that is, the portletsamples.war file):

    setenv DEPLOY_ADMIN_PASSWORD webcontainer-admin-password

    setenv IDSAME_ADMIN_PASSWORD AccessManager-admin-password

    cd PortalServer-base/lib

    ./postinstall_PortletSamples

    When prompted, enter the web container admin password and the Access Manager admin password.

  5. Restart the web container instance into which Portal Server and Portal Server Secure Remote Access was deployed.

    See your web container documentation for instructions on starting the web container instance. Additional information can be found in the Sun Java System Portal Server 6 2005Q4 Administration Guide and the Sun Java System Portal Server 6 2005Q4 Release Notes, respectively.

    Note –

    In the case of installation on a BEA WebLogic Server managed server, the WAR files do not get deployed. Deploy the WAR files using the BEA WebLogic Server administration console.

Configuring Portal Server and Portal Server Secure Remote Access After a Configure Later Installation

Final configuration steps for Portal Server differ depending on whether it is deployed in a Sun web container or a third-party web container. The following sections explain the details:

Note –

Information on configuring Portal Server Secure Remote Access can be found in the Sun Java System Portal Server 6 2005Q4 Secure Remote Access Administration Guide.

Configuring Portal Server After a Configure Later Installation on a Sun Web Container

Portal Server provides a common configurator that can be used to configure all Portal Server subcomponents as well as Portal Server Secure Remote Access.

ProcedureTo Configure Portal Server After a Configure Later Installation on Application Server or Web Server

Steps

  1. Create a runtime configuration for Portal Server by running the Portal Server configurator, PortalServer-base /lib/psconfig.

    Instructions for running the configurator as well as descriptions of the settings used by the configurator are contained in the Sun Java System Portal Server 6 2005Q4 Administration Guide.

  2. Apply changes to the instance.

    Use the instructions in the “ Post-Installation Tasks” section in the Postinstallation Configuration chapter of the Sun Java System Portal Server 6 2005Q4 Administration Guide.

Configuring Portal Server After a Configure Later Installation on a Third-Party Web Container

Portal Server provides a common configurator that can be used to configure all Portal Server subcomponents as well as Portal Server Secure Remote Access.

Note –

Deployment of Portal Server and Portal Server Secure Remote Access on third-party web containers is only supported on the Solaris OS.

ProcedureTo Configure Portal Server After a Configure Later Installation on BEA WebLogic Server or IBM WebSphere Application Server

Steps

  1. Create a runtime configuration for Portal Server by running the Portal Server configurator, PortalServer-base /lib/psconfig .

    Instructions for running the configurator as well as descriptions of the settings used by the configurator are contained in the Postinstallation Configuration chapter of the Sun Java System Portal Server 6 2005Q4 Administration Guide.

  2. Stop all web container instances, including the admin instance and, in the case of BEA WebLogic Server, managed server instances.

  3. Start the web container’s admin server instance. If you have installed on a BEA WebLogic Server managed instance, start the managed instance too.

  4. Deploy Portal Server by running the deploy command:

    cd PortalServer-base/bin ./deploy

    When prompted, choose the default for the deploy URI and server instance name, and enter the web container admin password.

  5. Deploy the Portlet samples (that is, the portletsamples.war file):

    setenv DEPLOY_ADMIN_PASSWORD web-container-admin-password setenv IDSAME_ADMIN_PASSWORD AccessManager-admin-password cd PortalServer-base/lib ./postinstall_PortletSamples

    When prompted, enter the web container admin password and the Access Manager admin password.

  6. Restart the web container instance into which Portal Server was deployed. See your web container documentation for instructions on starting the web container instance.

    Note –

    In the case of installation on a BEA WebLogic Server managed server, the WAR files do not get deployed. Deploy the WAR files using the BEA WebLogic Server administration console.

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 using the following procedure.

ProcedureTo Configure Service Registry After a Configure Later Installation Using Default Properties

Steps

  1. Change to the ServiceRegistry-base /install directory. For example:

    On Solaris OS:

    cd /opt/SUNWsoar/install

    On Linux:

    cd /opt/sun/SUNWsoar/install

  2. Verify that the JAVA_HOME environment variable is set.

    The usual value is /usr/jdk/entsys-j2se.

  3. Run the following command to configure:

    • On Solaris OS:/usr/sfw/bin/ant -f ./build-install.xml install

    • On Linux: /opt/sun/bin/ant --noconfig -f ./build-install.xml install

    Note –

    To perform configuration using custom property settings, edit the build-install.xml file before you run the install target. For instructions, refer to the Service Registry 3 2005Q4 Administration Guide.

Web Proxy Server Postinstallation Configuration

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

After a Configure Later configuration 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

Steps

  1. Create a properties file with your settings.

    For example, wps.properties:


    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.

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

If this component will be included in a Sun Cluster configuration, proceed to Sun Cluster Postinstallation Configuration.

ProcedureTo Configure Web Server After a Configure Later Installation

Steps

  1. Create a runtime configuration for Web Server by running the Web Server configurator, WebServer-base /setup/configure.

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

    Refer to Administration Server Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference as described in the tables in Web Server Configuration Information in Sun Java Enterprise System 2005Q4 Installation Reference.

  3. If needed, configure for use with the Sun Cluster software.

    Refer to Web Server Data Service.

Sun Cluster Data Services Configuration

After the cluster has been established and the components have been configured, you are ready to configure Sun Cluster data services for the various Java ES 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.

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.

More information on data services can be found in the Sun Cluster Overview for Solaris OS.

The following sections list the Java ES components whose agents are provided in the Sun Cluster Agents component of the installer. For each component, the high availability service and the installation process are summarized, including the documentation needed. In any data service installation procedure referred to by the documentation, substitute the Java ES Sun Cluster Agents 3.1 8.05 Accessory CD-ROM.

Note –

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 ES is not complete.

Administration Server Data Service

Administration Server can be configured for failover. Refer to Sun Cluster Data Services Planning and Administration Guide for Solaris OS for information on installing and configuring the Administration Server data service.

To install the necessary packages, run the Java ES installer on each node, installing the Administration Server and HA Sun Java System Directory Server subcomponent of the Sun Cluster Agents for Sun Java System component. Select the Configure Later option.

During configuration, use a location on the cluster file system as the Server Root.

Application Server Data Service

Application Server can be configured for failover. Use 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 as a guide to installation and configuration.

To install the necessary packages, run the Java ES installer on each node, installing Application Serverand the HA Sun Java System Application Server(PE/SE) subcomponent of the Sun Cluster Agents for Sun Java System components. Select the Configure Later option.

When specifying installation directories, use the location on the node's local file system for Application Server, and use locations on the cluster file system for AS Configuration and Product Location.

Application Server EE (HADB) Data Service

The Application ServerHADB can be mastered for multiple nodes. Use Sun Cluster Data Service for Sun Java System Application Server EE (HADB) Guide for Solaris OS as a guide to installation and configuration.

To install the necessary packages, run the Java ES installer on each node, installing the HA Sun Java System HADB subcomponent of the Sun Cluster Agents component. Select the Configure Later option. When the database is created, the configuration and data files are created by default on the local file system of each cluster node. Store static files and data on the local file system of each cluster node.

Calendar Server Data Service

Calendar Server can be configured for failover. See Chapter 7, Configuring for High Availability (Failover Service), in Sun Java System Calendar Server 6 2005Q4 Administration Guide as a guide to installation and configuration.

To install the necessary packages:

Directory Server Data Service

Directory Server can be configured for failover. To install the necessary packages, run the Java ES installer on each node, installing Directory Server and the HA Sun Java System Directory Server subcomponent of the Sun Cluster Agents component. Select the Configure Later option.

When specifying installation directories, use a location on the cluster file system for Directory Server, Server Root.

Instant Messaging Data Service

Instant Messaging can be configured for failover. Refer to theSun Java System Instant Messaging 7 2005Q1 Administration Guide for instructions on configuring high availability for Instant Messaging.

Message Queue Data Service

Message Queue can be configured for failover. Use Sun Cluster Data Service for Sun Java System Message Queue Guide for Solaris OS as a guide to installation and configuration.

To install the necessary packages, run the Java ES installer on each node, installing Message Queue and the HA Sun Java System Message Queue subcomponent of the Sun Cluster Agents component. Select the Configure Later option.

During configuration, use a location on each node’s local file system for static files and data, and use a location on the cluster file system for dynamic data.

Messaging Server Data Service

Messaging Server can be configured for failover. Use Chapter 3, Configuring High Availability, in Sun Java System Messaging Server 6 2005Q4 Administration Guide as a guide to installation and configuration.

To install the necessary packages, run the Java ES installer on each node, installing Messaging Server and the HA Sun Java System Messaging Server subcomponent of the Sun Cluster Agents component. Select the Configure Later option.

When specifying installation directories, use a location on the cluster file system for Messaging Server. During configuration, place the configuration and data on the cluster file system.

Web Server Data Service

Web Server can be configured for failover or scalability. The following sections have information related to each option.

Web Server Data Service for Failover

Use Sun Cluster Data Service for Sun Java System Web Server Guide for Solaris OSSun Cluster Data Service for Sun Java System Web Server Guide for Solaris OS as a guide to installation and configuration.

To install the necessary packages:

Web Server Data Service for Scalability

Use Sun Cluster Data Service for Sun Java System Web Server Guide for Solaris OS as a guide to installation and configuration.

To install the necessary packages, run the Java ES installer on each node, installing Web Server and the HA/Scalable Sun Java System Web Server subcomponent of the Sun Cluster Agents component. Select the Configure Later option.

Data Services for Other Products

If your installation plan calls for high availability of some other product, acquire the agent that supports the product, then install and configure the agent following the instructions in the appropriate Sun Cluster data service guide. One way to get agents for other products is from the Java ES accessory CD.

Configuring the Java Virtual Machine (JVM)

After you have finished the required post-installation configuration for your Java ES components, some 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 this Java ES release, there are several choices which can be made for the JVM. The best starting option is the –server option. (You can obtain the list of options by using the java –? command.) The –server option is a good tuning option for a JVM running in server mode.

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 Components With Non-root Identifiers

When performing configuration after installation, you can assign a non-root runtime user or group to some component products. For example, you might be deploying Access Manager in an instance of Web Server that is not owned by root.

For purposes of installation to administration, there are many reasons to configure a component with a non-root identifier. You can find examples of using a non-root identifier in Non-Root Examples.

The following sections provide information on configuring the applicable components with non-root identifiers.

Note –

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.

Configuring Administration Server With Non-root ID

To configure Administration Server with a non-root ID, use the mpsadmserver configure command. See the Sun Java System Administration Server 5 2005Q1 Administration Guidefor more details.

Configuring Application Server With Non-root ID

To configure Application Server with a non-root ID, you can set up an entire administrative domain owned and operated by a non-root user.

  1. Log in to the host using a non–root user ID.

  2. Run the asadmin create-domain command with the --domaindir option, pointing to the directory where you have write permissions. For example:

    /opt/SUNWappserver/appserver/bin ./asadmin create-domain --domaindir /export/domains --adminport 5050 --adminuser admin --passwordfile /tmp/passwordfile --instanceport 9090 domain2

    In this example domain2 directory will be created under /export/domains

  3. Start this domain using the --domaindir option again. For example:

    /opt/SUNWappserver/appserver/bin ./asadmin start-domain --domaindir /export/domains --user admin --passwordfile /tmp/passwordfile domain2

For more information, see the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Administration Guide.

Configuring Calendar Server With Non-root ID

To configure Calendar Server with a non-root ID, use the Calendar Server configurator. See the Sun Java System Calendar Server 6 2005Q4 Administration Guide) for details.

Configuring Directory Proxy Server With Non-root ID

To configure Directory Proxy Server with a non-root ID, become superuser and run the quickstart.tcl script. This script adopts the user ID specified for the Administration Server so, when Administration Server uses a non-root user ID, Directory Proxy Server will as well.

Configuring Directory Server With Non-root ID

Use the Directory Server configurator to configure Directory Server with a non-root ID. Install the Directory Server packages using the Configure Later option. After running the installer, set the default Directory Server version to 5.2. Run the Directory Server configurator and specify a non-root user ID. Select a port number greater than 1024.

Configuring Messaging Server With Non-root ID

To configure Messaging Server with a non-root ID, use the Messaging Server configurator. See the Sun Java System Messaging Server 6 2005Q4 Administration Guide for details.

Configuring Portal Server With Non-root ID

To configure Portal Server with a non-root ID, use the Portal Server configurator. 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 6 2005Q4 Administration Guide.

Configuring Web Server With Non-root ID

To configure Web Server with a non-root ID, use the Web Server configurator. See Web Server Postinstallation Configuration.

Next Steps

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