Printable Sun Java Communications Suite 6 on Multiple Hosts Deployment Example

Contents

Deployment Example: Sun Java Communications Suite 6 on Multiple Hosts

Communications Suite is designed to scale horizontally, enabling you to deploy server components as autonomous units on separate hosts. For example, you can deploy the Messaging Server MTA on one front-end host, and the Messaging Server message store on another back-end host. The Communications Suite product documentation includes guidance as well as the details to plan and build such scalable systems. A good place to begin planning your Communications Suite deployment is the Communications Suite 5 Deployment Planning Guide.

This deployment example describes how to install Sun Java Communications Suite 6 software on six computers for a functioning multi-host, tiered deployment. This document is intended for any evaluator, system administrator, or installation technician who wants to install and evaluate the services delivered by these components. This deployment example is intended as a proof-of-concept exercise and is not intended for a production deployment.

If you have never installed Communications Suite before, consider starting with the Sun Java Communications Suite 6 on a Single Host deployment example.

About This Deployment Example

This example represents an upgrade situation and shows how an existing Messaging Server 6.3 back end interoperates with the new Messaging Server 7.0 Webmail front end. (The Webmail 7.0 front end interoperates with both Messaging Server 6.3 and 7.0 back ends.) Fresh installations of Communications Suite 6/Messaging Server 7.0 will of course use a Messaging Server 7.0 back end.

This deployment example consists of the following six hosts, in a three-tiered architecture (client, access, and data tiers):

  • Calendar Server and Messaging Server front ends (Calendar Server and Messaging Server front-end components were installed on the same host to save on the number of machines.)
  • Calendar Server and Messaging Server back ends (Calendar Server and Messaging Server back-end components were installed on the same host to save on the number of machines.)
  • Directory Server for users and groups
  • Directory Server for Address Book Store
  • Instant Messaging
  • Convergence

Notes:

  • This deployment uses Schema 1 and relies on LDAP for authentication. This example does not use Access Manager.
  • LMTP is configured between the Messaging front and back ends.
  • Typically, in a large scale deployment, you can configure multiple front-end hosts behind a load balancer to improve response time.
  • Likewise, you can install the back-end Messaging servers with MMP to meet the response times expected for storage and retrieval of mail. Similar deployment considerations apply to Calendar and Instant Messaging servers. These features are not part of this deployment example.
  • Also out of scope for this example are opportunities for scalable Convergence deployments using multiple server instances or multiple HTTP Listeners.

In addition to its usefulness in testing and understanding the complexities of large scale deployments, this example can help illustrate how to use Sun's documentation. This example can also be helpful in identifying performance issues and other problems when a deployment is driven to operate at or near full capacity.

This document provides installation logs (captured from terminal sessions) that provide details for reproducing the deployment. However, be advised that this document also relies on the Single Host Deployment Example for background, detailed explanations of procedures, and in choosing values of various configuration parameters. See Sun Java Communications Suite 6 on a Single Host for more information.

What Is Different About a Multi-Host Communications Suite Deployment?

This multiple host deployment example differs from the Sun Java Communications Suite 6 on a Single Host deployment example in the following respects:

  • In a multiple host setting, you must decide whether to use a homogeneous or heterogeneous architecture. In making this decision, weigh economic, performance, and simple reuse considerations. Homogeneous architectures reduce operating system and platform dependencies and maintenance.
  • The multi-host scenario installs components onto multiple machines resulting in a tiered architecture.
  • Not all software components are required on all systems in a multi-host setting.
  • To improve performance, the multiple host scenario does not use default software installation locations.
  • The multiple host scenario installs and configures LMTP, DWP, and other Communications Suite components that the single host scenario does not.
  • Installation order in the multiple host scenario changes due to satisfying local and remote dependencies. Although out of scope for this document, a Schema 2 installation requires you to install Access Manager (and its dependencies) before running the comm_dssetup utility on a User/Group LDAP Directory Server.
  • Replication arrangements and schema updates: Although not discussed here, schema updates are incorporated either by running the comm_dssetup utility or by selectively copying schema files to all replicas. In a large scale deployment, this is in itself a large task that you need to carefully plan. Similar considerations apply for Address Book Stores.
  • Creating a multi-host deployment can require multiple passes of installation and configuration.

This Communications Suite deployment example contains the following sections. Use these sections in the order listed to install and configure the example.

  1. Preparing Hosts for Installation
  2. Products Installed by This Deployment Example
  3. Host Hardware, Operating System, and Resource Allocation
  4. Configuration Worksheets
  5. Installing and Configuring the Multi-Host Example
  6. Generalized Component Deployment Order
  7. Configuring LMTP
  8. Configuring Instant Messaging for Calendar Pop-ups
  9. Resetting the Default Address Book
  10. Provisioning Users for the Multi-Host Example
  11. Future To-do's
  12. Installation and Configuration Session Logs

Preparing Hosts for Installation (Communications Suite 6 Multi-Host Deployment Example)

The Communications Suite 6 Multi-Host Deployment Example does not cover how to prepare the individual systems for installation. This example assumes that you complete that process on your own. Refer to the platform specific documentation for items such as:

  • Hardware installation
  • Operating system software
  • Clustering/volume management software
  • Storage
  • Patches

Note: All systems were updated to use Java Development Kit (JDK) 1.6. These instructions are not provided as part of this example. You can download the JDK here.

Return to Communications Suite 6 Multi-Host Deployment Example

Products Installed (Communications Suite 6 Multi-Host Deployment Example)

Product Version
Sun Java System Directory Server 6.2 from Java ES 5 Update 1
Note: It is now recommended to install Directory Server 6.3.
comm_dssetup.pl 6.4 from Communications Suite 6
Application Server 9.1 Update 1
Java Development Kit 1.6 Unbundled
Messaging Server, front-end 7.0 from Communications Suite 6
Messaging Server, back-end 6.3 Communications Suite 5 + patch 120229-25 or later as specified in the Communications Suite 6 Release Notes.
Calendar Server, front-end 6.3 from Communications Suite 6
Calendar Server, back-end 6.3 Communications Suite 5 + patch 121658-19 or later as specified in the Communications Suite 6 Release Notes.
Instant Messaging 7.3 Communications Suite 6
Convergence 1.0 from Communications Suite 6

Return to Communications Suite 6 Multi-Host Deployment Example

Host Hardware, Operating System, and Resource Allocation (Communications Suite 6 Multi-Host Deployment Example)

Hosts used for this deployment example were as follows:

Host Name Model Architecture Operating System Logical Function Release/Patch
biotite Sun Fire T1000 SPARC Solaris 10 U4, 120011-14 Convergence Communications Suite 6
glaucodot Sun Fire X2100 I86 Solaris 10 U2, 118855-14 Calendar Server back end; Messaging Server store and MTA Communications Suite 5; 121658-19, 120229-25
pauling Sun LX50 I86 Red Hat Linux AS 4 U2 Directory Server for Address Book Store Communications Suite 6
pier1 Sun Fire V60 I86 Solaris 10 U3, 125101-10 Calendar Server front end; Messaging Server MTA and Webmail Server Communications Suite 6
pier3 Sun Fire V60 I86 Solaris 10 U3, 125101-10 Directory Server for Users/Groups and configuration Java ES 5 Update 1: 6.2
scalene Sun Fire 280R SPARC Solaris 10 U4, 120011-14 Instant Messaging server and resources Communications Suite 6: 7.3

The following figure depicts this multi-host deployment example:

Figure 1 Communications Suite 6 Multi-Host Deployment Example
Full Size
This figure shows the individual computers and the software installed on them for the multi-host deployment example.

Return to Communications Suite 6 Multi-Host Deployment Example

Configuration Worksheets (Communications Suite 6 Multi-Host Deployment Example)

Use the following configuration worksheets to supply values when configuring the component products for this example.

Note: Use default values for all port assignments.

Directory Server (Users and Groups)

Configuration Parameter Values Chosen for This Setup Notes
System user, group root, root Java ES 5, Instant Messaging
Directory Manager Password password Choose your own
Schema 1    
User/Group suffix o=sun Choose your own
DC Root o=internet  
Default domainname red.example.com For Calendar Server, Messaging Server, Instant Messaging and Convergence
Base DN o=red.example.com,o=sun Choose your own

Directory Server (Address Book Store)

Configuration Parameter Values Chosen for This Setup Notes
System user, group root, root Java ES 5, Instant Messaging
Directory Manager Password password Choose your own
Schema 1    
User/Group suffix o=sun Choose your own
DC Root o=internet  
Default domainname red.example.com For personal and corporate address books
Base DN o=red.example.com,o=sun Choose your own

Messaging Server

Configuration Parameter Values Chosen for This Setup Notes
Messaging Server Administrator Admin (default) Change by using configutil
Messaging Server Administrator Password password Choose your own
Messaging Server Runtime uid, gid mailsrv, mail  
Postmaster postoffice@red.example.com  
User/Group Server LdapURL pier3.red.example.com For both front end and back end

Calendar Server

Configuration Parameter Values Chosen for This Setup Notes
Calendar Server Administrator password calmaster, password
Calendar Server runtime uid, gid icsuser, icsgroup  
LDAP Server Host Name pier3.red.example.com  

Instant Messaging

Configuration Parameter Values Chosen for This Setup Notes
Instant Messaging runtime uid, gid root, root  
SMTP server host pier1.red.example.com  
Resources URI http://scalene.red.example.com:8080/im  
LDAP Host Name pier3.red.example.com  
Notification Server Hostname pier1.red.example.com  

Convergence

Configuration Parameter Values Chosen for This Setup Notes
Application Server Install Directory /mhd/deploy/as91  
Administrator User ID admin  
Password password  
Calendar Server Host Name pier1.red.example.com  
Webmail Server Host Name pier1.red.example.com  

Location for Server Root and Instance Directories
Choose to locate the server root and instance directories on different disk from that used by the operating system for better performance. Defaults might not be optimal. Despite the non-default choices, be advised that some data directories may end up in the /var/opt directory.

Configuration Parameter Values Chosen for This Setup Notes
Directory Server (Address Book) server root /opt/sun/dir  
Directory Server (Address Book) Instance /var/opt/sun/dsins1  
Directory Server /mhd/deploy/dir  
Directory Server Instance /mhd/deploy/dir/var/dsins1  
comm_dssetup /mhd/deploy/commds  
Application Server /mhd/deploy/as91  
Messaging Server /mhd/deploy/messasging Front end
Messaging Server /mhd/deploy/msg Back end
Calendar Server /mhd/deploy/calendar/SUNWics5 Front end
Calendar Server /mhd/deploy/SUNWics5 Back end
Instant Messaging /mhd/deploy/im  
Convergence /mhd/deploy/iwc  

Return to Communications Suite 6 Multi-Host Deployment Example

Installing and Configuring the Multi-Host Example (Communications Suite 6 Multi-Host Deployment Example)

The following two tables present two different views of the tasks used to install and configure this example. The first table provides you with an A-Z view of the steps. The second table shows which tasks can be carried out in parallel, to reduce total installation and configuration time.

Table 1: Installation and Configuration, A-Z Task Sequence

Task # System Components
1 pier3 comm_dssetup, installed by Communications Suite 6 commpkg.
2 pier3 Directory Server 6.2 Java ES 5 Update 1 installed and configured.
3 pier3 Run comm_dssetup. pier3 setup complete. Can add users such as postoffice, ulf, and Postmaster.
4 pauling Install comm_dssetup from Communications Suite 6 commpkg.
5 pauling Install and configure Directory Server 6.2 as Address Book Store.
6 pauling Run comm_dssetup to configure o=PiServerDB.
7 glaucodot Calendar Server and Messaging Server installed from Communications Suite 5. Download and apply patches 121658-19, 120229-25 for Calendar Server and Messaging Server from SunSolve.
8 glaucodot Run Messaging Server configure script. Webmail Server not configured.
9 glaucodot Run Calendar Server csconfigurator.sh script, choose back end.
10 scalene Install JDK updates
Optional: Install and configure Application Server 9.1 Update 1 or Web Server from Java ES 5 Update 1 as web container for Instant Messaging resources. Perferred to use a dedicated system.
Install Instant Messaging package.
11 pier1 Update JDK if necessary (to 1.6).
Install Application Server 9.1 Update 1 or Web Server from Java ES 5 Update 1 if planning a Communications Express deployment. Install Calendar Server and Messaging Server and optionally Communications Express package from Communications Suite 6 by using commpkg.
12 pier1 Messaging Server front-end configuration: run configure.
13 pier1 LMTP setup: pier1 LMTP to glaucodot (store). Restart Messaging Server.
14 glaucodot LMTP setup; restart Messaging Server.
15 pier1 Calendar Server front end configured and points to pier1 Messaging Server front-end (SMTP server) for alarm notifications. Follow up with httpbind and avatar configurations.
16 scalene Instant Messaging configuration: run configure. Point at Calendar Server front-end pier1 for calendar pop-up notifications and Messaging Server front-end pier1 for email archiving.
17 biotite Update JDK if necessary (to 1.6). Install and configure Application Server 9.1 Update 1.
18 biotite Run init-config to configure Convergence.
19 biotite Configure pauling as the default server for pstore (Address Book store) by running required iwcadmin commands.
20 pier3 Provision users.

Table 2: Parallelizing Configuration Tasks
The lines above and below the task indicate the start and completion time lines. If no such interleaving is planned, as it can be tedious to work it out in a large deployment, the block diagram below directs the sequence.

This figure shows which deployment tasks can be carried out in parallel.

Return to Communications Suite 6 Multi-Host Deployment Example

Generalized Component Deployment Order (Communications Suite 6 Multi-Host Deployment Example)

Installing components in the following order ensures that the component configuration scripts validate the required dependencies for a correct deployment:

  1. Directory Server (User/Groups) || Directory Server (Address Book Store), Messaging Server back end
  2. Calendar Server back end
  3. Messaging Server front end
  4. Calendar Server front end
  5. Instant Messaging
  6. Convergence

A indicates one or more of the same component installed sequentially or in parallel. The Address Book stores can also be installed in parallel to the Directory Server. Currently, running comm_dssetup does not selectively create suffixes for address books, but creates all four: o=internet; o=comms-config; o=PiServerDB; and o=pab.

Return to Communications Suite 6 Multi-Host Deployment Example

Configuring LMTP (Communications Suite 6 Multi-Host Deployment Example)

Configure LMTP as described in Chapter 16 LMTP Delivery in the Sun Java System Messaging Server 6.3 Administration Guide, with the following exceptions:

  • Configure only lmptpcs on the front end
  • Configure only lmtpss on the back end

Configuring lmtpcn and lmtpsn requires undocumented work-arounds for proper functioning and therefore are not recommended.

Front-End Files Changed

Make the following changes to the imta.cnf and option.dat files on the front-end host.

imta.cnf File Changes
Change:
.lmtp $U%$H@lmtpcs-daemon

to:
.lmtp $E$F$U%$H.lmtp@lmtpcs-daemon
.lmtp $B$F$U%$H@$H@lmtpcs-daemon

Change:
!tcp_lmtpcs defragment lmtp port 225 nomx single_sys subdirs 20 maxjobs 7 pool SMTP_POOL dequeue_removeroute
!lmtpcs-daemon

to:
tcp_lmtpcs defragment lmtp multigate connectcanonical fileinto @$4O:$U+$S@$D port 225 nodns single_sys subdirs 20 maxjobs 7 pool SMTP_POOL dequeue_removeroute
lmtpcs-daemon

option.dat File Changes
Add the following:

DELIVERY_OPTIONS=\
     #*mailbox=@$X.LMTP:$M%$\$2I$_+$2S@lmtpcs-daemon,\
     #&members=*,\
     #*native=@$X.LMTP:$M+$2S@native-daemon,\
     #*unix=@$X.LMTP:$M,\
     #*file=@$X.LMTP:+$F,\
     #&@members_offline=*,\
     #/hold=@hold-daemon:$A,\
     #program=$M%$P@pipe-daemon,\
     #forward=**,\
     #*^!autoreply=$M+$D@bitbucket

Back-End Files Changes

Make the following changes to the mappings, imta.cnf, and dispatcher.cnf files on the back-end host.

mappings File Changes
Add the following:

TCP|*225|192.18.76.45|* $Y
TCP|*225|192.18.74.48|* $Y
TCP|*|*|*|*  $N500$ Do$ Not$ connect$ to$ this$ machine

imta.cnf File Changes
Change:
tcp_local smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL
maytlsserver maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0 loopcheck

to:
tcp_local smtp nomx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL
maytlsserver maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0 loopcheck

Change:
tcp_intranet smtp mx single_sys subdirs 20 dequeue_removeroute maxjobs 7 pool SMTP_POOL maytlsserver
allowswitchchannel saslswitchchannel tcp_auth missingrecipientpolicy 4

to:
tcp_intranet smtp nomx single_sys subdirs 20 dequeue_removeroute maxjobs 7 pool SMTP_POOL maytlsserver
allowswitchchannel saslswitchchannel tcp_auth missingrecipientpolicy 4

Change:
!tcp_lmtpss lmtp flagtransfer
!tcp_lmtpss-daemon

to:
tcp_lmtpss lmtp flagtransfer
tcp_lmtpss-daemon

dispatcher.cnf File Changes
Uncomment the following:

[SERVICE=LMTPSS]
PORT=225
IMAGE=IMTA_BIN:tcp_lmtp_server
LOGFILE=IMTA_LOG:tcp_lmtpss_server.log
PARAMETER=CHANNEL=tcp_lmtpss
STACKSIZE=2048000

Return to Communications Suite 6 Multi-Host Deployment Example

Configuring Instant Messaging for Calendar Pop-ups (Communications Suite 6 Multi-Host Deployment Example)

Be sure to provide the Calendar Server front-end host name for "Notification Server Hostname." You need make no further changes to the Instant Messaging configuration (through the iim.conf file). You need to make the following changes on the Calendar Server front end (pier1) to complete setting up Calendar pop-ups feature.

In the ics.conf file:

caldb.serveralarms.binary.enable = "yes"
caldb.serveralarms.url = "enp:///ics/customalarm"
Note

To configure this example for Java Message Queue, see Configuring Java Message Service Support for Calendar Server Alerts.

Return to Communications Suite 6 Multi-Host Deployment Example

Resetting the Default Address Book (Communications Suite 6 Multi-Host Deployment Example)

Directory Server 6.2 is installed on pauling to act as the LDAP store for a personal address book. Separation of the Address Book Store from user/group directory is intended as a performance improvement measure and makes it easy to allocate resources and tune them with better control.

Installing and configuring Address Book Store by using the comm_dssetup command very closely mimics that of the user/group directory. Therefore, session logs are not captured for this setup. In the future, comm_dssetup might provide additional options to select the suffixes to be configured.

The init-config tool sets the user/group directory server as the address book store. For large scale deployments this is not a recommended practice. Use the iwcadmin commands that follow to reset the personal address book to a different Directory Server, pauling. For more information on running the iwcadmin command, see Overview of the Convergence Command-Line Utility.

iwcadmin -u admin -w nvempati -o ab.pstore.[pauling].ldaphost -v "pauling.red.example.com"
iwcadmin -u admin -w nvempati -o ab.pstore.[pauling].ldapport -v 389
iwcadmin -u admin -w nvempati -o ab.pstore.[pauling].ldapbinddn -v "cn=Directory Manager"
iwcadmin -u admin -w nvempati -o ab.pstore.[pauling].ldapbindcred -v "password"
iwcadmin -u admin -w nvempati -o ab.pstore.defaultserver -v pauling

In general,the Corporate Directory is usually a replica of the User/Group directory, to not impact the performance of the later. The following commands show how to configure this example for a Corporate Directory, corp-ds.mars.com, that is separate from the User/Group directory.

In the following commands, the parameter urlmatch takes values after LDAP URL as described in RFC 4516.

iwcadmin -u admin -w nvempati -o ab.corpdir.[default].ldaphost -v "corp-ds.mars.com"
iwcadmin -u admin -w nvempati -o ab.corpdir.[default].ldapport - v 389
"iwcadmin -u admin -w nvempati -o ab.corpdir.[default].urlmatch -v "ldap://corp-ds.mars.com:389/ou=people,dc=mars,dc=com"
iwcadmin -u admin -w nvempati -o ab.corpdir.[default].logintype -v "anon"
iwcadmin -u admin -w nvempati -o ab.corpdir.[default].searchattr -v 'entry/displayname,@uid'
iwcadmin -u admin -w nvempati -o ab.corpdir.[default].ldapbinddn -v "cn=Directory Manager"
iwcadmin -u admin -w nvempati -o ab.corpdir.[default].ldapbindcred -v "password"
iwcadmin -u admin -w nvempati -o ab.corpdir.[default].lookthrulimit -v "300"

If you want to connect to the LDAP directory anonymously, that is, when no binddn or bind password are available, make sure that credentials.xml file contains the elements shown in bold text as follows.

<ABStoreConfiguration>
<DefaultPSConfiguration>
<PStoreConfiguration>
<DataSource>
<PStoreDBConfig>
<DBLDAP>
<Identifier v='pauling' />
<LDAPConfiguration>
<LDAPCredentials>
<BindCred>
<BindPassword v='kQAw2m/dGvZ9tVUfD/OEUw==' />
<BindDN v='cn=Directory Manager' />
</BindCred>
</LDAPCredentials>
</LDAPConfiguration>
</DBLDAP>
</PStoreDBConfig>
<CorpDirDBConfig>
<Identifier v='default' />
<DBLDAP>
<Identifier v='default' />
<LDAPConfiguration>
<LDAPCredentials>
<BindCred>
<!- No Credentials ->
</BindCred>
</LDAPCredentials>
</LDAPConfiguration>
</DBLDAP>
</CorpDirDBConfig>
</DataSource>

Currently, the iwcadmin removes parameters from the xml files when their values are set to null ("") and hence the previous changes to the credentials.xml are required. Manual edits are not recommended as a general rule.

Notes:

  1. The Convergence configuration directory by default is located at installroot/iwc/config. In this example, the directory is /mhd/deploy/iwc/config.
  2. Clean up entries from an end-user's personal store: A user's personal store keeps LDAP entries for corporate directories. When Convergence is updated by replacing the current default with a new corporate directory, the user's personal store will have both old and new entries, such as corp-ds.earth.com and corp-ds.mars.com. The new entry is not seen (as well as the old one too) until the old entry is removed. Use caution when removing entries, if both Convergence and Communications Express are permitted to access the corporate directory at the same time.

    Be sure to clean up the incorrect Corporate Directory entries that do not show matching piRemotePiURL, for example: 
    dn: piEntryID=e11a92da87c91,piPStoreOwner=merlot,o=red.example.com,o=PiServerDb
objectClass: PITYPEBOOK
objectClass: piRemoteBook
objectClass: top
piBookType: abook
piRemotePiURL: ldap://corpdirectory
multiLineDescription: Corporate Directory
piEntryID: e11a92da87c91
displayName: Corporate Directory
  3. Currently, Convergence does not support multiple corporate address books.

Return to Communications Suite 6 Multi-Host Deployment Example

Provising Users (Communications Suite 6 Multi-Host Deployment Example)

Use the following LDAP templates, which include the essential object classes for provisioning users under LDAP Schema 1, to add users to this deployment example. Applications add attributes are based on the default values, which you can customize as necessary. Review the templates before using to ensure that they are appropriate for your deployment.

For performance reasons this auto-population feature might not be the best when adding a large number of users. In this case, use the second template with more of the commonly set options.

LDAP Provisioning Template for Multi-Host Deployment Example

dn: uid=<UID>,ou=People,o=<YOUR.DOMAIN.NAME>,o=<USER/GROUP ROOT>
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetorgPerson
objectClass: inetSubscriber
objectClass: inetUser
objectClass: inetMailUser
objectClass: inetLocalMailRecipient
objectClass: ipUser
objectClass: icsCalendarUser
objectClass: sunIMUser
objectClass: sunPresenceUser
objectClass: sunUCPreferences
objectClass: userPresenceProfile
inetUserStatus: Active
preferredLanguage: en
uid: <UID>
userPassword: <PASSWORD>
givenName: <FIRST NAME>
sn: <LAST NAME>
cn: <FIRST NAME> <LAST NAME>
mailHost: <FQDN of mail host>
mail: <UID>@<DOMAIN>

LDAP Provisioning Template for Multi-Host Deployment Example: Initially Setting More Options

dn: uid=<UID>,ou=People,o=<YOUR.DOMAIN.NAME>,o=<UserGroup Root>
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetorgPerson
objectClass: inetSubscriber
objectClass: inetUser
objectClass: inetMailUser
objectClass: inetLocalMailRecipient
objectClass: ipUser
objectClass: icsCalendarUser
objectClass: sunIMUser
objectClass: sunPresenceUser
objectClass: sunUCPreferences
objectClass: userPresenceProfile
inetUserStatus: Active
uid: <UID>
userPassword: <PASSWORD>
givenName: <FIRST_NAME>
sn: <LAST_NAME>
cn: <FIRST_NAME> <LAST_NAME>
mailHost: <Mail Host Name>.<YOUR.DOMAIN.NAME>
mail: <UID>@<YOUR.DOMAIN.NAME>
psRoot: ldap://<Mail Host Name>.<YOUR.DOMAIN.NAME>:389/piPStoreOwner=<UID>,o=<YOUR.DOMAIN.NAME>,o=PiServerDb
icsCalendar: <UID>@<YOUR.DOMAIN.NAME>
icsSubscribed: <UID>@<YOUR.DOMAIN.NAME>$<FIRST_NAME> <LAST_NAME>
icsCalendarOwned: <UID>@<YOUR.DOMAIN.NAME>$<FIRST_NAME> <LAST_NAME>
sunUCDateDelimiter: -
sunUCDateFormat: D/M/Y
sunUCTimeFormat: 24
preferredLanguage: en
sunUCTheme: sun_gray_theme
nswmExtendedUserPrefs: mePrevSent=Sent
nswmExtendedUserPrefs: meTrashFolder=Trash
nswmExtendedUserPrefs: meDraftFolder=Drafts
nswmExtendedUserPrefs: meComposeHtml=true
nswmExtendedUserPrefs: meAutoQuote=true
nswmExtendedUserPrefs: mePrevTrash=Trash
nswmExtendedUserPrefs: meSentFolder=Sent
nswmExtendedUserPrefs: meExpungeOnExit=false
nswmExtendedUserPrefs: meAutoSpell=true
sunUCTimeZone: <TIME ZONE>
icsFirstDay: 2
icsExtendedUserPrefs: ceDayTail=20
icsExtendedUserPrefs: ceDefaultView=monthview
icsExtendedUserPrefs: ceDayHead=7
icsExtendedUserPrefs: ceDefaultAlarmType=email
icsExtendedUserPrefs: ceNotifyEmail=<UID>@<YOUR.DOMAIN.NAME>
icsExtendedUserPrefs: ceDefaultAlarmStart=-PT30M
icsExtendedUserPrefs: ceNotifyEnable=1
icsExtendedUserPrefs: ceDefaultAlarmEmail=<UID>@<YOUR.DOMAIN.NAME>
icsExtendedUserPrefs: ceWeekEndDays=1,7
sunUCExtendedUserPrefs: imAwayWaitEnabled=true
sunUCExtendedUserPrefs: imAlertOnStatus=online,away,offline
sunUCExtendedUserPrefs: imAwayWaitTime=15
sunUCExtendedUserPrefs: imHideGroups=false
sunUCExtendedUserPrefs: imAutoApproveSubsc=false
sunUCExtendedUserPrefs: imIdleWaitTime=10
sunUCExtendedUserPrefs: imIdleWaitEnabled=true

Return to Communications Suite 6 Multi-Host Deployment Example

Future To-do's (Communications Suite 6 Multi-Host Deployment Example)

The following list describes potential items that might be added to this deployment example in the future:

  • Describe the Java Message Queue configuration configuration between pier1 and scalene.
  • Add the logging keyword to to the default channel in the imta.cnf file to get mail.log files.
  • Multiple Virtual Domains: Though this deployment example is configured for virtual domains, currently it utilizes only one.
  • DNS Server
  • Messaging Multiplexors (MMP) Setup: Such a configuration requires at least two MMPs, or multiple Messaging Server back ends.
  • SSL Configuration
  • LDAP Schema 2: Required for Access Manager for authentication and Single Sign-on
  • Load Balancing Plug-in From Application Server
  • Directory Server Multi-Master Replication
  • Demonstrating Horizontal Scalability of Address Book Server
  • Performance Tuning
  • Browser Speed-up: Firefox and Internext Explorer

Return to Communications Suite 6 Multi-Host Deployment Example

Installation and Configuration Session Logs (Communications Suite 6 Multi-Host Deployment Example)

Sample Session: Installing and Configuring Directory Server 6.2 (Users/Groups)

Script started on Wed 16 Apr 2008 01:36:58 PM PDT
Root@pier3 13:37:29 Solaris_x86} ./installer -nodisplay 

...

   License Agreement [No] {"<" goes back, "!" exits}? yes

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

 *  *  Directory Preparation Tool 6.4
[ ] 2. Web Server 7.0 Update 1
[ ] 3. Sun Cluster Geographic Edition 3.1 2006Q4
[ ] 4. Web Proxy Server 4.0.5
[ ] 5. Directory Server Enterprise Edition 6.2
 *  *  High Availability Session Store 4.4.3
[ ] 7. Access Manager 7.1
 *  *  Sun Cluster 3.1 8/05
[ ] 9. Message Queue 3.7 UR2
[ ] 10. Application Server Enterprise Edition 8.2 Patch 2
[ ] 11. Service Registry 3.1 Update 1
[ ] 12. Portal Server Secure Remote Access 7.1 Update 2
[ ] 13. Monitoring Console 1.0 Update 1
[ ] 14. Portal Server 7.1 Update 2
 *  *  Java DB 10.2.2.1
 *  *  Sun Cluster Agents 3.1 8/05
[ ] 17. All Shared Components

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

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

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

[X] 5. Directory Server Enterprise Edition 6.2



   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 "Directory Server Enterprise Edition 6.2
"

---------------------------------------------------------------------------------

*[X] 1. Directory Server 6 Core Server
*[X] 2. Directory Service Control Center
*[X] 3. Directory Server Command-Line Utility
*[X] 4. Directory Proxy Server 6.2 Core Server

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

*[X] 1. Directory Server 6 Core Server
*[X] 2. Directory Service Control Center
*[X] 3. Directory Server Command-Line Utility
*[X] 4. Directory Proxy Server 6.2 Core Server


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



Shared Component Upgrades Required
-----------------------------------

The shared components listed below are currently installed. They will be
upgraded for compatibility with the products you chose to install.

Component    Package
--------------------
ICU       SUNWicu
	1.2:PATCHES:119811-02 (installed)
	1.2:PATCHES:119811-04 (required)
MFWK       SUNWservicetagu
	1.1.2.1 (installed)
	2.0.1 (required)
MFWK       SUNWstosreg
	1.1.2.1 (installed)
	2.0.1 (required)
MFWK       SUNWservicetagr
	1.1.2.1 (installed)
	2.0.1 (required)

   Enter 1 to upgrade these shared components and 2 to cancel [1] {"<" goes
   back, "!" exits}: 



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

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


   Directory Server [/opt/SUNWdsee] {"<" goes back, "!" exits}: /sarma/deploy/dir


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          		



   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 Common Server Settings

   Enter Host Name [pier3] {"<" goes back, "!" exits} 
   Enter DNS Domain Name [red.example.com] {"<" goes back, "!" exits} 
   Enter IP Address [xxx.xxx.xxx.xxx] {"<" goes back, "!" exits} 
   Enter Server admin User ID [admin] {"<" goes back, "!" exits} 
   Enter Admin User's Password (Password cannot be less than 8 characters) []
   {"<" goes back, "!" exits}  
   Confirm Admin User's Password [] {"<" goes back, "!" exits}  
   Enter System User [root] {"<" goes back, "!" exits} 
   Enter System Group [root] {"<" goes back, "!" exits} 



Directory Server: Create Directory Instance

Directory Server Console requires Directory Server, but does not require
a directory instance.

Although not a requirement, you can create a directory instance now
during installation.

Create a directory instance (in addition to installing Directory Server)?


1. Yes
2. No

   Enter 1 or 2 [1] {"<" goes back, "!" exits} 



Directory Server: Specify Instance Creation Information

   Enter Instance Directory [/var/opt/SUNWdsee/dsins1] {"<" goes back, "!"
   exits} /sarma/deploy/dir/var/ds1
   Enter Instance Port [389] {"<" goes back, "!" exits} 
   Enter Instance SSL Port [636] {"<" goes back, "!" exits} 
   Directory Manager DN [cn=Directory Manager] {"<" goes back, "!" exits} 
   System User [root] {"<" goes back, "!" exits} 
   System Group [root] {"<" goes back, "!" exits} 
   Enter Instance password (At least 8 characters long) [] {"<" goes back, "!"
   exits}  
   Retype Password [] {"<" goes back, "!" exits} 
   Enter Suffix [dc=red,dc=iplanet,dc=com] {"<" goes back, "!" exits} o=sun
Ready to Install
----------------
The following components will be installed.

Product: Java Enterprise System 5
Uninstall Location: /var/sadm/prod/SUNWentsys5u1
Space Required: 117.63 MB
------------------------------------------------
	Sun Java(TM) System Directory Server Enterprise Edition 6.2
	   Sun Java(TM) System Directory Server Enterprise Edition 6.2 Command-Line
Utilities
	   Java Enterprise System Directory Server 6.2 Core Server
	   Java Enterprise System Directory Service Control Center
	   Java Enterprise System Directory Proxy Server 6.2 Core Server


1. Install
2. Start Over
3. Exit Installation

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

Java Enterprise System 5
|-1%--------------25%-----------------50%-----------------75%--------------100%|


Installation Complete


Software installation has completed successfully. You can view the installation
summary and log by using the choices below. Summary and log files are available
in /var/sadm/install/logs/.



Your next step is to perform the postinstallation configuration and
verification tasks documented in the Postinstallation Configuration and Startup
Chapter of the Sun Java(TM) Enterprise System Installation Guide. See: http:
//docs.sun.com/doc/820-2827.

   Enter 1 to view installation summary and Enter 2 to view installation logs
   [1] {"!" exits} 
Installation Summary Report
Install Summary
Java Enterprise System 5 : Installed
Sun Java(TM) System Directory Server Enterprise Edition 6.2 : Installed,
Configured
Configuration Data
Sun Java(TM) System Directory Server Enterprise Edition 6.2 :
    Directory Server Installation Directory : /sarma/deploy/dir
The configuration log is saved in :  /var/sadm/install/logs/JavaES_Install_log.
1442921950
   Enter 1 to view installation summary and Enter 2 to view installation logs
   [1] {"!" exits} !
In order to notify you of potential updates, we need to confirm an internet connection. Do you want to proceed [Y/N] : N
Root@pier3 13:51:07 Solaris_x86} exit

script done on Wed 16 Apr 2008 01:51:10 PM PDT

Sample Session: Preparing User/Group LDAP Directory with comm_dssetup

Script started on Wed 16 Apr 2008 01:54:40 PM PDT
Root@pier3 13:54:42 logs} cd /sarma/deploy/dssetup/dssetup/sbin
Root@pier3 13:54:59 sbin} comm_dssetup.pl 

Welcome to the Directory Server preparation tool for
Sun Java(tm) System communication services.
dssetup Version 6.4-1.04 (built Wed Mar 12 11:23:19 PDT 2008)

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_20080416135501.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 [/sarma/deploy/dir/var] : 


Please select a directory server instance from the following list:

[1]   ds1 


Which instance do you want [1]: 

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

Please enter the Users/Groups base suffix [o=sun] : 
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]: 

Please enter the DC Tree base suffix [o=internet]: 

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                        : /sarma/deploy/dir/var
  Server Instance                    : ds1
  Users/Groups Directory             : yes
  Update Schema                      : yes
  Schema Type                        : 1
  DC Root                            : o=internet
  User/Group Root                    : o=sun
  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]: 
Generating files...

Checking to see if Suffixes need to be added
  Will Create suffix o=comms-config
  Will Create suffix o=internet
  Will Create suffix o=pab
  Will Create suffix o=PiServerDb

...
Running /var/tmp/dssetup_20080416135501.sh will make changes to the Directory
  You can run this file now or at a later time
Ready to execute the script now.

Do you want to continue [y]: 
...
Successful Completion. Consult /var/tmp/dssetup_20080416135501.log for details

Wed 16 Apr 2008 02:02:04 PM PDT

Sample Session: Configuring the Messaging Server 6.3 Back End

Script started on Wed 16 Apr 2008 07:57:21 PM PDT
Root@glaucodot 19:57:24 logs} cd /sarma/deploy/msg/sbin
Root@glaucodot 19:57:43 sbin} ./configure -nodisplay 


   Enter fully qualified host name [glaucodot.red.example.com] 

Please specify the directory into which the Messaging Server configuration and
data files will be installed.

   Directory to install Messaging Server configuration and data files
   [/var/sarma/deploy/msg] {"<" goes back, "!" exits}: /sarma/deploy/msg/var



Messaging Server components showing a checked box will be configured. Please
change selection accordingly.


 [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}: 3

Messaging Server components showing a checked box will be configured. Please
change selection accordingly.


 [X]  1  Message Transfer Agent    0 bytes
 [X]  2  Message Store    0 bytes
 [ ]  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}: 
Checking Disk Space

Please enter the user and group which will be used to adminster the Messaging
Server. The user and group will be created if they do not exist. If the user is
created, it will have a password that is locked out.
   Enter Username [mailsrv]: 
   Enter Unix Group [mail]: 

Please specify the User/Group Directory (LDAP) server. The Ldap Server URL is
an url link to the directory server on which the users and groups information
is stored. The url should  be in the format of
ldap://<hostname>:<port>. e.g. 

ldap://ldapserver.mycompany.com:389.

The default bind DN is the distinguished name for the directory manager. The
URL should not specify a replica as normally you will not be able to write to
it.

   User/Group Server LdapURL [ldap://glaucodot.red.example.com:389]: ldap://pier3.red.example.com:389
   Bind As [cn=Directory Manager]: 
   Password: 


A Postmaster mailing list will be created and used to distribute administrative
email related to the Messaging Server.  Mail sent to the Postmaster will be
distributed to the members of the postmaster group.  An email address that will
be the initial member of the postmaster group is required.  The given address
(e.g. admin@domain.com) must be a valid address (it will NOT be created
automatically).

Do not use an email address that begins with "Postmaster@".  This email address
is already assigned to the Postmaster alias.

   Enter Postmaster email address [] postoffice@red.example.com
Enter a password to be used for Messaging Server (several administration
accounts)
   Enter password []: 
   Re-enter password to verify []: 

Please enter the default email domain that this Messaging Server will be
responsible for. The default email domain is the domain of unqualified user-
id's that do not belong to any particular domain.

   Enter Email Default Domain [red.example.com] 

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=red.example.com,o=sun] 

Checking disk space...


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

Product: Messaging Server
Location: /sarma/deploy/msg/var
Space Required: 0 bytes
-------------------------------
Message Transfer Agent
Message Store


Ready to Configure

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

   What would you like to do [1]? 
...
All Tasks Passed. Please check install log
/sarma/deploy/msg/install/configure_20080416195838.log for further details. 

 Hit NEXT to continue


Configuration Details:

     Product           Result      More Information
 1.  Messaging Server  Configured  Available

2. Done

   Enter the number corresponding to the desired selection for more
   information, or enter 2 to continue [2]: 
mv /sarma/deploy/msg/install/saveState20080416195825 /sarma/deploy/msg/install/configure_20080416195838/saveState
Copying factory settings to /sarma/deploy/msg/data/setup
Root@glaucodot 20:00:38 sbin} exit

script done on Wed 16 Apr 2008 08:00:46 PM PDT

Sample Session: Configuring the Calendar Server 6.3 Back End

Script started on Wed 16 Apr 2008 08:01:14 PM PDT
Root@glaucodot 20:01:17 logs} cd /sarma/deploy/SUNWics5/cal/sbin/
Root@glaucodot 20:04:57 sbin} ./csconfigurator.sh -nodisplay 
...

Administration, User Preferences and Authentication

User Preferences Directory
   LDAP Server Host Name [glaucodot.red.example.com]: 
   LDAP Server Port [389]: 
   Directory Manager DN [cn=Directory Manager]: 
   Directory Manager Password []: 


The Directory Manager password is empty. Enter a valid password.

   <Press ENTER to continue>


Administration, User Preferences and Authentication

User Preferences Directory
   LDAP Server Host Name [glaucodot.red.example.com]: pier3.red.example.com
   LDAP Server Port [389]: 
   Directory Manager DN [cn=Directory Manager]: 
   Directory Manager Password []: 
Please Wait: The configuration program is verifying that the LDAP Server is
reachable and that Directory Manager credentials are valid
Please Wait: Getting configuration of the LDAP server

Virtual domains settings


Here is a list of the existing domains

1. red.example.com
2. <New Default domain>

   Select the default domain from the list above [1]: 
   Calendar administrator user name [calmaster]: 
   Calendar administrator password []: 
   Calendar administrator email address [root@red.example.com]: calmaster@red.example.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@red.example.com could not be found on LDAP server pier3.red.
iplanet.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] 2
   Back end service port [59779] 

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

Email and Email Alarms

   Administrator Email Address [calmaster@red.example.com]: 
   SMTP Host Name [glaucodot.red.example.com] 

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

Runtime configuration

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

1. Yes
2. No

   Start after sucessful configuration [2] 1

1. Yes
2. No

   Start on system startup [1] 2

Please Wait: Verifying User...
Directories to store configuration and data files

   Config Directory [/etc/sarma/deploy/SUNWics5/config]: /sarma/deploy/SUNWics5/config
   Database Directory [/var/sarma/deploy/SUNWics5/csdb]: /sarma/deploy/SUNWics5/var/csdb
   Attachment store Directory [/var/sarma/deploy/SUNWics5/astore]: /sarma/deploy/SUNWics5/var/astore
   Logs Directory [/var/sarma/deploy/SUNWics5/logs]: /sarma/deploy/SUNWics5/var/logs
   Temporary Files Directory [/var/sarma/deploy/SUNWics5/tmp]: /sarma/deploy/SUNWics5/var/tmp

The directory /sarma/deploy/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 /sarma/deploy/SUNWics5/var/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 /sarma/deploy/SUNWics5/var/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 /sarma/deploy/SUNWics5/var/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 /sarma/deploy/SUNWics5/var/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]? 2

1. enable
2. disabled

   Do you want to enable hotbackup [1]? 2


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: /sarma/deploy/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]? 
Starting Task Sequence
===== Wed Apr 16 20:09:28 PDT 2008 ===== 
...

All Tasks Passed. Please check install log /var/sadm/install/logs/Sun_Java(tm)
_System_Calendar_Server_install.B04162006 for further details.


Wed 16 Apr 2008 08:09:51 PM PDT

Sample Session: Configuring the Messaging Server 7.0 Front End

Script started on Thu Apr 17 14:38:36 2008
Root@pier1 14:38:39 logs} cd /sarma/deploy/messaging/sbin
Root@pier1 14:38:46 sbin} ./configure -nodisplay 
...

Please enter the fully qualified host name for the Messaging Server.

   Enter fully qualified host name [pier1.red.example.com] {"<" goes back, "!"
   exits} 

Please specify the directory into which the Messaging Server configuration and
data files will be installed.

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

The directory "/sarma/deploy/messaging/var" 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 while components are being loaded...


Loading components ...


Messaging Server components showing a checked box will be configured. Please
change selection accordingly.


 [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}: 2

Messaging Server components showing a checked box will be configured. Please
change selection accordingly.


 [X]  1  Message Transfer Agent    0 bytes
 [ ]  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}: 
Checking Disk Space

Please enter the user and group which will be used to adminster the Messaging
Server. The user and group will be created if they do not exist. If the user is
created, it will have a password that is locked out.
   Enter Username [mailsrv]: 
   Enter Unix Group [mail]: 

Please specify the User/Group Directory (LDAP) server. The Ldap Server URL is
an url link to the directory server on which the users and groups information
is stored. The url should  be in the format of
ldap://<hostname>:<port>. e.g. 

ldap://ldapserver.mycompany.com:389.

The default bind DN is the distinguished name for the directory manager. The
URL should not specify a replica as normally you will not be able to write to
it.

   User/Group Server LdapURL [ldap://pier1.red.example.com:389] {"<" goes back,
   "!" exits}: ldap://pier3.red.example.com:389
   Bind As [cn=Directory Manager] {"<" goes back, "!" exits}: 
   Password {"<" goes back, "!" exits}: 


A Postmaster mailing list will be created and used to distribute administrative
email related to the Messaging Server.  Mail sent to the Postmaster will be
distributed to the members of the postmaster group.  An email address that will
be the initial member of the postmaster group is required.  The given address
(e.g. admin@domain.com) must be a valid address (it will NOT be created
automatically).

Do not use an email address that begins with "Postmaster@".  This email address
is already assigned to the Postmaster alias.

   Enter Postmaster email address [] {"<" goes back, "!" exits} postoffice@red.example.com
Enter a password to be used for Messaging Server (several administration
accounts)
   Enter password [] {"<" goes back, "!" exits}: 
   Re-enter password to verify [] {"<" goes back, "!" exits}: 

Please enter the default email domain that this Messaging Server will be
responsible for. The default email domain is the domain of unqualified user-
id's that do not belong to any particular domain.

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

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=red.example.com,o=sun] {"<" goes back, "!" exits} 

Checking disk space...


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

Product: Messaging Server
Location: /sarma/deploy/messaging/var
Space Required: 0 bytes
-------------------------------------
Message Transfer Agent
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}? 
Starting Task Sequence
===== Thu Apr 17 14:42:29 PDT 2008 ===== 

...

All Tasks Passed. Please check install log
/sarma/deploy/messaging/install/configure_20080417143904.log for further
details. 

 Hit NEXT to continue


Configuration Details:

     Product           Result      More Information
 1.  Messaging Server  Configured  Available

2. Done

   Enter the number corresponding to the desired selection for more
   information, or enter 2 to continue [2] {"!" exits}: 
mv /sarma/deploy/messaging/install/saveState20080417143855 /sarma/deploy/messaging/install/configure_20080417143904/saveState
Copying factory settings to /sarma/deploy/messaging/data/setup

-- Configuring Service Tag for Messaging Server
Root@pier1 14:42:40 sbin} start-msg
Connecting to watcher ...
Launching watcher ... 18400
Starting http server .... 18401
Starting sched server ... 18402
Starting dispatcher server .... 18404
Starting job_controller server .... 18410


Thu Apr 17 14:42:58 2008

Sample Session: Configuring the Calendar Server 6.3 Front End

Script started on Thu Apr 17 12:07:12 2008
Root@pier1 12:07:15 logs} cd /sarma/deploy/calendar/SUNWics5/cal/sbin
Root@pier1 12:07:29 sbin} ./csconfigurator.sh -nodisplay -saveState 

Welcome to the Sun Java(tm) System Calendar Server Configuration Program

We strongly recommend that you exit all programs before running the
configuration program. If you have other programs running, type Ctrl-C to end
the configuration program and then close any other programs you have running.

    <Press ENTER to Continue> 

Administration, User Preferences and Authentication

User Preferences Directory
   LDAP Server Host Name [pier1.red.example.com]: 
   LDAP Server Port [389]: 
   Directory Manager DN [cn=Directory Manager]: 
   Directory Manager Password []: 
Please Wait: The configuration program is verifying that the LDAP Server is
reachable and that Directory Manager credentials are valid


Could not connect to LDAP server. Error code 91. Connect Error

   <Press ENTER to continue>


Administration, User Preferences and Authentication

User Preferences Directory
   LDAP Server Host Name [pier1.red.example.com]: pier3.red.example.com
   LDAP Server Port [389]: 
   Directory Manager DN [cn=Directory Manager]: 
   Directory Manager Password []: 
Please Wait: The configuration program is verifying that the LDAP Server is
reachable and that Directory Manager credentials are valid
Please Wait: Getting configuration of the LDAP server

Virtual domains settings


Here is a list of the existing domains

1. red.example.com
2. <New Default domain>

   Select the default domain from the list above [1]: 
   Calendar administrator user name [calmaster]: 
   Calendar administrator password []: 
   Calendar administrator email address [calmaster@red.example.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

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] 
   Hostname of the back-end server [] glaucodot.red.example.com
   IP address of the back-end server [xxx.xxx.xxx.xxx] 
   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]? 


Email and Email Alarms

   Administrator Email Address [calmaster@red.example.com]: 
   SMTP Host Name [pier1.red.example.com] 

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

Runtime configuration

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

1. Yes
2. No

   Start after sucessful configuration [2] 

1. Yes
2. No

   Start on system startup [1] 2

Please Wait: The configuration program is checking that the local web service
port is available.
Please Wait: Verifying User...

User ID "icsuser" does not exist.



Do you want to create this user ID or enter a new user ID?

1. Create User ID
2. Choose New

   Enter the number corresponding to your choice  [1] 
Directories to store configuration and data files

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

The directory /sarma/deploy/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 /sarma/deploy/calendar/SUNWics5/var/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 /sarma/deploy/calendar/SUNWics5/var/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 /sarma/deploy/calendar/SUNWics5/var/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 /sarma/deploy/calendar/SUNWics5/var/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] 

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: /sarma/deploy/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]? 
Starting Task Sequence
===== Thu Apr 17 12:12:32 PDT 2008 ===== 
...
All Tasks Passed. Please check install log /var/sadm/install/logs/Sun_Java(tm)
_System_Calendar_Server_install.B04171207 for further details.


Configuration Details:

     Product                              Result      More Information
 1.  Sun Java(tm) System Calendar Server  Configured  Available

2. Done

   Enter the number corresponding to the desired selection for more
   information, or enter 2 to continue [2]: 
Root@pier1 12:13:24 sbin} start-cal
Connecting to watcher ...
Launching watcher ... 14674
Starting ens server ... 14675
Starting store server .... 14676
Checking store server status ..... ready
Starting admin server ....... 14677
Starting http server ...... 14678
Root@pier1 12:13:44 sbin} pgrep -lf cal
14675 /sarma/deploy/calendar/SUNWics5/cal/lib/enpd -p 57997
  474 /usr/lib/sendmail -bd -q15m -C /etc/mail/local.cf
 2751 /usr/sfw/bin/../lib/mozilla/mozilla-bin -UILocale en-US -contentLocale US
14676 /sarma/deploy/calendar/SUNWics5/cal/lib/csstored
14677 /sarma/deploy/calendar/SUNWics5/cal/lib/csadmind
14680 /sarma/deploy/calendar/SUNWics5/cal/lib/cshttpd -0 -d 0 -D -1
14678 /sarma/deploy/calendar/SUNWics5/cal/lib/cshttpd
14679 /sarma/deploy/calendar/SUNWics5/cal/lib/cshttpd -0 -d 0 -D -1
14674 /sarma/deploy/calendar/SUNWics5/cal/lib/watcher INADDR_ANY 49995 /sarma/deploy/
14681 /sarma/deploy/calendar/SUNWics5/cal/lib/cshttpd -0 -d 0 -D -1

Thu Apr 17 12:14:32 2008

Sample Session: Configuring Instant Messaging 7.3

Root@scalene 10:06:19 logs} date
Friday, April 18, 2008 10:06:20 AM PDT
Root@scalene 10:06:21 logs} cd /sarma/deploy/im
Root@scalene 10:06:31 im} ./configure -nodisplay 


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]: root
   Runtime Group ID [inetgroup]: root

   Runtime Directory [/var/opt/SUNWiim]: /sarma/deploy/im/var

User ID root has root (super-user) privileges. This is not recommended.



Are you sure you want the Instant Messaging Services installed and run with the
super-user?

1. Choose New
2. Accept

   Enter the number corresponding to your choice  [1] 2


Network Access Points

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


Directory Server Options

   LDAP Host Name [scalene.red.example.com]: pier3.red.example.com
   LDAP Port Number [389]: 
   Base DN [dc=red,dc=iplanet,dc=com]: o=sun
   Bind DN []: cn=Directory Manager
   Bind Password: 


Mail Server Options

   Enable Email Integration [yes] 
   SMTP Server Host Name [scalene.red.example.com]: pier1.red.example.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://scalene.red.example.com:80/im]: http://scalene.red.example.com:8080/im
   Enable Audio [no]? 

The following information is used to invoke your web container's deployment
interfaces.  Your web container may not require all fields to be filled.
   Webcontainer Path/sarma/deploy/as91
   Web Administration URL [https://scalene.red.example.com:4849/]: http://scalene.red.example.com:4848
   Web Administrator User ID [admin]: 
   Web Administrator Password:
Contacting admin server and processing the supplied information

Please enter the relevent info to configure the HTTP Gateway.

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

Please enter the relevent info to configure the IMPS Gateway.

   Do you want to deploy the IMPS Gateway  [yes]? no


Calendar Agent configuration

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


Startup Options

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

Configuration started

The configuration completed successfully. 

You may consult the log file for additional details:
/var/sadm/install/logs/Sun_Java_System_Instant_Messaging_install.B04181007.

April 18, 2008 10:17:04 AM PDT

Sample Session: Configuring Convergence 1.0

Script started on April 18, 2008 12:56:20 PM PDT
Root@biotite 12:56:33 logs} cd /sarma/deploy/iwc/sbin
Root@biotite 12:56:42 sbin} pwd
/sarma/deploy/iwc/sbin
Root@biotite 12:56:49 sbin} ./init-config -nodisplay -saveState /sarma/deploy/logs/iwcConf.state
...

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/sarma/deploy/iwc] {"<" goes back, "!" exits}: /sarma/deploy/iwc/var

The directory "/sarma/deploy/iwc/var" 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 [biotite] {"<" goes back, "!" exits}: 
   DNS Domain Name [red.example.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}: /sarma/deploy/as91
   Enter Application Server Domain Directory
   [/opt/SUNWappserver/domains/domain1] {"<" goes back, "!" exits}: /sarma/deploy/as91/domains/domain1
   Enter Application Server Document Root Directory
   [/opt/SUNWappserver/domains/domain1/docroot] {"<" goes back, "!" exits}: /sarma/deploy/as91/domains/domain1/docroot
   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  [no] {"<" goes back,
   "!" exits}? yes
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://biotite.red.example.com:389] {"<" goes back, "!" exits}: ldap://pier3.red.example.com:389
   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=internet] {"<" 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 [red.example.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 [biotite.red.example.com] {"<" goes back,
   "!" exits}: pier1.red.example.com
   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 [biotite.red.example.com] {"<" goes
   back, "!" exits}: pier1.red.example.com
   Enter the Calendar Server Port Number [80] {"<" goes back, "!" exits}: 
   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 [red.example.com] {"<" goes back, "!" exits}: 
   Enter the Server Host Name [biotite.red.example.com] {"<" goes back, "!"
   exits}: scalene.red.example.com
   Enter the Server Port Number [5222] {"<" goes back, "!" exits}: 5269
   Enter the httpbind compoent JID [biotite.httpbind.red.example.com] {"<" goes
   back, "!" exits}: scalene.httpbind.red.example.com
   Enter the httpbind Component Password [] {"<" goes back, "!" exits}: 
   Enter the avatar component JID [biotite.avatar.red.example.com] {"<" goes
   back, "!" exits}: scalene.avatar.red.example.com
   Enter the avatar Component Password [] {"<" goes back, "!" exits}: 


Please enter the Sun Convergence Administrator User ID and Password.

   Username [admin]: 
   Password: 
   Password Again: 


The passwords entered do not match

   <Press ENTER to continue>



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: /sarma/deploy/iwc/var
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
===== Fri Apr 18 13:05:40 PDT 2008 ===== 
...

All Tasks Completed. Please check configuration log
/sarma/deploy/iwc/install/Iwc-config_20080418125717.log for further details. 

The web container instance configuration was modified successfully.


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. Please refer to the Sun
Convergence Administration Guide for instructions on using the command line
tool (iwcadmin) for the ongoing administration of your deployment.

mv /sarma/deploy/iwc/install/saveState20080418125712 /sarma/deploy/iwc/install/Iwc-config_20080418125717/saveState
Copying factory settings to /sarma/deploy/iwc/data/setup

Root@biotite 13:07:06 sbin} cd /sarma/deploy/as91/bin
Root@biotite 13:07:23 bin} ls
appclient          asapt              jspc               verifier           wsgen
asadmin            asupgrade          package-appclient  wscompile          wsimport
asant              capture-schema     schemagen          wsdeploy           xjc
Root@biotite 13:07:24 bin} ./asadmin stop-domain domain1
Domain domain1 stopped.
Root@biotite 13:07:44 bin} exit

April 18, 2008  1:07:53 PM PDT

Return to Communications Suite 6 Mult-Host Deployment Example

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