Printable Communications Suite 6 Update 1 Installation Guide

Contents

Sun Java Communications Suite 6 Update 1 Installation Guide

This document contains the following sections:

See also:

Sun Java Communications Suite 6 Update 1 Installation Overview

This document describes how to install specific Communications products on a specific machine (a machine can mean either a computer or a Solaris Zone). It is designed to be a low-level document describing the product installation tasks required for new deployments and upgrades. The following products are available in the installer:

Table 1. Communications Suite 6 Update 1 Products and Components

Product & Version
Convergence 1 Update 1
Messaging Server 7 Update 1 (32-bit/64-bit)
Calendar Server 6.3
Instant Messaging 8
Comms Delegated Administrator 6.4
Communications Express 6.3
Comms DSsetup 6.4
Messaging Server Sun Cluster HA Agent 7.0
Calendar Server Sun Cluster HA Agent
Instant Messaging Sun Cluster HA Agent

The Communications Suite installer does not install the Sun Java System Connector for Microsoft Outlook or Sun Java System Communications Sync, although it will be on the distribution.

This document assumes you have already made your architectural and design decisions: for example, which products you want to install, the number of machines in your deployment, and the number of front-end and back-end servers. If you are still in the planning or evaluating process, see the following documents:

  • You also can use the Communications Suite 6 Update 1 Installation Flowchart to guide you to specific installation scenarios. The flowchart can help in the following ways:
    • Provides a decision tree for installing Communications Suite products and the Sun Java System products that support Communications Suite
    • Directs you to specific sets of installation instructions based on your decisions

The remainder of this document describes the steps for product installation, as follows:

  1. Check that your system requirements (platform and operating system) support Communications Suite.
  2. Install the required Sun Java System Software.
  3. Define and set up additional requirements for individual Communications Suite products.
  4. Install Communications Suite products one at a time on specific machines in a given sequence.
  5. Run the Comm Directory Setup script.
  6. Gather information required to configure the Communications Suite products.
  7. Perform initial configuration on each product.

1. Check That Your Platform and Operating System Support Communications Suite.

The Sun Java Communications Suite 6 Update 1 runs on SPARC or x86 hardware running Solaris 9 or 10, or Red Hat Linux 3 or 4. The recommended platform is at least Solaris 10 08/07.

For details, see this list of operating system and platform requirements.

In addition, certain Communications Suite products have minimum disk and memory requirements. For details, refer to Memory and Disk Space Requirements for Communications Suite 6 Update 1.

2. Install the Sun Java System Software Required to Run Communications Suite.

The Communications Suite products require other Sun Java System software products to be installed before you install Communications Suite. The dependencies vary among the Communications products, but many have a common set.

Which Products Do You Need?

  • Sun Java System Directory Server Enterprise Edition 5.x or 6.x (6.3 or later is recommended)
  • Web container:
    • Sun Java System Web Server 7.0
    • Sun Java System Application Server 9.1 Update 2

      Download the following version: Application Server 9.1 Update 2 with High Availability Database (HADB) - Zip/File Based. This version provides shared components needed by Application Server and Communications Suite. Note: You can configure this version of Application Server without using the HADB.
  • Sun Java System Access Manager

    Access Manager (AM) is required for Delegated Administrator and optional for Convergence, to support AM authentication and/or AM SSO.

The following table shows the software required by each product.

Table 2. Software Requirements for Communications Suite 6 Update 1 Products

Communications Suite Product Directory Server Web Container Access Manager
Convergence Yes App Svr 9.1 U2 only Optional. Required only if you want to use Access Manager for authentication and/or SSO.
Messaging Server Yes No Optional
Calendar Server Yes No Optional
Instant Messaging Yes 1 Optional
Delegated Administrator Yes 1 Yes
Communications Express Yes 1 Yes if want use Schema 2. Optional for Schema 1.

1 - Web Server 7.0 update 1, Application Server 8.2P2, or Application Server 9.1 Update 2 (recommended)

For more information about software product dependencies, see Product Version Compatibility.

For products needed to deploy Convergence, see the Product Version Compatibility Requirements for Convergence 1 Update 1.

  • Note: The Communications Suite installer does install Message Queue 4.1, Security NSS, and other shared components.

Where Do You Go to Install the Sun Java System Products?

The Communications Suite installer does not install these software products. To install these products, perform the following steps:

  1. Download the software.

    For links to download sites, go to Get the Software.

  2. Install Application Server 9.1 Update 2 with High Availability Database (HADB) - Zip/File Based.

    This version provides shared components needed by Application Server and Communications Suite. Note: You can configure this version of Application Server without using the HADB.

    Download the Application Server software zip file from the Communications Suite download site. Do not install the version of Application Server bundled with JES 5 Update 1. That is an older version of Application Server.

    If you are installing the software from the Communications Suite DVD, do not use the Application Server bundled on the DVD. Go to the Communications Suite download site to obtain the correct version of Application Server. (For a link to the site, see Get the Software.)

    To obtain a multi-language version of Application Server, go to the Application Server download site. (The Communications Suite download site does not provide a multi-language version.)



    Follow the instructions in the Sun Java System Application Server 9.1 Update 2 Installation Guide. Install Application Server before you install the other Sun Java System products.

    To verify which version of Application Server you have installed, see Verify Application Server Version.

  3. Install Directory Server 6.3 or later.

    Download Directory Server Enterprise Edition 6.3 (or later) from the Communications Suite download site before you run the JES 5 Update 1 installer. Do not install the Directory Server software bundled with JES 5 Update 1. That is an older version of Directory Server.

    If you already started with an older DSEE version, you can still upgrade to the recommended DSEE 6.3. You must apply an upgrade patch as well as other patches to upgrade to DSEE 6.3.

    For example, if you obtained the native package format of DSEE on the Solaris 10 x86 or SPARC platform, you must start by installing the DSEE 6.2 version bundled with JES 5 Update 1, then upgrade to DSEE 6.3.

    The simplest approach is to download and install the zip file version of DSEE 6.3 directly from the Communications Suite download site.


    To install Directory Server, follow the instructions in the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

  4. Install the following products by running the JES 5 Update 1 installer:
    Access Manager 7.1
    Web Server 7.0

To install Access Manager and Web Server, follow the instructions in the Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

Here are some other information sources and methods for installing these products:

If you are installing Access Manager 7.1 on a Linux system, you should verify that a compatible version of Java Development Kit (JDK) is installed. For details, see Verifying the Correct JDK Version to Support Access Manager.
If you install Delegated Administrator, do not deploy Access Manager as a single WAR file. This installation method does not support Access Manager Legacy mode, which is required by Delegated Administrator. Instead, install Access Manager with the JES 5 Update 1 Installer.

3. Define and Set Up Additional Requirements for Individual Communications Suite Products.

In addition to the generic suite requirements, some products might have specific requirements. For details about individual product requirements, see the Communications Suite 6 Update 1 Release Notes.

Messaging Server

  • You must ensure DNS is running and configured properly. For details, see DNS configuration.
  • Recommended file systems for the message store are listed in Message Store File Systems.
  • Make sure you do not configure conflicting port numbers on a machine when various components are running on a single machine. For a list of port numbers used by Messaging Server, see Default Port Numbers.

Calendar Server

4. Install Communications Suite 6 Update 1 Products.

After the platform and software requirements have been met (as described previously), take these steps:

  1. Download the software.

    To download Communications Suite, including the installer, go to Get the Software.

  2. Run the installer.

    The installer is a single unified utility called commpkg. It installs (but does not configure) the Communications Suite products. commpkg does all the necessary preparation work before installing the product software on the system. Run this command:

./commpkg install

For step-by-step instructions, see To Run the Communications Suite Installer.

For details about other features of the commpkg installer, see these articles:

Note: To install the localization version of Communications Express, you must install a localization patch. For details, see Installing the Localization Version of Communications Express.

Sample Sessions: Running commpkg

The following examples document the output of running commpkg:

5. Prepare Directory Server for Communications Suite (run comm_dssetup.pl).

All Communications Suite components require that you run the comm_dssetup.pl script against Directory Server. For example:

# cd INSTALLROOT/dssetup/sbin
# ./comm_dssetup.pl

For detailed instructions, see the following:

Note. If you install or upgrade Directory Server before you run the Communications Suite installer, the Directory Server installation process places an outdated version of comm_dssetup.pl on your system. You must use the current version of comm_dssetup.pl provided by the Communications Suite installer. However, the Comms Suite installer cannot install a new version with the commpkg install command. Instead, run the commpkg upgrade command to upgrade to the latest version of comm_dssetup.pl. If you install comm_dssetup.pl with the Comms Suite installer before you install Directory Server, you will have the up-to-date version. The DS installation process does not overwrite the latest version.

6. Gather Information Needed to Configure Communications Suite Products.

Before you run a configuration program, you need to gather specific configuration information for each product. Use the following worksheets:

7. Create Initial Configurations for the Individual Communications Suite Products.

For each Communications Suite product, you must run a separate configuration program. Each configuration program creates an initial runtime configuration to make the product operational. The program provides a generic, functional server configuration, which you can refine by making specific configurations and customizations.

You will typically want to configure the back-end servers before configuring clients. Client configurations require certain server attributes to be defined.

Delegated Administrator 6.4:

Run the initial configuration program:

# INSTALLROOT/da/sbin/config-commda

For detailed instructions, see Delegated Administrator 6.4: Initial Configuration.

Messaging Server 7 Update 1:

Run the initial configuration program:

For 32-bit: # INSTALLROOT/messaging/sbin/configure

For 64-bit: # INSTALLROOT/messaging64/sbin/configure

For detailed instructions, see Messaging Server 7 Update 1: Initial Configuration.

Calendar Server 6.3:

Run the initial configuration program:

For Solaris: # INSTALLROOT/calendar/SUNWics5/cal/sbin/csconfigurator.sh

For Linux: # INSTALLROOT/calendar/calendar/sbin/csconfigurator.sh

For detailed instructions, see Calendar Server 6.3: Initial Configuration.

Instant Messaging 8:

Run the initial configuration program:

# INSTALLROOT/im/sbin/configure

For detailed instructions, see Instant Messaging 8: Initial Configuration.

Convergence 1 Update 1:

Run the initial configuration program:

# INSTALLROOT/iwc/sbin/init-config

For detailed instructions, see Convergence 1 Update 1: Initial Configuration.

Communications Express 6.3:

Run the initial configuration program:

# INSTALLROOT/ce/sbin/config-uwc

For detailed instructions, see Communications Express 6.3: Initial Configuration.

Messaging Server Sun Cluster HA Agent 7.0:

Run the initial configuration program:

# <msg_scha_base>/bin/init-config

This command registers the HA agent with the Sun Cluster HA software. Note that you must have the Sun Cluster HA software installed prior to issuing this command.

For more information about configuring the Messaging Server Sun Cluster HA agent, see Configuring Messaging Server for High Availability.

Calendar Server Sun Cluster HA Agent:

Run the initial configuration program:

# <cs_scha_base>/bin/init-config

This command registers the HA agent with the Sun Cluster HA software. Note that you must have the Sun Cluster HA software installed prior to issuing this command.

For more information about configuring the Calendar Server Sun Cluster HA agent, see Configuring Calendar Server Software for High Availability (Failover Service).

Instant Messaging Sun Cluster HA Agent:

Run the initial configuration program:

# <im_scha_base>/bin/init-config

This command registers the HA agent with the Sun Cluster HA software. Note that you must have the Sun Cluster HA software installed prior to issuing this command.

For more information about configuring the Instant Messaging Sun Cluster HA agent, see Configuring Instant Messaging for High Availability.

Uninstalling Communications Suite

To uninstall the Communications Suite products installed on the local machine, run the following command:

# cd INSTALLROOT/CommsInstaller/bin
# ./commpkg uninstall

For detailed instructions, see the following:

Deployment Examples: Installation

The following deployment examples show how to install Communications Suite 6 Update 1 in different scenarios. The examples provide step-by-step records of running the installers and configuration programs.

Getting Information About Which Products Are Installed

To determine the Communications Suite software components installed on the machine, run the following command:

./commpkg info --verbose

This command prints product information installed in the INSTALLROOTS. To print information about one product, run this command:

./commpkg info --verbose installroot|product name.

For details about the commpkg info command, see the following:

To determine which version of Application Server you have installed, see Verify Application Server Version.

Additional Communications Suite 6 Update 1 Installation Information

The following information is what is linked to in the main body of this Installation Guide. The information is organized alphabetically by title.

Calendar Server Pre-Installation Planning

This article describes considerations you need to think about before installing Calendar Server. It contains the following sections:

Planning for Calendar Server Administrators

Administrators for Calendar Server include:

Calendar Server Administrator (calmaster)

The Calendar Server administrator is a specific user name with its associated password that can manage Calendar Server. For example, a Calendar Server administrator can start and stop Calendar Server services, add and delete users, create and delete calendars, and so on. This user has administrator privileges for Calendar Server but not necessarily for the directory server.

The default user ID for the Calendar Server administrator is calmaster, but you can specify a different user during Calendar Server configuration, if you prefer. After installation you can also specify a different user in the service.admin.calmaster.userid parameter in the ics.conf file.

The user ID you specify for the Calendar Server administrator must be a valid user account in your directory server. If the Calendar Server administrator user account does not exist in the directory server during configuration, the configuration program can create it for you.

See the Sun Java System Calendar Server 6.3 Administration Guide for the complete list of Calendar Server administrator configuration parameters in the ics.conf file.

Top

Calendar Server User and Group

On Solaris systems, these special accounts are the user ID and group ID under which Calendar Server runs. Use the default values, icsuser and icsgroup, which are automatically created by the configuration program, if they do not exist. If you prefer, however, you can specify values other thanicsuser and icsgroup when you run the Calendar Server configuration program. These values are stored in the local.serveruid and local.servergid parameters, respectively, in the ics.conf file.

Top

Superuser (root)

On machines running Solaris software, you must log in as or become superuser (root) to install Calendar Server. You can also run as superuser to manage Calendar Server using the command-line utilities. For some tasks, however, you should run as icsuser and icsgroup (or the values you have selected) rather than superuser to avoid access problems for Calendar Server files.

Top

Planning for Calendar Server Hosted Domains

Calendar Server supports hosted (or virtual) domains. In a hosted domain installation, each domain shares the same instance of Calendar Server, which enables multiple domains to exist on a single server. Each domain defines a name space within which all users, groups, and resources are unique. Each domain also has a set of attributes and preferences that you specifically set.

To configure hosted domains on a server, you should make these deployment choices:

  • Use Schema 2 only.
  • Install and configure Directory Server.
  • Install and configure a web container:  Application Server or Web Server.
  • Install and configure Access Manager.
  • Install and configure Delegated Administrator as part of the Communications Suite. Use the compkg installer to install Delegated Administrator, Calendar Server, and any other Communications Suite components you require.

For instructions on installing and configuring the components listed above, see the related articles in the Installation Guide.

Next, take the following configuration steps:

Top

Communications Suite Installer: General Syntax and Commands

The Communications Suite installer, commpkg, comprises several commands (verbs) that enable you to install, uninstall, and upgrade Communications Suite products and shared components.

Communications Suite Installer: Syntax

The following syntax applies to the Communications Suite installer in general:

commpkg [general options] verb [verb-specific options]
Communications Suite Installer: General Options

The general options for the installer are:

Option Description
-? or --help Displays Help
-V or --version Displays Version of Communications Suite components
--OSversionOverride Overrides the operating-system version check.
--fixEntsys [y|n] Fix an invalid Sun Java Enterprise System (Java ES) entsys symlink, making the link point to the latest Java version upgraded by commpkg. The Java ES symlink is located in /usr/jdk/entsys-j2se. Choose --fixEntsys y to fix the Java ES symlink to the Java files.
If you do not specify this switch, commpkg prompts you if the symlink is invalid. However, in silent mode, the default is not to fix the symlink (the equivalent of using a value of n). To fix the symlink in silent mode, enter commpkg install --fixEntsys y --silent INPUTFILE on the command-line.
NOTE: This feature was not available in the original (RR) version of commpkg.
Communications Suite Installer: Verbs

The verb is one of the following:

Verb Description
install Performs Communications Suite installation
uninstall Performs Communications Suite uninstallation
info Displays Communications Suite information
upgrade Performs Communications Suite upgrade

Communications Suite Installer: Commands

For information about the commpkg commands (verbs) and their options, see

commpkg info Usage

The commpkg info command obtains information about

  • The paths (installroots) where Communication Suite products are installed
  • The products that are installed in those paths

You can also use the command to repair the software list by adding known installroots and deleting bogus installroots in the software list. It is one of the commands available with the Communications Suite installer, commpkg.

Communications Suite Installer Verbs

This section lists the commands available with the Communications Suite installer.

Command Description
commpkg install Performs Communications Suite installation
commpkg uninstall Performs Communications Suite uninstallation
commpkg info Displays Communications Suite information
commpkg upgrade Performs Communications Suite upgrade

For information about the other commpkg commands and their options, see

commpkg info Syntax

commpkg info [options] [installroot|name]

The installroot|name specifies an installroot or name from the software list. The name is a friendly, shorthand name in the software list that indicates the installroot to use. If you enter a name that does not exist in the software list, an error results. If no installroot or name is specified, the commpkg info command prints information on all the installroots listed in the software list.

If installroot is specified and does not exist in the software list, and is a valid alternate root, the commpkg info command adds the installroot to the software list.

To specify the default root, use "/" or "". The friendly name for the default root is "".

commpkg info Options

The following options are used by the commpkg info command:

commpkg install options Description
-? or --help Displays Help
-V or --version Displays Version of Communications Suite components
--clean Removes entries in the software list when the corresponding products are not actually installed.
If installroot|name is specified, this option checks if the product really exists and removes the entry from the softlist if the product does not exist.
If no installroot|name is specified, the option checks all the entries in the softlist for existence and removes entries for products that do not exist.
To add a particular installroot to the software list, just specify it without the --clean option.
--listPackages Lists the packages that make up each Communications Suite product, shared component, and OS Auxiliary product. This option also displays the mnemonic for each Communications Suite product or component such as comm_dssetup.pl.

Commpkg Install Usage

The commpkg install command enables you to install the Communications Suite products and shared components. It is one of the commands available with the Communications Suite installer, commpkg.

This command lays down the Communications Suite components' installation bits on your machine, but it does not configure these components. To configure the components after installation, see Initial Configuration.

For information about the commpkg general syntax and options, see:

For information about the other commpkg commands and their options, see:

Tip
Installing Only Shared Components: To install just the shared components for a component product, launch the Communications Suite installer then prefix your product selection with a tilde (~). For example, to install only the shared components for Messaging Server 32-bit, at the Product Selection prompt, you would type ~1. You can type multiple selections, using a comma to separate your entries.

Commpkg Install Command: Syntax

commpkg install [options] [installroot|name]

Using the installroot|name Command-Line Argument

If you specify installroot|name on the command line, it is equivalent to specifying the --altroot and --installroot options. That is, the command-line argument implies an altroot installation. For example, specifying 

commpkg install /opt/sun/comms2

is equivalent to specifying

    --altroot --installroot /opt/sun/comms2

For details about these options, see Commpkg Install Command: Options, below.

Specifying an installroot of / is same as specifying the default root. It is the same as using neither
the --installroot nor the --altroot option, or of not specifying the installaroot|name command-line argument at all.

If you specify the --installroot option in addition to the installroot|name command-line argument, they must match.

Using the name Argument (Instead of installroot)

If you specify the name command-line argument and it exist in the software list, the the corresponding installroot is used and --altroot is implied.

If you also specify the --installroot option, it must correspond to the entry in the software list. If you specify name and it does not exist in the software list, it will be added to the software list.

Specifying any name other than "" implies an --altroot. A value for name of "" is reserved for the default root. Therefore, "" cannot be used with --altroot.

Commpkg Install Command: Options

The following options are used by the commpkg install command:

commpkg install options Description
--help or -? prints help information
--version or -V prints version information
--excludeOS Do not apply Operating System patches during product installation
--excludeSC Do not install, upgrade, or patch any Shared Components
--acceptLicense Accept the license conditions in the LICENSE.txt file
--altroot [name] Specify an alternate root directory during a multi-host installation. The INSTALLROOT (the top level installation directory for all products and shared components) will be the alternate root.

If you specify a name, it will be a friendly name associated with the altroot that will be registered in the software list. The name option is supported on Solaris only (not on Linux).

You can use this option to install multiple instances of Communications Suite products on the same host or Solaris zone. You use this option to perform a side-by-side upgrade of Communications Suite products.
--distro path Specify the path to packages/patches for the products

Default: Location of commpkg script
--installroot path Specify the path of INSTALLROOT, the top level installation directory for Communications Suite products and shared components.

Default INSTALLROOT on Solaris and Linux: opt/sun/comms

The subdirectories for individual Communications Suite products are installed under the INSTALLROOT. For example, Messaging Server (32-bit) software is installed by default in opt/sun/comms/messaging.
--silent INPUTFILE Run silent installation, taking the inputs from the INPUTFILE and the command line arguments. The command line arguments override entries in the INPUTFILE. Installation proceeds without interactive prompts.

Use --dryrun to test silent installation without actually installing the software.

When running a silent installation, you must use the --acceptLicense option in the command line or set ACCEPTLICENSE=YES in the INPUTFILE.

Specify NONE for INPUTFILE if you want to run in silent mode without using an input file. When you specify NONE, the installation uses default values.

For more information about running a silent installation, see Installing Communications Suite in Silent Mode.
--dry-run or -n Does not install Communications Suite components. Performs checks.
--upgradeSC [y|n] Indicate whether or not to upgrade shared components as required.

Note: If this option is not specified, you will be prompted for each shared component that needs to be upgraded.

Default: n
Caution

Upgrading shared components is irreversible. However, if you do not upgrade required shared components, products might not work as designed.


The --excludeSC flag has precedence over this flag.
--auditDistro Audit the installation distribution to verify that the required patches and packages are present and that the packages have the correct versions. Compares the installed distribution to the product files internal to commpkg.
--pkgOverwrite Overwrite the existing installation package. You might use this option when you are installing a shared component in a global zone where either the shared component does not exist in a global zone, or the shared component exists in the whole root zone. The default is not to override the existing package. In general, shared components should be managed in the global zone.
--components <comp1 comp2 ...> A space delimited set of component products. Each product has mnemonic associated with it. Use commpkg info --listPackages to see the mnemonic for a product. Do note that in most shells you will need to escape the space between each mnemonic. E.g. by adding double quotes around all the components.

Commpkg Uninstall Usage

The commpkg uninstall command enables you to uninstall the Communications Suite products and shared components. It is one of the commands available with the Communications Suite installer, commpkg.

For information about the commpkg general syntax and options, see

For information about the other commpkg commands and their options, see

Uninstalling Communications Suite Components

To uninstall one or more Communications Suite component, go to the INSTALLROOT/CommsInstaller/bin/ directory and run commpkg uninstall.

This command uninstalls the same products that commpkg install installs. However, it does not remove OS patches installed by commpkg install. In addition, it does not remove Shared Components.

Note

A fast way to uninstall a Communications Suite component in an alternate root is to simply remove the entire alternate root.

Commpkg Uninstall Command: Syntax

commpkg uninstall [options] [installroot|name]

If you specify installroot|name on the command line, it is equivalent to specifying the --rootdir option with either the specified installroot or the installroot corresponding
to name in the software list. That is, the value must be consistent.

If you specify name, it must exist in the software list. Otherwise, an error is returned immediately. The name is looked up in the software list and is used for the installroot.

Commpkg Uninstall Command: Options

The following options are used by the commpkg uninstall command:

commpkg uninstall options Description
--silent INPUTFILE Run the uninstaller silently, taking the inputs from the INPUTFILE and the command line arguments. The command line arguments override entries in the INPUTFILE. Uninstallation proceeds without interactive prompts.

Use --dry-run to test silent uninstallation.
--dry-run or -n Does not uninstall the Communications Suite components. Performs checks. Silent uninstallation INPUTFILE is created in /tmp.
--rootdir path This option is deprecated in favor of using the installroot or name command-line argument.
This option specifies the path of rootdir, the alternate root used for multi-installation. Supported on Solaris only.
Unable to render {include} Couldn't find a page to include called: Communications Suite Directory Server Setup Script (commdssetup)

Calendar Server Configuration Script Worksheet

Print and fill out this worksheet to use when responding to the Calendar Server csconfigurator.sh script configuration options.

Option Default Value Fill in Your Site's Value (to Respond to the Script)
LDAP Server Host Name FQDN of your host  
LDAP Server Port 389  
Directory Manager DN cn=Directory Manager  
Directory Manager Password –  
Enable Virtual Domains support Checked  
Virtual Domains setting: Default domain your domain  
Calendar Administrator Username calmaster  
Calendar Administrator Password –  
Calendar Administrator Email address calmaster@your domain  
Site administrator Yes  
Set up a Front End/Back End deployment Unchecked  
Email Alarms Enabled  
Administrator Email Address calmaster@your domain  
SMTP Host Name your domain  
Service Port 80  
Maximum Sessions 5000  
Maximum Threads 20  
Number of server processes 4  
Runtime User ID icsuser  
Runtime Group ID icsgroup  
Start Calendar Server after Successful Configuration Unchecked  
Start Calendar Serve on System Startup Checked  
Configuration Directory /etc/opt/calendar/SUNWics5/config  
Database Directory /var/opt/calendar/SUNWics5/csdb  
Attachment Store Directory /var/opt/calendar/SUNWics5/astore  
Logs Directory /var/opt/calendar/SUNWics5/logs  
Temporary Files Directory /var/opt/calendar/SUNWics5/tmp  
Enable Archive Checked  
Archive Directory /var/opt/calendar/SUNWics5/csdb/archive  
Enable Hot Backup Checked  
Hot Backup Directory /var/opt/calendar/SUNWics5/csdb/hotbackup  
Keep archives for (in days) Minimum: 3, Maximum: 6  
Keep hot backups for (in days) Minimum: 3, Maximum: 6  
Same as archive checkbox Checked  
Note

Do not change the location or names of the logs and temporary files directories.

config-uwc Script Worksheet

Print and fill out this worksheet to use when responding to the config-uwc script configuration options. You use config-uwc to configure Communications Express.

Option Default Value Fill in Your Site's Value (to Respond to the Script)
Directory to store configuration and data files uwc-deployed-dir i,e /var/opt/sun/comms/ce  
Hostname your hostname  
DNS Domain your DNS domain  
Web Container your web container  
Application Server Installation Directory /opt/SUNWappserver  
Application Server Domain Directory /opt/SUNWappserver/domains/domain1  
Application Server Document Root Directory /opt/SUNWappserver/domains/domain1/docroot  
Server Target Name server  
Virtual Server Identifier server  
HTTP Port 80  
Administration Server Port 8800  
Administrator User ID admin  
Administrator Password –  
Secure Administration Server Instance Unchecked  
Web Container User ID your web container user ID  
Web Container Group IP your web container group ID  
URI Path /uwc  
Enable Hosted Domain Support Checked  
URL of Directory Server ldap://your host:389/  
Bind DN cn=Directory Manager  
Password –  
DC Tree suffix your suffix  
Default Domain your domain  
Enable Access Manager for Single Sign-On Unchecked  
Webmail Server Host Name _FQDN of your host  
Webmail Server Port Number 8990  
Enable login in secure mode Unchecked  
Webmail Server SSL Port Number 8991  
Webmail Admin User ID –  
Admin Password –  
Calendar Server Hostname FQDN of your host  
Calendar Server Port 9004  
Calendar Admin User ID calmaster  
Calendar Administrator User Password –  
URL of PAB Directory Server ldap://FQDN of your host:389/  
Bind As cn=Directory Manager  
Password –  

Sun Convergence Configuration Worksheets

Before you configure Convergence, you should gather configuration information.

Worksheet 1-1 lists the configuration options required for Convergence.

Worksheet 1-2 lists the configuration options required by Convergence to be deployed to Sun Java TM System Application Server 9.1 Update 2.

Print and fill out these worksheets to use when responding to the Convergence init-config script configuration options.

Worksheet 1-1. Convergence: Configuration Options
Option Description and Default Value Fill in Your Site's Value (to Respond to the Script)
Configuration Directory Directory to store configuration and data files. Default directory (on Solaris and Linux): /var/opt/sun/comms/iwc. This directory should be different than the iwc-base directory. (On Solaris and Linux, this is /opt/sun/comms/iwc by default).  
Convergence server host name Host name of the machine where the Convergence software is installed. For example: mymachine.  
DNS domain name The DNS domain for the host machine where the Convergence software is installed. For example: siroe.com.  
Convergence URL URL where Convergence will be deployed. Enter the portion of the URI following the host name:port number For example: /iwc.  
Hosted domain support? Select this option only if you have configured hosted domain support for Calendar Server.  
User/Group LDAP URL Enter the Directory Server host and port where the User/Group is located. The URL should be in the format: ldap://LDAP host name with FQDN:LDAP port number. For example: ldap://siroe.com:389  
Bind DN Enter the LDAP DN to be used to bind to the Directory Server managing the User/Group data. This is the User/Group Directory Manager. For example: "cn=Directory Manager".  
Bind password Password for the Bind DN. Use the password defined in Directory Server for the Bind DN.  
DC Tree suffix For Schema 1 configurations, this option specifies the base distinguished name (DN) of the DC Tree root suffix. For Schema 2 configurations, this option specifies the base DN of the root suffix under which the User/Group tree is located. You must enter a value for this option whether you are using Schema 1 or Schema 2. For example: o=isp  
Default domain name When a user logs in to Convergence without including a mail domain component in the user name, this domain is used by default to supply the fully qualified domain name. For example: sesta.com. In this example, if a user logs in as fred, the user name is qualified as fred@sesta.com.  
Webmail host name Host name where Messaging Server is installed. For example: ms.sesta.com.  
Webmail port number Messaging Server HTTP (mshttpd) port number. For example, the default is: 8990.  
Webmail SSL port number Messaging Server SSL port number. Only needed if you enable login in secure mode.  
Webmail Admin user ID and password Messaging Server administrator user ID and password. For example: admin.  
Calendar Server host name Host name where Calendar Server is installed. For example: cs.siroe.com.  
Calendar Server port number Calendar Server HTTP port number. For example: 8004. Default: 80.  
Calendar Server SSL port number Calendar Server SSL port number. Only needed if you enable login in secure mode.  
Calendar Server Admin user ID and password Calendar Server administrator user ID and password. For example: calmaster.  
IM domain name Domain name of the Instant Messaging Server. For example varrius.com.
IM host name Host name where Instant Messaging is installed. For example: im.varrius.com.  
IM port number Instant Messaging HTTP port number. For example: 5269. Default: 5269.  
IM Httpbind Component JID Instant Messaging Server httpbind component jid. For example: httpbind.varrius.com.  
IM Httpbind Component password Instant Messaging Server httpbind component password.  
IM Avatar Component JID Instant Messaging Server avatar component jid. For example: avatar.varrius.com.  
IM Avatar Component password Instant Messaging Server avatar component password.  
Convergence administrator username Administrator username. For example admin.  
Convergence administrator password Administrator password.  
Worksheet 1-2. Sun Java System Application Server 9.1 Update 2 Configuration Options

These are the Application Server-specific options you are asked to enter when you run the Convergence init-config script.

Option Description Fill in Your Site's Value (to Respond to the Script)
Application Server 9.1 installation directory Directory where Application Server is installed. By default, this directory is /opt/SUNWappserver.  
Application Server 9.1 domain directory By default, this directory is /opt/SUNWappserver/domains/domain1.  
Application Server 9.1 document root directory By default, this directory is /opt/SUNWappserver/domains/domain1/docroot  
Application Server 9.1 target name Name of the instance. For example: server.  
Virtual server identifier Name of the Application Server 9.1 virtual server identifier. For example: server.  
Application Server 9.1 server instance HTTP port number HTTP port number for the Application Server server instance (target). Default port number: 8080.  
Administration Server port number Port number for the Administration Server instance for Application Server 9.1. For example: 4848.  
Administrator Server user ID and password. User ID and password for the Administration Server administrator. User ID example: admin  
Secure Administration Server Instance You will need to specify whether the HTTP access to the Administration Server instance is secure (HTTPS) or not (HTTP).
By default, the Secure Administration Server Instance box shown in the Convergence init-config program is checked. If your access is not secure, uncheck the box. 		 
Unable to render {include} Couldn't find a page to include called: Configuration Worksheets - Delegated+Administrator

Configuration Worksheets - Instant Messaging

You should gather this information before you begin. You will be prompted for some or all of the information depending on the components you installed.

Print out the following worksheet and write the values for your deployment in the space provided. You can reuse this checklist for multiple installations of Instant Messaging. This table contains passwords and other sensitive information, so you should store this information in a safe place.

(Solaris Only) If you will be configuring High Availability service for Instant Messaging, see Instant Messaging HA Overview for specific information about values you can use for these parameters and additional parameters for your checklist.

Configuration Parameters for Instant Messaging
Parameter Description Your Value
Installation Directory im-svr-base

Directory in which Instant Messaging is installed. By default, Instant Messaging is installed into the /opt directory as follows:

Solaris and Linux: /opt/sun/comms/im

(Solaris Only) If you will be configuring High Availability service for Instant Messaging, see Selecting the Installation Directory (im-svr-base) for information about choosing an installation directory.
Instant Messaging Server Domain Name Domain name for the users being served by this server.

Default: None		  
Multiplexor Port Number

(Multiplexor Configuration Only)		 The port number on which the Instant Messaging Server listens for incoming requests from Instant Messenger clients.

Default: 5222		  
Multiplexed XMPP Port Port on which the server listens for multiplexor connections
Default: 45222
Disable Server Select this option if the instance you installed will act as a multiplexor and not a server. If you select this option, you must provide a value for Remote Instant Messaging Server Host Name.  
Remote Instant Messaging Server Host Name

(Multiplexor Configuration Only)		 The host name of the Instant Messaging Server for which this multiplexor routes messages. If the multiplexor and server are installed on the same host, use localhost. (Solaris Only) If you will be configuring High Availability service for Instant Messaging, use the logical host's name.

Dependencies: The Disable Server parameter must be selected, that is, server functionality is disabled.		  
Enable Email Integration, Enable Email Archiving

(Optional)		 If selected, enables Instant Messaging email archiving. Sun Java System Portal Server search-based archiving for Instant Messaging.

Dependencies: SMTP Server such as Sun Java System Messaging Server

Alternatively, you can manually enable Sun Java System Portal Server search-based archiving for Instant Messaging.

Dependencies: Sun Java System Portal Server and Sun Java System Access Manager.		  
LDAP Host Name In a deployment with an LDAP server, the host name of the LDAP server that contains user and group information for Instant Messaging. For example, directory.siroe.com.

Dependencies: LDAP server such as Sun Java System Directory Server.		  
LDAP Port Number In a deployment with an LDAP server, the port number on which the directory server listens for incoming requests. For example, 389

Dependencies: LDAP server such as Sun Java System Directory Server.		  
Bind DN In a deployment with Sun Java System Access Manager, during installation, you must provide the Directory Manager Bind DN and password. This Bind DN is used to update the directory schema with the Instant Messaging and presence service templates and attributes only. This requires Directory Manager access. The Directory Manager Bind DN and password are not saved or used beyond installation and initial configuration.

