Multiple instances of JES Messaging Server 6 2005Q4 on 2-node cluster
We currently have a 2-node Sun cluster running iPlanet Messaging Server 5.2. On each node, there are two instances of iMS5.2. One instance is for clients with even numbered IDs; the other instance is for clients with odd numbered IDs. Under normal operation, one node serves the even numbered IDs whilst the other node serves the odd numbered IDs. In a failover event, the surviving node will serve both odd and even numbered IDs. This environment was set up by Sun PS.
We are currently considering building a JES 2005Q4 Messaging Server 6 environment that also uses a 2-node Sun cluster. My query is the following:
Is it possible to build a 2-node Sun Cluster with two instances of JES Messaging Server 6 2005Q4 on each cluster node?
According to the JES Messaging Server 6 2005Q4 Administration Guide, multiple instances are not supported.
If this is the case, does this mean we can only install one instance of JES Messaging Server 6 2005Q4 on each node in a failover environment in which the "live" cluster node serves both odd and even IDs?
[1080 byte] By [
mcleans] at [2007-11-26 10:52:39]
# 2
Hi,
Which schema are you using?
I recently installed SJES 2005Q4 on SunCluster 3.1.
I installed seperate Resource groups for Directory , Messaging & Calendar. These can run independently on any node with there own IPs
The messaging server is running perfectly so is cluster
I faced a issue - that when you configure the messaging server the installer complains that the IP of the messaging being different the the Directory..it will be installed unmanaged (Admin server will not be able to mange this)
I am writing the SaveState note the # ADMINSERVER_SERVERROOT_CONF = NO_ADMIN_SERVER
#
# Wizard Statefile created: Sat Sep 30 07:57:23 GMT+08:00 2006
# Wizard path: /opt/SUNWmsgsr/lib/configure.class
#
#
# Install Wizard Statefile section for Messaging Server
#
# List of internal WizardState variables - FYI ONLY
# productName = Messaging Server
# productVersion = 6.2
# INSTALLER_TYPE = PKGADD
# msg.RootPath = /opt/SUNWmsgsr
# msg.DataPath = /SJMS/var/opt/SUNWmsgsr
# ADMINSERVER_SERVERROOT_CONF = NO_ADMIN_SERVER
# ADMINSERVER_SERVERROOT = /opt/SUNWmsgsr/install
# PRODUCT_CDS_HOST = DIR.sjms.com
# PRODUCT_CDS_PORT = 389
# ADMINSERVER_SIE = cn=admin-serv-dummy, cn=Administration Server, cn=Server Gro
up, cn=dummyfqdn, ou=AdminDomain, o=comms-config
# ADMINSERVER_USER = admin
# ADMINSERVER_ISIE = cn=Administration Server, cn=Server Group, cn=DIR.sjms.com,
ou=sjms.com, o=NetscapeRoot
# ADMINSERVER_PORT = 390
# ADMINSERVER_QUALIFIED_DN = DIR.sjms.com
# ADMINSERVER_DOMAIN = AdminDomain
# SDK.installHostName = MS
# SDK.installDomainName = sjms.com
# msg.GroupName = Server Group
# HOST_FQDN = MS.sjms.com
# HOST_SHORTNAME = MS
# HOST_DOMAINNAME = sjms.com
# HOST_IPADDR = 172.10.100.20
# HOST_ALLIPADDR = 172.10.100.20
# install.logfile = /opt/SUNWmsgsr/install/configure_20060930074912.log
# install.status = 3
# LOCAL_TIMESTAMP = Sep 30, 2006 7:49:12 AM
# DEFAULT_TIMESTAMP = 20060930074912
# GMT_TIMESTAMP = 20060929234912Z
# DC_SUFFIX = o=internet
# SCHEMA_TYPE = 1
# CFGDIR_DSSETUP_VER = 6.3
# CFGDIR_DSSETUP_REV = 2.03
# UGDIR_DSSETUP_VER = 6.3
# UGDIR_DSSETUP_REV = 2.03
# MIN_DSSETUP_VERSION = 6.0
# MIN_DSSETUP_REVISION = 0.004
# CFGDIR_SUFFIX = o=comms-config
# CFGDIR_SUFFIX_NO_ADMIN_SERVER = o=comms-config
# UGDIR_SUFFIX = o=isp
# FQDNCHECK = null
# COMPONENT_LIST = imta:msma:webmail:imta
# imta_selected = true
# msma_selected = true
# webmail_selected = true
# mmp_selected = null
#
[STATE_BEGIN Messaging Server c281c1c51474c6883c813cbceea6fe6cf7b6e786]
Fqdn.TextField = MS.sjms.com
msg.DataPath = /SJMS/var/opt/SUNWmsgsr
com.sun.setup.panels.common.ComponentPanel.selectedcomponents = imta,msma,webmail,imta
iMS.UserId = mailsrv
iMS.Password =
iMS.GroupId = sjms
CFGDIR_URL = ldap://DIR.sjms.com:389
CFGDIR_BINDDN = cn=Directory Manager
CFGDIR_BINDPW = qrtdvaqbuisnpbuppejbtveznantre
UGDIR_URL = ldap://DIR.sjms.com:389
UGDIR_BINDDN = cn=Directory Manager
UGDIR_BINDPW = qrcxxsrrjnrrtlcqbqweyveznantre
Postmaster.TextField = pma@sjms.com
imsPassword.Password = sadmin
EmailDomain.TextField = sjms.com
OrgName.TextField = o=sjms.com,o=isp
[STATE_DONE Messaging Server c281c1c51474c6883c813cbceea6fe6cf7b6e786]
I needed the admin server to mange the Messaging instance b'cz I used schema 1 and hence iPlanet DA.
For purging it uses imadmin which needs the admin server to manage the messaging.
Don't know y the messaging configurator script installs a unmanaged instance.
The iDA webpart works fine - I can create domains/users/maillists from web interface...but CLI (hence purging) is not working now.
One more point you should note while moving from iMS 5.2 clustered env to SJES env is that....
Sun recommended single binary installation in iMS 5.2 , because it was possible. The reason given was patching is easy - so is maintenance of single version. So the binary stays on the shared DiskSet
Moving to 6.x the documents suggested using two binary method ...probably b'cz it was pkg add and there was local dependence.
There is no single binary method here, atleast not documented.
So u need to install the pkgs twice once on each node, configure twice once on each node.
Calendar server u don't need to install binaries on both sides ..it puts the binaries on shared storage.
In SJES 2005Q4 documents, they have not even mentioned about single binary installation...!!
Ok last thing....patching SJES on cluster is lot tougher...u have to decluster the messaging before u can patch!!!! which was quite simple in iMS5.2 case.
Rgds
msg_admin
