> Content Filtering Applications Installation and Administration
> This chapter provides information and procedures to install and configure different components for Content Filtering service support and management.
> This chapter includes the following topics:

> l | Before You Begin

> l | Installing CF-CDP Server in GUI Mode

> l | Installing CF-CDP Server in Console Mode

> l | Installing WEM

> l | Installing CF Customer Care Interface (CF-CCI)

> l | Uninstalling CF Application Components

> l | Modifying CF Components’ Configuration Files

> l | Managing Application Level Traps and Alarms

> Before You Begin
> Prior to performing the installation procedure, this section previews each step to ensure that you are ready to successfully complete the installation.

> 1 | Verifying hardware status.

> The first thing that you need to do is to ensure that the system hardware has been provisioned properly for your application. This includes:

> l | Verifying the operating system using the uname -a command.

> l | Verifying that the hard disk has been partitioned properly using df -k command.

> l | Verifying network connectivity through the management LAN using ping command.

> 2 | Obtaining the licenses.

> To use these components different licenses are required from your vendor. To obtain these licenses, contact your local representative.

> 3 | Setting the database environment strings.

> This step is required to configure how the PostgreSQL database engine processes, stores, and retrieves information contained in the various databases stored using the UNIX file subsystem. Failure to configure these settings may cause data loss and will minimally cause errors in the operation. For information on setting the database environment strings, refer to the Setting the PostgreSQL Database System Environment Configurations section.

> 4 | Unpacking the Content Filtering Application files.

> CF Component installation files are distributed as a single compressed file. After the file is obtained, it must be copied to the server and unpacked. It is recommended that you copy the file to a temporary directory on the server.

> 5 | Installing the Content Filtering Application software.

> IMPORTANT: For URL Blacklisting functionality, only the WEM and CF-CDP components need to be installed. For Category-based Content Filtering functionality, the WEM, CF-CCI, and CF-CDP with RE components must be installed.
> Setting the PostgreSQL Database System Environment Configurations
> Prior to installing the CF software components onto the different server hardware, there are numerous system environment configuration settings that should be configured. While PostgreSQL will be installed during the GUI-based installation procedure, these settings must be configured manually.
> Add following values to the system file in the /etc directory and restart the system before continuing with the installation of the CF application components.
> set msgsys:msginfo_msgmnb=65536
> set msgsys:msginfo_msgtql=1024
> set shmsys:shminfo_shmmax=0x2000000
> set shmsys:shminfo_shmmin=1
> set shmsys:shminfo_shmmni=256
> set shmsys:shminfo_shmseg=256
> set semsys:seminfo_semmap=256
> set semsys:seminfo_semmni=512
> set semsys:seminfo_semmns=512
> set semsys:seminfo_semmsl=32
> IMPORTANT: After adding the above values to the system file in the /etc directory, restart the system before installation of CF components.
> Unpacking the CF Component Application Installation Files
> CF application installation files are distributed as a single compressed file with a “.tar.gz” extension. After copying the installation file to the server, use the following procedure to unpack the file.
> To unpack the CF Component Application installation files:

> 1 | Create a directory, and move the distributed compressed application installation file to it by entering the following commands:

> mkdir CFAPPS_directory
> mv cf-apps_x.x.xx.tar.gz CFAPPS_directory

> 2 | Change to the directory in which the cf-apps_x.x.xx.tar.gz file is placed.

> 3 | Unzip the file by entering the following command:

> gunzip cf-apps_x.x.xx.tar.gz
> x.x.xx is the version of the CF Component Application installation file. Unzipping this file creates the cf-apps_x.x.xx.tar file from cf-apps_x.x.xx.tar.gz.

> 4 | Un-tar the cf-apps_x.x.xx.tar file by entering the following command:

> tar -xvf cf-apps_x.x.xx.tar
> Decompressing the installation file results in the following files:

> l | cdp_SunOS_x_x_xx.tar: A compressed file containing all of the application files required for CDP, Report Engine, and Database Deliver application.

> l | cci_x_x_xx.tar: A compressed file containing all of the application files required for CF Customer Care Interface application installation.

> Follow the given sequence for CF component installation:

> 1 | Installing CF-CDP Server in GUI Mode or Installing CF-CDP Server in Console Mode

> 2 | Installing WEM

> 3 | Installing CF Customer Care Interface (CF-CCI)

> Installing CF-CDP Server in GUI Mode
> This section describes the procedure to install Central Decision Point (CF-CDP) server application in GUI mode. The procedure described here assumes that you have already verified the minimum system requirements as specified in the Before You Begin section of this chapter and that the CF-CDP application installation tar file is in your user directory on the server.
> The CF-CDP components can be installed in one of the following modes:

> l | GUI: This is the most often used mode. Requirements for this mode of operation include:

> l | Login account to the server with display terminal (monitor) attached and some X-Windows client installed on server.

> l | Network connectivity to the CDP server via Telnet or SSH, using some X-Windows client on remote workstation.

> l | Console: This mode is available to users who do not have an X-Windows client available for remote network connectivity to the CDP server via Telnet or SSH.

> l | Silent: This mode is used only if the CF-CDP is already installed on the machine. For silent-based mode, user needs to update the installvariables.properties file in the Uninstall_CDP directory while executing “inst” script in silent mode.

> To install the CF-CDP application through the GUI-based interface:

> 1 | Go to the directory where cdp_x.x.xx.tar file is located and un-tar it by entering the following command:

> tar -xvf cdp_SunOS_x_x_xx.tar
> Decompressing the installation file results in the following files:

> l | CDP_Installer.bin: The CDP installation binary file.

> l | uninst: A script to uninstall CF-CDP application.

> l | README: A text file containing information pertaining to the release.

> l | inst: A script to install the CF-CDP server.

> The usage format for the CF-CDP installation and uninstallation scripts is as follows:
> ./inst [ -ui | -console | -silent ] | [ -help]
> ./uninst [ -ui | -console | -silent ] | [ -help]
> The following table denotes the different keywords/options used with this command:

> Keyword | Description
> -ui | Starts the installer in GUI mode. By default, the script starts in GUI mode.
> -console | Starts the installer in console mode.
> -silent | Starts the installer in silent mode.
> -help | Displays the supported keywords/options associated with this command.

> 2 | Go to CDP_Install_dir/cdp folder and initiate the installation procedure by entering the following command:

> ./inst
> or
> ./inst -ui
> The CDP Introduction dialog box is displayed.
> CDP Installer Dialog Box

> 3 | Respond to the on-screen prompts with the help of inputs given in the following table and configure various parameters as required.

> CF Central Decision Point Server Installation Parameter Descriptions
> Parameter | Description | Default Value
> System Environment Variable Prompt
> | This dialog or script asks user to add variable values in ‘/etc/system’ file and restart the system. For more information, refer to Setting the PostgreSQL Database System Environment Configurations section. | N/A
> Central Decision Point Installation
> CDP Installation Mode | Select the mode of installation for the CF-CDP application from the following options:
> n | Standard
> n | Custom
> Selection of Standard mode skips the parameters specified in Report Engine Configuration section of this table. | Standard
> Central Decision Point Server Installation Directory
> Directory Name | Enter the directory path in which the CF-CDP server application is to be installed. | /users/cdp
> CDP IP Address Configuration
> IP Address of machine | Select the IP address of machine from the displayed list of IP address configured on the machine. | IP_address
> Process Monitor Configuration
> SMTP Server Name | Enter a host name or IP address for a Simple Mail Transfer Protocol (SMTP) server, if needed, in the field provided. This is the mail server to which notifications are sent when processes fail/start. | Null
> Email-ID | Configure the email address of the individual to be notified in the field provided. Email notifications are sent to this individual when the system can not communicate with a process. The email address should be in the form username@domain. | Null
> Alarm Configuration
> Enable Alarm Forwarding | Select this check box to enable alarm forwarding. By default, this option is disabled. | Disabled
> IP Address | Enter the IP address of alarm/trap receiver i.e. SNMP server. | Null
> Port Number | Enter the port number of SNMP server. | 162
> PostgreSQL Server Configuration
> Administrator Login | Enter an administrator name for the Postgres database administration. | postgres
> Administrator Password | Enter a password for the administrator name for the Postgres database. The password is case sensitive. | postgres
> Port | Enter the port number over which PostgreSQL communication will occur with the CDP. The valid range is from 1 through 65535. To ensure proper operation and data integrity, the PostrgreSQL database instances installed with this installation should only be used by the application. | 5432
> Report Engine Configuration This section is applicable only for the Category-based Content Filtering solution. NOTE: This configuration panel appears only when Custom installation mode is selected.
> EDR Data Directory | Specify the location of CF-EDR reports to store for Report Engine as input to generate reports. | local_base_di rectory/data
> EDR Date-Time Format | Select the date format that will be used by the CF-EDRs coming into CDP. The options are as follows:
> n | MM/DD/YYYY-HH:MM:SS
> n | MM/DD/YY-HH:MM:SS
> n | YYYY/MM/DD-HH:MM:SS
> n | YYYYMMDDHHMMSS
> n | seconds
> | MM/DD/YYYY-HH:MM:SS
> Enable archive for EDR files | Select Yes to enable or No to disable the archiving of CF-EDR files. | Yes
> CDP Parameter Configuration Confirmation
> Modify Configuration | This dialog or script section is informational and contains information regarding configured parameters. If you want to change any parameter, enter Y or press Enter to proceed. | No

> After you have provided the required inputs, the installation process starts and you receive a message indicating that CDP application installation starts on the basis of user inputs.
> WARNING: Please ensure that you have enough disk space for the installation of CDP application. If sufficient space is not available in the installation directory, cancel the installation process and free-up the disk space to proceed with the installation.

> 4 | During the CF-CDP installation, the CDP Server Startup dialog box appears prompting the user with an option to start all the servers after installation.

> CDP Server Startup Dialog Box
> After all components have started, the Install Complete dialog box appears indicating that the installation was successful.
> CDP Installation Complete Dialog Box

> 5 | Copy the un-installation script to the cdp_base_directory directory by entering the following command:

> cp uninst cdp_base_directory/

> 6 | Verify that all the CF-CDP components and processes are successfully started by entering the following command:

> ./serv status
> The following is a sample message:
> -----------------------------------------------------------
> PID Process Status
> -----------------------------------------------------------
> - PS Monitor Application Not running
> - Report Engine Server Not running
> - Database Deliver application Not running
> - Central Decision Point Server Not running
> 7315 Postgres Server Running
> -----------------------------------------------------------
> All of the parameters configured get stored in configuration files located in /<application_base_directory>/etc directory. For more information on the configuration files, see the Modifying CF Components’ Configuration Files section.
> Installing CF-CDP Server in Console Mode
> This section describes the procedure to install Central Decision Point (CF-CDP) server application in console mode. The procedure described here assumes that you have already verified the minimum system requirements as specified in the Before You Begin section of this chapter and that the CF-CDP application installation tar file is in your user directory on the server.
> The following procedure describes how to install the CF-CDP application in console mode through the installation script.

