ecs application install guide - itaas, a cognizant · web viewecs install guide release 2.2.2...

ECS Install GuideRelease 2.2.2May 2008

Proprietary NoticeInformation in this document is confidential and proprietary to itaas, Inc. Access to and use of this information is limited strictly to licensees of itaas, Inc. and is subject to the terms of a separate and appropriate written license agreement between the Licensee and itaas, Inc. The information in this document may be protected by patent applications owned by itaas, Inc.In addition, the information in this document is subject to change without notice and does not represent a commitment on the part of itaas, Inc. The software described in this document may be used only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license or non-disclosure agreement. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the licensee’s personal use without express written permission of itaas, Inc.All specifics of the product, its use and implementation contained in this document are provided in good faith. However, all warranties, implied or expressed, including but not limited to implied warranties of merchantability or fitness for a particular purpose are excluded.This document is intended solely to assist the Licensee in the use of the itaas, Inc. Licensed Software Product and for no other purpose. itaas, Inc. shall not be liable, in any way under any theory of law, for any loss or damage of any kind what so ever, arising from the use of any of the information contained in this manual, or any error or omission in the information, or any incorrect use of the Software Product.Copyright © 2006 itaas, Inc. All rights reserved.itaas is a. registered trademark of itaas, Inc.

itaas, Inc., Confidential and Proprietary - 2 -

Revision HistoryRevision Number Date Changes Made

1.0 07/25/2007 Initial version.1.1 05/07/2008 Revised.

- 3 - itaas, Inc., Confidential and Proprietary

Table of Contents1 INTRODUCTION....................................................................................................................................... 6

1.1 SCOPE............................................................................................................................................... 61.2 AUDIENCE........................................................................................................................................... 61.3 CONVENTIONS.................................................................................................................................... 6

2 ECS SERVER SOFTWARE INSTALLATION...........................................................................................72.1 ECS APPLICATION SOFTWARE INSTALL.................................................................................................7

2.1.1 Verify user accounts.......................................................................................................................................72.1.2 Create appropriate install structure..............................................................................................................72.1.3 Install the ECS server application from the archive files..............................................................................72.1.4 Install 3rd Party Packages..............................................................................................................................82.1.5 Setup the ECS server software.......................................................................................................................92.1.6 Verify Setup Files.........................................................................................................................................122.1.7 Move the ECS data log processing area (Optional step).............................................................................13

2.2 ECS DATABASE CREATION...............................................................................................................142.2.1 Create the Database Instance......................................................................................................................142.2.2 Create ECS Database objects......................................................................................................................152.2.3 Set start date for database partitions...........................................................................................................172.2.4 Modify oracle configuration to allow for redundancy of control and redo files.........................................18

2.3 SET UP THE STARTUP SCRIPTS..........................................................................................................192.3.1 Set Oracle to start up on boot......................................................................................................................192.3.2 Validate the TNS listener to be active..........................................................................................................192.3.3 Validate dbshut script..................................................................................................................................192.3.4 Validate /etc/init.d/dbora.............................................................................................................................192.3.5 Set to launch oracle at run level 3...............................................................................................................202.3.6 Update system startup script........................................................................................................................20

2.4 LOAD THE SG/QAM DATA................................................................................................................. 222.4.1 Extracting topology from the DNCS............................................................................................................222.4.2 Loading DNCS topology into the ECS database.........................................................................................22

2.5 UPGRADING APPLICATION CODE.........................................................................................................252.5.1 Code Patch 1 install.....................................................................................................................................25

2.6 HEAD-END SPECIFIC CONFIGURATIONS..............................................................................................252.6.1 Setting the Time zone...................................................................................................................................252.6.2 DNCS information validation in the database.............................................................................................252.6.3 Update collector with DNCS information....................................................................................................262.6.4 Configure ECS processes based on VOD vendors.......................................................................................262.6.5 Update conf files based on remote server version.......................................................................................292.6.6 Customizing Headend GUI..........................................................................................................................30

2.7 VERIFY APPLICATION SCRIPTS............................................................................................................312.7.1 Verify /etc/files.............................................................................................................................................31

2.8 APPLICATION STARTUP...................................................................................................................... 322.8.1 Set ECS cronjobs..........................................................................................................................................322.8.2 Start the rsync daemon.................................................................................................................................322.8.3 Start the ECS processes...............................................................................................................................33

2.9 CHANGING THE SERVER RUN-LEVEL...................................................................................................352.10 TEST THE INSTALLATION....................................................................................................................362.11 FINAL CHECKLIST.............................................................................................................................. 37

2.11.1 RedHat Checklist / Notes.........................................................................................................................372.11.2 Oracle Checklist / Notes..........................................................................................................................37


3 Support.................................................................................................................................................... 38


1IntroductionThis document provides the information needed to install and configure the ECS application software for the client’s ECS Server. The ECS server is the server component of the MSO Video on Demand (VOD) monitoring system that provides statistics and error/event information from all the various components, which can help with troubleshooting problems throughout the network. As many different vendors provide system components for the VOD infrastructure, the tool collects information from the various sources and brings it into a consolidated information model that can be used to monitor system health and troubleshoot problems. Installed on a web server and accessed from virtually anywhere, its robust interface gives you the ability to “drill down” through the information to go from big picture to the details of your cable systems.

1.1ScopeThis document defines the procedure for the installation of the ECS application. It also provides steps for creating and optimizing ECS database, as well as configuring the server to collect and parse site-specific remote system logs.

1.2AudienceThe target audience for this document is the installer of the ECS Server, typically a system administrator.

1.3ConventionsThis document contains examples of text that appears on the computer screen of the installer during specific steps of the procedure.

Commands shall appear as bold text with grey color background.

# Shell Command.

Script/Code snippets shall appear as text with blue color background. This is a sample script snippet.

Script/Code output shall appear with grey color background.

This is an output data.

The “$” prompt indicates the user is logged in as “isaecs”, or “oracle”.

The “#” prompt indicates the user is logged in as “root”.


2ECS Server software installation

2.1ECS application software installThe ECS software distribution package includes several system configuration files, scripts and database templates as well as the ECS Application software. This section provides detail instructions to install the ECS system.

2.1.1 Verify user accountsInstallation and operation of the ECS server software requires user id ‘isaecs’ with home directory ‘/opt/isaecs’. The directory, ‘/opt/isaecs’, is referred to as ISAECS_HOME and is the top level directory for the ECS installation. For proper installation, the ‘oracle’ user must be a member of the ‘isaecs’ user group. 1 Verify the home directory for user ‘isaecs’.

$ su – isaecs$ pwd

[isaecs@isaecs ~]$ pwd/opt/isaecs

Note: If the output of the above ‘pwd’ command is not ‘/opt/isaecs’, then issue the below command to set the correct home directory.$ su - // login as user ‘root’# usermod -d /opt/isaecs isaecs

2 Verify the group for user ‘oracle’. Change it if required.

# usermod -G isaecs,dba oracle

2.1.2 Create appropriate install structure.1 Login as user ‘isaecs’.

$ su - isaecs

2 Create a directory called ‘download’. This directory is used to hold all the install packages for the ECS Server.

$ mkdir download


2.1.3 Install the ECS server application from the archive files

The distribution archives should be copied to the ‘ISAECS_HOME/download’ directory. The naming convention for the ECS server distribution archive is as follows:

isaecs-RELEASE-DATE.tar.gz1 Use the ECS applications’ install CD to copy the application release 2.2.2 distribution archive

“isaecs-ECS_2_2_2-27Aug2007.tar.gz” into the directory /opt/isaecs/download on the ECS server. The tar ball is also available on itaas ftp server (under /ECS_2/release2.2.2 folder).

# su - isaecs$ cp /media/cdrom/download/isaecs-ECS_2_2_2-27Aug2007.tar.gz /opt/isaecs/download

Note: You may use cp, scp, ftp or whatever is appropriate in your environment for copying the archive distribution file.2 Copy all the other remaining files into “/opt/isaecs/download” by giving the following command.

$ cd /opt/isaecs/download$ cp /media/cdrom/download/* .

3 Check to see if the following files are present in “/opt/isaecs/download” folder.

$ ls /opt/isaecs/download

-bash-3.00$ ls -ltotal 211224-rwxr-xr-x 1 isaecs isaecs 5949295 Jul 30 12:07 apache-tomcat-5.5.20.tar.gz-rw-r--r-- 1 isaecs isaecs 160337644 Jul 30 11:32 isaecs-ECS_2_2_2-27Aug2007.tar.gz-rw-rw-r-- 1 isaecs isaecs 55 Aug 27 2007 cksumEcs2.2.2.txt-rwxr-xr-x 1 isaecs isaecs 49529389 Jul 30 12:01 jdk-1_5_0_10-linux-i586.bin

Note: If any of the above files are not present, download it from itaas ftp server under “/ECS_2/release2.2.2” folder. 4 Verify the cksum of the install tarball with the contents of ‘cksumEcs2.2.2.txt’ file. The output of

the below two commands must be equal.

$ cat cksumEcs2.2.2.txt$ cksum isaecs-ECS_2_2_2-27Aug2007.tar.gz

5 Extract the contents of the archive.

$ cd /opt/isaecs$ tar -xzvf download/isaecs-ECS_2_2_2-27Aug2007.tar.gz

6 Verify the directory structure under ‘/opt/isaecs’ directory.

$ ls

-bash-3.00$ lsbin conf ddl Docs download etc lib remote UI_2_1

Note: The ECS Application software is now loaded on your server. However, it is not yet configured to run.

2.1.4 Install 3rd Party PackagesThis section provides detail about installing 3rd party software.


2.1.4.1 Install Java SDKThe ECS UI requires the Java Software Development Kit (JDK) version 1.5.1 Login as user ‘root’.

$ su –

2 Verify file size and executable permissions on the java 1.5 self-extracting binary.

# cd /opt/isaecs/download# cksum jdk-1_5_0_10-linux-i586.bin

[root@isaecs download]# cksum jdk-1_5_0_10-linux-i586.bin 4195168891 49529389 jdk-1_5_0_10-linux-i586.bin

# chmod +x jdk-1_5_0_10-linux-i586.bin

3 Change directory to the ‘/opt’, and run the self-extracting binary.

# cd /opt# ./isaecs/download/jdk-1_5_0_10-linux-i586.bin

Note: The binary code license is displayed, and you are prompted to agree to its terms. The Java SDK files are installed in a directory called jdk1.5.0_10 in the current directory.# ls –l ./jdk1.5.0_10/

[root@isaecs opt]# ls -l ./jdk1.5.0_10/total 17348drwxr-xr-x 2 root root 4096 Nov 9 19:33 bin-r--r--r-- 1 root root 2487 Nov 9 19:00 COPYRIGHTdrwxr-xr-x 8 root root 4096 Nov 9 19:33 demodrwxr-xr-x 3 root root 4096 Nov 9 19:33 includedrwxr-xr-x 6 root root 4096 Nov 9 19:33 jredrwxr-xr-x 2 root root 4096 Jan 11 16:09 lib-r--r--r-- 1 root root 17292 Nov 9 19:00 LICENSEdrwxr-xr-x 4 root root 4096 Nov 9 19:33 man-r--r--r-- 1 root root 20415 Nov 9 19:00 README.htmldrwxr-xr-x 4 root root 4096 Nov 9 19:33 sample-rw-r--r-- 1 root root 17540706 Nov 9 19:00 src.zip-r--r--r-- 1 root root 66673 Nov 9 19:00 THIRDPARTYLICENSEREADME.txt

4 Verify JSDK is installed properly, by checking the java version, as user ‘isaecs’.

# su – isaecs$ /opt/jdk1.5.0_10/bin/java -version

[isaecs@isaecs ~]$ /opt/jdk1.5/bin/java -versionjava version "1.5.0_10"Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)

2.1.5 Setup the ECS server software1 Login as user “root”.

$ su -

2 Execute the below command to verify the DNCS_LIST tag in the “/opt/isaecs/conf/HeadEnd.cfg” file.

# grep DNCS_LIST /opt/isaecs/conf/HeadEnd.cfg


Note: If the server needs to be configured to monitor multiple DNCSs; then set the DNCS_LIST variable to be a list that corresponds the number of Head Ends (DNCSs) being monitored. The DNCS_LIST variable should be enclosed in double quotes and set to a numerical sequence starting with one and separated by spaces (e.g. the default setting is DNCS_LIST=”1” for sites monitoring only one Head End. For three DNCSs, set DNCS_LIST=”1 2 3”)3 Execute the “setupECS” script by giving the following command at the prompt.

Note: You’ll be prompted to enter ‘yes’ to confirm if HeadEnd.cfg file is updated with site specifications. This script will unpack several system scripts and configuration files, install Tomcat, create appropriate log structure for receiving and processing logs from remote components; as well as put the ECS database templates in place for building the Oracle database objects needed by the ECS Application.# cd /opt/isaecs/bin# ./setupECS

[root@localhost bin]# ./setupECSHas the file: "/opt/isaecs/conf/HeadEnd.cfg"been updated with this sites specfic information (yes:no) ? yes

Installing configuration files to /etc ..../etc/./etc/init.d/./etc/init.d/dbora./etc/init.d/tomcat./etc/catalina.sh./etc/rc.local./etc/rsyncd.conf./etc/server.xml./etc/profile.d/./etc/profile.d/setAlias.sh./etc/profile.d/setCVS.sh./etc/profile.d/setEnv.sh./etc/profile.d/setJava.sh./etc/profile.d/setLD.sh./etc/profile.d/setLocale.sh./etc/profile.d/setManPath.sh./etc/profile.d/setTZ.sh./etc/profile.d/setora.sh./etc/snmp/./etc/snmp/snmpd.conf./etc/snmp/snmptrapd.conf./etc/xinetd.d/./etc/xinetd.d/rsyncDone

Create /usr/javaInstalling Tomcat ...Installing Jakarta Tomcat-5.5.20 ... OK.

Done

Installing Oracle listener files ...Installing Oracle templates for dbca ...Adding listener to dbstart/dbshut script ... Adding listener to dbstart script ...DoneInstalling Oracle startup script ...Done

Creating directories for rsync-ed files.


/opt/isaecs/archiveoda btm bms drm dsm qam modServer snoop tcpdump vod OK/opt/isaecs/logsoda btm bms drm dsm qam modServer snoop tcpdump vod OK/opt/isaecs/rsync/logsoda btm bms drm dsm qam modServer snoop tcpdump vod OK/opt/isaecs/rsync/laboda btm bms drm dsm qam modServer snoop tcpdump vod OKDone

Creating directories for locally generated files./opt/isaecs/archivealerts ecs-runtime/opt/isaecs/logsalerts ecs-runtimeDone

Creating links from /data to /opt/isaecsDone

Checking runtime directories.Create /opt/isaecs/logs/ecs-runtime/statusCreate /opt/isaecs/logs/uiDone

Create /opt/ecsdocsInstalling perl Modules ... warning: /opt/isaecs/bin/perl-Time-HiRes-1.38-3.i386.rpm: V3 DSA signature: NOKEY, key ID db42a60e package perl-Time-HiRes-1.55-3 (which is newer than perl-Time-HiRes-1.38-3) is already installed file /usr/share/man/man3/Time::HiRes.3pm.gz from install of perl-Time-HiRes-1.38-3 conflicts with file from package perl-Time-HiRes-1.55-3Done

Putting the Library files for GNU compiler ... /usr/local/lib/libccext2-1.0.so.0tar: Removing leading `/' from member names/usr/local/lib/libccext2-1.0.so.0.0.8/usr/local/lib/libccext2.so/usr/local/lib/libccgnu2-1.0.so.0/usr/local/lib/libccgnu2-1.0.so.0.0.8/usr/local/lib/libccgnu2.soDone

The Library files are placed at /usr/local/lib

setupECS Completed.

total 96drwxr-sr-x 14 isaecs isaecs 4096 Jul 30 12:21 archivedrwxr-xr-x 2 isaecs isaecs 4096 Jul 30 11:10 bindrwxr-xr-x 5 isaecs isaecs 4096 Jul 30 11:06 confdrwxr-xr-x 4 isaecs isaecs 4096 Jul 30 11:06 ddldrwxr-xr-x 2 isaecs isaecs 4096 Jul 30 11:06 Docsdrwxr-xr-x 2 isaecs isaecs 4096 Jul 30 12:07 downloaddrwxr-xr-x 6 isaecs isaecs 4096 Jul 30 11:06 etcdrwxr-xr-x 2 isaecs isaecs 4096 Jul 30 11:10 libdrwxr-sr-x 15 isaecs isaecs 4096 Jul 30 12:21 logsdrwxr-xr-x 2 isaecs isaecs 4096 Jul 30 11:10 remotedrwxr-sr-x 4 isaecs isaecs 4096 Jul 30 12:21 rsyncdrwxr-xr-x 9 isaecs isaecs 4096 Jul 30 11:10 UI_2_1


You should now log in as oracle and run the DBCA application:su - oracle/opt/oracle/product/9.2.0/bin/dbca

4 Verify that ownership of symbolic file links “logs”, “archive” and “rsync” under “/data” folder is isaecs:isaecs.

$ ls –l /data/

-bash-3.00$ ls -l /data/total 36lrwxrwxrwx 1 isaecs isaecs 19 Nov 21 11:32 archive -> /opt/isaecs/archivelrwxrwxrwx 1 isaecs isaecs 16 Nov 21 11:32 logs -> /opt/isaecs/logsdrwx------ 2 root root 16384 Nov 20 13:12 lost+founddrwxr-xr-x 3 oracle dba 4096 Nov 21 11:33 oradatalrwxrwxrwx 1 isaecs isaecs 17 Nov 21 11:32 rsync -> /opt/isaecs/rsync

5 Make sure each directory under “/opt/isaecs” is owned by isaecs:isaecs.

$ cd /opt/isaecs$ ls -l

-bash-3.00$ ls -ltotal 88drwxr-sr-x 12 isaecs isaecs 4096 Nov 22 15:44 archivedrwxrwxr-x 2 isaecs isaecs 4096 May 21 2004 bindrwxrwxr-x 2 isaecs isaecs 4096 Nov 27 05:41 confdrwxrwxrwx 2 isaecs isaecs 4096 Nov 27 15:24 ddldrwxr-xr-x 2 isaecs isaecs 4096 Nov 27 15:40 Docsdrwxr-xr-x 2 isaecs isaecs 4096 Nov 21 11:29 downloaddrwxrwxr-x 5 isaecs isaecs 4096 May 21 2004 etcdrwxr-sr-x 13 isaecs isaecs 4096 Nov 21 16:47 logsdrwxr-sr-x 4 isaecs isaecs 4096 Nov 21 11:32 rsyncdrwxrwxr-x 2 isaecs isaecs 4096 Nov 27 05:45 remote drwxrwxr-x 14 isaecs isaecs 4096 May 21 2004 UI_2_1

2.1.6 Verify Setup FilesThe setup script installs 3 files in the “/etc/profile.d” directory that should be verified before proceeding. These files are “setora.sh”, “setEnv.sh” and “setJava.sh”. The default values for the environmental settings should be correct for most installations, but you should verify that values in these files match your system configuration. The following tables show the default settings for each file.a Variables in “/etc/profile.d/setJava.sh”:

Variable Name Default ValueCLASSPATH /usr/java/java/jre/lib:/opt/oracle/product/9.2.0/JRE/lib/:/opt/oracle/product/9.2.0/

jdbc/lib/ojdbc14.jar

b Variables in “/etc/profile.d/setora.sh”:

Variable Name Default ValueORACLE_HOME /opt/oracle/product/9.2.0ORACLE_SID ECSISAECS_DB //localhost:1521/ecsPATH $PATH:$ORACLE_HOME/bin


LD_LIBRARY_PATH $LD_LIBRARY_PATH:$ORACLE_HOME/lib

c Variables in “/etc/profile.d/setEnv.sh”:

Variable Name Default ValueISAECS_HOME /opt/isaecsPATH /opt/isaecs/bin:$PATH

2.1.7 Move the ECS data log processing area (Optional step)

Depending on the disk partitioning and file system setup, you may want to move the directories involved in ECS data log processing. Large amounts of data are moved through these areas as the ECS processes incoming data from the monitored systems. The basic data flow is as follows:

ECS Log Processing Flow

Note: The contents of directories “/opt/isaecs/rsync/logs” and “/opt/isaecs/logs” must be on the same file system. This is required since hard links are used to manipulate the files.If you determine that these directories need to be moved, perform the following steps as root user:

su -cd /opt/isaecsmv rsync <-new location->mv logs <-new location->mv archive <-new location->ln -s <-new location->/rsync /opt/isaecs/rsyncln -s <-new location->/logs /opt/isaecs/logsln -s <-new location->/archive /opt/isaecs/archivechmod 777 rsync logs archivecd <-new location->chown isaecs:isaecs rsync logs archivechmod 777 rsync logs archive


Note: These steps can be performed later, but may be more time consuming and will require turning off the rsync daemon and stopping the ECS server processes.


2.2ECS Database CreationCreating the ECS database is basically 2 steps. The first step is to create an Oracle database instance. The second step is to create the ECS database objects.

2.2.1 Create the Database Instance1 As user ‘root’, reboot the server by giving the following command,

# shutdown –r now

2 After the server is up, Log in as user ‘oracle’ in order to create a database.

# su - oracle

3 Verify the database templates under ‘/opt/oracle/product/9.2.0/assistants/dbca/templates’ directory. The template ‘vodmon.dbt’ is for the production ECS installation, whereas ‘ecs_lab.dbt’ is for the Lab ECS installation.

4 Run the ‘dbca’ utility located in the $ORACLE_HOME/bin directory. Execute the below commands,

$ cd $ORACLE_HOME/bin$ ./dbca

5 A ‘Database Configuration Assistant’ GUI Java application will walk you through the creation of a database. Accept the default of ‘create a database’. Click Next. For the type of database, select the option that says vodmon if you are building the Production ECS Box and ecs_lab, if you are building the Lab ECS box. The next few windows are all default choices.

6 In the screen for selecting percentage of the memory to be given to the oracle, enter 50% if the system memory is 1GB or less. Enter 40% if the system memory is 2GB or more.

7 Choose the default options for remaining screens. Creating the database takes a significant amount of time (about ½ an hour), so be prepared to wait for it to finish.

8 If you encounter the error message “ORA-29807:'specified operator does not exist'” during 'create data dictionary views.' part of dbca, then follow instructions in step 9, 10, and 12. Otherwise, skip to step 11.

9 Edit the script ‘catxml.sql’ under ‘$ORACLE_HOME/rdbms/admin’, and comment out the last line which will run prvtxml.plb. Execute the below commands as user ‘oracle’.

$ cd $ORACLE_HOME/rdbms/admin$ vi catxml.sql

Note: Put – at the beginning of the last line of the catxml.sql script to comment out the execution of prvtxml.plb script. See the below few lines of the ‘catxml.sql’ script after commenting out the last line.-bash-3.00$ tail catxml.sqlRem

@@dbmsxmlt.sql@@prvtxmlt.plb

@@dbmsuri.sql@@prvturi.plb

@@dbmsxml.sql--@@prvtxml.plb


10 Once the script is edited, go back to your DBCA screen and click 'Ignore'’. The database creation using DBCA should now proceed without additional errors.

11 During the final stages of database instance creation you will be prompted for passwords for “SYS” and “SYSTEM” database users. Enter the values as per in table below.

USER PASSWORDSYS itaasecsSYSTEM itaas

Execute step 12 only if steps 9 and 10 were executed. Otherwise, skip to step 13.12 Once DBCA has completed database creation, run the 'prvtxml.plb' script independently, as the

user SYS. Also verify that there are no invalid objects. Execute the below commands as user ‘oracle’.

$ su – oracle$ cd $ORACLE_HOME/rdbms/admin$ sqlplusUser Name: connect /oracle as sysdbaSQL> @prvtxml.plbSQL> select * from dba_objects where owner = 'SYS' and status = 'INVALID';

Note: If the above sql command displays any invalid object, then run the 'utlrp.sql' script to validate those objects. If there are significant errors, you may need to drop the database and start over. If, and only if, the database creation is not completed, and you need to re-install the database, then you must first ‘drop the database’ and start with a clean slate as follows.$ cd $ORACLE_HOME/bin$ ./dbca

Choose the ‘Delete a Database’ Radio Button. Click ‘Next’. Select ‘ecs’ as the db you wish to delete. Click ‘OK’. Click on ‘YES’ to confirm deletion of database. Close the applet. Once the database is deleted, re-execute steps 4 to 12 as required.

Note: The web site http://www.puschitz.com is useful for researching Oracle and dbca issues.

2.2.2 Create ECS Database objectsOnce the database creation is completed, then you must run one of the scripts ‘Create_emon_custom.sql’ or ‘Create_emon_lab_custom.sql’ as appropriate, to create ECS database tables and partitions.

2.2.2.1 Set the DNCS information for the ECS Database1 Login in as “isaecs” user.

$ su – isaecs # if not already logged in as isaecs.

2 Execute the ‘createSiteDncsData.sh’ script, to gather information of each monitored DNCS. (i.e. name for dncs_id = 1).

$ cd ddl$ ./createSiteDncsData.sh

Note: You’ll be prompted to enter the name for each Head End (DNCS) being monitored (e.g. Kansas City).


2.2.2.2 Create the ECS database tables.1 The database script is located in the “$ISAECS_HOME/ddl” directory. The permissions on the

directory should be 755 (which gives the permission structure of: drwxr-xr-x). If the required permissions are not set, execute the below command as user ‘root’ to change it.

$ su -# cd /opt# chmod 755 isaecs

2 Change back to user “isaecs”, and then perform the following commands.

$ su – isaecs$ cd /opt/isaecs/ddl $ sqlplus system/itaas

3 Execute ‘Create_emon_custom.sql’ script when building a production ECS server. Execute the below SQL command,

SQL> set pages 1024;SQL> spool /tmp/dbCreate.out SQL> @Create_emon_custom.sql;

Incase of building ECS server for Lab, execute the ‘Create_emon_lab_custom.sql’ script, by giving the below command.

SQL> @Create_emon_lab_custom.sql;

You will be prompted to enter answers for two questions. The ‘number of periods’ is the number of days of ECS data the site wants to store. For Production sites, the default value set for ‘number of periods’ is 120 days. If disk space is an issue, you may choose a lower number of days, depending upon available disk usage on the server. For the lab server, the value is 14 days. Input the values for the remaining questions as below,

-How many periods --> 120 -Enter value for data files location -- > /data/oradata/ecs/

Note: This process usually takes about an hour to complete for the Production server and about 20 Minutes for the Lab setup, depending on the answer to the first question.4 Exit out of the SQL prompt by executing the below command.

SQL> quit

5 Verify that all 14 ECS tables are created. Execute the below commands.

$ sqlplus vodmon/vodmonSQL> select table_name from user_tables;

TABLE_NAME------------------------------ALERT_ACTIONALERT_ACTION_MAPALERT_CONFIGCAPACITY_AGGREGATEDNCS_DESCEVENT_LOGHUB_NUMBER_MAPNETWORK_CONGESTION_FORMULAOPERATIONAL_PARAMSOPERATION_PARAMSQAM_NUMBER_MAPSERVICE_AGGREGATESESSIONS_TEMP


SESSION_AGGREGATESESSION_EVENTSESSION_STATESG_LOCATIONSG_NAMESTEMP_SQLTRACE_SQLTSIDOUT_INFO

21 rows selected.

SQL> quit

6 Again connect to SQL*Plus with ‘ecsread’ privileges,

$ sqlplus ecsread/ecsread.SQL> select count (*) from session_state;

SQL> select count (*) from session_state;

COUNT (*)-------------- 0

Note: A ‘0’ means that all is well. SQL> select * from dncs_desc;

Note: It must display row for each of the DNCS_ID configured for the site. (Long and short description of each of the headends).SQL> select * from dncs_desc;

DNCS_ID SHORT_DESC LONG_DESC---------- ------------------------- ------------------------------ 1 Milwaukee Milwaukee

SQL> quit

2.2.3 Set start date for database partitions1 Execute the ‘fixParts’ script to set database partition mapping correctly. You will need to know

the first date for which you want to load data. If you do not know this date, then use the current date when running this script (the default).

2 Login as user “isaecs”, and give the following command.

$ /opt/isaecs/bin/fixParts

$ /opt/isaecs/bin/fixParts.shYou are setting up the partitions to start on this date:26 Aug 2003Do you want to change this date (y/n) ? n Enter ‘y’ if you want to set the date from which partition will begin. Enter the new date in the format : 07 Jul 2004First pass sets everything to the year 2000.Second pass sets your date, 26 Aug 2003. Please be patient...

Note: The fixParts script is executed immediately after setting up the ECS database objects and before any row is added to the database.


2.2.4 Modify oracle configuration to allow for redundancy of control and redo files

1 Login as user ‘root’.

$ su – root # if not already logged in as root.

2 Invoke the script “/opt/isaecs/ddl/ecsAlterCtrlRedo.sh” to update the oracle configuration. Note that path names for files altered by this script are specified in the file “/opt/isaecs/bin/ecsCommon.sh”. If your site has a non-standard database installation, the ‘ecsComon.sh’ script may need to be altered in order for the script to run.

# /opt/isaecs/ddl/ecsAlterCtrlRedo.sh > /tmp/ecsAlterCtrlRedo.log 2>&1 &

3 Invoke script “/opt/isaecs/ddl/rel_2.2/dbInitParamsModify.sh” to modifiy Db init parameters.

# /opt/isaecs/ddl/rel_2.2/dbInitParamsModify.sh &


2.3Set up the startup scriptsThis section provides instructions to configure server to startup/shutdown oracle and ECS web application on Boot.

2.3.1 Set Oracle to start up on boot1 Log in as root and edit ‘/etc/oratab’ file. This file contains the information on which Database is

currently active.

# vi /etc/oratab

This file will have only one un-commented line. If there is more than one line that is un-commented, make sure to comment all lines, except the below line.ecs:/opt/oracle/product/9.2.0:N

Change the above line to look as below.ecs:/opt/oracle/product/9.2.0:Y

2.3.2 Validate the TNS listener to be active1 Login as user ‘oracle’, and open the file ‘$ORACLE_HOME/bin/dbstart’.

# su - oracle$ vi $ORACLE_HOME/bin/dbstart

Note: Remove the first line with “:”, if it is present in the script. At the end of the file, check that the following line is in its place at the very last line after the word ‘done’ (it should have been added by the ‘setupECS’ script, but if not present, then add it at the end of the file)## Start the listenerlsnrctl start

This will start the Oracle listener each time the database is started.

2.3.3 Validate dbshut script 1 Verify that the “opt/oracle/product/9.2.0/bin/dbshut” does not contain a colon “:” at the start of the

script. If there is a colon “:” in the first line, then delete the line.

$ vi $ORACLE_HOME/bin/dbshut

2.3.4 Validate /etc/init.d/dbora1 Login as user ‘root’.

$ su -

2 Verify that “/etc/init.d/dbora” script contains the below contents.


# cat /etc/init.d/dbora#!/bin/sh# Set ORA_HOME to be equivalent to the $ORACLE_HOME# from which you wish to execute dbstart and dbshut;## Set ORA_OWNER to the user id of the owner of the# Oracle database in ORA_HOME. ORA_HOME=/opt/oracle/product/9.2.0ORA_OWNER=oracle if [ ! -f $ORA_HOME/bin/dbstart ]then echo "Oracle startup: cannot start" exitfi case "$1" in 'start') # Start the Oracle databases: # The following command assumes that the oracle login # will not prompt the user for any values su - $ORA_OWNER -c $ORA_HOME/bin/dbstart & ;; 'stop') # Stop the Oracle databases: # The following command assumes that the oracle login # will not prompt the user for any values su - $ORA_OWNER -c $ORA_HOME/bin/dbshut & ;; esac

Note: This file will login as user ‘oracle’, and run the script ‘dbstart’ to start the Oracle and the listener. The ‘dbora’ script is also used to shut down the database when the system goes down. If either of the above parameters is not correct, edit the file to correct them.

2.3.5 Set to launch oracle at run level 31 As user root, make a soft link from ‘/etc/rc3.d/K99dbora’ to ‘/etc/init.d/dbora’.

# cd /etc/rc3.d# ln -s ../init.d/dbora K99dbora# ls –l K99dbora

lrwxrwxrwx 1 root root 10 Dec 9 12:01 K99dbora ../init.d/dbora

2.3.6 Update system startup script1 Make backup of the “/etc/rc.local” and “/etc/rc.d/rc.local” files prior to beginning the below

modifications.

# cp /etc/rc.local /etc/rc.local.orig


# cp /etc/rc.d/rc.local /etc/rc.d/rc.local.orig

2 Set the “rc.local” to start the Oracle listener as well as Tomcat at the Linux Bootup time. This file is copied by the “setupECS” script. Open the file “/etc/rc.local” and make sure that it is in the “UNIX” format (Do “: set fileformat”, which will show you the file format). If not then perform “dos2unix” on this file.

# vi /etc/rc.local

3 Open the file “/etc/rc.d/rc.local” in another terminal window.

# vi /etc/rc.d/rc.local

4 Now copy and paste the contents of “/etc/rc.local” below the existing contents of “/etc/rc.d/rc.local”,

5 Remove the file “/etc/rc.local”. Now make a soft link “/etc/rc.local” to “/etc/rc.d/rc.local”. Go to “/etc/” and give the following command.

# cd /etc# rm rc.local# ln -s rc.d/rc.local rc.local# ls –l rc.local

lrwxrwxrwx 1 root root 10 Dec 9 14:01 rc.local rc.d/rc.local

Verify that the “/etc/rc.local” belongs to user ‘root’, and group ‘root’.


2.4Load the SG/QAM dataBefore the ECS Application can be run successfully in a head end or lab environment, the QAM-Service Group mapping from the DNCS needs to be loaded into the database. This section provides detail instructions to extract the SG/QAM data from the DNCS, and load it into the ECS database.

2.4.1 Extracting topology from the DNCS1 Login as a user ‘dncs’ on your DNCS.2 Copy the scripts '/opt/isaecs/ddl/extractTopology.sh' and '/opt/isaecs/ddl/extractSGnames.sql'

from the ECS server to the DNCS under 'export/home/dncs' folder. Perform the dos2unix operation on these files.

Note: Get the latest version of the ‘extractTopology.sh’ (Version 1.2) script from itaas, Inc.$ dos2unix extractTopology.sh extractTopology.sh $ dos2unix extractSGnames.sql extractSGnames.sql

3 Give the executable permissions for the above scripts, by giving the following command,

$ chmod +x queryDncsTopology.sql extractSGnames.sql

4 Execute the script by giving the below command.

$ dbaccess dncsdb < queryDncsTopology.sql

Note: The script generates the output file ' /tmp/dncsTopology.csv' in comma-separated-values (CSV) format.5 Execute the below command to generate output file ‘/tmp/sg_names_info.txt' with SG_id/Names

association,

$ dbaccess dncsdb < extractSGnames.sql

6 Copy the '/tmp/dncsTopology.csv' and ‘/tmp/sg_names_info.txt’ files to the ECS server.

$ ftp ecs //where ecs is the DNS name or IP address of the ECS server.$ put /tmp/dncsTopology.csv$ put /tmp/sg_names_info.txt

2.4.2 Loading DNCS topology into the ECS database

1 Log on to the ECS server as user 'isaecs'.2 Change directory to /opt/isaecs/ddl/topology.

Note: create ‘topology’ directory if not already present.$ mkdir /opt/isaecs/ddl/topology$ cd /opt/isaecs/ddl/topology

3 Rename existing 'dncsTopology.csv' and 'sg_names_info.txt' files if present under '/opt/isaecs/ddl/topology' folder.

$ mv dncsTopology.csv dncsTopology.csv.sav$ mv sg_names_info.txt sg_names_info.txt.sav


4 Copy the '/tmp/dncsTopology.csv' and '/tmp/sg_names_info.txt' files under '/opt/isaecs/ddl/topology' directory.

$ cp /tmp/dncsToplogy.csv .$ cp /tmp/sg_names_info.txt .

5 Modify the 'HUB_NAME' parameter line in the 'convertDatToCsv.sh' as per site-specific Hub/QAM mapping pattern.

Note: Copy the site specific ‘converDatToCsv.sh’ script from ‘/opt/isaecs/ddl’ folder if already present.$ cp /opt/isaecs/ddl/convertDatToCsv.sh /opt/isaecs/ddl/topology

Note: Extract unique QAM names from the ‘dncsTopology.csv’ file by executing the below command; and verify with site if Hub name can be extracted from the QAM name.$ cut -d',' -f8 dncsTopology.csv |sort -u > uniqQam.out

Note: Verify and modify the file if required. $ vi convertDatToCsv.sh

Note: Below line is modified for extracting hub name from QAM name pattern,# Apply filtering here for site-specific naming convention.HUB_NAME=`echo $QAM_NAME | awk '{print "Hub_"substr($1, 1, 2)}'`

If required, contact itaas ECS support team to make necessary update to the script.6 Execute the 'convertDatToCsv.sh' script to add hub name to the CSV file.

$ ./convertDatToCsv.sh dncsTopology.csv SiteName

Note: This will create 'ecsQamSgData-$DATE.csv' with hub name added.7 Verify 'ecsQamSgData-$DATE.csv' contains the following 8 fields,

$porttype,$portnum,$tsid,$svcgroup_id,$ipaddr,$macaddres,$hubName,$qam_name

Note: If required, execute the ‘topologyHub.sh’ script to replace the partial Hub names with complete Hub names using HUB_MAPPING_FILE (HubInfo.txt).

8 Convert the 'ecsQamSgData-$DATE.csv' file to a SQL file, by running the perl script as follows,

$ perl makeTopology.v3.pl 1 ecsQamSgData-$DATE.csv Headendname.sql AreaName

Where

makeTopology.v3.pl - Perl Script used.

1 - DNCS_ID

ecsQamSgData-$DATE.csv - The File that we got in step 6.

Headendname.sql - The Output SQL file that we want to generate.

AreaName - Area Name used for the Hubs. (Example Charlotte)9 Stop ECS processes, if already running.

$ iecs stop

10 Verify that all ECS processes have stopped.

$ ps –ef |grep collector$ ps –ef |grep Capture


11 If you are updating the topology data on the ECS server, then execute the ‘archiveTopologyData.sh’ script to save the existing topology information.

Note: Verify that the ‘archiveTopologyData.sh’ script is present under ‘/opt/isaecs/ddl/topology’ directory.$ /opt/isaecs/ddl/topology/archiveTopologyData.sh

12 Execute the Headendname.sql script,

$ sqlplus vodmon/vodmon < Headendname.sql

13 To update the Service Group names in 'sg_names' table, execute the ‘loadSGdata.sh’ script to load the data.

$ /opt/isaecs/ddl/topology/loadSGdata.sh

14 Verify that the SG data is loaded into the ‘sg_location’ and sg_names tables.

$ sqlplus vodmon/vodmonSQL> select count(*) from sg_location;SQL> select count(*) from sg_names;SQL> select count(*) from tsidout_info;

Note: The record count in TSIDOUT_INFO table must be 1 more than the number of lines in the ‘dncsTopology.csv’ file generated from the DNCS. And, the count in ‘SG_LOCATION’ table must be 1 more than the no. of unique SGs extracted from the ‘dncsTopology.csv’ file. The count in ‘SG_LOCATION’ table must also be 1 more than the number of lines in the ‘sg_names_info.txt’ file extracted from the DNCS.Execute this step only if; this section is executed for updating an existing SG/QAM data. Start the ECS tool and bounce the tomcat to view the updated information on the GUI.$ iecs start (starts ECS tool)$ su - (login as user ‘root’# /opt/tomcat-5/bin/shutdown.sh (stops tomcat application)# /opt/tomcat-5/bin/startup.sh (starts tomcat application)


2.5Upgrading application codeThis section provides details about applying application code patch 1 to address bug fixes.

2.5.1 Code Patch 1 install1 Download the ‘ECS_2_2_2-27Aug2007_Patch_01.tar.Z’ and ‘ecs2.2.2Patch1_README’ files

from the itaas ftp site to install Patch 1 code update.2 Refer to ‘ecs2.2.2Patch1_README’ file for instructions to apply the patch.

2.6Head-End Specific Configurations

2.6.1 Setting the Time zone1 Edit the file ‘/etc/profile.d/setTZ.sh’ to fix the timezone on ECS server.

# vi /etc/profile.d/setTZ.sh#!/bin/bash# Set the time zone and daylight savings time values.# See: tzselect# $Id: setTZ.sh,v 1.1 2003/08/04 16:19:15 randy Exp $############################################3export TZ=America/New_York

Note: Change the “export TZ=America/New_York” line with an appropriate time zone, as required. To identify the correct time zone, execute the ‘tzselect’ command, and enter options as prompted.

2.6.2 DNCS information validation in the database1 Verify the contents of ‘dncs_desc’ table to check the values for DNCS id, short description and

long description of the site. Execute the below commands.

$ sqlplus vodmon/vodmonSQL> select * from dncs_desc;

Note: If the above output doesn’t show the site-specific values for short_desc and long_desc fields, then give the following command to update the values.SQL> update dncs_desc set short_desc = 'Wilmington_1' where short_desc ='Dncs1';

SQL> update dncs_desc set short_desc = 'Wilmington_1' where short_desc ='Dncs1';

1 row updated.

SQL> update dncs_desc set long_desc = 'Wilmington_1' where long_desc = ‘Dncs1 long Description’;


SQL> update dncs_desc set long_desc = 'Wilmington_1' where long_desc = ‘Dncs1 long Description’;

1 row updated.

SQL> commit;

2.6.3 Update collector with DNCS information1 Collect the below information from the DNCS.

a Value of 'Send Session In Progress Every' field (time in minutes) b Value of 'Stop Waiting for User Response After field' (in seconds)

Note: The above information is available from DNCS console --> 'System Provisioning' tab --> 'DNCS System' tab --> 'DSM-CC' tab.

2 Update the ‘collector.tmpl’ file with the above DNCS information. Execute the below commands.

$ vi /opt/isaecs/conf/collector.tmpl

Note: The variable "sip_timeout_secs=3600" should be set to 1.5 times the value in seconds of the Session In Progress time (step ‘a’ above). The variable "sess_msg_relate_time=60" should be set to the value in seconds of the Message Time Out value i.e. step ‘b’ value as set on the DNCS ("Stop Waiting for User Response After").The variable "long_session_check_interval=1800" should be set to half the sip_timeout_secs.

2.6.4 Configure ECS processes based on VOD vendors

This section provides details to configure ECS tool, as per the site-specific VOD components. Collect the remote VOD server details from the site headend administrator, including the remote server versions. Gather the data in the format given in Table 1.

Table 1: VOD Remote Server List

Equipment Name Vendor Type VersionBMS Tandberg Business Management System 5.9BMS (HERM) Concurrent Business Management System 5.02 SP2DNCS SciAtl DNCS SR 4.0XOD SciAtl VOD application/platform 1.5.0.1ShowRunner Pioneer VOD application/platformnCube** nCube VOD Server 2.0.3.7SeaChange SeaChange VOD ServerConcurrent Concurrent VOD Server 7.0Broadbus


MDN Mystro VOD Server 2.4Arroyo VOD Server 1.4.1Navic

In the “/opt/isaecs/conf” file, there are Configuration scripts for all these vendors.

Note: For the DNCS, there are five conf files: drm, dsm, dsm-cc, qam and ipcapture. For SeaChange, there are two: snmpcol and snmp-sc. For all other VOD vendors, select the respectively named config files.1 Login as user ‘isaecs’.2 Edit the ‘/opt/isaecs/conf/runECS.conf’ file with site-specific VOD details, as gathered in Table 1

above.

$ vi /opt/isaecs/conf/runECS.conf################### EDIT THIS FILE FOR EACH INSTALLATION ##################

###################################################################################### No spaces are allowed after the '=' sign.### Everything after the '=' sign becomes value.###################################################################################

### List of DNCS# The value in DNCS_LIST must match dncs_idDNCS_LIST=1#DNCS_LIST=2

# The reason we need list of dependencies in each DNCS is that each DNCS may# have a different AppServer,# If there is only one '1.bms' common to all DNCS, then add 'bms' to# COMMON_PROCS, as is done in this example for vod-ncube# String format : dncs_id.logCaptureName# dncs_id : Valid dncs id as in DNCS_LIST# logCaptureName: The config file names; so make sure logCaptureName.conf exists# in $ECS_HOME/conf directory

DNCS_DEPS=1.qamDNCS_DEPS=1.dsmDNCS_DEPS=1.drmDNCS_DEPS=1.ipCaptureDNCS_DEPS=1.bms#DNCS_DEPS=1.xod // Un-comment this if the site runs XOD#DNCS_DEPS=1.showrunner // Un-comment this if the site runs Showrunner#DNCS_DEPS=2.qam#DNCS_DEPS=2.dsm#DNCS_DEPS=2.drm#DNCS_DEPS=2.ipCapture#DNCS_DEPS=2.bms#DNCS_DEPS=2.showrunner

# List of logCaptures common to all DNCS#COMMON_PROCS=vod-nCube // Un-comment this if the site has nCube#COMMON_PROCS=snmp-sc // Un-comment this if the site has Seachange server#COMMON_PROCS=vod-concurrent // Un-comment this if the site has Concurrent VOD //server


COMMON_PROCS=eam

################################################################################

# List of ECS application names.APP_PROCS=logCaptureAPP_PROCS=ipCaptureAPP_PROCS=collectorAPP_PROCS=ecsAlertMgr

BASE_PORT =7800START_TIME=2004-01-21 01:00:00.000

################################################################################### Configure the hostnames (as reported by 'hostname' on the remote host) for### each RT before you can run the ECS Server. Do that by listing the hostnames"runECS.conf" 119L, 3423C

################################################################################

:::::::::::::::::::

# Database Latency timeout in secondsDATABASE_LATENCY=1800# ALert codes to be used.PROCESS_INACTIVE_ALERT_CODE=300PROCESS_FAILED_ALERT_CODE=500####### mkLinks status file nameMKLINKS_STATUS_FILE=mkLinks.status# Launch history file nameLAUNCH_HISTORY_FILE=LaunchHistory.status# Maximum number of status file required in Status directoryMAX_STATUS_FILES=10# To specify that BMS log file in GMT format set IS_BMS_GMT=1IS_BMS_GMT=0

####### Set the default debug level DB_LEV=6

DB_USER=vodmonDB_PASS=vodmon

Note: For a single DNCS system, verify that all references to DNCS_LIST=2 and all 2.name lines are commented-out. Comment/un-comment ‘DNCS_DEPS=’ lines as per site VOD setup. For sites with multiple DNCS, add appropriate processes. 3 If the BMS server version is 2.5 or higher, then change ‘IS_BMS_GMT’ parameter value to 1 in

the ‘runECS.conf’ file.# To specify that BMS log file in GMT format set IS_BMS_GMT=1IS_BMS_GMT=1

4 For sites with n-Cube VOD server, specify the appropriate RT names in the ‘RT_HOSTS=’ parameter.

Note: To verify the correct host name for each of the RT servers, go to each of the RT Machines in the headend and type command ‘hostname’.


Make sure to add the same hostname(s) name in the above “RT_HOSTS” variable in the “runECS.conf”. For example, if there are two RT’s in the headend with the names “liberty-1” and “liberty-2”, then multiple RT_HOSTS are comma separated and should look like below. RT_HOSTS=”liberty-1, liberty-2”

5 For sites with Broabus server, specify the appropriate BBus host names in the ‘BB_HOSTS=’ parameter.

## Supporting multiple BroadBus Vod PumpsBB_HOSTS=BroadbusStreamCommander-9VK4G51

2.6.5 Update conf files based on remote server version

This section describes the changes to be made in the configuration files to support various vendor servers’ upgraded versions.

2.6.5.1 DNCS SR 4.2 versiona Update the config files by issuing the following commands.

$ cd /opt/isaecs/conf/DNCS/rel4.2$ cp *.conf /opt/isaecs/conf/

2.6.5.2 BMS 2.8 or higher versiona Update the config files by issuing the following commands.

$ cd /opt/isaecs/conf/BMS/rel_2.8$ cp bms.conf /opt/isaecs/conf/$ cd /opt/isaecs/conf$ echo "BMS_LOG_FILE_BASENAME=\"n2bb\"" >> HeadEnd.cfg

b If BMS 2.8 upgrade results in loss of AssetId in Session Details screen, then make the below changes,

$ vi /opt/isaecs/ui/styles/SessDetails.xsl:

Note: Replace:<xsl:variable name="assetNameVal" select="@EVENT_PAYLOAD"/>

# with<xsl:variable name="assetNameVal" select="substring-

before(@EVENT_PAYLOAD,'for session')"/>$ vi /opt/isaecs/logEventCodes.csv

Note: Comment out (Put # in the beginning of each below line): 727,BMS,ASSET,Asset Info,NORMAL,NORMAL DATA_FIELD,SOURCEEVENTDESCRIPTION,1,string,"(): Total time (msecs) to ",":" DATA_FIELD,STREAM_NAME,1,string,"stream : "," for" DATA_FIELD,XMAC_ID,1,string,"session :",":" # Replace with


727,BMS,ASSET,Asset Info,NORMAL,NORMAL DATA_FIELD,SOURCEEVENTDESCRIPTION,1,string,"ASSET ",":" DATA_FIELD,XMAC_ID,1,string,"for session :",": for ServiceGroup"

2.6.5.3 CCOR release 2.0.3.7a Update the config file by issuing the following commands:

$ cd /opt/isaecs/conf/ccorNcube/rel_2.0.3.7$ cp vod-nCube.conf /opt/isaecs/conf/

b If the CCOR VOD server updated caused the log files to be renamed, then the following changes must be made.

$ cd /opt/isaecs/conf$ echo "NCUBE_LOG_FILE_BASENAME=\"rtdebug\"" >> HeadEnd.cfg$ echo "NCUBE_VENDOR_TYPE=\"rtd\"" >> HeadEnd.cfg

c Edit vod-nCube.conf file to match the new file name.

vi vod-nCube.conf

Note: Change the below ‘logName’ parameter value. < "logName = hedebug.txt" > < to > < logName = rtdebug >

2.6.6 Customizing Headend GUIFollow the steps below to configure the application GUI to display MSO logo.1 Change the client logo, if required for the GUI. Place the desired MSO logo image file in the

‘/opt/isaecs/UI_2_1/build/web/images’ directory and rename it as ‘msologo.jpg’.

Note: The ‘msologo.jpg’file must be of size 150 pixels wide x 40 pixels.


2.7Verify application scripts

2.7.1 Verify /etc/files1 Login as user “root”.2 Do a diff between the ‘catalina.sh’, ‘server.xml’, ‘rc.local’, ‘setEnv.sh’ and ‘rsyncd.conf’ files under

‘/etc’ folder and their respective copies under ‘/opt/isaecs/etc’ folder.

# diff /opt/isaecs/etc/catalina.sh /opt/apache-tomcat-5.5.20/bin# diff /opt/isaecs/etc/server.xml /opt/apache-tomcat-5.5.20/conf/server.xml# diff /opt/isaecs/etc/rc.local /etc/rc.local# diff /opt/isaecs/etc/profile.d/setEnv.sh /etc/profile.d/setEnv.sh# diff /opt/isaecs/etc/rsyncd.conf /etc/rsyncd.conf

Note: If you find any differences in the above files, make sure to add appropriate differences from /opt/isaecs/etc/* in the /etc/* folder. If you are not sure which differences to add, check with itaas ECS support team.


2.8Application startup

2.8.1 Set ECS cronjobs1 As user ‘root’, place the crontab entry in ‘/var/spool/cron/root’ file by executing the below

command.

# crontab < /opt/isaecs/bin/ecsCrontTabLines# crontab -l

[root@ecs2dev ~]# crontab –l# DO NOT EDIT THIS FILE - edit the master and reinstall.# (/tmp/crontab.25874 installed on Mon Dec 8 21:05:46 2003)# (Cron version -- $Id: ecsCronTabLines,v 1.6 2005/05/17 20:18:06 bwyatt Exp $)2,7,12,17,22,27,32,37,42,47,52,57 * * * * /opt/isaecs/bin/mkLinks -x31 * * * * /opt/isaecs/bin/gzOldLogs44 * * * * /opt/isaecs/bin/archiveLogFiles41 3 * * * /opt/isaecs/bin/ecsLogClean46 4 * * * /opt/isaecs/bin/ecsRsyncClean41 4 * * * /opt/isaecs/bin/rollPartitions41 5 * * * /opt/isaecs/bin/runCpd.sh4,9,14,19,24,29,34,39,44,49,54,59 * * * * /opt/isaecs/bin/iecs latency

2.8.2 Start the rsync daemon1 Verify that rsync daemon is enabled. Open the file ‘/etc/xinetd.d/rsync’.

# vi /etc/xinetd.d/rsync

Note: Make sure “disable=no” is set at the beginning of the file.###################################################################################service rsync{ disable = no socket_type = stream wait = no user = root server = /opt/isaecs/bin/nice_rsync server_args = --daemon log_on_failure += USERID}

2 Start xinetd process, by executing the below command.

# cd /# /etc/init.d/xinetd start


2.8.3 Start the ECS processes 1 Login as user ‘isaecs’.2 Start ECS processes.

$ iecs start

3 Verify logCapture and collector processes.

$ psg col$ psg Cap$ psg logSplit

Note: Verify that corresponding logCapture and logSplit processes are running for each of the process configured in ‘runECS.conf’ file.4 Perform application status check, by executing the below command.

$ iecs status ECS environment check done.Checking status of ECS system ...Process Name : ecsAlertMgrProcess Port : 7800Process Id : 7142DNCS Id :Config Source : ecsAlertMgrRunTime Config File : ecsAlertMgrRsynced :logFileLastMessageTime :inputLogFileName :hardLinkModifiedTime :ecsLogFileLastMessageTime:dbLastMessageTime :inputDir :dbTag :============================Process Name : logCaptureProcess Port : 7801Process Id : 7148DNCS Id : 1Config Source : qamRunTime Config File : 1_qamRsynced : 2004-02-18 17:05:02logFileLastMessageTime : 2004-02-18 17:05:02inputLogFileName : qamManagerhardLinkModifiedTime : 2004-02-18 17:07:04ecsLogFileLastMessageTime: 2004-02-18 17:07:35dbLastMessageTime : 2004-02-17 03:35:12

…Process Name : logCaptureProcess Port : 7815Process Id : 7218DNCS Id :Config Source : eamRunTime Config File : eamRsynced : 2004-02-18 17:07:40logFileLastMessageTime : 2004-02-18 17:07:39inputLogFileName : eam.loghardLinkModifiedTime : 2004-02-18 17:07:39


ecsLogFileLastMessageTime: 2004-02-18 17:07:11dbLastMessageTime : 2004-02-17 09:24:02inputDir : alertsdbTag : eam_time============================Process Name : collectorProcess Port :Process Id : 7223DNCS Id :Config Source : collectorRunTime Config File : collectorRsynced : 2004-02-18 17:07:40logFileLastMessageTime : 2004-02-18 17:07:39inputLogFileName :hardLinkModifiedTime : 2004-02-18 17:07:39ecsLogFileLastMessageTime: 2004-02-18 15:37:06dbLastMessageTime : 2004-02-18 17:07:40inputDir :dbTag :============================Status written in /opt/isaecs/logs/ecs-runtime/status/status.1077142060/opt/isaecs/bin/ecsReqAlert -p 7800 -a 500 -t "ECS Process: 1_ipCapture rsync - is inactive for last ( 1 days 7:35:12 )" /opt/isaecs/bin/ecsReqAlert -p 7800 -a 500 -t "ECS Process: 1_ipCapture Database update - is inactive for last ( 1 days 7:38:36 )" /opt/isaecs/bin/ecsReqAlert -p 7800 -a 500 -t "ECS Process: 2_bms Database update - is inactive for last ( 2 days 4:47: 6 )" /opt/isaecs/bin/ecsReqAlert -p 7800 -a 500 -t "ECS Process: 1_qam Database update - is inactive for last ( 1 days 13:32:28 )"

5 Start the java program for populating ‘capacity_aggregate’ data. Verify that ‘JAVA_HOME’ parameter is set to appropriate ‘java’ path.

$ export JAVA_HOME=/usr/java/java$ export PATH=/usr/java/java/bin:$PATH$ nohup $JAVA_HOME/bin/java -classpath "/opt/isaecs/lib/ecs.jar:/opt/isaecs/lib/axis-ant.jar:/opt/isaecs/lib/ojdbc14.jar:/opt/isaecs/lib/log4j-1.2.8.jar:." com.itaas.ecs.core.capacityAggregate.SessionAggregator > /tmp/ca.out 2>&1 &

6 Bring up ECS UI in web browser and, verify Homepage is displayed with ‘No Data’.

Note: You will see data on the GUI only when the logs from the remote servers are rsynced over to the server, and the tool starts processing the logs. Refer to ‘itaas_ECS_RemoteComponent_InstallGuide’ to install ECS agent on the VOD remote servers.


2.9Changing the server run-LevelIt is recommended that the user run level is changed back to level 3 at this point. 1 Login as root.2 Edit ‘/etc/inittab’ file.

# vi /etc/inittab

Note: Change the default runlevel to “3” instead of “5”. (The line reads “id:5:initdefault” and when modified should read “id:3:initdefault”)3 Restart the start the server at runLevel-3.

# shutdown –r now

4 Check that the Oracle and Java processes are running after server startup.

# psg ora # psg java


2.10 Test the installation1 Reboot the machine.

# shutdown –r now

2 After the server boots-up, verify that oracle database, oracle listener and the tomcat application is running. Execute the following commands.

# psg ora

[root@ecs2dev ~]# psg oraoracle 13900 1 0 Nov10 ? 00:00:04 ora_pmon_ecsoracle 13902 1 0 Nov10 ? 00:01:41 ora_dbw0_ecsoracle 13904 1 0 Nov10 ? 00:01:08 ora_lgwr_ecsoracle 13906 1 0 Nov10 ? 00:01:49 ora_ckpt_ecsoracle 13908 1 0 Nov10 ? 00:00:26 ora_smon_ecsoracle 13910 1 0 Nov10 ? 00:00:01 ora_reco_ecsoracle 13912 1 0 Nov10 ? 00:00:00 ora_s000_ecsoracle 13914 1 0 Nov10 ? 00:00:00 ora_d000_ecsoracle 16199 1 0 Nov10 ? 00:00:00 /opt/oracle/product/9.2.0/bin/tnslsnr LISTENER -inheritoracle 30817 1 0 Nov20 ? 00:04:26 oracleecs (LOCAL=NO)oracle 15381 1 0 Nov27 ? 00:00:00 oracleecs (LOCAL=NO)

$ psg java

root 1096 1 0 11:57 ? 00:00:29 /usr/java/java/bin/java –Xbootcl

Note: If either of the above processes are not running, check for errors during startup by giving the below command. # dmesg | more

3 Verify the time on the ECS server. Check the server time is displayed as per the correct time zone set in section 2.5.1.

# date

4 Bring-up ECS UI on a web browser, and verify Home page is displaying correct Hub information. Verify the ‘LAST DSMCC MSG TIME’ moves ahead upon refreshing the page.

5 Click on the ‘Service Group’ and ‘QAM’ button on the main menu bar, and verify the data on each of the pages. Verify that all Service Groups and QAMs are displayed on the GUI.

6 Click on the Events button from the main menu bar, and verify values in the drop down list of ‘source System’ and ‘ECS Event Code’ fields. The values must be headend-specific.

7 Click on the Reports button on the main menu bar, and run each report. Validate the data outputted from the reports.

8 From the homepage, drill down the error events, and validate the information.9 Click on the Latency button on the main menu bar, and verify that latency for all processes is

displayed in green.10 Click on the Search button on the main menu bar, and enter a STB Mac Address, to view the

details for that set-top. Verify the information.11 Click on the Help button on the main menu bar, and verify that the FAQs and technical

documents are available.


2.11 Final Checklist 2.11.1 RedHat Checklist / Notes

1 ISAECS_HOME is /opt/isaecs.2 ECS application is installed in ‘/opt’3 ECS data is loaded into ‘/data’ partition.4 /data/rsync/logs is the target location for all rsync deliveries5 /data/logs is the directory where mkLinks puts the hard links into production6 Kernel parameters are set in /etc/sysctl.conf7 Users – ‘isaecs’ and ‘oracle’ are created.

2.11.2 Oracle Checklist / Notes

1 ORACLE_HOME is /opt/oracle/product/9.2.0. ECS data is on /data/oradata/ecs.2 ORACLE_SID is ecs.


3SupportFor clarifications about the ECS application install that were not answered here, you can contact the itaas ECS Support team at:

Email: [email protected]

Phone: 770-368-4024 (Between 8.30 a.m. to 5.30 p.m. EST Monday to Friday)

For support after business hours, please contact 1-888-Go-itaas (1-888-464-8227).

Our office address:

itaas Inc.

11695 John's Creek Parkway, Suite 300,

Duluth, GA 30097

Tel: 770-368-4024

Fax: 770-246-0616

Website: www.itaas.com


http://www.itaas.com/

ecs application install guide - itaas, a cognizant · web viewecs install guide release 2.2.2...

Documents