Chapter 2. Configuration File Blocks for WebFORCE MediaBase

Configuration parameters for WebFORCE MediaBase must be specified in the configuration file /var/ha/ha.conf. The sections in this chapter describe each block that must be added for WebFORCE MediaBase and the configuration parameters within each of those blocks. The sections are as follows:

The examples in this chapter show the WebFORCE MediaBase configuration file blocks for the example discussed in the section “Planning IRIS FailSafe WebFORCE MediaBase Configuration” in Chapter 1. A complete example of /var/ha/ha.conf for this example appears in Appendix A, “Example Configuration File.”

Application-Class Block

Example 2-1 shows the application-class block in a WebFORCE MediaBase configuration.

Example 2-1. application-class Block


application-class mediabase
{
        server-node = mb1
}

The application-class mediabase block contains this configuration parameter:

server-node  

Lists the node that is the primary WebFORCE MediaBase server. The value must match a node block label. Because WebFORCE MediaBase is supported only in an active/backup configuration, this block should have only one server-node parameter.

Mediabase Block

IRIS FailSafe configuration files contain one mediabase block. Example 2-2 shows an example mediabase block.

Example 2-2. mediabase Block


mediabase mbserver
{
        server-node = mb1
        backup-node = mb2
        check-services = ( “Media Delivery Service” “Informix Online Daemon” )
        httpd-dir = /usr/ns-home/httpd-mbasesrvr
        httpd-options-file = ns_fasttrack.options
        httpd-script = /etc/init.d/ns_fasttrack
}

The label for the mediabase block, mbserver in this example, is a name of your choice. The configuration parameters used in the mediabase block are as follows:

server-node  

The primary node for the WebFORCE MediaBase server. The value must be the same as the value of the server-node parameter in the application-class mediabase block.

backup-node  

The backup node for the WebFORCE MediaBase server. Its value matches the label of the node block for the node that is not the primary node for WebFORCE MediaBase.

check-services  

A list of the names of the services provided by the WebFORCE MediaBase server that should be monitored by IRIS FailSafe. The full list of services is available from the Service Status window of the WebFORCE MediaBase Monitoring Tool.

httpd-dir  

The pathname of the server root for the Netscape FastTrack or Enterprise Server used by WebFORCE MediaBase.

httpd-options-file  


The name of the configuration file in the directory /etc/config that is used to start multiple Netscape servers. The script that is listed as the value of httpd-script reads this configuration file.

httpd-script  

The location of the script that is used to start and stop the Netscape FastTrack or Enterprise server.

Action and Action-Timer Blocks

Example 2-3 shows the action and action-timer blocks for WebFORCE MediaBase. The action block specifies the pathnames of the local monitoring script, and the action-timer block specifies monitoring timing and timeout values for the monitoring of WebFORCE MediaBase server.

Example 2-3. action and action-timer Blocks


action mediabase
{
        local-monitor = /var/ha/actions/ha_mbase_lmon
}

action-timer mediabase
{
        start-monitor-time = 120
        lmon-probe-time = 120
        lmon-timeout = 90
}

The parameters used in action and action-timer blocks for mediabase are as follows:

local-monitor  

The pathname of the local monitoring script for WebFORCE MediaBase. Do not change this value.

start-monitor-time  


Specifies the amount of time in seconds that the application monitor waits before it starts using the local monitoring script to monitor the WebFORCE MediaBase server. The suggested value is 120.

lmon-probe-time  


The local monitoring script for WebFORCE MediaBase is executed by the application monitor this often (in seconds). The suggested value is 120.

lmon-timeout  


The local monitoring script for WebFORCE MediaBase is considered to have timed out if no response is received in this many seconds. The suggested value is 90.