> 1 | Go to the directory where cdp_x.x.xx.tar file is located and un-tar that by entering the following command:

> tar -xvf cdp_SunOS_x_x_xx.tar
> Decompressing the installation file results in the following files:

> l | CDP_Installer.bin: The CDP installation binary file.

> l | uninst: A script to uninstall CF-CDP application.

> l | README: A text file containing information pertaining to the release.

> l | inst: A script to install the CF-CDP server.

> 2 | Go to CDP_Install_dir/cdp folder and initiate the installation procedure by entering the following command:

> ./inst -console
> A message appears welcoming you to the CF-CDP installation.

> 3 | Follow the on-screen prompts to proceed through the installation script and configure the various parameters as required. Refer to Table 3-1 for descriptions of the configurable parameters within each of the sections of the script.

> WARNING: Please ensure that you have enough disk space for the installation of CDP application. If sufficient space is not available in the installation directory, cancel the installation process and free-up the disk space to proceed with the installation.
> After you have completed the installation configuration and all processes have started, you receive a message indicating that the CF-CDP was successfully installed.

> 4 | Copy the uninstallation script to the cdp_base_directory directory by entering the following command:

> cp uninst cdp_base_directory/

> 5 | Verify that all the CF-CDP components and processes are successfully started by entering the following command:

> ./serv status
> The following is a sample message:
> -----------------------------------------------------------
> PID Process Status
> -----------------------------------------------------------
> - PS Monitor Application Not running
> - Report Engine Server Not running
> - Database Deliver application Not running
> - Central Decision Point Server Not running
> 7315 Postgres Server Running
> -----------------------------------------------------------
> All of the parameters configured get stored in configuration files located in /<application_base_directory>/etc directory. For more information on the configuration files, see the Modifying CF Components’ Configuration Files section.
> Installing WEM
> For WEM installation and configuration procedure, refer to the Web Element Manager Installation and Administration Guide.
> Installing CF Customer Care Interface (CF-CCI)
> IMPORTANT: This section is applicable only for the Category-based Content Filtering solution.
> This section describes the procedure to install Customer Care Interface server application. The procedure described here assumes that you have already verified the minimum system requirements as specified in the Before You Begin section of this chapter and that the CCI application installation tar file is in your base directory on the server.
> The CF-CCI installation supports the following modes:

> l | GUI: This is the most often used mode. Requirements for this mode of operation include:

> l | Login account to the server with display terminal (monitor) attached and some X-Windows client installed on server.

> l | Network connectivity to the CCI server via Telnet or SSH, using some X-Windows client on remote workstation.

> l | Silent: This mode is used only if the CF-CCI is already installed on the machine. For silent-based mode, user needs to update the installvariables.properties file in Uninstall_CDP directory while executing 'inst' script in silent mode.

> IMPORTANT: Before the installation of this CF-CCI server application make sure that Central Decision Point (CF-CDP) application is installed and running on CF-CDP server.
> The following procedure describes how to install the CF-CCI application through the GUI-based interface.

> 1 | Change to the directory where the cci_x.x.xx.tar file is located and un-tar it by entering the following command:

> tar -xvf cci_x_x_xx.tar
> Decompressing the installation file results in the following files:

> l | CCI_Installer.bin: The CCI installation binary file.

> l | README: A text file containing information pertaining to the release.

> l | inst: The installation script used to install Customer Care Interface server application.

> The usage format for the CF-CCI installation and uninstallation scripts is as follows:
> ./inst [ -ui | -silent ] | [ -help]
> ./uninst [ -ui | -silent ] | [ -help]
> The following table denotes the different keywords/options used with this command:

> Keyword | Description
> -ui | Starts the installer in GUI mode. By default, the script starts in GUI mode.
> -silent | Starts the installer in silent mode.
> -help | Displays the supported keywords/options associated with this command.

> IMPORTANT: Before proceeding to CF-CCI installation make sure that JDK5.0 is installed.

> 2 | Change to the base directory /cci and then enter the following command:

> ./inst
> or
> ./inst -ui
> The CCI Introduction dialog box is displayed.
> CCI Installer Dialog Box

> 3 | Respond to the on-screen prompts with the help of inputs given in following table and configure various parameters as required.

