Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System Installation Guide for Microsoft Windows 

Chapter 7
Post-installation Configuration for Configure Later Option

After installing in the Configure Later mode, for all components (except Message Queue) you will have to perform the additional task of configuration before the Sun Java Enterprise System environment is operational. You might also require to do some configuration even if you installed with the Quick Configure option, for example, if you want to configure Instant Messenger channel on Portal Server.

This chapter contains the following sections:

Installed Components

If you select the Configure Later option during installation, the Sun Java Enterprise System installer places the component executable and files in their respective directories. No parameter setting is done and most components are not operational because runtime services are still not available.

During configuration, the configurator creates a folder in the Server-Root with names slapd-(instance name), adm-serv for Directory Server and Administration Server respectively.

Registry entries are created in:

HKLM\SOFTWARE\Sun Microsystems\Java ES\<Productname>\<Version>

and

HKLM\SOFTWARE\Sun Microsystems\Java ES\Installer

The path is set in the Environment variables after the files are copied.

The following sections contain post-installation configuration information for the Configure Later option:

Configuring Access Manager After a Configure Later Installation

The installation directory for Access Manager is <INSTALLDIR>\AccessManager. The following files are used to configure the Access Manager:

After a Configure Later installation, these files are installed and you are ready to configure Access Manager.

Note

Web Server is the default container for Access Manager.

    To Configure Access Manager After a Configure Later Installation

The default values are written to AMConfigurator.properties file.

Access Manager has the following installable components:

To configure the Access Manager, perform the following steps:

  1. Manually populate the properties file of Access Manager located at AccessManager\Setup\AMConfigurator.properties.
  2. Partial deployment of Access Manager can be done by setting the DEPLOY_LEVEL property value to any of the following:

1 - Full install (Configures Web Container, directory server, installs services)

2 - Console only install (Installs AMSDK and configures web container)

3 - SDK only (Installs only the SDK)

4 - SDK with container configuration (Installs SDK and configures web container)

All the above choices configure samples too.

5 - Federation only - (configures Web Container only)

6 - Server only (same as 1)

11 - Full Uninstall

12 - Console only uninstall

13 - SDK uninstall

14 - Uninstall SDK only with container unconfig

15 - Federation only uninstall

16 - Server only uninstall

21 - Full reinstall

26 - Server reinstall

31 - SDK reinstall

32 - Console reinstall

33 - Console and SDK reinstall

35 - Liberty reinstall.

Note

WS61_HOST key in the AMConfigurator.properties file is case sensitive. It has to be the exact replica of the Web Server instance name.

  1. Change the command path to <INSTALLDIR>\AccessManager\Setup.
  2. Run the AMConfig.bat to configure Access Manager.
  3. Restart the Web Container Service before using the AM Console.
  4. To verify configuration, proceed to Starting and Stopping Access Manager.

    Note

    Web Container: If Application Server and Web Server both are selected for installation, Web Server is the default web container used.

Configuring Administration Server After a Configure Later Installation

After a Configure Later installation, components are installed and you are ready to begin Administration Server configuration. The installation directory for Administration Server is <INSTALLDIR>\Server-Root. The following files are used to configure Administration Server:

configure-ad.class

ADConfig.bat

Note

During configuration you must first configure the Directory Server and then the Administration Server.

    To Configure Administration Server After a Configure Later Installation
  1. Change the command path to <INSTALLDIR>\Server-Root\setup
  2. Run the ADConfig.bat to complete the configuration.
  3. Give the required information in the panels
  4. To verify configuration, proceed to Starting and Stopping Administration Server.

    Tip

    During unconfiguration you must first unconfigure the Administration Server first and then the Directory Server.

Configuring Application Server After a Configure Later Installation

The installation directory for Application Server is <INSTALLDIR>\AppServer. After a Configure Later installation, components are installed and you are ready to begin Application Server configuration. The following files are used to configure Application Server:

The default values are written to ASConfigurator.properties file.

Note

Application Server cannot be installed and configured with folder names having space.

    To Configure Application Server After a Configure Later Installation

Application Server has the following installable components which can be configured separately:

1. Domain Administration Server

2. Load Balancer Plugin

To configure the Application Server, perform the following steps:

  1. Manually populate the properties file of Application Server located at AppServer\Setup\ASConfigurator.properties
  2. Change the command path to <INSTALLDIR>\AppServer\Setup
  3. Run the DASConfigure.bat to configure Domain Administration Server.
  4. Run the LBConfigure.bat to configure Load Balancer Plugin.
  5. To verify configuration, proceed to Starting and Stopping Application Server.

Configuring HADB After a Configure Later Installation

  1. Check whether all the properties are populated in mgt.cfg and hadb.properties under <installdir>\Hadb\4.4.1-2\lib
  2. Change the command path to <INSTALLDIR>\Hadb\4.4.1-2\lib
  3. Run the HADBConfig.bat to configure HADB management agent
  4. To verify configuration, proceed to Starting and Stopping HADB Management Agent

Configuring Calendar Server After a Configure Later Installation

Before installing Calendar Server, ensure Directory Preparation Script is configured successfully. The installation directory for Calendar Server is <INSTALLDIR>\Calendar Server.

To configure the Calendar Server you need to specify the details of Directory Server. The details below is required if you choose to run the comm_dssetup.pl perl script while configuration. This Directory Preparation Script has to be run against the Directory server, if not already run, before configuring the Calendar Server.

    To Configure Calendar Server After a Configure Later Installation
Step 1: Running the Directory Preparation Script
  1. Configure Directory Server for communications services (Calendar Server, Messaging Server and the Delegated Administrator Utility) by running the Directory Preparation Script (comm_dssetup.pl).

    Note

    Skip this step if you have already run the Directory Preparation Script on the same Directory Server during configuration of another communications component.

    1. Verify that Directory Server is running. Refer to Starting and Stopping Directory Server if needed.
    2. On the machine where Directory Server is installed, you must run the Directory Preparation Script:

      3.   perl comm_dssetup.pl

    3. In the command prompt change the path to <INSTALLDIR>\DSSetup.

      4. Note

      If you get a response Detected DS version. Run this tool as Root, then you must check the perl, which the system is using. Active perl or the nsperl which comes along with Directory Server should be set in the PATH variable, before running the script again.

    4. Run the dssetup.bat to complete the configuration
Step 2: Configuring the Calendar Server

Calendar Server has a GUI based configurator. It can be invoked by the following steps.

  1. Change the command path to <INSTALLDIR>\Calendar Server\bin\config
  2. Run the CSConfig.bat to complete the configuration.
  3. Proceed with the panels.
  4. To verify configuration, proceed to Starting and Stopping Calendar Server.

Configuring Communications Express After a Configure Later Installation

The installation directory for Communications Express is <INSTALLDIR>\CommsExpress. The following files are used to configure Communications Express:

    To Configure Communications Express After a Configure Later Installation
  1. Manually populate the Communications Express properties files located at <INSTALLDIR>\CommsExpress\lib with Directory Server and Web Server entries.
  2. Change the command path to <INSTALLDIR>\CommsExpress\lib
  3. Run the CEConfig.bat to complete the configuration.

    Note

    Ensure Directory Preparation Script is configured successfully before running the Communications Express configurator.

Post Configuration Steps:

We have to do some post configuration steps before logging into Communications Express

    1. Restart Calendar Server.
    2. Restart Web Server or the Application Server, depending on which you have selected as the web container.

Configuring Delegated Administrator After a Configure Later Installation

The installation directory for Delegated Administrator is <INSTALLDIR>\DelegatedAdmin.

Note

Before configuring Delegated Administrator, commdssetup has to be run on Schema-2.

    To Configure Delegated Administrator After a Configure Later Installation
  1. Change the command path to <INSTALLDIR>\DeligatedAdmin\lib.
  2. Run the DAConfig.bat to complete the configuration.
  3. A series of panels appear where information about Access Manager, Web Server, and Directory Server have to be entered. Enter the details and complete the configuration.
  4. To verify configuration, proceed to Starting and Stopping Web Server.

    Note

    Ensure that Access Manger and Directory Server are successfully configured before running the Delegated Administrator configurator.

Configuring Directory Proxy Server After a Configure Later Installation

After a Configure Later installation, the components are installed and you are ready to perform the configuration tasks for Directory Proxy Server. The installation directory for Directory Proxy Server is <INSTALLDIR>\Server-Root. The following file is used to configure Directory Proxy Server:

    To Configure Directory Proxy Server After a Configure Later Installation
  1. Change the command path to <INSTALL DIR>\Server-Root\setup
  2. Type the following command from the above mentioned location

    3. DPSConfig.bat

    • <INSTALLDIR> is the directory where the product is installed
    • Enter the Admin Name and Password as in the Administration Server
    • Enter a valid port number. The default is port is 489.
    • Ensure to use back and forward slashes in the same way as shown above when replacing the <INSTALL DIR> value.
    • Enter a valid instance name in the instance selection panel
  3. To verify configuration, proceed to Starting and Stopping Directory Proxy Server.

Configuring Directory Server After a Configure Later Installation

After a Configure Later installation, the components are installed and you are ready to perform the configuration tasks for Directory Server. The installation directory for these products are <INSTALLDIR>\Server-Root. The following files are used to configure Directory Server:

    To Configure Directory Server After a Configure Later Installation
  1. Change the command path to <INSTALLDIR>\Server-Root\setup
  2. Run the DSConfig.bat to complete the configuration
  3. Give the required information in the panels
  4. To verify configuration, proceed to Starting and Stopping Directory Server.

Configuring Instant Messaging After a Configure Later Installation

The installation directory for Instant Messaging is <INSTALLDIR>\Instant Messaging. The following files are used to configure Instant Messaging:

When you select Configure Later option, these files are copied and the properties file are populated with the default values.

Note

Web Server Instance should be started before configuring Instant Messaging.

    To Configure Instant Messaging After a Configure Later Installation
  1. Change the command path to <INSTALLDIR>\Instant Messaging
  2. Run the IMConfig.bat to which will invoke Instant messaging configurator in GUI mode.
  3. Give the required information in the panels.
  4. To verify configuration, proceed to Starting and Stopping Instant Messaging.

