OmniMessaging Installation Guide 1.7

OmniMessaging Installation Guide
07/22/04 Opsol Integrators Inc. Confidential and Proprietary 30
11 Installing the Java Client
Refer to the OmniMessaging Provisioning Client User Guide.
12 Adding users, domains etc
This information is provided in the OmniMessaging Provisioning Client User Guide.
13 Other considerations
13.1 Disk Selection
OmniMessaging requires an audited disk for installation.
13.2 Ongoing Configuration changes
After the install macro completes, the edit files are permanently altered to reflect the
user environment. From this point on the user is encouraged to directly maintain the
configuration using the edit files. Obeying/running the files again will result in an
upgraded environment.
13.3 Pathmon Usage
The Pathmon Monitor is used get persistence. It starts the NUMSTATIC servers but
will never start the dynamic servers. We do not accept Pathway requests and hence
the dynamic servers will never start. Our processes are multithread and hence can
manage multiple simultaneous connections. Pathmon is thus used to ensure 24 * 7
availability in case the processes fail.
13.4 Creating multiple instances
The modified edit files cannot be used again with the INSTALL macro for
creating another instance.
To create a new instance it is recommended that you use the install macro. Copy the
PAK release file and install macro to a new clean subvolume and then execute the
install macro.
13.5 Uninstall
The uninstall process is carried out by obeying the CLEANUP macro. It stops all
servers and shuts down the Pathmon, drops all tables, server objects and catalog,
and purges all files in the subvol. It is to be used only in the rare case that you
want to delete the OmniMessaging instance from the system.
13.6 DNS Server accessibility
OmniMessaging requires a DNS Server for processing. The Himalaya Server should
have access to a DNS Server on the Network. The ZTCPIP.RESCONF file should have
an entry of the DNS Server for the same.