OmniMessaging Installation Guide 1.7

ManualsBrandsHP ManualsServerHP NonStop G-Series

OmniMessaging Installation Guide

07/22/04 Opsol Integrators Inc. Confidential and Proprietary 1

OmniMessaging

Installation Guide

Version 1.7

Summary of content (39 pages)

PAGE 1
OmniMessaging Installation Guide OmniMessaging Installation Guide Version 1.7 07/22/04 Opsol Integrators Inc.
PAGE 2
OmniMessaging Installation Guide 1 OVERVIEW .......................................................................................... 4 1.1 3 EASY STEPS ...................................................................................... 4 2 FTP COMMANDS TO COPY FILES FROM THE CD TO THE HIMALAYA ......... 4 3 EMS EVENTS DURING INSTALLATION ................................................... 4 4 STEPS TO EXECUTE THE INSTALL MACRO ..............................................
PAGE 3
OmniMessaging Installation Guide 9.18 9.19 9.20 9.21 9.22 9.23 9.24 9.25 10 MTAII SERVER PARAMS AND DEFINES ...................................................19 MTAR SERVER PARAMS AND DEFINES ...................................................20 DUD SERVER PARAMS AND DEFINE S .....................................................20 RECOVERY SERVER PARAMS AND DEFINE S ............................................21 OSR SERVER PARAMS AND DEFINES .....................................................
PAGE 4
OmniMessaging Installation Guide 1 Overview The install process consists of 3 easy steps, needs approximately 5 user inputs and takes approximately 15 minutes. The primary goal is simplicity for the novic e user and hence some assumptions have been made. E.g. Extracting objects, creating database files on a single volume etc. The experienced user is encouraged to edit the configuration files (using Notepad or Tedit) to tune the pathway or the SQL obey files to partition the database.
PAGE 5
OmniMessaging Installation Guide During the installation step you will be prompted to start the OmniMessaging™ EMS Distributor in a new TACL window. The OBYDIS macro uses an OmniMessaging™ EMS template. In a new TACL window type tacl> volume $omnivol.omnisubvol tacl> obey OBYDIS tacl> pause Leave this window open to receive OmniMessaging™ EMS messages. Once you are happy with the product please consider merging the system template with the OmniMessaging™ template with instructions provided later.
PAGE 6
OmniMessaging Installation Guide 5.1 Installation Location (Default Current Volume.Subvol) This is the Location where all the above- mentioned files are downloaded from the CD. 6 User Inputs needed 6.1 Instance Number (Default = 1) In normal circumstances there will be only one OmniMessaging™ instance on the system. However we support multiple instances and the Instance Number can very from 0 to 9. The instance number is used to create unique database instance and unique process names.
PAGE 7
OmniMessaging Installation Guide 6.6 MIMAP Port (Default 9723) This is the port for MIMAP server. You need to be a super group user to use a port number less than 1024. Maximum value can be 65535. 6.7 POP Port (Default 110) ** This is the port for POP server. You need to be a super group user to use a port number less than 1024. Maximum value can be 65535. 6.8 LISTNR Port (Default 1111) This is the port for Listnr server. You need to be a super group user to use a port number less than 1024.
PAGE 8
OmniMessaging Installation Guide The database files should have been created on your [database volume].imapdb[instance number] Tacl> fileinfo $[database volume].imapdb[instance number].
PAGE 9
OmniMessaging Installation Guide PROV LISTNR XLATOR SMS AMS OMNICOM ZLEADAPT Provisioning Server TCP/IP listener for the Provisioning Server Translator Server used by Provisioning Server Server for Short Messaging Service Application Management Server Command Line Interface for OmniMessaging Server accepting Serverclass send requests for sending and retrieving messages 8.3 Other files NSIMLIC SETNDR License File - 180 code. An object to populate database with default NDR messages.
PAGE 10
OmniMessaging Installation Guide 9.
PAGE 11
OmniMessaging Installation Guide 9.
PAGE 12
OmniMessaging Installation Guide PARAM NSIM-MTA-DIST PARAM NSIM-MTA-SERVERCLASS-TAG $D111 0 PARAM NSIM-MTA-STICK-TO-DOMAIN Y(RelayD)/N(Relay) PARAM OMNI-INSTANCE-NAME Insname PARAM RECOVERY -FILE-LOCATION .
PAGE 13
OmniMessaging Installation Guide 9.5 IMAP/MIMAP Distributor PARAMs Server Param PARAM NSIM-PCOL PARAM NSIM-ACOL PARAM NSIM-SERVER-CLASS PARAM NSIM-DIST-LISTEN-PORT PARAM NSIM-SERVER-TYPE PARAM NSIM- DIST-TCPNAME-1 PARAM NSIM-LIC PROCESS Suggested Value $0 $0 IMD01-SRV / MMD01-SRV 143 IMAPDST $ZTC0 NSIMLIC $S111/$M111 Description EMS Primary Collector EMS Accounting Collector Server Class Name for IMAP/MIMAP Distributor Port on which IMAP Distributor Listens Server class type TCP/IP process name.
PAGE 14
OmniMessaging Installation Guide Server Param PARAM NSIM-PCOL PARAM NSIM-ACOL PARAM NSIM-LIC TIMEOUT PARAM OWN-INSTANCE-NAME PARAM NAM-LIST-PARAM Suggested Value $0 $0 NSIMLIC 1000 MINS Insname DEFINE =MBM^QUEUE^FILE SET SERVER DEFINE =MBM^QUEUE^FILE, CLASS MAP, FILE MBMQUEUE "INSNAME,$omni1" Description EMS Primary Collector EMS Accounting Collector License file Pathway server timeout Instance name for that particular node List of node names and pathmon process names for a node.
PAGE 15
OmniMessaging Installation Guide 9.
PAGE 16
OmniMessaging Installation Guide PARAM NSIM-SERVER-TYPE PARAM NSIM-LIC PARAM NSIM-POP3-MAX-SESSION PARAM OMNI-INSTANCE-NAME POP NSIMLIC 256(SingleNode) / 15(MultiNode) Insname OMNI-OPSW- REQUESTOR $OSR1 PARAM NSIM-POP3-INACT-TIMEOUT PARAM NSIM-POP3-LOGON-TIMEOUT PARAM NSIM- HOST-NAME 30 (minutes) PARAM NSIM-POP3-DIST DEFINE =MBM^QUEUE^FILE $P111 SET SERVER DEFINE =MBM^QUEUE^FILE, CLASS MAP, FILE MBMQUEUE 9.
PAGE 17
OmniMessaging Installation Guide PARAM NSIM-PCOL PARAM NSIM-ACOL PARAM NSIM-SERVER-CLASS $0 $0 ZLE01-SRV PARAM NSIM-LIC PARAM NSIM-ZLEADAPT-MAX-SESSION PARAM NSIM- HOST-NAME PARAM OMNI-TEMP-FILE-LOC NSIMLIC 100 DEFINE =MBM^QUEUE^FILE SET SERVER DEFINE =MBM^QUEUE^FILE, CLASS MAP, FILE MBMQUEUE SET SERVER DEFINE =LDS^QUEUE^FILE, CLASS MAP, FILE LDSQUEUE DEFINE =LDS^QUEUE^FILE EMS Primary Collector EMS Accounting Collector Server Class Name for the Zle adaptor License file Number of threads OMNIMAIL $V
PAGE 18
OmniMessaging Installation Guide 9.
PAGE 19
OmniMessaging Installation Guide DEFINE =LDS^QUEUE^FILE DEFINE =RELAY^QUEUE^FILE DEFINE =MBM^QUEUE^FILE 9.
PAGE 20
OmniMessaging Installation Guide CLASS MAP, FILE MBMQUEUE 9.
PAGE 21
OmniMessaging Installation Guide PARAM NSIM-MTA-TCP-NAME-1 $ZTC0 PARAM NSIM-DUD- DOWN-MSG 75 PARAM NSIM- DUD-MAXSESSION PARAM NSIM-DUD- DOWN-NOTE-TIME 76 PARAM NSIM-DUD- DOWN- KEEP-TIME 300 PROCESS PARAM NSIM-DUD-MAX-OPEN PARAM OMNI-MX-WORKING-CACHE $dud1 100 9.21 300 32 TCP/IP process name that can access DNS server.
PAGE 22
OmniMessaging Installation Guide PARAM PARAM PARAM PARAM NSIM-ACOL NSIM-SERVER-CLASS NSIM-LIC NSIM- HOST-NAME $0 OSR01-SRV NSIMLIC OMNIMAIL PARAM OMNI-INSTANCE-NAME PARAM OMNI-OPSW-SERVERS INSNAME "insname, $OSS1" PARAM OMNI-OPSWREQ-MAX-OPENS 20 DEFINE =MBM^QUEUE^FILE SET SERVER DEFINE =MBM^QUEUE^FILE, CLASS MAP, FILE MBMQUEUE 9.
PAGE 23
OmniMessaging Installation Guide PARAM NSIM-LIC DEFINE =MBM^QUEUE^FILE TIMEOUT PARAM PARAM-COPYSRV-NAME PROCESS 9.25 NSIMLIC SET SERVER DEFINE =MBM^QUEUE^FILE, CLASS MAP, FILE MBMQUEUE 1000 MINS COPYSERVER License file Queue File Define $CP01 Copy Server process name Pathway server timeout Server Class type X-PARAMS X-params are not default server parameters, but should be added whenever a particular functionality is to be enabled.
PAGE 24
OmniMessaging Installation Guide OMNI-X-DUD-REQ-TIMEOUT 300 OMNI-X-FILTER-KEYWORD a OMNI-MTA -X-ENABLE-DUDINTERFACE i NSIM -X-SCAN-HOST-FILE i OMNI-MTA -X-ENABLE-DSN a Configurable only for RELAY server. All other MTA serverclasses use default 300 seconds. MTA or RELAY will time out if DUD does not reply back within this set value. It must be between 90 secs. to 900 secs. Used to filter recipient addresses for keywords such as “TELEX=”, “FAX=”. Only required for MTA.
PAGE 25
OmniMessaging Installation Guide 10 DATABASE TABLE INFO 10.1 System Parameter Table (NOTE: “i”= inactive, “a”= active, “-1”= no limits, relay = mail sent to outside user, NDR = Non Delivery Report The constraints are added for the following cache values for the System Parameter table.
PAGE 26
OmniMessaging Installation Guide POP_RESTRICTED_TO_SUBNETS IGNORE_QUOTAS_FOR_REPORTS IGNORE_QUOTAS_FOR_ALERTS CHAR(1) CHAR(1) CHAR(1) 'i', NOT NULL 'i', NOT NULL 'i', NOT NULL Boolean Boolean Boolean KEEP_UNDELIVERABLE_REPORTS CHAR(1) 'i', NOT NULL Boolean NDR_RELAY_OMIT_ORIG_MSG DOMAIN_LEVEL_SPAM_CHECKING MAILBOX_LEVEL_SPAM_CHECKING MAX_BLIST_DOM_CACHE CHAR(1) CHAR(1) CHAR(1) INT UNSIGNED INT UNSIGNED INT UNSIGNED LARGEINT 'a', NOT NULL 'i', NOT NULL 'i', NOT NULL 100, NOT NULL Boolean Boolean B
PAGE 27
OmniMessaging Installation Guide MAX_WLIST_DOM_KEEP_PERIOD UNSIGNED LARGEINT AUTOREPLY_INTERVAL LARGEINT WARN_MAIL_SEND_INTERVAL LARGEINT DANGLING_MSG_KEEP_PERIOD LARGEINT MAX_MBOX_PER_USER MAX_SUBSCRIPTION_PER_USER MAX_LOGIN_ATTEMPTS 300000000 NOT NULL 604800000000 NOT NULL 86400000000 NOT NULL Milli Seconds Milli Seconds Milli Seconds INT INT INT 7200000000 NOT NULL -1, NOT NULL -1, NOT NULL -1, NOT NULL Milli Seconds Number Number Number MAX_SESSIONS_PER_USER REMOVE_BCC_HEADER INT CHAR(1)
PAGE 28
OmniMessaging Installation Guide 10.2 Service Package Table (NOTE: “i”= inactive, “a” = active, “-1” = no limits ,”-2” = Use System Parameter Table value, relay = mail sent to outside user.
PAGE 29
OmniMessaging Installation Guide 10.3 Quota Table Note: This table is not populated during Installation with any default values. It gets populated only if any user specific value is modified for a user.
PAGE 30
OmniMessaging Installation Guide 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.
PAGE 31
OmniMessaging Installation Guide 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.
PAGE 32
OmniMessaging Installation Guide Similar change has to be made for PROV-SRV param PARAM NAM-LIST-PARAM "INSNAME,$omni1" Modify it to give semi-colon separated list of Node Name and fully qualified pathmon name for each node. For example Pathcom>ALTER PROV-SRV, PARAM NAM-LIST-PARAM "INSNAM1,\SYS1.$omni1;INSNAM2,\SYS2.$omni2" After this change, please start the servers at each node. Please verify your installation as mentioned below.
PAGE 33
OmniMessaging Installation Guide 14.3 Verify Installation Installation can be verified in the same way as for Single Node except for below mentioned exceptions: 1) Multinode Installation process configures pathway environment and various server classes but it doesn’t start the pathway servers. Before starting the servers above mentioned modification in the OSR and PROV server classes are to be done. 2) Instead of Instance Number Multinode Installation uses Instance alphabet. 14.3.
PAGE 34
OmniMessaging Installation Guide A. APPENDIX – SAMPLE OUTPUT A.1.1. Install Sample The following is a sample of a typical run of the Omnimessaging INSTALL macro. Bold type indicates input and sample responses. Install $OMNI04 DEMO 2> run install UNPAK - File decompression program (Kari Kujansuu/Tandem Finland 1996) Compression routines: 'zlib' by Jean-loup Gailly and Mark Adler. (ftp://ftp.uu.
PAGE 35
OmniMessaging Installation Guide RSQLCMP SETNDR SMS XLATOR ZLEADAPT ZNIMTMPL 101 700 700 700 700 839 1026 2Aug2002 17:26 255,100 NUNU 36464 31Jul2002 11:31 255,100 NUNU 1516880 3Aug2002 16:17 255,100 NUNU 521664 7Aug2002 10:53 255,100 NUNU 2008360 18NOV2002 13:34 11,255 NUNU 86016 26Jul2002 11:23 255,100 NUNU K 2 100 510 4 Summary Information Files restored = 30 Files not restored = 0 **** Installation Macro for OmniMessaging **** Enter An Instance Number: Please Enter A Number Between 0 to 9.
PAGE 36
OmniMessaging Installation Guide Enter Port For LISTNER : For Port Below 1024 You Must Be A SUPER Group User!!! Press Enter To Select Default 1111 !! 7011 7011 Listner Port Selected !! Enter Port For SMSC Usage : For Port Below 1024 You Must Be A SUPER Group User!!! Press Enter To Select Default 8702 !! 7002 7002 SMSC Port Selected !! Enter TCP/IP Process Na me : Press Enter To Select Default $ztc0. $ztc0 TCP/IP Process Name Selected !! Enter Pathway Process Name : Press Enter to select Default $omni7.
PAGE 37
OmniMessaging Installation Guide B. APPENDIX: DAT ABASE PART ITION INFORM AT ION 15 Command to add partitions ALTER TABLE ==\system.$vol1.subvol.tablename ADD PARTITION ==\system.$vol2.subvol.
PAGE 38
OmniMessaging Installation Guide =USER_MESSAGE_TB PRIMARY KEY (MAILBOX_ID, LOGIN_USER_ID, UID) =MAILBOX_BASE PRIMARY KEY (MAILBOX_ID) UNIQUE INDEX =MAILBOX_I0 ON =MAILBOX_BASE ( PARENT_MAILBOX_OR_NAME_SPACE ,PARENT_ID_TYPE ,NAME_HASH_KEY ,MAILBOX_ELEMENT_NAME ,MAILBOX_STATUS) INDEX =MAILBOX_I1 ON =MAILBOX_BASE (QUOTA_ROOT, MAILBOX_SIZE, MAILBOX_STATUS, NO_OF_MESSAGES) VIEW =MAILBOX_TB AS SELECT * FROM =MAILBOX_BASE WHERE MAILBOX_STATUS <> "d" =MAILBOX_CONTENT_BASE PRIMARY KEY ( MAILBOX_ID ,UID ) UNIQUE IN
PAGE 39
OmniMessaging Installation Guide =SUBMISSION_ADDRESS_BASE PRIMARY KEY (NAME_HASH_KEY, DOMAIN_ID, SMTP_USER) UNIQUE INDEX =SUBMISSION_ADDRESS_I0 ON =SUBMISSION_ADDRESS_BASE (ADDRESS_ID) CREATE INDEX =SUBMISSION_ADDRESS_I1 ON =SUBMISSION_ADDRESS_BASE (TARGET_MAILBOX, SUBADDR_STATUS) CREATE INDEX =SUBMISSION_ADDRESS_I2 ON =SUBMISSION_ADDRESS_BASE (ACCOUNT_ID, ADDRESS_TYPE) CREATE VIEW =SUBMISSION_ADDRESS_TB AS SELECT * FROM =SUBMISSION_ADDRESS_BASE WHERE SUBADDR_STATUS <> "d" =SUBSCRIPTION_TB PRIMARY KEY ( US