Configuring Central Logger

To run the Central Logger instances in a fault tolerant mode, you must set the Max Active property. Optionally, you can configure Agent Priority parameter. The Max Active and Priority parameters are defined in the ASG_HOME/bin/asg_cl.cdd file. See Configuring Fault Tolerance ParametersFor the Core Engines, you should run the multiple instances across the servers in a load balanced setup. The configuration for load balanced setup is defined in the asg_core.cdd file. See Configuring Core Engines. For the Cache Cleanup Agent, Global Throttle Manager and Central Logger components, the instances must be deployed as one active engine and one or more stand by agents that run on a separate server. See Configuring Cache Cleanup Agent, Configuring Global Throttle Manager and Configuring Central Logger. The maximum number of active instances are configured as an agent class configuration parameter. An agent class is an agent type, defined in the CDD file that deploys as an agent instance. The following parameters define the fault tolerant configuration of runtime components: Fault Tolerant Configuration ParametersParameter Description Max Active Specifies the maximum number of active agents. This value is used for fault tolerance. Deployed agents that are acting as standbys can take over from active instances that fail. In many cases, there is no need to keep standby instances. Priority Specifies the priority of the agent for fault tolerant setup of agents. The priority is set at the processing unit level. The priority indicates the order in which standby agents become active, and conversely, the order in which active agents become standbys, when new agents join the cluster. The lower the number, the higher the agent is in the activation priority list. For example, an agent with priority 2 has a higher priority than an agent with a priority of 6. This value determines the order of each instance of an agent class for startup, as well as fail over and fail back in fault tolerance situations. If the priority values are same for agents in fault tolerant setup (active passive), the agent which is started first gets the higher priority to become active agent instance. This section explains the steps for setting the maximum number of active instances and priority required for the high availability of runtime components. for description of parameters.

You can set the number of the active instances and priority for the Central Logger instances:

    Procedure
  1. Navigate to the ASG_HOME/bin directory.
  2. Edit the asg_cl.cdd file. You can edit the file either using a text editor or using the Studio. See Edit Cluster Deployment Descriptor (CDD) File. If you use the Studio, follow these steps:
    1. Open the ASG_HOME/bin/asg_cl.cdd file using the steps described in Editing CDD File using Studio.
    2. Select Agent Classes tab.
    3. Select the BusinessEvents_Archive (Inference) node.
    4. On the right side, set the following property as follows: 
            Max Active 1
    5. Save the changes.
  3. Optionally, you can set the priority for the asg-cl processing unit using the Studio as follows. See Setting Priority.
    1. Go to the Processing Units tab.
    2. Select the asg_cl node.
    3. Go to the Agents section, and select the row with BusinessEvents_Archive agent.
    4. Double-click the Priority column to set a value. For example, you can set this value to 5.
    5. Save the changes.