· For information on hardware and software requirements for setting up of secondary AM server, see Hardware and Software Requirements section in OFS AAAI Application Pack Installation Guide.
· Execute the following SQL script on Configuration Schema by replacing <NEWAMIPADDRESS> with the IP address/Hostname of the new AM node you want to set up and <EXISTINGAMIPADDRESS> with the IP address/IP address of the existing AM server:
INSERT INTO ficsysmaster (WEBIPADDRESS,APPIPADDRESS,DBIPADDRESS,ETLAPPHOME,NOOFCPUS,VMEMORY,PMEMORY,CACHE,NOOFTHREADS,IOTRANSFER,MAXTRANSPERSEC,DISKSDBSTRIPING,DISKSFILESTRIPING,MAXFILESIZE,MAXFTPFILESIZE,MAXFILENAMELEN,OSDATABLOCKSIZE,DATASETTYPE,STAGEPATH,DBFTPSHARE,DBFTPUSERID,DBFTPPASSWD,DBFTPPORT,DBFTPDRIVE,APPFTPSHARE,APPFTPPORT,APPFTPDRIVE,APPFTPUSERID,APPFTPPASSWD,WEBFTPSHARE,WEBFTPPORT,WEBFTPUSERID,WEBFTPDRIVE,WEBFTPPASSWD,OSTYPE,SOCKETSERVERPORT,SEC_SHARE_NAME,SEC_USERID,SEC_PASSWD,F_ISPRIMARY,N_PRECEDENCE)
SELECT WEBIPADDRESS,APPIPADDRESS,'<NEWAMIPADDRESS>',ETLAPPHOME,NOOFCPUS,VMEMORY,PMEMORY,CACHE,NOOFTHREADS,IOTRANSFER,MAXTRANSPERSEC,DISKSDBSTRIPING,DISKSFILESTRIPING,MAXFILESIZE,MAXFTPFILESIZE,MAXFILENAMELEN,OSDATABLOCKSIZE,DATASETTYPE,STAGEPATH,DBFTPSHARE,DBFTPUSERID,DBFTPPASSWD,DBFTPPORT,DBFTPDRIVE,APPFTPSHARE,APPFTPPORT,APPFTPDRIVE,APPFTPUSERID,APPFTPPASSWD,WEBFTPSHARE,WEBFTPPORT,WEBFTPUSERID,WEBFTPDRIVE,WEBFTPPASSWD,OSTYPE,SOCKETSERVERPORT,SEC_SHARE_NAME,SEC_USERID,SEC_PASSWD,F_ISPRIMARY,N_PRECEDENCE FROM ficsysmaster
WHERE DBIPADDRESS='<EXISTINGAMIPADDRESS>'
To set the newly added AM node as primary node, execute the following SQL script by replacing <NEWAMIPADDRESS> with the IP address/Hostname of the newly added AM node:
UPDATE FICSYSMASTER SET F_ISPRIMARY = 'Y', N_PRECEDENCE=200 WHERE DBIPADDRESS = '<NEWAMIPADDRESS>'
Following are the steps involved in setting up of secondary AM servers:
1. Copy the following folders to the secondary AM server from the primary OFSAA server:
1 $FIC_HOME/conf
2 Entire ficdb and its sub-directories
3 .profile file from $HOME directory of primary OFSAA server
2. Perform the following configurations in the secondary AM server:
a. Modify the following variables in the .profile file:
i. Set FIC_HOME variable to the directory which is created as OFSAA home (should contain ficdb and conf folders).
NOTE |
It is advisable to setup the OFSAA secondary AM under the same user as in the primary server. For example, if OFSAA is installed on the primary server under /scratch/ofsaausr, you can setup the secondary OFSAA instance as well under /scratch/ofsaausr user. |
3. Set FIC_DB_HOME variable to the directory where the /ficdb folder is copied under secondary AM server.
AM_HOME=$FIC_HOME/ficdb
export AM_HOME
AM_CONF_FILE=$FIC_DB_HOME/conf/am.conf
export AM_CONF_FILE
FICTEMP=$FIC_DB_HOME/conf
export FICTEMP
4. Ensure the following variables are pointed to valid hostname/IP address on which Message Server and Router server and Router engines are running.
MESSAGE_SERVER_HOST=10.XXX.XXX.XXX
export MESSAGE_SERVER_HOST
MESSAGE_SERVER_PORT=6666
export MESSAGE_SERVER_PORT
FIC_ROUTER_HOST=10.XXX.XXX.XXX
export FIC_ROUTER_HOST
FIC_ROUTER_PORT=7777
export FIC_ROUTER_PORT
5. Set JARPATH variable to $FIC_DB_HOME/lib.
6. Ensure ORACLE_SID variable is pointed to correct Oracle Instance and user can successfully connect to this instance from the Secondary AM server using sql/plus.
7. Update secondary AM node details in the AM.conf file present under $FIC_HOME/ficdb/conf path.
<AM_HOST>`<Secondary AM node host name/IP Address>`
<AM_PORT>`<Secondary AM node Port number>`
NOTE |
Do not alter <ROUTER_NAME> and <ROUTER_PORT> values. |
8. Modify the logger XML files such as MFLogger.xml, OFSAALogger.xml, DQLogger.xml, and PR2Logger.xml available under $FIC_DB_HOME/conf folder with the secondary AM Server $FIC_HOME path.