In a deployment with an LDAP server but without Access Manager, Instant Messaging uses this Bind DN to search users and groups in the directory. Leave this blank if the directory can be searched anonymously. You can change the bind credentials later if required as described in To Configure Bind Credentials for the Instant Messaging Server.

Dependencies: LDAP server such as Sun Java System Directory Server.		  
Bind Password In a deployment with an LDAP server, the Bind DN password.  
SMTP Server Host Name

(Optional)		 The host name of the SMTP server used to send email notification of messages to offline users. For example, mail.siroe.com. If the SMTP server does not use port 25, specify the port along with the host name. For example, if the SMTP server uses port 1025:

mail.siroe.com:1025

Dependencies: SMTP server such as Sun Java System Messaging Server.		  
Database, Logs, and Runtime Files Pathname The location where the runtime files, database, and logs are stored. Also referred to as im-runtime-base. Runtime files are read, created, and modified by the server during its normal operations. Some examples include log files, and persistent state information tied to client actions such as alert messages, roster information, conferences, news channels, and so on.

If you are configuring High Availability (HA) for Instant Messaging, this path must be globally available. See Chapter 4, Configuring Instant Messaging for High Availability (Solaris Only) for more information about HA.

The configure utility appends a directory (/default) to the path you provide for the runtime files. The name of this directory is the instance to which the runtime files apply. Later, you can create multiple instances of Instant Messaging by creating additional instance directories with different names (for example /secure) and copying over files from the /default instance runtime directory. See Creating Multiple Instances from a Single Instant Messaging Installation for specific instructions.

If you accept the following defaults when you run configure:

Solaris and Linux: /var/opt/sun/comms/im/

The configure utility creates the following directories for the runtime files:

Solaris and Linux: /var/opt/sun/comms/im/default

In addition, the following two subdirectories are created under the runtime directory.

The database directory (im-db-base) defaults are as follows:

Solaris and Linux: /var/opt/sun/comms/im/default/db

The log directory defaults are as follows:

Solaris and Linux: /var/opt/sun/comms/im/default/log
Resources, Help Files, and HTTP Gateway Pathname Resource Directory.

The directory in which the resource files, online help, and the XMPP/HTTP Gateway are installed.

If you want to customize the resource files for your deployment, you should run configure utility, customize the files, then redeploy the resource files. You need to run configure first because the configure utility creates some of the index and .jnlp files that you can customize. See Redeploying Resource Files for information.
Default: im-svr-base/html		  
XMPP/HTTP Gateway Deployment Determines whether or not the XMPP/HTTP gateway will be deployed. If you choose to deploy the gateway, the configure utility creates a default gateway configuration file (httpbind.conf) in the default Instant Messaging server instance's im-cfg-base directory if one does not already exist. If httpbind.conf already exists, the configure utility does not alter or overwrite the file.
Default:

True (gateway is deployed)

Note: If you are configuring the Instant Messaging Server to support Convergence, do not enable the XMPP/HTTP Gateway Deployment here. Set this value to false. The XMPP/HTTP Gateway is deployed through the Convergence server; its value is set when you configure Convergence.
  
XMPP/HTTP Gateway URI Defines the URI for the HTTP component of the XMPP/HTTP gateway.
Default:

http://web-svr-host:80/httpbind		  
Codebase The URL from which Instant Messenger accesses resources, including the start page for initial downloads of the Instant Messaging client.

The installation program installs the resource files into the following locations:

Solaris and Linux: //opt/sun/comms/im/html

The configure utility uses the codebase to determine which web container instance to use. If it succeeds, the configure utility deploys the Instant Messenger resources as a web application in the web container, according to the URL provided. If no supported web container is detected, you will be prompted for a file system location in which to copy or link the resources.

See your web container documentation for more information about deploying resource files as a web application. See Changing the Codebase if you need to modify the location of the resource files after initial configuration.		  

Messaging Server configure Script Worksheet

Print and fill out this worksheet to use when responding to the Messaging Server configure script configuration options.

Option Default Value Fill in Your Site's Value (to Respond to the Script)
Fully Qualified Host Name (FQHN) your host.your domain For example: myhost.west.sesta.com  
Directory to store Messaging Server configuration and data files /var/msg-svr-base  
System user name that will own the configuration files mailsrv  
System group that will own the configuration files mail  
User/Group Server LDAP ldap://your host:389  
Bind As cn=Directory Manager  
Password –  
Postmaster email address –  
Password for Messaging Server accounts –  
Default email Domain your domain  
Organization DN o=your domain,o=suffix Marc, is this correct?  

Configuring a Host to be Multi-Homed

In a multiple installation of the same Communications Suite product on the same host, the different instances of the product are initially configured to use the same ports. If you run both instances of the product simultaneously, the ports will conflict.

One solution is to use a different IP address for each installation and configure the host to be multi-homed (accepting multiple IP addresses).

To Change the IP Address for Each Installation

Run the ha_ip_config utility. Note that you must configure each installation to use a specific IP address, since the out-of-the-box default is to respond to any IP address (INADDR_ANY).

Note: The ENS service that needs a separate step in order to change the IP address it responds to. A workaround for now is to either disable the ENS server for one of the installations (use local.ens.enable), or to change the port used by the ENS server. If you don't do this, one of the ENS servers will not start up. This may not be a huge issue at this time since the other ENS server will handle requests.

To Configure the Host to be Multi-Homed

My guess is to edit /etc/hosts. For Solaris 10, also edit /etc/inet/ipnodes. Next, plumb the IP addresses to the ethernet addresses by using (ifconfig). This procedure would be similar on Linux systems.

Next, update your naming service (/etc/hosts, /etc/inet/ipnodes, NIS, and/or DNS) to recognize the new IP address.

For more information, see the Solaris 2 FAQ.

To Configure Multiple Addresses Per Interface

Solaris 2.x provides a feature in ifconfig that allows having more than one IP address per interface. This feature is undocumented but prior to Solaris 2.5 but it exists; it is documented in versions 2.5 and later.

Syntax

# This command is only required in later releases
ifconfig IF:N plumb
ifconfig IF:N ip-address up

where "IF" is an interface (for example, le0) and N is a number between 1 and .

To remove the pseudo interface and associated address, perform the following: 

ifconfig IF:N 0.0.0.0 down
# In newer release you must use the following command, but
# beware that this unplumbs your real interface on older
# releases, so try the above command first.
ifconfig IF:N unplumb

As with physical interfaces, all you need to do is make the appropriate /etc/hostname.IF:X file.

The maximum number of virtual interfaces, above, is 255 in Solaris releases prior to 2.6. Solaris 2.6 and Solaris 2.5.1 with the Solaris Internet Server Supplement (SISS) allow you to set this value with ndd, up to a hard maximum of 8192.

/usr/sbin/ndd -set /dev/ip ip_addrs_per_if 4000

There is no limit inspired by the code; so if you bring out adb you can increase the maximum even further.

Multi-Home Example

In the following example creates a multi-home on the host myhost.

Begin by creating the new interface:

# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.1.110.114 netmask ffffff80 broadcast 10.1.110.127
        ether 0:c:f1:8e:fb:4
# ifconfig  e1000g0:1 plumb
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.1.110.114 netmask ffffff80 broadcast 10.1.110.127
        ether 0:c:f1:8e:fb:4
e1000g0:1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 0.0.0.0 netmask 0
# ifconfig e1000g0:1 10.1.110.16 up

Set the IP address for the Messaging Server on the alternate root (on /var/tmp/altroot/opt/SUNWmsg2 in the following example):

# cd /var/tmp/altroot/opt/SUNWmsg2
# sbin/ha_ip_config

Please specify the IP address assigned to the HA logical host name. Use
dotted decimal form, a.b.c.d

Logical IP address: 10.1.110.16

Please specify the path to the top level directory in which iMS is
installed.

iMS server root: /var/tmp/altroot/opt/SUNWmsg2

The iMS server root directory does not contain any slapd-* subdirectories.
Skipping configuration of LDAP servers.

        Logical IP address: 10.1.110.16
        iMS server root: /var/tmp/altroot/opt/SUNWmsg2

Do you wish to change any of the above choices (yes/no) [no]?

Updating the file /var/tmp/altroot/opt/SUNWmsg2/config/dispatcher.cnf
Updating the file /var/tmp/altroot/opt/SUNWmsg2/config/job_controller.cnf
Setting the service.listenaddr configutil parameter
Setting the service.http.smtphost configutil parameter
Setting the local.watcher.enable configutil parameter
Setting the local.autorestart configutil parameter
Configuration successfully updated

Do the same for the Messaging Server on the default root.

# cd /opt/SUNWmsg
# sbin/ha_ip_config

Please specify the IP address assigned to the HA logical host name. Use
dotted decimal form, a.b.c.d

Logical IP address: 10.1.110.114

Please specify the path to the top level directory in which iMS is
installed.

iMS server root: /opt/SUNWmsg

The iMS server root directory does not contain any slapd-* subdirectories.
Skipping configuration of LDAP servers.

        Logical IP address: 10.1.110.114
        iMS server root: /opt/SUNWmsg

Do you wish to change any of the above choices (yes/no) [no]?

Updating the file /opt/SUNWmsg/config/dispatcher.cnf
Updating the file /opt/SUNWmsg/config/job_controller.cnf
Setting the service.listenaddr configutil parameter
Setting the service.http.smtphost configutil parameter
Setting the local.watcher.enable configutil parameter
Setting the local.autorestart configutil parameter
Configuration successfully updated

Disable the ENS server on one of the installation by setting local.ens.enable to 0:

sbin/configutil -o local.ens.enable -v 0

Configure the netmask and broadcast on the new IP address:

# ifconfig e1000g0:1 down
# ifconfig e1000g0:1 netmask 0xffffff80
# ifconfig e1000g0:1
e1000g0:1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.1.110.16 netmask ffffff80 broadcast 10.255.255.255
# ifconfig e1000g0:1 broadcast 10.1.110.127
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
        inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.1.110.114 netmask ffffff80 broadcast 10.1.110.127
        ether 0:c:f1:8e:fb:4
e1000g0:1: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.1.110.16 netmask ffffff80 broadcast 10.1.110.127
# ifconfig e1000g0:1 up

Edit /etc/hosts to add the new IP address 10.1.110.16 to it:

# cat /etc/hosts
127.0.0.1       localhost
10.1.110.114    myhost.west.sesta.com myhost        loghost
10.1.110.4      elegit.west.sesta.com
# multi-home - second IP address on ethernet port
10.1.110.16     myhost2.west.sesta.com myhost2

Configuring Individual Ports for Multiple Installations of the Same Product on One Host

In a multiple installation of the same Communications Suite product on the same host, the different instances of the product are initially configured to use the same ports. If you run both instances of the product simultaneously, the ports will conflict.

One solution is to configure the individual ports on each installation so that they are different.

For example, for Messaging Server, you need to change the following ports in one instance:

  • SMTP
  • IMAP
  • POP
  • HTTPD
  • ENS
  • job_controller
  • watcher

The ports have SSL versions, too. Also, there may be other ports to use like SMTP SUBMIT.

The best place to look for MTA-related processes is the dispatcher.cnf file. store and mshttpd ports are probably in configutil. MMP ports may be in configutil and/or its configuration files.

In addition, you can identify ports by taking these actions:

  • See Default Port Numbers in the Communications Suite Component Products Release Notes.
  • See "Configuring POP, IMAP, and HTTP Services" in the Messaging Server Administration Guide.
  • You can grep the masterconfig file (lib/config.meta) for "port".
  • Query the following configutil variables:
Service configutil variable default comments
watcher local.watcher.port 49994  
metermaid metermaid.config.port 63837  
IMAP service.imap.port 143  
IMAP SSL service.imap.sslport 993  
POP service.pop.port 110  
POP over SSL service.pop.sslport 995  
Webmail service.http.port 80  
Webmail SSL service.http.sslport 443  
ens local.store.notifyplugin.ensport 7997  
jmq local.store.notifyplugin.jmqport 7676  
Unable to render {include} Couldn't find a page to include called: Installation Worksheets - Directory+Server

Installing Communications Suite in Silent Mode

If you run the installer in Silent mode, you are running a non-interactive session. The installation inputs are taken from a silent installation file (also known as a state file), from command line arguments, or defaults.

You can use silent mode to install multiple instances of the same software component/configuration without having to manually run an interactive installation for each instance.

To run a silent installation, follow these steps:

1. Run an interactive installation session. (See To Begin Installation.) A state file similar to /var/opt/CommsInstaller/logs/silent_CommsInstaller_20070501135358 is automatically created for every run of the installation.

You can create a silent state file without actually installing the software during the interactive session by using the --dry-run option, then modifying the state file. For example:

# commpkg install --acceptLicense --dry-run

2. Copy the state file to each host machine and edit the file as needed. See Silent Mode File Format.

3. Run the silent installation on each host. For example:

# commpkg install --acceptLicense --silent <Input File>

where Input File is the path and name of the silent state file. For example: /var/opt/CommsInstaller/logs/silent_CommsInstaller_20070501135358.

For details about the --silent option, see the silent installation usage in commpkg usage.

Note

Command-line arguments override the values and arguments in the state file.

About Upgrading Shared Components

By default, shared components are not upgraded when you run a silent installation. The option to upgrade shared components in the silent state file is automatically disabled. That is, the option is set to UPGRADESC=No. This is true even if you explicitly asked to upgrade shared components when you ran the interactive installation that generated the silent state file. That is, you ran commpkg install --upgradeSC y.

The reason to disable upgrading shared components in the silent state file is this: the other hosts on which you are propagating the installation may have different shared components installed, or different versions of the shared components. These versions may be required for other applications running on the different hosts. Therefore, it is safer not to upgrade the shared components by default.

You can upgrade shared components when you run a silent installation by taking either of these actions:

  • Use the --upgradeSC y option when you run the silent installation. (The command-line argument overrides the argument in the state file.)
  • Edit the UPGRADESC=No option in the silent state file to: UPGRADESC=Yes.

Silent Mode File Format

The silent mode file (also known as a state file) is formatted like a property file: blank lines begin with a number sign (#) and properties are key/value pairs separated by an equals (=) sign. You can change the following parameters:

  • VERB— indicate which function to perform. For example VERB=install

    You can add CLI arguments described in commpkg usage, however the —dry-run argument cannot be added to the install function in the state file.
  • ALTDISTROPATH— indicate an alternate distro path if —distro is not specified. For example, ALTDISTROPATH=SunOS5.10_i86pc_DBG.OBJ/release
  • PKGOVERWRITE— set this flag if you want to overwrite the existing installation packages. For example, PKGOVERWRITE=YES
  • INSTALLROOT— specify installation root. For example, INSTALLROOT=/opt/sun/comms
  • ALTROOT— set this flag if you want to use an alternate root. For example, ALTROOT=yes
  • EXCLUDEOS— set this flag if you don't want to upgrade Operating System patches. For example, EXCLUDEOS=YES
  • COMPONENTS— list the components you want to install.* For example:
    • COMPONENTS=MS64 for 64–bit Messaging Server.
    • COMPONENTS=MS64_L10N for localized 64–bit Messaging Server.
    • COMPONENTS=MS for 32–bit Messaging Server.
    • COMPONENTS=MS_L10N for localized 32–bit Messaging Server.
    • COMPONENTS=CS for Calendar Server.
  • ACCEPTLICENSE- indicate whether or not to accept license. For example, ACCEPTLICENSE=yes.

    This property must be specified either in the state file or as a command line argument.
  • UPGRADESC– indicate whether all shared components should or should not be upgraded without prompting. For example, UPGRADESC=no

* To display a complete list of the product names (such as MS, MS64, CS) to use with the COMPONENTS property, run the commpkg info --listPackages command. This command displays the mnemonics for each product.

Installing Communications Suite on Solaris Zones

This section explains how to install Communications Suite on Solaris 10 Zones. For an overview of Solaris 10 with Communications Suite, see Overview of Solaris Zones in Sun Java Communications Suite 5 Installation Guide.

This page includes the following topics:

Installing on Solaris 10 Zones: Best Practices

You can install Communications Suite components in the global zone, whole root non-global zones, and sparse non-global zones. Follow these guidelines:

  • Treat the global zone as an "administration zone". Install shared components and OS patches there that will be shared among all zones. But don't install and run products from the global zone.
  • You can have different shared component versions in the whole root non-global zone, but it isn't entirely insulated. If you do a packaging/patch operation in the global zone for a shared component, that operation will be attempted in the whole root zone. So if you really want different shared component versions then an alternate root would be one way to go. Unfortunately, you can't use alternate root for this purpose because of a bug (6548217) in Messaging Server.
  • You could try just having whole root zones and never ever installing and patching shared components in the global zone. I don't know how realistic it is to believe that you'll never have to install or patch a shared component in the global zone. For example, NSS is a shared component, but it is part of Solaris. So to say you'll never install and patch it in the global zone seems unrealistic, especially given it is a security component.
  • In sparse non-global zones, shared components can not be installed into the default root because many of them install into a readonly shared filesystem (/usr). Thus you must run the installer in the global zone to install shared components into the default root. Prepend your selection with ~ in the global zone to install only the dependencies (i.e. shared components). You do not have to install in the global zone first before installing in the sparse zone, the installer will allow you to continue even when you don't install all the dependencies.

Top

Solaris 10 Zones Installation Sequences

This section describes how to install Communications Suite components in the four Solaris 10 Zone scenarios:

  • Global zone with existing non-global zones
  • Global zone with no existing non-global zones
  • Non-global whole root zone
  • Non-global sparse root zone

Top

Global zone with existing non-global zones

Note

This Zone scenario is not recommended for Communications Suite implementation. It requires the same version of shared components be running on each zone. Futhermore, the global zone should be reserved for administrative zone support.

If you install Communications Suite components in a global zone with existing non-global zones, you install the appropriate OS patches, shared component patches, and Communications Suite components into the global zone. It will propagate the shared component patches into the non-global zones. To install Communications Suite in a global zone with existing non-global zones:

  1. Follow pre-installation requirements as described in Installation Overview.
  2. Run the installer in the global zone by following the steps in To Begin Installation.

Top

Global zone with no existing non-global zones

If you install Messaging Server in a global zone with no existing non-global zones, you need to prepare your installation as if you might add non-global zones in the future. Modifying your deployment at a later time becomes difficult if you don~t plan for this step. To do this, follow the steps in Global zone with existing non-global zones.

Top

Non-global whole root zone

The non-global whole root zone scenario is the equivalent of installing Messaging Server on a single box with no zones. Simply install Communications Suite as described in To Begin Installation.

Caution

Any operations performed in the global zone (such as installations, uninstallations, and patching) affects the whole root zones.

Top

Non-global sparse root zone

To install Communications Suite in a non-global sparse root zone, you first need to install/upgrade the applicable OS patches and shared components in the global zone. You are unable to do so in the sparse root zone, because the /usr directory (where the shared components reside) is a read-only directory in the sparse root zone.

  1. Follow pre-installation requirements as described in Installation Overview.
  2. Verify that you are about to install the shared components and OS patches in the global zone and not the sparse root zone.
  3. Run the installer in the global zone and only install/upgrade the OS patches and the Shared Components:

    commpkg install -upgradeSC y
  4. Do not install Communications Suite components in the global zone. To do this, add a ~ (tilde) to the component number you want to install in the sparse zone. For example, if you plan to install Messaging Server in the sparse zone, you select ~3 during the global zone installation. The installer will know to only install dependencies and not the product itself.
  5. Once you have the shared components and OS patches installed, install Communications Suite components in the sparse root zone by following the steps in the To Begin Installation section.

Guidelines for Using SunCluster HA Packages in a Non-Global Zone

Take the following steps to install the Communications Suite 6 Update 1 Sun Cluster HA agent in non-global zones:

  1. Run the Communications Suite command in the global zone only:
    # commpkg install

    This command installs the Sun Cluster HA Agent package on global zone and all non-global zones.

    Note

    In case of IM_SCHA, run the command from global and non-global zones.

  2. Run the Sun Cluster HA Agent pre-configuration command in the global zone only: 
    # <scha_base>/bin/init-config

Performing Multiple Installations with an Alternate Root

The Communications Suite installer allows multiple installations of the same product version on the same machine or Solaris zone by using different INSTALLROOTS. By using the altroot option of the commpkg install command, you can create multiple INSTALLROOTS on the same machine.

This document contains the following sections:

Using Multiple Installations in a Side-by-Side Upgrade Scenario

The multiple-installation feature lets you perform side-by-side upgrades of some Communications Suite products.

In a side-by-side upgrade, the existing software on the host can continue to run while you install the new versions of the products on an alternate root on the same host. This approach minimizes downtime, so that end users can have continuous (or near-continuous) access to their email, calendars, and so on.

Summary of Side-by-Side Upgrade Steps

In a side-by-side upgrade scenario, you perform the following tasks:

  1. Install the new Communications Suite software on the same host as the earlier versions. You can use the commpkg install commands shown in To Install a Communications Suite Product in an Alternate Root.

  2. Configure the new software. Run the configuration script for the product.

  3. Migrate data to the new directories under the alternate root's INSTALLROOT.

  4. Configure alternate ports for the new installation under the alternate root. Alternatively, configure the host as a multi-home. For details, see Running Multiple Installations of the Same Product on One Host - Conflicting Ports.

  5. Test the new software.

  6. Switch end users to the new environment.

For more information about the side-by-side upgrade scenario, see Using the Side-by-Side Strategy to Upgrade Messaging Server.

To Install a Communications Suite Product in an Alternate Root

Install the product in the alternate root with the —altroot option:

  1. Install OS patches and Shared Components in the default INSTALLROOT. See To Begin Installation.

    To install only the shared components, you can run commpkg install without --altroot and select the product you want to install. You select a product by entering the number displayed next to it in the install list. Add a ~ (tilde) in front of the product number.

    For example, if you plan to install Messaging Server in the alternate root, you select ~3 during the default installation. This tells the installer to install the dependencies but not the product itself.

    Note

    OS patches are always applied in the default INSTALLROOT, never in the alternate root.



  2. Install the product in the altroot, as in the following example:

    commpkg install --altroot --installroot /opt/sun/comms2



    Be sure to use —installroot with —altroot to specify the alternate root.

    You can also avoid installing the shared components in the altroot by using the --excludeSC option, as in the following example: 

    commpkg install --excludeSC --altroot --installroot /opt/sun/comms2



    You may create as many alternate roots as you like. However, you should manually keep track of all the alternate roots you have created.

Understanding INSTALLROOT and Altroot

The following concepts define an altroot:

  • An altroot is an alternate root directory.
  • The altroot is used for multiple installations of Communications Suite products on the same host.
  • The default root is the standard root directory, which can be indicated with a /.
  • An altroot implies the existence of a default root.

The following concepts define an INSTALLROOT:

  • An INSTALLROOT is the top-level installation path for the Communications Suite products and shared components.
  • There is an INSTALLROOT (an installation path) for each instance of the installed products. That is, if your system has a default root and an altroot, the default root has one INSTALLROOT, and the altroot must have a different INSTALLROOT.

Now let's put them together:

  • You define an altroot by specifying its INSTALLROOT and using the --altroot option with the commpkg install command.

What's the Default?

If you use the default root and the default INSTALLROOT, the commpkg install command installs products under the following top-level directory:

/opt/sun/comms/

An Example

Now suppose you want to install one instance of the products in /opt/sun/mycompany/comms/; and another instance of the same products in /opt/sun/mycompany/comms2/. You would use the following commands:

For the default root:

commpkg install --installroot /opt/sun/mycompany/comms/

For the altroot:

commpkg install --altroot --installroot /opt/sun/mycompany/comms2/

Running Multiple Installations of the Same Product on One Host: Conflicting Ports

By default, after you initially configure the product on alternate roots, the ports used by the different product installations are the same and thus conflict with each other.

This is not a problem if you install multiple installations of the same product on the same host but only intend to have one instance running at one time. For example, you may perform a side-by-side upgrade scenario in which you plan to stop the old instance before you start the new instance.

However, you may plan to test the new instance while the old instance is still running (and supporting end users). In this scenario, the ports are used simultaneously.

There are two ways to resolve this conflict:

  • Configure individual ports
  • Use a multi-home configuration

These approaches are described in the following sections.

Configuring Individual Ports

See Configuring Individual Ports for Multiple Installations of the Same Product.

Configuring a Host to Be Multi-Homed

See Configuring a Host to be Multi-Homed.

Unable to render {include} Couldn't find a page to include called: Sample Session - Communications Suite 6 Install Using altroot
Unable to render {include} Couldn't find a page to include called: Sample Session - Communications Suite 6 Simple Install and Uninstall

Deployment Example: Installing Communications Suite 6 on a Solaris Zone

The sample sessions in this article describes how to install Communications Suite 6 software on a Solaris zone.

Installation Overview

This scenario provides an example of how to install Communications Suite 6 into a Solaris zone. It accomplishes these salient goals:

  • Installs and configures the Convergence client and the other Communications Suite 6 components.
  • Installs the Sun Java System software products required by Communications Suite.
  • Creates a ZFS file system for the zone.
  • Installs Delegated Administrator for user provisioning.
  • Installs Sun Java System Access Manager, required by Delegated Administrator.

To complete the scenario, perform these tasks:

  1. Obtain an IP address for the zone.
  2. Download the software.
  3. Install service tags in the global zone.
  4. Create a zone configured with a ZFS file system.
  5. Install Application Server 9.1 with the JDK.
  6. Install the Communications Suite with the Communications Suite installer, commpkg.
  7. Install Sun Java System Directory Server.
  8. Install the Identity Management Suite: Sun Java System Web Server and Sun Java System Access Manager.
  9. Run the Comms Directory Server Setup script, comm_dssetup.pl.
  10. Configure Delegated Administrator on Web Server 7. Create user accounts.
  11. Configure Messaging Server 7.0.
  12. Configure Calendar Server 6.3 Update 2.
  13. Configure Instant Messaging Server 7.3.
  14. Deploy and Configure Convergence 1.0.
  15. Take a ZFS snapshot of the software you have installed in this zone.

These tasks are described in the remaining sections in this document.

How to Use This Document

Each section below records the command-line interactions that perform one installation or configuration task. Taken together, these sessions demonstrate one particular installation scenario.

You can use this document in the following ways:

  • If this scenario matches your installation goals, follow all the sessions described below.
  • If you have different installation objectives, use any sessions that apply to your own scenario.

This document is intended for any system administrator or installation technician who wants to install and configure the services delivered by these components. It assumes you are familiar with creating and configuring Solaris zones.

Which Components Are Installed?

This example installs and configures the following Communications Suite and dependent Sun Java System components:

Communication Suite Products:

  • Comms DSsetup 6.4 (6.4-1.02)
  • Comms Delegated Administrator 6.4 (6.4-2.03)
  • Messaging Server 7.0 (7.0-0.01)
  • Calendar Server 6.3 (6.3-6.01)
  • Instant Messaging 7.3 (7.3)
  • Convergence 1.0 (Integrated Web Client 0.1) (0.1)

Sun Java System products required by Communications Suite:

  • Application Server 9.1 Update 1
  • Sun Java System Directory Server 6.3
  • Sun Java System Access Manager 7.1 (required by Delegated Administrator)
  • Sun Java System Web Server 7.0 (required by Access Manager)

Obtain an IP address for the zone.

In this example, IP addresses are obtained for four zones: 

192.168.100.22    niag1-z4.example.mydomain.com niag1-z4
192.168.100.23    niag-fe.example.mydomain.com niag-fe
192.168.100.24    niag1-z1.example.mydomain.com niag1-z1
192.168.100.25    niag1-z3.example.mydomain.com  niag1-z3

Download the software.

Go here to link to the software download sites: Get the Software to Install a Communications Suite Deployment.

Install service tags in the global zone.

Before you can create and configure the zone in which Communications Suite will be installed, you need to install service tags in the global zone.

You can accomplish this by running the Communications Suite installer to install one Comms component, the Comms Directory Server setup script, comm_dssetup.pl. The following example installs

  • comm_dssetup.pl
  • The Communications Suite installer, commpkg
  • Service tags

Service tags are installed in the global zone.

# perl commpkg install

Communication Services Products:

   Item  Description
   ----  -----------
      1  Messaging Server 7.0 (7.0-0.01)
      2  Messaging Server (64bit) 7.0 (7.0-0.01)
      3  Comms DSsetup 6.4 (6.4-1.02)
      4  Comms Delegated Administrator 6.4 (6.4-2.03)
      5  Calendar Server 6.3 (6.3-6.01)
      6  Calendar Server Localization 6.3
      7  Instant Messaging 7.3 (7.3)
      8  Integrated Web Client 0.1 (0.1)
      9  Communications Express 6.3 (6.3-3.01)
     10  Messaging Server Sun Cluster HA agent 7.0 (7.0-0.01)


Enter the items you wish to install.
Prefix an item with ~ to indicate you only want
 to install shared component dependencies of that product
You can enter multiple items using commas to separate them.
For example: 1,2

Please select the products you wish to install [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]: 3
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Generating list of things to install...
Checking for Shared Component Upgrade Requirements...
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 WILL INSTALL: Comms DSsetup 6.4
 WILL INSTALL: CommsInstaller 6.0
 WILL INSTALL: Service Tags 1.0
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ready to install

Create a Solaris zone configured with a ZFS file system.

This session creates a Solaris zone (niag1-z4.example.mydomain.com) and configures a ZFS file system called onebox for the zone. The session comprises the following steps:

  • Create a ZFS pool.
  • Create file system for the zone.
  • Create, configure, and verify the zone.
  • Remove unneeded directories from the zone.
  • Install and boot the zone.

These steps are just one particular way to create a zone. For more information about creating zones, see OpenSolaris Community: Zones.

Create a ZFS pool.

This step creates a ZFS pool called zones on the two physical drives named below in a mirror configuration. It then creates a ZFS file system called zones/onebox. (Note: You do not need to add this file system to /etc/vfstab because ZFS automatically mounts it during system startup.)

# zpool create zones mirror c1t2d0s6 c1t1d0s6
# zfs create zones/onebox
# chmod 700 /zones/onebox

(Note: if you forget to do the chmod, you will get an error later when you do zoneadm verify.)

Create, configure, and verify the zone.

This step configures a zone called onebox-comms.

/net/brandy/wspace/jhawk/msg70/comms-lab/onebox-comms

# zonecfg -z onebox-coms
onebox-coms: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:onebox-coms> create
zonecfg:onebox-coms> set zonepath=/zones/onebox
zonecfg:onebox-coms> set autoboot=true
zonecfg:onebox-coms> add net
zonecfg:onebox-coms:net> set address=192.168.100.22
zonecfg:onebox-coms:net> set physical=ipge0
zonecfg:onebox-coms:net> end
zonecfg:onebox-coms> add attr
zonecfg:onebox-coms:attr> set name=comment
zonecfg:onebox-coms:attr> set type=string
zonecfg:onebox-coms:attr> set value="onebox comms zone"
zonecfg:onebox-coms:attr> end
zonecfg:onebox-coms> remove inherit-pkg-dir dir=/usr
zonecfg:onebox-coms> remove inherit-pkg-dir dir=/sbin
zonecfg:onebox-coms> verify
zonecfg:onebox-coms> commit
zonecfg:onebox-coms> exit
# zoneadm -z onebox-coms verify

(Note: the remove inherit-pkg-dir lines above remove the inheritance of the specified directory by the zone. By default, /usr, /sbin, /lib, and /platform are inherited from the global zone - meaning it will be a sparse zone. By removing the inherit-pkg-dir directive, you cause the zone to get its own copy of the specified directory, thus making it a whole-root zone. In this example, /lib and /platform are still inherited from the global zone, but the zone will have its own copy of /usr and /sbin.)

Install and boot the zone.
# zoneadm -z onebox-coms verify
# time zoneadm -z onebox-coms install
Preparing to install zone <onebox-coms>.
Creating list of files to copy from the global zone.
Copying <120988> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <1063> packages on the zone.
Initialized <1063> packages on zone.                                 Zone <onebox-coms> is initialized.
Installation of these packages generated errors: <SUNWgnome-a11y-libs-share>
The file </zones/onebox/root/var/sadm/system/logs/install_log> contains a log of the zone installation.

real    17:44.7
user     3:54.7
sys      9:26.4
#

# zoneadm -z onebox-coms ready
# zoneadm -z onebox-coms boot
# zlogin -C onebox-coms

Install Application Server 9.1 with the JDK.

This session installs the Java Platform, Enterprise Edition 5 SDK, which includes Application Server 9.1 and Sun Java System Message Queue 4.1:

# cp java_ee_sdk-5_04-solaris-sparc.bin /tmp
# cd /tmp
# chmod 777 java_ee_sdk-5_04-solaris-sparc.bin
# ./java_ee_sdk-5_04-solaris-sparc.bin -console


The Java Platform, Enterprise Edition 5 SDK components will be installed in the
following directory, which is referred to as the "Installation Directory".To
use this directory, press only the Enter key. To use a different directory,
type in the full path of the directory to use followed by pressing the Enter
key.

  Installation Directory [/opt/SDK] {"<" goes back, "!" exits}:

The directory "/opt/SDK" does not exist.
Do you want to create it now or choose another directory?

1. Create Directory
2. Choose New

  Enter the number corresponding to your choice  [1] {"<" goes back, "!"
  exits} 1
Supply the admin user's password and override any of the other initial
configuration settings as necessary.
  Admin User [admin] {"<" goes back, "!" exits}:
  Admin User's Password (8 chars minimum):
  Re-enter Password:
  Do you want to store admin user name and password in .asadminpass file in
  user's home directory [yes] {"<" goes back, "!" exits}?
  Admin Port [4848] {"<" goes back, "!" exits}:
  HTTP Port [8080] {"<" goes back, "!" exits}:
  HTTPS Port [8181] {"<" goes back, "!" exits}:

Please choose installation options.

  Do you want to enable Updatecenter client [yes] {"<" goes back, "!" exits}?
  Do you want to upgrade from previous Application Server version [no] {"<"
  goes back, "!" exits}?


Checking disk space...


The following items for the product Java Platform, Enterprise Edition 5 SDK
will be installed:

Product: Java Platform, Enterprise Edition 5 SDK
Location: /opt/SDK
Space Required: 266.89 MB
------------------------------------------------
Java 2 SDK, Standard Edition 6.0
Sun Java System Message Queue 4.1
Sun Java System Application Server 9.1
Sample Applications
Java BluePrints
Your First Cup: An Introduction to the Java EE Platform


Ready to Install

1. Install Now
2. Start Over
3. Exit Installation

  What would you like to do [1] {"<" goes back, "!" exits}?
Installing Java Platform, Enterprise Edition 5 SDK
|-1%--------------25%-----------------50%-----------------75%--------------100%|

Installation Successful.

Next Steps:

   1. Access the About Java EE 5 SDK welcome page at:
      file:///opt/SDK/docs/about.html

   2. Start the Application Server by executing:
      /opt/SDK/bin/asadmin start-domain domain1

   3. Start the Admin Console:
      http://localhost:4848
      Please press Enter/Return key to exit the installation program. {"!" exits}

Deleting temporary files...

# /opt/SDK/bin/asadmin start-domain domain1

Starting Domain domain1, please wait.
Log redirected to /opt/SDK/domains/domain1/logs/server.log.
Redirecting output to /opt/SDK/domains/domain1/logs/server.log
Domain domain1 is ready to receive client requests. Additional services are being started in background.
Domain [domain1] is running [Sun Java System Application Server 9.1_01 (build b09d-fcs)] with its configuration and logs at: [/opt/SDK/domains].
Admin Console is available at [http://localhost:4848].
Use the same port [4848] for "asadmin" commands.
User web applications are available at these URLs:
[http://localhost:8080 https://localhost:8181 ].
Following web-contexts are available:
[/web1  /__wstx-services ].
Standard JMX Clients (like JConsole) can connect to JMXServiceURL:
[service:jmx:rmi:///jndi/rmi://niag1-z4.example.mydomain.com:8686/jmxrmi] for domain management purposes.

Domain listens on at least following ports for connections:
[8080 8181 4848 3700 3820 3920 8686 ].
Domain does not support application server clusters and other standalone instances.

Install the Communications Suite with the Communications Suite installer, commpkg.

This session runs the Communications Suite installer, commpkg, to install these components:

  • Messaging Server 7.0 (7.0-0.01)
  • Comms DSsetup 6.4 (6.4-1.02)
  • Comms Delegated Administrator 6.4 (6.4-2.03)
  • Calendar Server 6.3 (6.3-6.01)
  • Instant Messaging 7.3 (7.3)
  • Convergence 1.0 (Integrated Web Client 0.1) (0.1)
  • Communications Express 6.3 (6.3-3.01)

This step invokes the installer:

#  perl commpkg install

The installer prompts which components you want to install. This step selects the components:

Communication Services Products:

   Item  Description
   ----  -----------
      1  Messaging Server 7.0 (7.0-0.01)
      2  Messaging Server (64bit) 7.0 (7.0-0.01)
      3  Comms DSsetup 6.4 (6.4-1.02)
      4  Comms Delegated Administrator 6.4 (6.4-2.03)
      5  Calendar Server 6.3 (6.3-6.01)
      6  Calendar Server Localization 6.3
      7  Instant Messaging 7.3 (7.3)
      8  Integrated Web Client 0.1 (0.1)
      9  Communications Express 6.3 (6.3-3.01)
     10  Messaging Server Sun Cluster HA agent 7.0 (7.0-0.01)


Enter the items you wish to install.
Prefix an item with ~ to indicate you only want
 to install shared component dependencies of that product
You can enter multiple items using commas to separate them.
For example: 1,2

Please select the products you wish to install [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]: 1,3,4,5,7,8,9

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Generating list of things to install...
Checking for Shared Component Upgrade Requirements...
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 WILL INSTALL: Messaging Server 7.0
 WILL INSTALL: Comms DSsetup 6.4
 WILL INSTALL: Comms Delegated Administrator 6.4
 WILL INSTALL: Calendar Server 6.3
 WILL INSTALL: Instant Messaging 7.3
 WILL INSTALL: Integrated Web Client 0.1
 WILL INSTALL: Communications Express 6.3
 WILL INSTALL: CommsInstaller 6.0
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ready to install
A Note About Installing the Directory Server Setup Script
In the preceding task, you install comm_dssetup.pl with the Comms Suite installer before you install Directory Server (described in the next step). If you follow this sequence, you will have the up-to-date version of comm_dssetup.pl. The Directory Server installation process does not overwrite the latest version.

If you install or upgrade Directory Server before you run the Communications Suite installer, the Directory Server installation process places an outdated version of comm_dssetup.pl on your system. You must use the current version of comm_dssetup.pl provided by the Communications Suite installer. However, the Comms Suite installer cannot install a new version with the commpkg install command. Instead, run the commpkg upgrade command to upgrade to the latest version of comm_dssetup.pl.

Install Sun Java System Directory Server 6.3

This session comprises the following steps:

  • Install and configure Directory Server Enterprise Edition 6.3.
  • Create the Directory Manager user ID.
  • Start Directory Server.
Install and configure Directory Server Enterprise Edition 6.3

This example installs the zip file version of Directory Server 6.3. (It does not install the older 6.2 version of Directory Server available with the Sun Java Identity Management Suite.)

Note that you do not need to install the "Directory Preparation Tool" (also called the Comms Directory Server setup script, comm_dssetup.pl), because the latest version of comm_dssetup.pl was already installed by the Communications Suite installer in an earlier step. 

# cd /<root>/DSEE_ZIP_Distribution
# ./dsee_deploy install -i /opt/SUNWdsee 

Sun Microsystems, Inc. ("Sun") SOFTWARE LICENSE AGREEMENT ("SLA") 
and ENTITLEMENT for SOFTWARE

A. ENTITLEMENT for SOFTWARE 
Software: <List of Sun software and Third-Party software...>

B. SOFTWARE LICENSE AGREEMENT 
<Definitions and Terms of Software License Agreement...>

Do you accept the license terms ? <yes/no> : yes

Check availability of port 11169
Checking running Directory Server instances
Checking running Directory Proxy Server instances
Unzipping sun-ldap-base.zip ...
Unzipping sun-ldap-dsrk6.zip ...
Unzipping sun-ldap-dsrk-man.zip ...
Unzipping sun-ldapcsdk-tools.zip ...
Unzipping sun-ldapcsdk-dev.zip ...
Unzipping sun-ldap-ljdk.zip ...
Unzipping sun-ldap-jre.zip ...
Unzipping sun-ldap-shared.zip ...
Unzipping sun-ldap-shared-l10n.zip ...
Unzipping sun-ldap-directory.zip ...
Unzipping sun-ldap-directory-l10n.zip ...
Unzipping sun-ldap-directory-config.zip ...
Unzipping sun-ldap-directory-man.zip ...
Unzipping sun-ldap-directory-dev.zip ...
Unzipping sun-ldap-mfwk.zip ...
Unzipping sun-ldap-cacao.zip ...
Unzipping sun-ldap-console-agent.zip ...
Unzipping sun-ldap-console-cli.zip ...
Unzipping sun-ldap-console-common.zip ...
Unzipping sun-ldap-console-var.zip ...
Unzipping sun-ldap-jdmk.zip ...
Unzipping sun-ldap-directory-client.zip ...
Unzipping sun-ldap-directory-client-l10n.zip ...
Unzipping sun-ldap-proxy.zip ...
Unzipping sun-ldap-proxy-l10n.zip ...
Unzipping sun-ldap-proxy-man.zip ...
Unzipping sun-ldap-proxy-client.zip ...
Unzipping sun-ldap-proxy-client-l10n.zip ...
Unzipping sun-ldap-console-gui.zip ...
Unzipping sun-ldap-console-gui-help.zip ...
Unzipping sun-ldap-console-gui-l10n.zip ...
Unzipping sun-ldap-console-gui-help-l10n.zip ...
Creating WAR file for Console

Configuring Cacao at /opt/SUNWdsee/dsee6/cacao_2
Setting Cacao parameter jdmk-home with default value [/opt/SUNWdsee/dsee6/private]
Setting Cacao parameter java-home with default value [/opt/SUNWdsee/jre]
Setting Cacao parameter nss-lib-home with default value [/opt/SUNWdsee/dsee6/private/lib]
Setting Cacao parameter nss-tools-home with default value [/opt/SUNWdsee/dsee6/bin]
Setting Cacao parameter jmxmp-connector-port with value [11169]
Registering DSCC agent into cacao
Starting Cacao if necessary
Registering JESMF agent into Cacao
Making a copy of dsee_deploy
Making a copy of listrunnings64
You can now start your Directory Server Instances
You can now start your Directory Proxy Server Instances
Create the Directory Manager user ID.
#cd /opt/SUNWdsee/ds6/bin
#./dsadm create -p 389 -D "cn=Directory Manager" -P 636 /opt/SUNWdsee/dsins1
Choose the Directory Manager password:
Confirm the Directory Manager password:
Start Directory Server.

You must start Directory Server before you run the Comms Directory Server setup script, comm_dssetup.pl, during a later step.

# ./dsadm info /opt/SUNWdsee/dsins1
Instance Path: /opt/SUNWdsee/dsins1  
Owner: dsuser(dsuser)  
Non-secure port: 389  
Secure port: 636  
Bit format: 64-bit  
State: Stopped  
DSCC url: -  
SMF application name:  -  
Instance version: D-A00  

#./dsadm start /opt/SUNWdsee/dsins1
Server started: pid=29494

# ldapsearch -b "" -s base objectclass=top
version: 1
dn:
objectClass: top
namingContexts: o=ugdata

From the Sun Java Identity Management Suite: Install Sun Java System Web Server and Sun Java System Access Manager.

This session comprises the following steps:

  • Install and configure Access Manager 7.1 and Web Server 7.0 Update 1 by running the Identity Management Suite installer.
  • Start Web Server.
  • Log in to the Access Manager console, amconsole.
Install and configure Access Manager 7.1 and Web Server 7.0 Update 1 by running the Identity Management Suite installer.

This session configures Access Manager in Legacy mode. Delegated Administrator requires that Access Manager run in Legacy mode.

# ./installer -nodisplay

Choose Software Components - Main Menu
-------------------------------
Note: "*  *" indicates that the selection is disabled

[X] 1. Web Server 7.0 Update 1
*  *  Directory Preparation Tool 6.4
[ ] 3. Application Server Enterprise Edition 8.2 Patch 2
*  *  Directory Server Enterprise Edition 6.2
[ ] 5. Monitoring Console 1.0 Update 1
[ ] 6. High Availability Session Store 4.4.3
[ ] 7. Access Manager 7.1
[ ] 8. Message Queue 3.7 UR2
[ ] 9. Java DB 10.2.2.1
*  *  All Shared Components

  Enter a comma separated list of products to install, or press R to refresh
  the list [1] {"<" goes back, "!" exits}: 7

Choose Software Components - Confirm Choices
--------------------------------------------

Based on product dependencies for your selections, the installer will install:

[X] 7. Access Manager 7.1


  Press "Enter" to Continue or Enter a comma separated list of products to
  deselect. Enter "-" with product number to deselect a product (for eg. -5
  will deselect product number 5). To return to the component selection list,
  press "r". [1] {"<" goes back, "!" exits}

Component Selection - Selected Product "Access Manager 7.1 "
------------------------------------------------------------

*[X] 1. Access Manager Core Services
*[X] 2. Access Manager Administration Console
*[X] 3. Common Domain Services for Federation Management
*[X] 4. Access Manager SDK
*[ ] 5. Access Manager Distributed Authentication User Interface
*[ ] 6. Access Manager Client SDK
*[ ] 7. Access Manager Session Failover Client

  Enter a comma separated list of components to install (or A to install all )
  [A] {"<" goes back, "!" exits}

*[X] 1. Access Manager Core Services
*[X] 2. Access Manager Administration Console
*[X] 3. Common Domain Services for Federation Management
*[X] 4. Access Manager SDK
*[X] 5. Access Manager Distributed Authentication User Interface
*[X] 6. Access Manager Client SDK
*[X] 7. Access Manager Session Failover Client


  Press "Enter" to Continue or Enter a comma separated list of products to
  deselect. Enter "-" with product number to deselect a product (for eg. -5
  will deselect product number 5). To return to the component selection list,
  press "r". [1] {"<" goes back, "!" exits}

  Install multilingual package(s) for all selected components [Yes] {"<" goes
  back, "!" exits}:

For component product [ Access Manager 7.1  ]
--------------------------------------------------------------

1. Web Server 7.0 Update 1
2. Application Server Enterprise Edition 8.2 Patch 2
3. A compatible web container previously installed on this system.

  Please choose a web container for your selected products [1] {"<" goes back,
  "!" exits} 1


Installation Directories
------------------------

Enter the name of the target installation directory for each product:


  Access Manager [/opt] {"<" goes back, "!" exits}:
  Web Server [/opt] {"<" goes back, "!" exits}:
  Web Server Instance [/var/opt/SUNWwbsvr7] {"<" goes back, "!" exits}:


Checking System Status

   Available disk space...        : Checking .... OK                  
   Memory installed...            : Checking .... OK                  
   Swap space installed...        : Checking .... OK                  
   Operating system patches...    : Checking .... OK                  
   Operating system resources...  : Checking .... OK                  

System ready for installation                  

System Ready for Installation. Memory detection is disabled in a non-global zone.                      


  Enter 1 to continue [1] {"<" goes back, "!" exits}


Screen for selecting Type of Configuration

1. Configure Now - Selectively override defaults or express through

2. Configure Later - Manually configure following installation


  Select Type of Configuration [1] {"<" goes back, "!" exits}


Specify Administrator Account Preferences

You must specify administrator accounts and passwords for most
Java Enterprise System products.


1. Use a single administrator account when possible.

2. Use different administrator account for each product.



  Enter 1 or 2 [1] {"<" goes back, "!" exits}:
  Administrator User Id [admin] {"<" goes back, "!" exits}
  Administrator Password [] {"<" goes back, "!" exits}    Retype Password [] {"<" goes back, "!" exits} 


Specify Common Server Settings

  Enter Host Name [niag1-z4] {"<" goes back, "!" exits}
  Enter DNS Domain Name [example.mydomain.com] {"<" goes back, "!" exits}
  Enter IP Address [192.168.100.22] {"<" goes back, "!" exits}
  Enter System User [root] {"<" goes back, "!" exits} dsuser
  Enter System Group [root] {"<" goes back, "!" exits} dsuser


Web Server: Choose Configuration Type

Warning: If you plan to deploy Access Manager (or) Portal Server
in this Web Server, please select 'Admin'.

  Configure Administration Instance as Server OR Node. Valid values are Admin
  and Node [Admin] {"<" goes back, "!" exits}
  Start servers after system startup [No] {"<" goes back, "!" exits} yes



Web Server: Specify Administration Server Settings

  Enter Host Name [niag1-z4.example.mydomain.com] {"<" goes back, "!" exits}:
  Enter Runtime User ID [root] {"<" goes back, "!" exits}:
  Enter SSL Administration Port [8989] {"<" goes back, "!" exits}:
  Enter Non SSL Administration Port [8800] {"<" goes back, "!" exits}:



Web Server: Specify Instance Settings

  Server Name [niag1-z4.example.mydomain.com] {"<" goes back, "!" exits}:
  Enter HTTP Port [80] {"<" goes back, "!" exits}:
  Enter Runtime UNIX User ID [webservd] {"<" goes back, "!" exits}: dsuser

If you plan to deploy Portal Server in this instance of Web Server, set Runtime
User ID to superuser (usually root) and the Runtime Group to the superuser's
group (usually other).

  Enter Document Root Directory [/var/opt/SUNWwbsvr7/https-niag1-z4.example.
  mydomain.com/docs] {"<" goes back, "!" exits}:

Access Manager: Specify Configuration Information

  Install type (Realm/Legacy) Mode [Legacy] {"<" goes back, "!" exits}:
  Administrator User ID: amAdmin
  Administrator Password [] {"<" goes back, "!" exits}:    Retype Password [] {"<" goes back, "!" exits}:    LDAP User ID: amldapuser
  LDAP Password [] {"<" goes back, "!" exits}:    Retype Password [] {"<" goes back, "!" exits}:  Passwords for LDAP User do not match.


  LDAP User ID: amldapuser
  LDAP Password [] {"<" goes back, "!" exits}:    Retype Password [] {"<" goes back, "!" exits}:    Password Encryption Key [g98luZpRMHiBcm40H/uhgoPZyLCYeVni] {"<" goes back,
  "!" exits}: thequickfoxrandownthehill


Access Manager: Choose Deployment Container

1. Sun Java(TM) System Application Server
2. Sun Java(TM) System Web Server

  Select the container to deploy the component and hit enter key [2] {"<" goes
  back, "!" exits}

Access Manager: Specify Web Container for Running Access Manager Services

  Host Name [niag1-z4.example.mydomain.com] {"<" goes back, "!" exits}:
  Services Deployment URI [amserver] {"<" goes back, "!" exits}:
  Common Domain Deployment URI [amcommon] {"<" goes back, "!" exits}:
  Cookie Domain(Assure it is not a top level domain) [.mydomain.com] {"<" goes
  back, "!" exits}: .example.mydomain.com
  Password Deployment URI [ampassword] {"<" goes back, "!" exits}:

1. HTTP
2. HTTPS

  Console Protocol [1] {"<" goes back, "!" exits}:

Access Manager: Choose Access Manager Console

  Administration Console [Yes] {"<" goes back, "!" exits}:
  Console Deployment URI [amconsole] {"<" goes back, "!" exits}:


Access Manager: Specify Directory Server Information

  Directory Server Host [] {"<" goes back, "!" exits}: niag1-z4.example.mydomain.com
  Directory Server Port [389] {"<" goes back, "!" exits}:
  Directory Root Suffix [dc=example,dc=mydomain,dc=com] {"<" goes back, "!" exits}: o=ugdata
  Directory Manager DN [cn=Directory Manager] {"<" goes back, "!" exits}:
  Directory Manager Password [] {"<" goes back, "!" exits}: 
Access Manager: Specify Directory Server Data

  Is Directory Server provisioned with user data [No] {"<" goes back, "!"
  exits}?
Ready to Install
----------------
The following components will be installed.

Product: Java Enterprise System Identity Management Suite
Uninstall Location: /var/sadm/prod/SUNWident-entsys5u1
Space Required: 189.14 MB
---------------------------------------------------------
       Sun Java(TM) System Web Server 7.0 Update 1
          Sun Java(TM) System Web Server 7.0 Update 1 Samples
          Sun Java(TM) System Web Server 7.0 Update 1 CLI
          Sun Java(TM) System Web Server 7.0 Update 1 Core
       Sun Java(TM) System Access Manager 7.1
          ClientSDK
          SessionFailOverClient
          DistributedAuthentication
          Common Domain Services for Federation Management
          Access Manager SDK
          Access Manager Administration Console
          Access Manager Core Services


1. Install
2. Start Over
3. Exit Installation
Start Web Server 7.0.

This step first starts the Admin Server, then starts Web Server.

# cd /var/opt/SUNWwbsvr7/admin-server/bin/
# ./startserv
Sun Java System Web Server 7.0U1 B07/18/2007 15:51
info: CORE3016: daemon is running as super-user
info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_12] from [Sun Microsystems Inc.]
info: WEB0100: Loading web module in virtual server [admin-server] at [/admingui]
info: WEB0100: Loading web module in virtual server [admin-server] at [/jmxconnector]
info: HTTP3072: admin-ssl-port: https://niag1-z4.example.mydomain.com:8989 ready to accept requests
info: HTTP3072: admin-http-port: http://niag1-z4.example.mydomain.com:8800 ready to accept requests
info: CORE3274: successful server startup
#

# cd /var/opt/SUNWwbsvr7/https-niag1-z4.example.mydomain.com/bin/
# ./stopserv
server has been shutdown
# ./startserv
Sun Java System Web Server 7.0U1 B07/18/2007 15:51
info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_12] from [Sun Microsystems Inc.]
info: WEB0100: Loading web module in virtual server [niag1-z4.example.mydomain.com] at [/amserver]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [niag1-z4.example.mydomain.com] at [/ampassword]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [niag1-z4.example.mydomain.com] at [/amcommon]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [niag1-z4.example.mydomain.com] at [/amconsole]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: url: jar:file:/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar!/com/sun/mfwk/config/MfConfig.class
info: "mfwk.multicast.disableloopback" set to false
info: url: jar:file:/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar!/com/sun/mfwk/config/MfConfig.class
info: LogFile is: //var/opt/SUNWmfwk/logs/instrum.%g
warning: Warning: unable to initialize log file!
warning: Couldn't get lock for //var/opt/SUNWmfwk/logs/instrum.%g
info: group = 227.227.227.1, port  = 54320
info: Set Time-to-live to 0
info: join Group /227.227.227.1
info: Starting listening thread
info: sends initial RESP message in SDK
info: Packet received
info: HTTP3072: http-listener-1: http://niag1-z4.example.mydomain.com:80 ready to accept requests
info: CORE3274: successful server startup
Log in to the Access Manager console, amconsole.
try to log into http://niag1-z4.example.mydomain.com/amconsole
user name: amadmin
password: adminpass

Run the Comms Directory Server Setup script, comm_dssetup.pl.

This task prepares Directory Server by installing the schema needed to support Communications Suite. You set up the directory by running the comm_dssetup.pl script. This session installs Schema 2, required for Delegated Administrator and Access Manager.

Before you run comm_dssetup.pl, be sure that Directory Server is running (see earlier step).

/opt/sun/comms/dssetup/sbin
# ls
comm_dssetup.pl  schema
# perl comm_dssetup.pl

Welcome to the Directory Server preparation tool for
Sun Java(tm) System communication services.
dssetup Version 6.4-1.02 (built Wed Oct 10 13:54:08 PDT 2007)

This tool prepares your directory server for use by the
communications services which include Messaging, Calendar and their components.

The logfile is /var/tmp/dssetup_20071220160633.log.

Do you want to continue [y]:

Please enter the full path to the directory where the
Directory Server instance(s) reside ("server-root"), or
an explicit Directory Server instance directory

Directory server root [/var/opt/SUNWdsee/dsins1] :

Please enter the directory manager DN [cn=Directory Manager]:

Password:


Detected DS version 6.2

Will this directory server be used for users/groups [yes]:
A list of suffixes are as follows:
 o=ugdata

Please enter the Users/Groups base suffix [o=ugdata] :
There are 3 possible schema types:
 1   - schema 1 for systems with iMS 5.x data
 1.5 - schema 2 compatibility for systems with iMS 5.x data
       that has been converted with commdirmig
 2   - schema 2 native for systems using Access Manager

Please enter the Schema Type (1, 1.5, 2) [1]: 2
Access Manager does not appear to have been installed for this suffix
Note that you will not be able to use features that depend on Access Manager

Are you sure you want this schema type? [n]: y

Do you want to update the schema files [yes]:

Do you want to configure new indexes [yes]:

Do you want to Reindex the new indexes now [yes]:

Here is a summary of the settings that you chose:

 Server Root                        : /var/opt/SUNWdsee
 Server Instance                    : dsins1
 Users/Groups Directory             : yes
 Update Schema                      : yes
 Schema Type                        : 2
 DC Root                            : o=ugdata
 User/Group Root                    : o=ugdata
 Add New Indexes                    : yes
 ReIndex New Indexes Now            : yes
 Directory Manager DN               : cn=Directory Manager


Now ready to generate a shell script and ldif file to modify the Directory.
No changes to the Directory Server will be made this time.

Do you want to continue [y]:

# ldapsearch -b "" -s base objectclass=top
version: 1
dn:
objectClass: top
namingContexts: o=PiServerDb
namingContexts: o=pab
namingContexts: o=comms-config
namingContexts: o=ugdata

Configure Delegated Administrator on Web Server 7 and create user accounts.

This session comprises the following steps:

  • Run the Delegated Administrator configuration program, config-commda.
  • Stop and restart Web Server.
  • Create user accounts with the Delegated Administrator command-line utility, commadmin.
Run the Delegated Administrator configuration program, config-commda.

This session runs the Delegated Administrator configuration program, config-commda. In this configuration, Delegated Administrator is deployed to Web Server 7.0. Next, you use Delegated Administrator to create user accounts.

The session accepts the default values for the configuration attributes. The session selects Web Server as the web container. Note that the Web Server configuration and administration details appear twice. This is because both the Delegated Administrator console and the Delegated Administrator server must be configured to a web container.

Before you run the Delegated Administrator configuration program, be sure that Web Server is running.

# ./config-commda -nodisplay

  Specify the directory in which the configuration and data files should be
  installed [/var/opt/sun/comms/da] {"<" goes back, "!" exits}:



Delegated Administrator components showing a checked box will be configured.
Please change selection accordingly.


[X]  1  Delegated Administrator Utility    0 bytes
[X]  2  Delegated Administrator Console    0 bytes
[X]  3  Delegated Administrator Server    0 bytes

  To check a particular component, enter its number, or 0 when you are
  finished [0] {"<" goes back, "!" exits}:
Checking Disk Space


Please enter the Access Manager Host name and Port number

  Hostname [niag1-z4] {"<" goes back, "!" exits}:
  Port [8080] {"<" goes back, "!" exits}:

Please enter the default domain that will be used if none is specified on the
command line.

  Enter Default Domain [example.mydomain.com] {"<" goes back, "!" exits}

Please enter the default SSL Port that the Delegated Administrator Utility will
use if none is specified.


The default SSL Port if none is specified to the Delegated Administrator Utility

  Enter Default SSL Port [443] {"<" goes back, "!" exits}
You can deploy Delegated Administrator Console on Web Server or Application
Server
  Type WEB, WEB7, APP7 or APP8 to specify your web container (WEB, WEB7, APP7
  or APP8)  [WEB] {"<" goes back, "!" exits}? WEB7

Web Server Configuration Details

Specify the local Web Server instance details used by the configurator to
configure Delegated Administrator Console on Web Server. Enter the following
web server instance details to configure Delegated Administrator Console:

Install Root Directory Name: Enter the local directory in which Web Server is
installed.

Instance Root Directory: Enter the local directory in which Web Server
instances are created.

Server Instance Identifier: Enter the Web Server Identifier for which Delegated
Administrator Console is to be configured.

Virtual Server Identifier: Enter the Virtual Server Identifier for which
Delegated Administrator Console is to be configured.

HTTP Port Number: Enter the Web Server port number where HTTP service is
available.

  Enter Web Server Install Root Directory [/opt/SUNWwbsvr7]:
  Enter Web Server Instance Root Directory [/var/opt/SUNWwbsvr7]:
  Enter Web Server Instance Identifier [niag1-z4.example.mydomain.com]:
  Enter Virtual Server Identifier [niag1-z4.example.mydomain.com]:
  Enter Web Server HTTP Port [80]:
Please Wait: Verifying whether the Web Server Instance connection is alive


Web Server: Administration Instance Details

Enter the following Administration Server instance details to configure
Delegated Administrator Console:

Administration Server Port: Enter the Administration Server port number.

Administrator User ID: Enter the administrator user identifier.

Administrator Password: Enter the administrator password.

Secure Administration Server Instance: Specify whether the Web Server's
Administration Instance is running in secure mode.

  Enter the Administration Server Port [8800]:
  Enter the Administrator User ID [admin]:
  Enter the Administrator Password []:
  Is the Administration Server instance running in the secure mode  [no]?
Please Wait: Verifying whether the Administration Server instance connection is
alive

Information

You have specified that the Web Server's Administration Server instance is
running in the normal mode.


Please enter the domain separator for user logon authentication


The domain separator for user logon authentication

  Enter domain separator [@] {"<" goes back, "!" exits}

Please enter the Access Manager Base Directory

  Access Manager Base Directory [/opt/SUNWam] {"<" goes back, "!" exits}:


Web Server Configuration Details

Specify the local Web Server instance details used by the configurator to
configure Delegated Administrator Server on Web Server. Enter the following web
server instance details to configure Delegated Administrator Server:

Install Root Directory Name: Enter the local directory in which Web Server is
installed.

Instance Root Directory: Enter the local directory in which Web Server
instances are created.

Server Instance Identifier: Enter the Web Server Identifier for which Delegated
Administrator Server is to be configured.

Virtual Server Identifier: Enter the Virtual Server Identifier for which
Delegated Administrator Server is to be configured.

HTTP Port Number: Enter the Web Server port number where HTTP service is
available.

  Enter Web Server Install Root Directory [/opt/SUNWwbsvr7]:
  Enter Web Server Instance Root Directory [/var/opt/SUNWwbsvr7]:
  Enter Web Server Instance Identifier [niag1-z4.example.mydomain.com]:
  Enter Virtual Server Identifier [niag1-z4.example.mydomain.com]:
  Enter Web Server HTTP Port [80]:
Please Wait: Verifying whether the Web Server Instance connection is alive


Web Server: Administration Instance Details

Enter the following Administration Server instance details to configure
Delegated Administrator Server:

Administration Server Port: Enter the Administration Server port number.

Administrator User ID: Enter the administrator user identifier.

Administrator Password: Enter the administrator password.

Secure Administration Server Instance: Specify whether the Web Server's
Administration Instance is running in secure mode.

  Enter the Administration Server Port [8800]:
  Enter the Administrator User ID [admin]:
  Enter the Administrator Password []:
  Is the Administration Server instance running in the secure mode  [no]?
Please Wait: Verifying whether the Administration Server instance connection is
alive

Information

You have specified that the Web Server's Administration Server instance is
running in the normal mode.


Please specify the Directory (LDAP) server. The Ldap Server URL
is an url link to the directory server on which the console
component is configured. The url should  be in the format of
ldap://<hostname>:<port>. e.g.

ldap://ldapserver.mycompany.com:390.

The default bind DN is the distinguished name for the directory manager. Also
note that you should point the URL at the master Directory Server and not a
replica, as you normally would not be able to write to the replica.

  LdapURL [ldap://niag1-z4.example.mydomain.com:389]:
  Bind As [cn=Directory Manager]:
  Password:

Please enter the Access Manager Admin User and Password. The username is hard
coded.

Username: amadmin

  Password:

Please enter the Access Manager Internal LDAP Authentication Password. The
username is hard coded.

Username: amldapuser

  Password:

The Organization DN will be the LDAP subtree under which all email users and
groups that belong to the default email domain are located. Note that the DN
must be located under the user/group suffix.

  Enter Organization DN [o=example.mydomain.com,o=ugdata] {"<" goes back, "!"
  exits}
Please enter the User and Password for a top level administrator to be created
in the Default Organization Name

  Username [admin]:
  Password:
  Confirm Password:

Please choose whether to load sample Service Packages and Organizations into
Directory

  Do you want to load sample service packages [Y]?

  Do you want to load sample organizations [Y]?

  Please enter preferred mailhost for the sample organizations [niag1-z4] {"<"
  goes back, "!" exits} niag1-z4.example.mydomain.com

Checking disk space...


The following items for the product Delegated Administrator will be configured:

Product: Delegated Administrator
Location: /opt/SUNWam
Space Required: 0 bytes
--------------------------------
Delegated Administrator Utility
Delegated Administrator Console
Delegated Administrator Server


Ready to Configure

1. Configure Now
2. Start Over
3. Exit Configure Program

  What would you like to do [1] {"<" goes back, "!" exits}? 1
Starting Task Sequence

All Tasks Passed. Please check install log /opt/sun/comms/da/install/commda-
config_20071220190220.log for further details.


The web server configuration was modified. For the changes to take effect, you
must restart the Web Server.

  <Press ENTER to continue> {"!" exits}


To enable mail and calendar service on the default domain,

please use commadmin domain modify -S mail -S cal -H mailhost


after restarting the web container.  Please consult documentation for details.

  <Press ENTER to continue> {"!" exits}


Configuration Details:

    Product                  Result     More Information
1.  Delegated Administrator  Installed  Available

2. Done

  Enter the number corresponding to the desired selection for more
  information, or enter 2 to continue [2] {"!" exits}:
mv /opt/sun/comms/da/install/saveState20071220190214 /opt/sun/comms/da/install/commda-config_20071220190220/saveState
Copying factory settings to /opt/sun/comms/da/data/setup
Stop and restart Web Server.
# /var/opt/SUNWwbsvr7/https-niag1-z4.example.mydomain.com/bin/stopserv
server not responding to exit command
killing process group
# /var/opt/SUNWwbsvr7/https-niag1-z4.example.mydomain.com/bin/startserv
Sun Java System Web Server 7.0U1 B07/18/2007 15:51
info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_12] from [Sun Microsystems Inc.]
info: WEB0100: Loading web module in virtual server [niag1-z4.example.mydomain.com] at [/amserver]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [niag1-z4.example.mydomain.com] at [/ampassword]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [niag1-z4.example.mydomain.com] at [/amcommon]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [niag1-z4.example.mydomain.com] at [/amconsole]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [niag1-z4.example.mydomain.com] at [/da]
info: WEB0100: Loading web module in virtual server [niag1-z4.example.mydomain.com] at [/commcli]
info: url: jar:file:/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar!/com/sun/mfwk/config/MfConfig.class
info: "mfwk.multicast.disableloopback" set to false
info: url: jar:file:/opt/SUNWmfwk/lib/mfwk_instrum_tk.jar!/com/sun/mfwk/config/MfConfig.class
info: LogFile is: //var/opt/SUNWmfwk/logs/instrum.%g
warning: Warning: unable to initialize log file!
warning: Couldn't get lock for //var/opt/SUNWmfwk/logs/instrum.%g
info: group = 227.227.227.1, port  = 54320
info: Set Time-to-live to 0
info: join Group /227.227.227.1
info: Starting listening thread
info: sends initial RESP message in SDK
info: Packet received
Create user accounts with the Delegated Administrator command-line utility, commadmin.

Before adding user accounts with the commadmin utility, the session must add mail and calendar service to the default domain configured by the Delegated Administrator configuration program. To do this, use the commadmin domain modify command.

Next, the session runs the commadmin user create command to add three user accounts to the LDAP directory.

# ./commadmin domain modify -D admin -w adminpass -X niag1-z4.example.mydomain.com -H niag1-z4.example.mydomain.com -n example.mydomain.com -d example.mydomain.com -p 80 -S mail,cal -T "America/Los_Angeles"


# ./commadmin user create -D admin -w adminpass -n example.mydomain.com -F Test  -L User -l testuser -p 80 -E testuser@example.mydomain.com -W demo -S mail,cal
OK

# ./commadmin user create -D admin -w adminpass -n example.mydomain.com -F Postmaster  -L User -l postmaster-user -p 80 -E postmaster-user@example.mydomain.com -W demo -S mail,cal
OK

# ./commadmin user create -D admin -w adminpass -n example.mydomain.com -F John  -L Doe -l jhawk -p 80 -E John.Doe@example.mydomain.com -W demo -S mail,cal
OK

Configure Messaging Server 7.0.

This session configures Messaging Server; it comprises the following steps:

  • Configure DNS setup.
  • Disable Sendmail.
  • Configure Messaging Server by running the configuration program, configure.
  • Start Messaging Server.
  • Send a test message via telnet.
  • Enable logging on the MTA.
  • Configure the http port.
Configure DNS setup.

A high-quality caching DNS server on the local network is a requirement for a production deployment of Messaging Server. Messaging Server depends heavily on the responsiveness and scalability of the DNS server.

This step ensures that the DNS setup is properly configured, and that it specifies how to route to hosts that are not on the local subnet. The /etc/nsswitch.conf and /etc/resolve.conf files are edited.

# vi /etc/nsswitch.conf
"/etc/nsswitch.conf" 43 lines, 1228 characters
#
# /etc/nsswitch.nis:
#
# An example file that could be copied over to /etc/nsswitch.conf; it
# uses NIS (YP) in conjunction with files.
#
# "hosts:" and "services:" in this file are used only if the
# /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports.

# NIS service requires that svc:/network/nis/client:default be enabled
# and online.

# the following two lines obviate the "+" entry in /etc/passwd and /etc/group.
passwd:     files nis
group:      files nis

# consult /etc "files" only if nis is down.
hosts:      dns nis [NOTFOUND=return] files

# Note that IPv4 addresses are searched for in all of the ipnodes databases
# before searching the hosts databases.
ipnodes:    nis [NOTFOUND=return] files

# vi /etc/resolv.conf
"/etc/resolv.conf" [New file]
domain example.mydomain.com
nameserver 192.168.100.149
nameserver 192.168.100.150
search example.mydomain.com west.sesta.com sesta.com
Disable Sendmail.

Sendmail must be disabled to allow Messaging Server to send and receive mail properly.

# svcadm disable Sendmail
Configure Messaging Server 7.0.

This step runs the configure program. 

# cd /opt/sun/comms/messaging/sbin

# ./configure -nodisplay

  Enter fully qualified host name [niag1-z4.example.mydomain.com] {"<" goes back,
  "!" exits}

  Directory to install Messaging Server configuration and data files
  [/var/opt/sun/comms/messaging] {"<" goes back, "!" exits}:

[X]  1  Message Transfer Agent    0 bytes
[X]  2  Message Store    0 bytes
[X]  3  Webmail Server    0 bytes
[ ]  4  Messaging Multiplexor    0 bytes

  To check a particular component, enter its number, or 0 when you are
  finished [0] {"<" goes back, "!" exits}:

  Enter Username [mailsrv]: dsuser
  Enter Unix Group [mail]: dsuser

  User/Group Server LdapURL [ldap://niag1-z4.example.mydomain.com:389] {"<" goes
  back, "!" exits}:
  Bind As [cn=Directory Manager] {"<" goes back, "!" exits}:
  Password {"<" goes back, "!" exits}: adminpass

  Enter Postmaster email address [] {"<" goes back, "!" exits} postmaster-user@example.mydomain.com

  Enter password [] {"<" goes back, "!" exits}:  adminpass
  Re-enter password to verify [] {"<" goes back, "!" exits}:  adminpass

  Enter Email Default Domain [example.mydomain.com] {"<" goes back, "!" exits}

  Enter Organization DN [o=example.mydomain.com,o=ugdata] {"<" goes back, "!"
  exits}

The following items for the product Messaging Server will be configured:

Product: Messaging Server
Location: /var/opt/sun/comms/messaging
Space Required: 0 bytes
--------------------------------------
Message Transfer Agent
Message Store
Webmail Server

Ready to Configure

1. Configure Now
2. Start Over
3. Exit Configure Program

  What would you like to do [1] {"<" goes back, "!" exits}?
Start Messaging Server with the ./start-msg command.
# ./start-msg
Connecting to watcher ...
Launching watcher ... 24020
Starting store server .... 24021
Checking store server status ..... ready
Starting purge server .... 24022
Starting imap server .... 24023
Starting pop server .... 24024
Starting http server .... 24025
Starting sched server ... 24026
Starting dispatcher server .... 24028
Starting job_controller server .... 24034
Send a test message through Messaging Server via telnet.
# telnet . 25
Trying 0.0.0.0...
Connected to ..
Escape character is '^]'.
220 niag1-z4.example.mydomain.com -- Server ESMTP (Sun Java(tm) System Messaging Server 7.0-0.01 32bit (built Nov 21 2007))
ehlo example.mydomain.com
250-niag1-z4.example.mydomain.com
250-8BITMIME
250-PIPELINING
250-CHUNKING
250-DSN
250-ENHANCEDSTATUSCODES
250-EXPN
250-HELP
250-XADR
250-XSTA
250-XCIR
250-XGEN
250-XLOOP A0DCB6E4B6F1EA64A997266D291AAE2C
250-ETRN
250-NO-SOLICITING
250 SIZE 0
mail from: John.Doe@sesta.com
250 2.5.0 Address Ok.
rcpt to: John.Doe@example.mydomain.com
250 2.1.5 John.Doe@example.mydomain.com OK.
data
354 Enter mail, end with a single ".".
Subject: Welcome to Messaging Server 7.0!!

I hope everything works as planned!

Jon
.
250 2.5.0 Ok.
quit
221 2.3.0 Bye received. Goodbye.
Connection to . closed by foreign host.
#

# telnet . 110
Trying 0.0.0.0...
Connected to ..
Escape character is '^]'.
+OK niag1-z4.example.mydomain.com POP3 service (Sun Java(tm) System Messaging Server 7.0-0.01 32bit (built Nov 21 2007))
user jhawk
+OK Name is a valid mailbox
pass demo
+OK Maildrop ready
list
+OK scan listing follows
1 713
.
retr 1
+OK 713 octets
Return-path: <John.Doe@sesta.com>red.
Received: from example.mydomain.com ([127.0.0.1]) by niag1-z4.example.mydomain.com
(Sun Java(tm) System Messaging Server 7.0-0.01 32bit (built Nov 21 2007))
with ESMTP id <0JU200I02YYJJK00@niag1-z4.example.mydomain.com> for
John.Doe@example.mydomain.com; Thu, 03 Jan 2008 10:21:34 -0800 (PST)
Original-recipient: rfc822;John.Doe@example.mydomain.com
From: John.Doe@sesta.com
Date-warning: Date header was inserted by niag1-z4.example.mydomain.com
Date: Thu, 03 Jan 2008 10:21:24 -0800 (PST)
Message-id: <0JU200I03YYVJK00@niag1-z4.example.mydomain.com>
Subject: Welcome to Messaging Server 7.0!!
To: Undisclosed recipients: ;

I hope everything works as planned!

Jon
.
quit
+OK
Connection to . closed by foreign host.
#
Enable logging on the MTA.
# cd /var/opt/sun/comms/messaging/config/
# cp imta.cnf imta.cnf.orig
# vi imta.cnf

!
! part II : channel blocks
!
defaults logging notices 1 2 4 7 copywarnpost copysendpost postheadonly noswitchchannel immnonurgent maxjobs 7 defaulthost example.mydomain.com example.mydomain.com

!
! delivery channel to local /var/mail store
l subdirs 20 viaaliasrequired maxjobs 7
niag1-z4.example.mydomain.com
Configure the http port.

This step reconfigures the mshttpd port number from the default value of 80 to 85. It configures this value by modifying the configutil service.http.port option.

#  ./configutil -o service.http.port -v 85
OK SET
# ./stop-msg
Connecting to watcher ...
shutting down all servers...
Stopping job_controller server 24034 .... done
Stopping dispatcher server 24028 ... done
Stopping sched server 24026 ... done
Stopping http server 24025 ... done
Stopping pop server 24024 ... done
Stopping imap server 24023 ... done
Stopping purge server 24022 ... done
Stopping store server 24021 .... done
stopping watcher process 24020 ... done
# ./start-msg
Connecting to watcher ...
Launching watcher ... 24367
Starting store server .... 24368
Checking store server status .... ready
Starting purge server .... 24370
Starting imap server .... 24371
Starting pop server .... 24372
Starting http server .... 24373
Starting sched server ... 24374
Starting dispatcher server .... 24376
Starting job_controller server .... 24382
# telnet . 85
Trying 0.0.0.0...
Connected to ..
Escape character is '^]'.
GET / HTTP/1.1

HTTP/1.1 404
Date: Thu, 03 Jan 2008 19:15:13 GMT
Content-type: text/html
Content-length: 108
Last-modified: Thu, 03 Jan 2008 19:15:13 GMT
Pragma: no-cache
Expires: 0
Cache-Control: no-cache

Configure Calendar Server 6.3 Update 2.

This session runs the csconfigurator.sh utility to configure Calendar Server. The Calendar Server front end and back end are both configured into this zone.

# cd /opt/sun/comms/calendar/SUNWics5/cal/sbin/
# ./csconfigurator.sh -nodisplay

User Preferences Directory
  LDAP Server Host Name [niag1-z4.example.mydomain.com]:
  LDAP Server Port [389]:
  Directory Manager DN [cn=Directory Manager]:
  Directory Manager Password []: adminpass

Here is a list of the existing domains

1. abc.com
2. example.mydomain.com
3. siroe.com
4. <New Default domain>

  Select the default domain from the list above [2]: 2
  Calendar administrator user name [calmaster]:
  Calendar administrator password []: adminpass
  Calendar administrator email address [root@example.mydomain.com]: calmaster-user@example.mydomain.com


Is this user also the site administrator?

1. Yes
2. No

  Enter your choice [1]:

Please Wait: The configuration program is verifying the credentials for the
Calendar administrator



User calmaster@example.mydomain.com could not be found on LDAP server niag1-z4.example.mydomain.com.

1. Create it
2. Choose New

  Enter the number corresponding to your choice  [1]

Front End / Back End settings


1. Yes
2. No

  Set up a Front End / Back End deployment [2] 1

1. Front End
2. Back End
3. Both

  Set up this server as  [1] 3
  Back end service port [59779]
  Hostname of the back-end server [] niag1-z4.example.mydomain.com
  IP address of the back-end server [192.168.100.22]
  Port on which to contact the back-end server [59779]

1. View the back-end servers list
2. Add a back-end server
3. Set the default backend server
4. Edit one of the back-end server
5. Remove a back-end server
6. Validate your choices and go to next configuration panel

  What do you want to do [6]? 1

1. niag1-z4.example.mydomain.com (192.168.100.22) on port 59779 *

1. View the back-end servers list
2. Add a back-end server
3. Set the default backend server
4. Edit one of the back-end server
5. Remove a back-end server
6. Validate your choices and go to next configuration panel

  What do you want to do [6]?

Please Wait: The configuration program is checking that the local DWP service
port is available

Email and Email Alarms

  Administrator Email Address [calmaster-user@example.mydomain.com]:
  SMTP Host Name [niag1-z4.example.mydomain.com]

Please Wait: The configuration program is verifying that the SMTP Server system
is reachable on the network.

Runtime configuration

  Service Port [80] 2080
  Maximum Sessions [5000]
  Maximum Threads [20]
  Number of server processes [1] 5
  Runtime User ID [icsuser] dsuser
  Runtime Group ID [icsgroup] dsuser

1. Yes
2. No

  Start after sucessful configuration [2] 1

1. Yes
2. No

  Start on system startup [1]


Please Wait: The configuration program is checking that the local web service
port is available.
Please Wait: Verifying User...
Directories to store configuration and data files

  Config Directory [/etc/opt/sun/comms/calendar/SUNWics5/config]:
  Database Directory [/var/opt/sun/comms/calendar/SUNWics5/csdb]:
  Attachment store Directory [/var/opt/sun/comms/calendar/SUNWics5/astore]:
  Logs Directory [/var/opt/sun/comms/calendar/SUNWics5/logs]:
  Temporary Files Directory [/var/opt/sun/comms/calendar/SUNWics5/tmp]:

The directory /etc/opt/sun/comms/calendar/SUNWics5/config" does not exist.



Do you want to create it now or choose another directory?

1. Create Directory
2. Choose New

  Enter the number corresponding to your choice  [1]

The directory /var/opt/sun/comms/calendar/SUNWics5/csdb" does not exist.



Do you want to create it now or choose another directory?

1. Create Directory
2. Choose New

  Enter the number corresponding to your choice  [1]

The directory /var/opt/sun/comms/calendar/SUNWics5/astore" does not exist.



Do you want to create it now or choose another directory?

1. Create Directory
2. Choose New

  Enter the number corresponding to your choice  [1]

The directory /var/opt/sun/comms/calendar/SUNWics5/logs" does not exist.



Do you want to create it now or choose another directory?

1. Create Directory
2. Choose New

  Enter the number corresponding to your choice  [1]

The directory /var/opt/sun/comms/calendar/SUNWics5/tmp" does not exist.



Do you want to create it now or choose another directory?

1. Create Directory
2. Choose New

  Enter the number corresponding to your choice  [1]

Archive and Hot Backup configuration


1. enable
2. disabled

  Do you want to enable archiving [1]?
  Enter the path where you want archives to be stored
  [/var/opt/sun/comms/calendar/SUNWics5/csdb/archive]
  What is the minimum number of days to keep these archives [3]?
  What is the maximum number of days to keep these archives [6]?

1. enable
2. disabled

  Do you want to enable hotbackup [1]?
  Please enter the path where you want hot backups to be  stored
  [/var/opt/sun/comms/calendar/SUNWics5/csdb/hotbackup]
  What is the minimum number of days to keep these hot backups [3]?
  What is the maximum number of days to keep these hot backups [6]?


The directory /var/opt/sun/comms/calendar/SUNWics5/csdb/archive" does not exist.



Do you want to create it now or choose another directory?

1. Create Directory
2. Choose New

  Enter the number corresponding to your choice  [1]

The directory /var/opt/sun/comms/calendar/SUNWics5/csdb/hotbackup" does not
exist.



Do you want to create it now or choose another directory?

1. Create Directory
2. Choose New

  Enter the number corresponding to your choice  [1]

Checking disk space...


The following items for the product Sun Java(tm) System Calendar Server will be
configured:

Product: Sun Java(tm) System Calendar Server
Location: /opt/sun/comms/calendar/SUNWics5
Space Required: 0 bytes
--------------------------------------------
CalServer6


Ready to Configure

1. Configure Now
2. Start Over
3. Exit Configure Program

  What would you like to do [1]?

Configure Instant Messaging Server 7.3.

This session runs the Instant Messaging configure utility to configure Instant Messaging. 

# cd /opt/sun/comms/im/SUNWiim/

# ./configure -nodisplay

# ./configure -nodisplay

Java Accessibility Bridge for GNOME loaded.

Select all components you wish to configure.

     1. [X] Server components
     2. [X] Client components

  Enter the index of a component to change its state, or 0 when you are
  finished [0]


User Management Options

  Use Access Manager for Single-Sign-On [no]:
  Use Access Manager for Policy [no]:

  Instant Messaging user properties can be maintained using one of the
following storage systems:

     1. File System
     2. LDAP Directory
  Enter the number corresponding to your choice [2]:


Runtime Options

  Runtime User ID [inetuser]: dsuser
  Runtime Group ID [inetgroup]: dsuser

  Runtime Directory [/var/opt/sun/comms/im]:


Network Access Points

  Domain Name [example.mydomain.com]:
  XMPP Port [5222]:
  Multiplexed XMPP Port [45222]:
  Disable Server (enable only multiplexor) [no]?



Directory Server Options

  LDAP Host Name [niag1-z4.example.mydomain.com]:    LDAP Port Number [389]:
  Base DN [dc=example,dc=mydomain,dc=com]: o=ugdata
  Bind DN []: cn=Directory Manager
  Bind Password:


Mail Server Options

  Enable Email Integration [yes]
  SMTP Server Host Name [niag1-z4.example.mydomain.com]:
  Do you want to enable Email Archiving [yes]?


Messenger Resources Deployment Options

  Do you want to deploy Instant Messenger Resources  [yes]?

  Messenger Resources Code Base URL [http://niag1-z4.example.mydomain.com:80/im]:

The following information is used to invoke your web container's deployment
interfaces.  Your web container may not require all fields to be filled.
  Web Administration URL [https://niag1-z4.example.mydomain.com:4849/]:
  Web Administrator User ID [admin]:
  Web Administrator Password:
Contacting admin server and processing the supplied information


Verify the configuration information provided.
Unable to obtain information from admin server using these.

  <Press ENTER to continue>



Messenger Resources Deployment Options

  Do you want to deploy Instant Messenger Resources  [yes]? no

Please enter the relevent info to configure the HTTP Gateway.

  Do you want to deploy the XMPP/HTTP Gateway  [yes]? no


Calendar Agent configuration

  Do you want to enable calendar integration [no]? yes
  Notification Server Hostname [niag1-z4.example.mydomain.com]:
  Notification Server Port [57997]:
  Calendar alarm URL [enp:///ics/customalarm]:


Startup Options

  Start services after successful configuration [yes]?
  Start services on system startup [yes]?

Deploy and Configure Convergence 1.0. 

Script started on Wed 09 Apr 2008 01:57:17 PM PDT
# pwd
/opt/sun/comms/iwc/sbin
# ./init-config -nodisplay -saveState /tmp/iwc_in.NEW
/usr/jdk/entsys-j2se/bin/java -Djava.library.path=/opt/sun/comms/iwc/lib -Djava.awt.headless=true -classpath /opt/sun/comms/iwc/lib:/usr/jdk/entsys-j2se/lib/classes.zip config-iwc -saveState /opt/sun/comms/iwc/install/saveState20080409135736 -nodisplay
Finished Loading Default Properties...


You are running the configuration program for Sun Convergence. This program
asks you to supply configuration preference settings that it uses to configure
the server.

The configuration program consists of one or more selections that provide you
with information and let you enter preferences that determine how Sun
Convergence is configured.

When you are presented with the following question, the configuration process
pauses to allow you to read the information that has been presented. When you
are ready, press Enter to continue.

 <Press ENTER to Continue>

Some questions require more detailed information that you are required to type.
The question may have a default value that is displayed inside of brackets [].
For example, the following question has a default answer of yes:

   Are you sure? [yes]

If you want to accept the default answer, press only the Enter key (which on
some keyboards is labeled Return).

If you want to provide a different answer, type it at the command prompt and
then press Enter.

If yes is your answer, type yes or y at the command prompt and press Enter. If
your answer is no, type no or n and press Enter.

At any point in the configuration program, if you wish to exit the
configuration program midway, press the ! key and you will be given the option
to exit or continue.

    <Press ENTER to Continue> 

Welcome to the Sun Convergence Configuration Program.

    <Press ENTER to Continue>

Please specify the directory in which the configuration and data files should
be installed. It is recommended that you configure the Sun Convergence in the
directory suggested by this configurator program.

   Specify the directory in which the configuration and data files should be
   installed [/var/opt/sun/comms/iwc] {"<" goes back, "!" exits}: 

The directory "/var/opt/sun/comms/iwc" does not exist.



Do you want to create it now or choose another directory?

1. Create Directory
2. Choose New

   Enter the number corresponding to your choice  [1] {"<" goes back, "!"
   exits} 

Please wait for the components to be loaded...


Loading components...


Select the components to be configured.


 [X]  1  Mail Service    0 bytes
 [X]  2  Calendar Service    0 bytes
 [X]  3  Instant Messaging Service    0 bytes

   To select a component, enter its number, or 0 when you are done [0] {"<"
   goes back, "!" exits}: 
Checking Disk Space

Please verify that the host name and DNS domain name mentioned in the fields
below are correct for this system, then click Next. The configuration program
will again attempt to establish a network connection to this system using these
values.

The host name or DNS domain name field will be blank if the configuration
program is unable to detect its value.
   Host Name [niag1-z4] {"<" goes back, "!" exits}: 
   DNS Domain Name [example.mydomain.com] {"<" goes back, "!" exits}: 


Application Server Configuration Details

Specify the local Application Server instance details used by the configurator
to configure Sun Convergence on Application Server. Enter the following
application server instance details to configure Sun Convergence:

Install Directory: Enter the local directory in which the Application Server is
installed.

Domain Directory: Enter the Application Server domain directory.

Document Root Directory: Enter the Application Server document root directory.

Server Target Name: Enter the Application Server Name for which the Sun
Convergence is to be configured.

Virtual Server Identifier: Enter the Virtual Server Identifier for which the
Sun Convergence is to be configured.

Server Instance HTTP Port: Enter the Application Server port number where HTTP
service is available.

   Enter Application Server Install Directory [/opt/SUNWappserver] {"<" goes
   back, "!" exits}: 
   Enter Application Server Domain Directory
   [/opt/SUNWappserver/domains/domain1] {"<" goes back, "!" exits}: 
   Enter Application Server Document Root Directory
   [/opt/SUNWappserver/domains/domain1/docroot] {"<" goes back, "!" exits}: 
   Enter Application Server Instance HTTP Port [8080] {"<" goes back, "!"
   exits}: 
Please Wait: Verifying whether the Application Server Instance connection is
alive


Application Server: Administration Instance Details

Specify Application Server's Administration instance details used by the
configurator to configure Sun Convergence on Application Server.

   Enter the Administration Server Port [4848] {"<" goes back, "!" exits}: 
   Enter the Administrator User ID [admin] {"<" goes back, "!" exits}: 
   Enter the Administrator Password [] {"<" goes back, "!" exits}: 
   Is the Administration Server instance running in the secure mode  [no] {"<"
   goes back, "!" exits}? 
Please Wait: Verifying whether the Administration Server instance connection is
alive

Information

You have specified that the Application Server's Administration Server instance
is running in the normal mode.



URI Path

Enter the URI Path for Sun Convergence.

URI Path: Enter the URI Path where the Sun Convergence is to be deployed.

Note: Ensure you have specified a new URI Path. If there exists a web
application already configured at the specified URI, it will be deleted before
Sun Convergence is deployed.

   Enter URI Path for Sun Convergence [/iwc] {"<" goes back, "!" exits}: 


Do you want Hosted Domain support ?

This step enables you to select Hosted Domain support.

   Do you want Hosted Domain support for Sun Convergence  [yes] {"<" goes back,
   "!" exits}? 
INFO: Hosted Domain support will be "enabled"

Enter the User/Group LDAP Server details. The User/Group LDAP Server URL
should  be in the format ldap://<hostname>:<port>. For example, ldap:
//ldapserver.siroe.com:389

   Ldap URL [ldap://niag1-z4.example.mydomain.com:389] {"<" goes back, "!" exits}: 
   Bind DN [cn=Directory Manager] {"<" goes back, "!" exits}: 
   Bind Password {"<" goes back, "!" exits}: 



DC Tree Suffix

Specify the base distinguished name for the DC Tree Suffix. This suffix is used
by Sun Convergence to search for configured hosted domains.

   Enter DC Tree Suffix [o=mailQA] {"<" goes back, "!" exits}: 

Please enter the Default Domain Name


Enter the Default Domain Name. This is the default domain that will be used
when a user logs in without specifying a domain name.

   Enter the Default Domain Name [example.mydomain.com] {"<" goes back, "!" exits} 


Mail Service Configuration Details

Enter the Webmail Server host name, port number, whether to use SSL, Admin User
ID and password.

   Enter the Webmail Server Host Name [niag1-z4.example.mydomain.com] {"<" goes
   back, "!" exits}: 
   Enter the Webmail Server Port Number [8990] {"<" goes back, "!" exits}: 
   Is the webmail server running in secure mode [no] {"<" goes back, "!"
   exits}? 
INFO: Access to webmail will be in non-SSL mode
   Enter the Webmail Server Admin UserID [admin] {"<" goes back, "!" exits}: 
   Enter the Webmail Admin User Password [] {"<" goes back, "!" exits}: Please Wait: Verifying whether the Webmail Server Instance connection is alive


Calendar Service Configuration Details

Enter the Calendar Server host name, port number, whether to use SSL,
administrator ID and password.

   Enter the Calendar Server Host Name [niag1-z4.example.mydomain.com] {"<" goes
   back, "!" exits}: 
   Enter the Calendar Server Port Number [80] {"<" goes back, "!" exits}: 98
   Is the calendar server running in secure mode [no] {"<" goes back, "!"
   exits}? 
   Enter the Calendar Server Administrator User ID [calmaster] {"<" goes back,
   "!" exits} 
   Enter the Calendar Server Administrator Password [] {"<" goes back, "!"
   exits} 

INFO: Access to calendar server will be in non-SSL mode
Please Wait: Verifying whether the Calendar Server Instance connection is alive


Instant Messaging Service Configuration Details

Enter the IM Server default domain, host name, port number, httpbind component
JID and password, and avatar component JID and password.

   Enter the Server Domain Name [example.mydomain.com] {"<" goes back, "!" exits}: 
   Enter the Server Host Name [niag1-z4.example.mydomain.com] {"<" goes back, "!"
   exits}: 
   Enter the Server Port Number [5222] {"<" goes back, "!" exits}: 
   Enter the httpbind compoent JID [niag1-z4.httpbind.example.mydomain.com] {"<"
   goes back, "!" exits}: 
   Enter the httpbind Component Password [] {"<" goes back, "!" exits}: 
   Enter the avatar component JID [niag1-z4.avatar.example.mydomain.com] {"<" goes
   back, "!" exits}: 
   Enter the avatar Component Password [] {"<" goes back, "!" exits}: 


Please enter the Sun Convergence Administrator User ID and Password.

   Username [admin]: 
   Password: 
   Password Again: 

Checking disk space...


The following items for the product Sun Convergence will be configured:

Product: Sun Convergence
Location: /var/opt/sun/comms/iwc
Space Required: 0 bytes
--------------------------------
Mail Service
Calendar Service
Instant Messaging Service


Ready to Configure

1. Configure Now
2. Start Over
3. Exit Configure Program

   What would you like to do [1]? 
Starting Task Sequence
===== Wed Apr 09 13:59:37 PDT 2008 ===== 
Running /bin/rm -rf /opt/sun/comms/iwc/config /opt/sun/comms/iwc/data
/opt/sun/comms/iwc/log

===== Wed Apr 09 13:59:38 PDT 2008 ===== 
Running /opt/sun/comms/iwc/lib/devinstall -l schema2native:pkgcfg:config:iwc -v
-m -i /opt/sun/comms/iwc/lib/config-templates/config.ins
/opt/sun/comms/iwc/lib/config-templates /opt/sun/comms/iwc/lib

===== Wed Apr 09 13:59:38 PDT 2008 ===== 
Running /bin/sh -c echo fqRWiPL1h6c9INw7GkDq5g== >
/var/opt/sun/comms/iwc/config/.ngc_enc

===== Wed Apr 09 13:59:38 PDT 2008 ===== 
Running /bin/sh -c /opt/sun/comms/iwc/sbin/config-appsvr deploy ********

===== Wed Apr 09 14:01:07 PDT 2008 ===== 
Running /bin/rm -rf
/opt/SUNWappserver/domains/domain1/docroot/iwc_static/c11n_sample
/opt/SUNWappserver/domains/domain1/docroot/iwc_static/js
/opt/SUNWappserver/domains/domain1/docroot/iwc_static/layout

===== Wed Apr 09 14:01:08 PDT 2008 ===== 
Running /usr/bin/unzip -q /opt/sun/comms/iwc/lib/jars/iwc-client.zip -d
/opt/SUNWappserver/domains/domain1/docroot

===== Wed Apr 09 14:01:12 PDT 2008 ===== 
Running /bin/sh -c /bin/mkdir -p /opt/sun/comms/iwc/install/Iwc-
config_20080409135740

===== Wed Apr 09 14:01:12 PDT 2008 ===== 
Running /bin/sh -c /bin/cp -p /opt/sun/comms/iwc/lib/config-templates/IwcCfg.
properties /opt/sun/comms/iwc/install/Iwc-config_20080409135740/IwcCfg.
properties

Sequence Completed

PASSED: /bin/rm -rf /opt/sun/comms/iwc/config /opt/sun/comms/iwc/data
/opt/sun/comms/iwc/log : status = 0

PASSED: /opt/sun/comms/iwc/lib/devinstall -l schema2native:pkgcfg:config:iwc -v
-m -i /opt/sun/comms/iwc/lib/config-templates/config.ins
/opt/sun/comms/iwc/lib/config-templates /opt/sun/comms/iwc/lib : status = 0

PASSED: /bin/sh -c echo fqRWiPL1h6c9INw7GkDq5g== >
/var/opt/sun/comms/iwc/config/.ngc_enc : status = 0

PASSED: /bin/sh -c /opt/sun/comms/iwc/sbin/config-appsvr deploy ******** :
status = 0

PASSED: /bin/rm -rf
/opt/SUNWappserver/domains/domain1/docroot/iwc_static/c11n_sample
/opt/SUNWappserver/domains/domain1/docroot/iwc_static/js
/opt/SUNWappserver/domains/domain1/docroot/iwc_static/layout : status = 0

PASSED: /usr/bin/unzip -q /opt/sun/comms/iwc/lib/jars/iwc-client.zip -d
/opt/SUNWappserver/domains/domain1/docroot : status = 0

PASSED: /bin/sh -c /bin/mkdir -p /opt/sun/comms/iwc/install/Iwc-
config_20080409135740 : status = 0

PASSED: /bin/sh -c /bin/cp -p /opt/sun/comms/iwc/lib/config-templates/IwcCfg.
properties /opt/sun/comms/iwc/install/Iwc-config_20080409135740/IwcCfg.
properties : status = 0


All Tasks Completed. Please check configuration log
/opt/sun/comms/iwc/install/Iwc-config_20080409135740.log for further details. 

The web container instance configuration was modified successfully.

The application server instance configuration was modified.


For the changes to take effect, you must restart the Application Server
Instance.

   <Press ENTER to continue>



Configuration Details:

     Product          Result      More Information
 1.  Sun Convergence  Configured  Available

2. Done

   Enter a number corresponding to the desired selection for more information,
   or enter 2 to continue [2]: 


You have successfully configured Sun Convergence. You are now requested to
follow the  post configuration instructions mentioned in Chapter 1 of the Sun
Convergence Administration Guide.

mv /opt/sun/comms/iwc/install/saveState20080409135736 /opt/sun/comms/iwc/install/Iwc-config_20080409135740/saveState
Copying factory settings to /opt/sun/comms/iwc/data/setup
# ^D
script done on Wed 09 Apr 2008 02:04:49 PM PDT

Shared Components Bundled With the Communications Suite Installer

The Communications Suite installer, commpkg, installs the following shared components. Sun Java System Message Queue is automatically installed with the other shared components.

Shared Component Version
SECURITY NSS 4.2.6
SECURITY NSPR 4.6.7
SECURITY JSS 4.2.5
SASL 2.19
LDAPCSDK5 5.11
LDAPCSDK6 6.0
ICU 3.2.1
JDK 1.6.0_07
JavaHelp 2.0
Message Queue 4.1p1
Sleepycat Berkeley DB*
Calendar Server		 4.2.52
Sleepycat Berkeley DB*
Messaging Server 7 Update 1 		4.7.25

To Run the Communications Suite Installer

  1. Log on as root to become a superuser.
  2. Start the text-based installer. Use the commpkg usage as described in commpkg install Usage. When commpkg is invoked, a log file will record the installation parameters.)
    # ./commpkg install

    -- LOGFILE: /tmp/CommsInstaller_20070501132825.log
  3. Accept the License Agreement. If you have already read the agreement in its entirety, you have the option of skipping the agreement and accepting the terms. To accept the terms of the agreement without viewing the entire license agreement, hit Enter to continue, then enter n to skip reading the agreement, and enter yes to accept the terms.
  4. Specify Installation Location where server files will be installed (also known as the INSTALLROOT) or accept the default location.
    Note

    The default INSTALLROOT has changed from /opt/SUNWmsgsvr to /opt/sun/comms/messaging (for 32–bit installations) and /opt/sun/comms/messaging64 (for 64–bit installations)

    After specifying the INSTALLROOT, notices for Operating System and Shared Components patches may appear if previous versions of patches are installed on the machine.

  5. Select Products to Install

    The following products are included in this release:
    Messaging Server 7 Update 1
    Messaging Server (64bit) 7 Update 1
    Comms DSsetup 6.4
    Calendar Server 6.3 (with upgrade patch installed by compkg)
    Instant Messaging 8
    Convergence 1 Update 1
    Delegated Administrator 6.4 (with upgrade patch installed by compkg)
    Communications Express 6.3 (with upgrade patch installed by compkg).
    Messaging Server Sun Cluster HA agent 7.0
    Calendar Server Sun Cluster HA agent 6.3

  6. Generate List of Items to Install

    In this step, the installer lists all the products as well as shared components that will be installed or upgraded. If items need to be upgraded, the installer will give you the choice to upgrade.
    Caution

    Remember, upgrading shared components is an irreversible process. However, if you do not install the correct version of the shared components, the product may not work as designed. So, proceed carefully when installing and upgrading shared components and products.

    Once you determine what you are going to install and upgrade, the installer will create a summary.

  7. Ready to Install

    Once you specify the components you~re installing and upgrading, the installer is ready to install Messaging Server files into INSTALLROOT.

    If everything installs properly, you will see All tasks PASSED in the summary panel.
  8. Log Files

    Once installation has completed, time-stamped log files are created like in the following example:
    • To undo your installation, go to your undoCommsInstall script like the following example:/var/opt/CommsInstaller/logs/undoCommsInstall_20070501135358
    • To run silent installation for multiple installations, use the silent installation file like in the following example:/var/opt/CommsInstaller/logs/silent_CommsInstaller_20070501135358
    • The installer creates a log file of the installation process in the following location. For example:/var/opt/CommsInstaller/logs/CommsInstaller_20070501135358.log
  9. Undo Installation

    If you want to remove the installation that you just ran, you can undo your installation by running the undoCommsInstall script like the following example:/var/opt/CommsInstaller/logs/undoCommsInstall_20070501135358 .

    Undo reverses the specific steps taken during installation. It will also undo Shared Component installations. If, however, you want to pick and choose specific components to uninstall, use the commpkg uninstall command: commpkg uninstall Usage. The uninstaller does not uninstall shared components.
  10. Directory Layout

    In the INSTALLROOT (default: /opt/sun/comms), you may see the following directories:
    • CommsInstaller, where a copy of the Installer resides.
      Note

      The log files listed in the previous step are located in the /var/opt/CommsInstaller/log directory. If you install Messaging Server in an alternate root, the logfiles are located in the alternate root~s INSTALLROOT/var/opt/CommsInstaller/log directory.

    • messaging, the 32–bit Messaging Server version
    • messaging64, the 64–bit Messaging Server version

Uninstalling Communications Suite in Silent Mode

If you run the uninstaller in Silent mode, you are running a non-interactive session. The uninstallation inputs are taken from a silent uninstallation file (also known as a state file), from command line arguments, or defaults.

To run a silent uninstallation, follow these steps:

1. Run an interactive uninstallation session.

A state file similar to /var/opt/CommsInstaller/logs/silent_CommsInstaller_20070501135358 is automatically created.

Note

The silent installation and uninstallation files have the same file naming convention. You need to scan the contents of the file to determine if it~s an installation or uninstallation silent file.

2. Copy the state file to each host machine and edit the file as needed.

3. Run the silent uninstallation on each host. See the silent uninstallation usage.

Note

Command-line arguments override the values and arguments in the state file.

The following is a sample uninstall silent file: 

# Silent File for CommsInstaller 5.0-1.03}}
# Generated on 20070604120325}}
# verb used to create this silent file
VERB=uninstall
# root directory}}
ROOTDIR=/
# list of components to uninstall (using mnemonics)
COMPONENTS=MS64 MS64_L10N CS CS_L10N
# friendly name for the installroot
INSTALLNAME=

Verify the Version of Application Server

To verify which version of Application Server you have installed, run the following command on the host where you have installed Application Server:

# /opt/SUNWappserver/bin/asadmin version
Version = Sun Java System Application Server 9.1_02

You can obtain other relevant information by running the following commands:

# grep -i admin_profile /opt/SUNWappserver/config/asadminenv.conf
AS_ADMIN_PROFILE=enterprise

# grep -i hadb /opt/SUNWappserver/config/asenv.conf
AS_HADB="/opt/SUNWappserver/hadb/4.4.3-6"

# grep -i jdk /opt/SUNWappserver/config/asenv.conf
AS_JAVA="/opt/SUNWappserver/jdk"

# /opt/SUNWappserver/jdk/bin/java -version
java version "1.5.0_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
Java HotSpot(TM) Server VM (build 1.5.0_14-b03, mixed mode)

Labels

printable printable Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact