Does The Order Of Defining Peers Matter In Configuring Instant Messaging Server Pool? (Doc ID 2180419.1)

Last updated on SEPTEMBER 18, 2016

Applies to:

Oracle Communications Instant Messaging Server - Version 10.0.0 and later
Information in this document applies to any platform.

Goal

Using:  Instant Messaging 10u1 for configuring multiple nodes for server pooling.

Example on each individual system in the IM server pool, will need to do something like this:

imconfutil --config ./iim.conf.xml set-prop iim_server.serverid=peer7.imhostname04 iim_server.password=xx iim_server.domainname=imserver.oracle.com

imconfutil --config ./iim.conf.xml add-coserver id=coserver1 serverid=peer1.imhostname01 password=xx host=imhostname01.oracle.com domain=imserver.oracle.com
imconfutil --config ./iim.conf.xml add-coserver id=coserver2 serverid=peer2.imhostname02 password=xx host=imhostname02.oracle.com domain=imserver.oracle.com
imconfutil --config ./iim.conf.xml add-coserver id=coserver3 serverid=peer3.imhostname03 password=xx host=imhostname03.oracle.com domain=imserver.oracle.com
imconfutil --config ./iim.conf.xml add-coserver id=coserver4 serverid=peer4.mmpp01 password=xx host=mmpp01.oracle.com domain=imserver.oracle.com
imconfutil --config ./iim.conf.xml add-coserver id=coserver5 serverid=peer5.mmpp02 password=xx host=mmpp02.oracle.com domain=imserver.oracle.com
imconfutil --config ./iim.conf.xml add-coserver id=coserver6 serverid=peer6.mmpp03 password=xx host=mmpp03.oracle.com domain=imserver.oracle.com

The "peerN" number must be consistent across all of them.
On every system, peer1 must be imhostname01.
Peer2, must be imhostname02 and so on.

But on each one, it must be defined to itself via the first set-prop command above, rather than add-coserver.

The question is: Does it matter what order the above commands are executed in??

i.e. Is there any reason the following would not work just as well:

imconfutil --config ./iim.conf.xml add-coserver id=coserver1 serverid=peer1.imhostname01 password=xx host=imhostname01.oracle.com domain=imserver.oracle.com
imconfutil --config ./iim.conf.xml set-prop iim_server.serverid=peer7.imhostname04 iim_server.password=xx iim_server.domainname=imserver.oracle.com
imconfutil --config ./iim.conf.xml add-coserver id=coserver2 serverid=peer2.imhostname02 password=xx host=imhostname02.oracle.com domain=imserver.oracle.com
imconfutil --config ./iim.conf.xml add-coserver id=coserver3 serverid=peer3.imhostname03 password=xx host=imhostname03.oracle.com domain=imserver.oracle.com
imconfutil --config ./iim.conf.xml add-coserver id=coserver4 serverid=peer4.mmpp01 password=xx host=mmpp01.oracle.com domain=imserver.oracle.com
imconfutil --config ./iim.conf.xml add-coserver id=coserver5 serverid=peer5.mmpp02 password=xx host=mmpp02.oracle.com domain=imserver.oracle.com
imconfutil --config ./iim.conf.xml add-coserver id=coserver6 serverid=peer6.mmpp03 password=xx host=mmpp03.oracle.com domain=imserver.oracle.com

It is exactly the same commands, just they are in order by peer number instead of doing "this system" first.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms