OmniMessaging Installation Guide 1.7

OmniMessaging Installation Guide
07/22/04 Opsol Integrators Inc. Confidential and Proprietary 31
13.7 Merging the EMS template
OmniMessaging™ has its own EMS template that should be merged with the system
template. The system template normally resides in the current sysnn and the
following steps are used to create a merged template
tacl> volume $omnivol.omnisubvol
tacl> templi omnires, omniems
>file $system.sysnn.template
>file znimtmpl
>exit
These steps have created the OMNIEMS nonresident EMS template and the OMNIRES
resident EMS template. We will use the OMNIEMS template when starting our
EMSDIST by specifying the define as
tacl> ADD DEFINE =_EMS_TEMPLATES, FILE OMNIEMS
Now start the EMSDIST as you did before or use the OBYDIS macro provided.
14 Multinode Considerations
Multinode Installation has an additional wrapper macro to take Multinode specific
inputs.
14.1 Steps to execute Multinode Installation
1) Multinode consists of single PAK file ZIMAPxxx. FTP it to desired subvol on
Himalaya.
2) At the desired location on Himalaya where the PAK file is downloaded give the
following set of commands.
3) Tacl>unpak ZIMAPxxx ,*.*.*,LISTALL,VOL $vol.subvol,myid
Tacl>RUN MULTIINS
MULTIINS macro will generate sets of INSTALLx and ZINSTALLx depending upon
the number of nodes.
Please copy these to desired nodes. And give the following commands at that
particular node where files are copied.
Tacl>run INSTALLx
The tacl prompt is displayed when the installation macro has completed.
In the pathmon environment of each node, Please change the following params;
For server class OSR0x-SRV modify
PARAM OMNI-OPSW-SERVERS "insname, $OSS1"
to give a semi-colon separated list of Node Name and fully qualified OSS process
name for each node.
For example,
Pathcom>ALTER SERVER OSR01-SRV, PARAM OMNI-OPSW-SERVERS
“INSNAM1,\SYS1.$OSS1;INSNAM2,$OSS2"
Where \SYS1 and \SYS2 are node names.