> CF Customer Care Interface Server Installation Parameter Descriptions
> Parameter | Description | Default Value
> System Setting for Postgres
> | This dialog or script section is informational and contains no configurable parameters. Information pertaining to these variables is located in the Setting the PostgreSQL Database System Environment Configurations section in this chapter. | N/A
> Customer Care interface Server Installation Path
> Installation Directory | Enter the absolute installation path and directory on the server in which the CF-CCI server application is to be installed. This parameter creates a base directory cci_base_directory for CF-CCI installation. | Null
> Global Configuration
> IP Address of machine | Select the IP address of machine from the displayed list of IP address configured on the machine. Otherwise, enter the IP address in the field provided. | IP_address
> J ava development Kit (JDK) 5.0 Installation Root Directory
> Root Directory of java installation | Enter the root directory on the server in which the Java Development Kit 5 (JDK5) is installed. The absolute directory path can be manually entered in the field provided. | Null
> Central Decision Point Server Configuration
> CDP IP Address | Enter the IP address of the server on which the Central Decision Point server application is installed. | Null
> Create SSL Key and Certificate
> Common Name [CN] | Enter a common user name for Customer Care Interface user. This parameter creates common name cci_user for CCI users. | Null
> Organization Unit [OU] | Enter the organizational department name of the user of Customer Care Interface. This parameter creates organization unit name cci_user_org_unit for CCI users. | Null
> Organization Name [O] | Enter the organization name of the user of Customer Care Interface. This parameter creates organization name cci_user_org for CCI users. | Null
> Country [C] | Enter the country from where the installation of the Customer Care Interface will be accessed. This parameter creates country name cci_user_country for CCI users. | Null
> Alias | An alias name for the user and organization. | Null
> Keystore | Specify the filename and location to store the key and the certificate with absolute path. This parameter creates key and certificate files at the specified location as keystore_location/keyfile_name for CCI user with absolute path an. | Null
> Certificate Validity (Days) | Enter the validity duration of created certificate for specified user and organization in days. Any value from 1 through 99999 is acceptable. | 1095
> PostgreSQL Server Configuration
> Administrator Login | Enter the username for the Postgres database administrator in the field provided. | postgres
> Administrator Password | Enter the password for the user in the field provided. The password is case sensitive. | Null
> Database Port | Enter the port number over which CCI PostgreSQL server will run. The valid range is from 1 through 65535. To ensure proper operation and data integrity, the PostgreSQL database instances installed with the CF Element Manager should only be used by this application. | 5432
> CCI Application Server Configuration
> HTTPS Port | Enter the port number for the CF-CCI application server. Valid range is 1 through 65535. | 81
> Port to Listen Shut Down Command | Enter the port number to receive SHUTDOWN command for CF-CCI server. Valid range is from 1 through 65535. | 8005
> Session Timeout (Mins) | Enter the timeout duration in minutes to reset link connectivity. Any value from 1 through 30 is acceptable. | 30
> Trap Configuration | Select this check box to enable the trap configuration. | Disabled
> Trap Receiver Host | Enter the IP address of the SNMP server. | Null
> Trap Receiver Port | Specify the port number where alarms will be generated. Valid range is from 1 through 65535. | 162
> Start CCI server during installation | Select this check box if you want to start the CCI server automatically after installation. | Enabled

> After you have provided the inputs, the installation process starts and you receive a message indicating that CCI application installation starts on the basis of user inputs.
> WARNING: Please ensure that you have enough disk space for the installation of CCI application. If sufficient space is not available in the installation directory, cancel the installation process and free-up the disk space to proceed with the installation.
> The installation script starts different processes and the following dialog box appears reporting that the installation was successful.
> .
> CCI Installation Complete Dialog Box
> All of the parameters configured get stored in a configuration file located in the /<application_base_directory>/etc directory. For more information on the configuration files, see the Modifying CF Components’ Configuration Files section.

> 4 | Verify that the CF-CCI is running and accessible by entering the following link in your Web browser:

> https://cci_installation server name or IP Address:HTTPS Port/cci/login.jsp
> In case any of the process is stopped the PSMON process will restart all required processes. However you can stop and restart the CCI server manually by entering the following commands:
> ./stopserver.sh
> ./startserver.sh
> After verifying the CF-CCI server application installation, user can access the CCI through client station with the following link in web browser address field:
> https://cci_installation server name or IP Address:HTTPS Port/cci/login.jsp
> To start using CCI and Report Engine, refer to the Customer Care Interface and Report Engine appendix.
> Uninstalling CF Application Components
> This section describes the procedures to uninstall CF application components.
> Uninstalling CF-CDP Application
> The following steps describe how to uninstall the CF-CDP application:

> 1 | Log on to the CF-CDP server with “root” privilege.

> 2 | Change to the /cdp_base_directory/ and enter the following command:

> ./uninst
> The script uninstalls CF-CDP, Report Generator, and all related components from the CF-CDP server.
> Uninstalling CF-CCI Application
> IMPORTANT: This section is applicable only for the Category-based Content Filtering solution.
> The following steps describe how to uninstall the CF-CCI application:

> 1 | Log on to the CF-CCI server with “root” privilege.

> 2 | Change to the /cci_base_directory/cci directory and enter the following command:

> ./uninst
> The Uninstall CCI dialog box appears.
> Uninstall CCI Dialog Box

> 3 | To proceed with the uninstallation, click Uninstall.

> The uninstall script leaves the /cci_base_directory/ directory in place with several sub-directories.

> 4 | Optional. Delete the secure key and certificate file keyfile_name from the key store locations provided during installation.

> IMPORTANT: If you want to keep secure key and certificate file keyfile_name, skip this step.
> Modifying CF Components’ Configuration Files
> Once the CF components have been installed according to the information and instructions in this chapter, this information can be used as a reference for performing further configuration of the CF components to customize it to your needs.
> The CF provides a number of configuration files which can be modified to fine-tune the operation of the application. These files are located in the /<application_base_directory>/etc directory by default.
> This section provides descriptions for each of the configuration files. Details on the parameters each file contains is located within the files. The default values for these parameters are suitable for most installations. However, the values can be modified using a text editor (such as Vi Editor) if required.
> CAUTION: For many of these files, the CF application must be stopped and restarted in order for the modifications to take effect. To ensure proper operation, be sure to read and understand all of the information provided in the files prior to making changes.
> CF-CDP Specific Configuration Files
> This section provides descriptions for each of the configuration files that are associated with the CF-CDP application.
> The following are the CF-CDP specific configuration files:

> l | The cdp.cfg File

> l | The img.cfg File

> l | The processmonitor.cfg File

> l | The psmon.cfg File

> l | The reportengine.cfg File

> l | The reports.cfg File

> l | The thr.cfg File

> The cdp.cfg File
> This file contains CF-CDP specific parameters that are configured for generation of ad-hoc reports. The parameters are also configured to export Optimized Customer Master Database (OPTCMDB) files to CF-CDP.

> Parameter | Description | Minimum Value | Maximum Value | Default Value
> CF-CDP Parameters
> cdpcfemsdbpollinterval | This indicates the time interval, in minutes, in which CF-CDP Server will check if any database is available from WEM in a preconfigured path. | 1 min | 1440 min (24 hrs) | 5 min
> cdplocalbasedirpath | This is the local base directory where CF-CDP will be installed. | -- | -- | <Absolute_Path>/cdp
> optlocaldirpathcfems | This is the directory where WEM can export the latest Optimized Database (OPTCMDB) in CF-CDP. | -- | -- | <Absolute_Path>/cdp/cfems
> optlocaldirpathcdp | This is the path where CF-CDP will keep full DB to be loaded in memory. | -- | -- | <Absolute_Path>/cdp/optcmdb
> optlocalarchivedirpath | This is the path to keep archives of full and incremental updates of OPTCMDB. | -- | -- | <Absolute_Path>/cdp/archive
> cdpdbexportpollinterval | This indicates the time interval, in minutes, in which CF-CDP Server will push incremental DBs to STxx in a preconfigured path. | 1 min | 1440 min (24 hrs) | 120 min
> Miscellaneous Parameters
> enabledebugoptions | This identifies the debugging levels for the CF-CDP logs. The levels are:
> n | 1. CRITICAL
> n | 2. ERROR
> n | 3. WARNING
> n | 4. INFO
> n | 5. DEBUG
> This config is used only in cdp_deliver script. This can be changed dynamically. | 1 | 5 | 2
> cdpserversupressalarm | This is a flag for suppressing alarms. The possible values are:
> n | 1: Enables generation of alarms
> n | 0: Disables generation of alarms
> | -- | -- | 0
> alarmserveripaddress | This field will carry the IP address of the server where alarms and traps are to be sent. If this field is empty the CF-CDP will not generate and send traps. | -- | -- | IP address of alarm server
> alarmserverportnumber | This field will carry the port number of the server where alarms and traps are to be sent. If this field is empty the CF-CDP will not generate and send traps. | 0 | 20000 | 162
> alarmservercommunitystr | This field will configure community string of the server where alarms and traps are to be sent. If this field is empty the CF-CDP will not generate and send traps. | -- | -- | public
> CORBA Parameters
> ServerIIOPPort | This indicates the port that will be used to create POAs. | 18000 | 27000 | 19000
> cdpServerIpAddress | This specifies the IP address that will be used by CF-CDP Server for generating IOR files. If the field has default loopback interface value then CF-CDP Server will take the first active interface present on the machine. If the specified IP is not active, the CF-CDP Server will not start. | -- | -- | IP address of CF-CDP Server
> cdpServerPort | The TCP port to which CF-CDP Server binds. | 28000 | 38000 | 29000

> The img.cfg File
> This file contains the parameters that are used for configuring the chassis. These parameters can be changed dynamically.

> Parameter | Description | Default Value
> HOSTINFO
> mgmt_count | This indicates the management IP address count. | 0
> mgmt_host | This indicates the CF-ST16 Management IP address. | IP address of CF-ST16
> cfstxxusername | This indicates the user name used to logon to CF-STxx. | Null
> cfstxxpassword | This indicates the password used to logon to CF-STxx. | Null
> optcmdbremotedirpath | This is the remote Directory Path for each CF-STxx to where Optimized Database can be exported. | /pcmcia1/cf
> cdpenableblackListing | This is a flag to enable Blacklisting feature. Possible values are:
> n | 1: Enable Blacklisting
> n | 0: Disable Blacklisting
> | 0
> optcmdbblistremotedirpath | This is the Black List Remote Directory Path for each CF-STxx to where Optimized Black Listing Database can be exported. | /flash/cf

> The processmonitor.cfg File
> This file contains parameters used by the Process Monitor module. These include parameters such as the directories from which CF-related processes are started, polling intervals, and maximum percentage thresholds.

> Parameter | Description | Minimum Value | Maximum Value | Default Value
> CDPServer
> ExeName | This indicates the Process executable's name. | -- | -- | cdpserver
> ExePath | This indicates the Absolute or Relative path for executable file. | -- | -- | ./bin
> PidName | File name which contains PID of the process. |  |  | cdpserver.pid
> PidPath | This indicates the Absolute or Relative path for PID file. | -- | -- | .
> MultiProc | This is a flag indicating whether the process information should include the information of child processes or not. Valid values are:
> n | 0: Disable
> n | 1: Enable
> | -- | -- | 0
> Report Engine (RE) Server
> ExeName | This indicates the Process executable's name. | -- | -- | reserver
> ExePath | This indicates the Absolute or Relative path for executable file. | -- | -- | ./bin
> PidName | File name which contains PID of the process. |  |  | reserver.pid
> PidPath | This indicates the Absolute or Relative path for PID file. | -- | -- | .
> MultiProc | This is a flag indicating whether the process information should include the information of child processes or not. Valid values are:
> n | 0: Disable
> n | 1: Enable
> | -- | -- | 0
> DB: Database Process Information
> ExeName | This indicates the Process executable's name. | -- | -- | postgres
> ExePath | This indicates the Absolute or Relative path for executable file. | -- | -- | ./postgres/bin
> PidName | File name which contains PID of the process. |  |  | postmaster.pid
> PidPath | This indicates the Absolute or Relative path for PID file. | -- | -- | ./postgres/data
> MultiProc | This is a flag indicating whether the process information should include the information of child processes or not. Valid values are:
> n | 0: Disable
> n | 1: Enable
> | -- | -- | 1
> DirectoryInfo: This section provides information needed for monitoring the directory size.
> DirCDPServer
> DirPath | This is the directory path where CF-CDP Server exists. | -- | -- | .
> DirREServer
> DirPath | This is the RE server's data directory path. | -- | -- | ./data
> DirDB
> DirPath | This is the path of Database directory. | -- | -- | ./postgres/data
> PollInterval
> ProcInfoPollInterval | The process which changes frequently can be monitored for threshold limits with a smaller poll interval, say 5 seconds. | 1 sec | 3600 sec | 5 sec
> DirInfoPollInterval | The directory size does not change suddenly and can be monitored with 1 min or greater than 1min poll interval for threshold limit. | 60 sec | 36000 sec | 300 sec
> Threshold Information: This section provides information needed for the configuration of default threshold values for various parameters monitored by the module. These values are used for default configuration of the threshold values for the parameters.These values indicate maximum percentage threshold limits for the individual parameters as the default values.
> ThreshProcCDPServer | This is the CPU Utilization Threshold for CF-CDP Server. | 0% | 100% | 25%
> ThreshProcREServer | This is the CPU Utilization Threshold for Report Engine server. | 0% | 100% | 25%
> ThreshProcDB | This is the CPU Utilization Threshold for database server. | 0% | 100% | 25%
> ThreshProcTotalSwap | This is the Swap space Utilization Threshold. | 0% | 100% | 25%
> ThreshDirCDPServer | This is the Disk Utilization Threshold for CF-CDP Server. | 0% | 100% | 25%
> ThreshDirREServer | This is the Disk Utilization Threshold for Report Engine server. | 0% | 100% | 25%
> ThreshDirDB | This is the Disk Utilization Threshold for Database server. | 0% | 100% | 25%
> CPU: This section describes the parameters used to calculate the CPU utilization.
> NumberofSample | This calculates the average of 'NumberofSample' given in the cfg file. | 1 | 360 | 5

> The psmon.cfg File
> This file contains parameters for the operation of the PSMon (Process Monitor) function supported by CF.

> Parameter | Description | Default Value
> NotifyEmail | Defines the e-mail address where notification e-mails are to be sent. | root@localhost
> SmtpHost | Defines the IP address or hostname of the SMTP server to be used to send e-mail notifications. | localhost
> Frequency | Defines the frequency of process table queries. This is the polling interval. The value must not be less than 10 seconds. | 60 sec
> MemoryUsed | This is the threshold indicating the total memory used in percentage (%). | 50%
> SwapUsed | This is the threshold indicating the total swap used in percentage (%). | 50%
> FinalDirThreshold | This is the final directory threshold (in % on the file system where FinalDirPath present). Keep it blank if you do not want to monitor the final directory. | --
> LastSafePID | When defined, psmon will never attempt to kill a process ID which is numerically less than or equal to the value defined by the last safe PID. Psmon will never attempt to kill its own process ID or a process ID that is lesser than or equal to 1. | 100
> ProtectSafePIDsQuietly | Accepts a boolean value of On or Off. Suppresses all notifications from preserved process IDs when used in conjunction with the last safepid directive. | Off
> DryRun | Forces this psmon as if the --dryrun command line switch had specified. This is useful if you want to force a specific configuration file to only report and never actually take any automated action. This is enabled in this default distribution configuration to prevent people from blindly executing psmon “out of the box” and causing damage in live environments. The <Process *> scope is commented out by default. It should be used with extreme care. If used, run psmon in 'DryRun' mode by adding the 'DryRun' directive in this configuration file. Read the config file thoroughly before enabling this feature. | Enabled
> Cron Daemon
> Use the following format to configure each process: <Process %%% CDP_POSTGRES_RUN_CMD %%% > spawncmd (cd %%% CDP_SCRIPT_PATH %%%; %%% CDP_POSTGRES_RUN_CMD %%%) pidfile %%% CDP_PATH %%%/postgres/data/postmaster.pid numretry 10 tmintval 330 cpupct 10 mempct 10 </Process> <Process %%% CDP_REPORTENGINE_RUN_CMD %%% > spawncmd (cd %%% CDP_SCRIPT_PATH %%%; %%% CDP_REPORTENGINE_RUN_CMD %%%) pidfile %%% CDP_PATH %%%/reserver.pid numretry 10 tmintval 330 cpupct 10 mempct 10 </Process> <Process %%% CDP_SCRIPT_PATH %%%/bin/cdp_deliver.py > spawncmd (cd %%% CDP_SCRIPT_PATH %%%; %%% CDP_PROCESS_FULL_RUN_CMD %%%) pidfile %%% CDP_PATH %%%/cdp_deliver.pid numretry 10 tmintval 330 cpupct 10 mempct 10 </Process> <Process %%% CDP_FETCH_RUN_CMD %%% > spawncmd (cd %%% CDP_SCRIPT_PATH %%%; %%% CDP_FETCH_RUN_CMD %%%) pidfile %%% CDP_PATH %%%/cdpserver.pid numretry 10 tmintval 330 cpupct 10 mempct 10 </Process> Where:
> n | numretry and tmintval are optional
> n | Edit %%% <TAG> %%% with appropriate path.
> n | “tmintval” is measured in seconds and must be greater than ('numretry' * 'Frequency').
> n | cpupct and mempct are used to check CPU and memory thresholds of a process. The default value for cpupct and mempct is 10 %.
> n | In case of wrong values, this will not work properly.
> Sendmail SMTP Mail Daemon <Process sendmail> spawncmd /sbin/service sendmail start pidfile /var/run/sendmail.pid </Process>
> Apache Group HTTP Daemon <Process httpd> spawncmd /sbin/service httpd restart pidfile /var/run/httpd.pid # instances 200 # pctcpu 80 </Process>
> MySQL Database <Process mysqld> spawncmd /sbin/service mysqld restart killcmd /sbin/service mysqld stop pidfile /var/run/mysqld/mysqld.pid # pctcpu 90 # pctmem 60 </Process>

> The reportengine.cfg File
> This file contains parameters that are specific to the Report Engine (RE) server.

> Parameter | Description | Minimum Value | Maximum Value | Default Value
> Directory
> InputDir | This directory contains the EDR files to be parsed by Report Engine. | -- | -- | <cdp_install_dir>/data
> OutputDir | This directory contains the reports which will be generated by Report Engine. | -- | -- | <cdp_install_dir>/reports
> ArchiveDir | This directory contains the archive files which are moved from input directory after completion of parsing. | -- | -- | <cdp_install_dir>/archive
> FileArchiveEnable | This flag enables the archiving of report engine files. Possible values are:
> n | 1: Enables the archiving functionality
> n | 0: Disables the archiving functionality
> | -- | -- | 1
> Database
> REPORTSDBASE | This database can be postgres, oracle, etc. | -- | -- | postgres
> ThreadPool
> ParserThreadPoolSize | This indicates the parser thread pool size. | 5 | 100 | 10
> InsertionThreadPoolSize | This indicates the record insertion thread pool size. This parameter is used to open number of database connections. | 2 | 50 | 25
> Polling: This section contains parameters that are used for optimization of report engine module in terms of polling.
> FilePollInterval | This is the file polling interval (in seconds) in the data directory. | 5 sec | 60 sec | 30 sec
> ParserPollInterval | This Parser manager threads poll on file InfoMap and allocates file parsing jobs to worked threads. | 1 sec | 30 sec | 2 sec
> InsertionPollInterval | This DB Insert manager threads poll on DB insertion vector queue and allocates record insertion jobs to worked threads. | 1 sec | 10 sec | 2 sec
> ArchivePollInterval | This archive manager threads poll on archive file InfoMap and allocates file archiving jobs to worked threads. | 5 sec | 60 sec | 30 sec
> Reportengine
> ReportEnginePort | The TCP port to which Report engine binds. | 22000 | 29000 | 22000
> ReportEngineStatsInterval | This is the time interval, in seconds, after which the statistics will be generated for Report Engine (RE). | 1 sec | 30 sec | 5 sec
> ReportEngineServer | This is the IP address of the machine where the RE server is running. |  |  | 127.0.0.1
> EdrDateFormat | This indicates the Date-Time format that is supported in EDR files which are getting parsed by RE. Possible values are:
> n | [1] MM/DD/YYYY-HH:MM:SS
> n | [2] MM/DD/YY-HH:MM:SS
> n | [3] YYYY/MM/DD-HH:MM:SS
> n | [4] YYYYMMDDHHMMSS
> n | [5] seconds
> | 1 | 5 | 1
> TableSplitInterval | This indicates the split interval of 'detailinfo' table in hours. | 1 hr | 24 hrs | 3 hrs
> CreateIndexAfterInterval | This indicates the time interval after which the index table will be created. | 5 min | 120 min | 60 min
> DBRetentionPeriod | This is the retention period for reportsdb (detailinfo tables) in days. | 1 day | 60 days | 30 days

> The reports.cfg File
> This file provides information on the configurables that are associated with the different report types.

> Parameter | Description | Default Value
> Reports
> NAI | This specifies the NAI/MSID (radius-user-name) of the user for which to generate report. | --
> SCBRID | This specifies the subscriber ID (radius-calling-station-id) of the user for which to generate report. | --
> ReportSchemaFields: The following fields are used for Subscriber Detail report. Each field represents the column in the report. You can select the columns to be represented in report by setting or unsetting these field values. Some fields are set by default.
> n | 0: Unset
> n | 1: Set
> startdate | 1
> enddate | 1
> duration | 0
> imgid | 0
> uplinkbytes | 0
> downlinkbytes | 0
> uplinkpkts | 0
> downlinkpkts | 0
> url | 1
> scbrid | 0
> cfpolicy | 1
> cfratingtype | 1
> cfaction | 1
> cfcategory | 1
> nai | 0
> URLList
> URL | This is the absolute path of the file mentioning the list of URLs with each URL at new line. This is required for generating URL Summary report. | --
> Multi Threaded Query Manager (MTQM)
> NoOfQueryThreads | This is the number of threads to be spawned to execute parallel distributed queries. The value must be an integer from 1 through 10. | 4

> The thr.cfg File
> This is the configuration file for the thread pool.
> IMPORTANT: Any changes to the parameters in the thr.cfg file need server restart for the modifications to take effect.

> Parameter | Description | Minimum Value | Maximum Value | Default Value
> PoolEnable | This is a flag for enabling or disabling thread pool. The possible values are:
> n | 1: Enable thread pool
> n | 0: Disable thread pool
> | 0 | 1 | 1
> Size | This indicates the size of the thread pool. | 10 | 100 | 10
> MaxSize | This indicates the maximum size of the thread pool. | 10 | 100 | 30

> CF-CCI Configuration File
> This section provides descriptions for each of the parameters in the configuration file, psmon.cfg, associated with the CF-CCI application.
> The psmon.cfg File
> This file contains parameters for the operation of the PSMon (Process Monitor) function supported by CF.

> Parameter | Description | Default Value
> Frequency | Defines the frequency of process table queries. This is the polling interval. It is recommended to configure the Frequency above180 seconds. | 180 sec
> LastSafePID | When defined, psmon will never attempt to kill a process ID which is numerically less than or equal to the value defined by the last safe PID. Psmon will never attempt to kill its own process ID or a process ID that is lesser than or equal to 1. | 100
> ProtectSafePIDsQuietly | Accepts a boolean value of On or Off. Suppresses all notifications from preserved process IDs when used in conjunction with the last safepid directive. | Off
> DryRun | Forces this psmon as if the --dryrun command line switch had specified. This is useful if you want to force a specific configuration file to only report and never actually take any automated action. This is enabled in this default distribution configuration to prevent people from blindly executing psmon “out of the box” and causing damage in live environments. The <Process *> scope is commented out by default. It should be used with extreme care. If used, run psmon in 'DryRun' mode by adding the 'DryRun' directive in this configuration file. Read the config file thoroughly before enabling this feature. | Enabled
> Cron Daemon
> Use the following format to configure each process. For example, copy the following 6 lines for each CCI process to monitor and modify according to the CCI path <Process /users/cci/server/bin/server> spawncmd (cd /users/cci/server; /users/cci/server/bin/server) pidfile /users/cci/server/server.pid numretry 2 tmintval 300 </Process> <Process /usr/java/bin/java > spawncmd (cd /users/cci/cci; /users/cci/cci/serv start cciserver >> logs/.server.log) pidfile /users/cci/cci/java.pid numretry 10 tmintval 2000 cpupct 10 mempct 10 </Process> # Please do not edit these lines if you do not have enough information # Instances should not be 0 <Process /users/cci/cci/perl/bin/perl -w ./psmon --daemon --cron> pidfile /users/cci/cci/psmon.pid instances 1 </Process> Where,
> n | numretry and tmintval are optional
> n | “tmintval” is measured in seconds and must be greater than ('numretry' * 'Frequency').
> n | cpupct and mempct are used to check CPU and memory thresholds of a process. The default value for cpupct and mempct is 10%.
> n | In case of wrong values, this will not work properly.

> Managing Application Level Traps and Alarms
> This section describes the procedure to configure the application level traps and alarms for Content Filtering applications.
> All traps need to be defined manually in processmonitor.cfg file in /etc directory at the base directory of CF applications.

> 1 | Log on to the required application server with “root” privilege.

> 2 | Change to the /etc directory by entering the following command:

> cd /application_base_directory/etc

> 3 | Open the processmonitor.cfg file in vi editor by entering the following command:

> vi processmonitor.cfg
> This configuration file contains the supported threshold and trap configuration fields for all CF applications.

> 4 | After opening the file in vi editor, press the Insert key to enable the INSERT mode.

> 5 | Go to the desired section in the processmonitor.cfg and edit the values as required:

> #(1) Section = DirCDPServer | To configure the EDR path on CDP server
> #(2) Section = DirREServer | To configure the data directory path on Report Engine server
> #(3) Section = DirDB | To configure the database directory path on Report Engine server
> [PollInterval] | To configure the different polling intervals for different thresholds
> [ThreshProcCDPServer] | To configure the CDP server process thresholds
> [ThreshProcREServer] | To configure the Report Engine server process thresholds
> [ThreshProcDB] | To configure the Database (Postgres) process thresholds
> [ThreshProcTotalSwap] | To configure the swap space usage thresholds
> [ThreshDirCDPServer] | To configure the disk usage threshold at the CDP server
> [ThreshDirREServer] | To configure the disk usage threshold at the Report Engine server
> [ThreshDirDB] | To configure the disk usage threshold for database
> [CPU] | To configure the CPU usage threshold for database

> 6 | Save and close the processmonitor.cfg file by entering the following commands:

> Esc
> :wq

> 7 | After setting the parameters, restart the related application server and application to apply the changes.

> For more information on supported traps and objects at the chassis and application level, refer to the Content Filtering Application MIB and Default Trap Severities in SNMP MIB Reference.

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883