Configuring Message Queue After a Configure Later Installation

The Message Queue component requires no additional configuration. It is configured as a part of the installation. It does not support Configure Later option. The following service entry is created: Message Queue Broker (MQ_broker). The installation directory for Message Queue is <INSTALLDIR>\MessageQueue.

Note

Although MQ does not support Configure Later installation mode, you can still install MQ in Configure Later mode. However you need to manually start the Message Queue Broker service from service panel in Configure Later mode.

To verify configuration, proceed to Starting and Stopping Message Queue.

Configuring Messaging Server After a Configure Later Installation

The installation directory for Messaging Server is <INSTALLDIR>\Server-Root. The following files are used to configure Messaging Server:

To configure the Messaging Server you need to specify the details of Directory Server. The details below is required if you choose to run the comm_dssetup.pl perl script while configuration. This Directory Preparation Script has to be run against the Directory server, if not already run, before configuring the Messaging Server.

    To Configure Messaging Server After a Configure Later Installation
Step 1: Running the Directory Preparation Script
  1. Configure Directory Server for communications services (Calendar Server, Messaging Server and the Delegated Administrator Utility) by running the Directory Preparation Script (comm_dssetup.pl).

    Note

    Skip this step if you have already run the Directory Preparation Script on the same Directory Server during configuration of another communications component.

    1. Verify that Directory Server is running. Refer to Starting and Stopping Directory Server if needed.
    2. On the machine where Directory Server is installed, you must run the Directory Preparation Script:

      3. perl comm_dssetup.pl

    3. In the command prompt change the path to <INSTALLDIR>\DSSetup
    4. Run the dssetup.bat to complete the configuration
Step 2: Configuring the Calendar Server
  1. Change the command path to <INSTALLDIR>\Server-Root\sbin
  2. Run the MSConfig.bat to complete the configuration.

    3. If there is a port conflict reported during configuration then change the port using the configutil command as below:

    • Change the current directory to <INSTALLDIR>\Server-Root\lib
    • Run the following command from cmd: configutil –o <service.servicename.nsmsgport> -v <new port number>
      <new port number> is the value of the new port number.
  3. To verify configuration, proceed to Starting and Stopping Messaging Server.

Configuring Portal Server After a Configure Later Installation

Final configuration steps for Portal Server differ depending on whether or not it is deployed in a Sun web container or a third party web container. The following file is used to configure Portal Server Core:

    To Configure Portal Server After a Configure Later Installation
  1. Change the command path to <INSTALLDIR>\PortalServer\config
  2. Run the PSConfig.bat which will invoke Portal Server configurator
  3. Give the required information
  4. To verify configuration, proceed to Starting and Stopping Portal Server.

Configuring Portal Server SRA After a Configure Later Installation

    To Configure Portal Server SRA After a Configure Later Installation
  1. Change the command path to <INSTALLDIR>\PortalServer\config
  2. Run the SRAConfig.bat which will invoke Portal Server SRA configurator.
  3. Give the required information.
  4. To verify configuration, proceed to Starting and Stopping Portal Server.
    To Configure Gateway After a Configure Later Installation
  1. Change the command path to <INSTALLDIR>\PortalServer\config
  2. Run the GWConfig.bat which will invoke Gateway configurator.
  3. Give the required information.
  4. To verify configuration, proceed to Starting and Stopping Portal Server.
    To Configure Netlet Proxy After a Configure Later Installation
  1. Change the command path to <INSTALLDIR>\PortalServer\config
  2. Run the NLPConfig.bat which will invoke Netlet Proxy configurator.
  3. Give the required information.
  4. To verify configuration, proceed to Starting and Stopping Portal Server
    To Configure Rewriter Proxy After a Configure Later Installation
  1. Change the command path to <INSTALLDIR>\PortalServer\config
  2. Run the RWPConfig.bat which will invoke Rewriter Proxy configurator.
  3. Give the required information.
  4. To verify configuration, proceed to Starting and Stopping Portal Server

Configuring Web Server After a Configure Later Installation

After a Configure Later installation, the components are installed and you are ready to configure Web Server. The installation directory for Web Server is <INSTALLDIR>\WebServer. The following files are used to configure Web Server:

config.jar

WSConfigurator.exe

WSprop.properties

    To Configure Web Server After a Configure Later Installation
  1. Manually populate the properties file of Web Server located at WebServer\Setup\WSprop.properties.
  2. Change the command path to <INSTALLDIR>\WebServer\Setup
  3. Run the WSConfig.bat to complete the configuration.
  4. To verify configuration, proceed to Starting and Stopping Web Server.

    Note

    Web Server cannot be installed and configured with folder names having space.

Next Steps

After you have completed the configuration tasks in this chapter, verify post installation configuration by following the component-specific procedures in Chapter 9, "Starting and Stopping Components".



Previous      Contents      Index      Next     

Part No: 819-1652-10.   Copyright 2005 Sun Microsystems, Inc. All rights reserved.