Configuring event processing

The event processors Audit Log and Mail Processor need to be dedicated to a single server for a specific database, this is because these events must be processed in sequential order, or there is no way of preventing timer based retrievals from conflicting with each other. However this doesn’t mean that a different workgroup server can be used for that process type for another database. So, for the rollout of Content Manager databases, the configuration of event processing for Managed Service Provider's (MSP) must work within this limitation. While some events are dedicated, Content Manager can still distribute individual instances across the event servers and for the remainder of events to be able to share the load across all event servers.

For load balancing to work correctly for the event processor types:

  • content indexing
  • word indexing
  • schedule event triggers
  • event statistical aggregator

across multiple Workgroup Servers, follow these steps:

  1. For the event processor types above, set Configuration Status to Enabled and for Run on Workgroup, select Any.
  2. Set the Content Manager clients to connect to the dataset through a Workgroup Server that is not set to process events.
    This Workgroup Server then distributes these events evenly to other Workgroup Servers that are configured to process these events.
  1. Click to expand Datasets
  2. Right-click the dataset to configure and on the Event Processing menu, click Configure.

    The Configure Event Processing for Dataset <name> <dataset ID> dialog box appears.

  3. Configure Processes tab
    1. Event processor type - the Content Manager processors.

      For descriptions of the events, see Processors and events.

      • Content Indexing - processes the content indexing for Content Manager. You must suspend this processor when conducting content index maintenance functions.
      • Audit Log - needs to run on a single Workgroup Server so that there is a single log per dataset
      • System Monitor - monitors Content Manager for actions that need to be initiated because they are due, for example, when items become inactive or expire

        NOTE: The View Counter option that can be added to the View Pane for records in Content Manager requires the System Monitor event to be configured and running. If this event type is not configured and running the View Counter will not be updated and displayed correctly.

      • Mail Notification - can be allocated to multiple Workgroup Servers
      • Schedule Event Triggers - can be allocated to multiple Workgroup Servers
      • Word Indexing - mandatory. Can be allocated to multiple Workgroup Servers
      • Automated Part Creation - can be allocated to multiple Workgroup Servers
      • Alerts Service - can be allocated to multiple Workgroup Servers
      • SharePoint Integration - needs to run on a Workgroup Server that is part of a SharePoint Server farm.

        You can set the SharePoint Server farm for a Workgroup Server in its Properties - General tab.

      • Event Statistical Aggregator - Content Manager has a statistical feature which allows you to build up a time series showing the activity happening within the system. The Event Statistics Aggregator is notified of key events of interest. There are around 56 key statistical counters, each of which is tied to a particular event. Whenever one of these events happens, the Event Statistics Aggregator is notified and increments the corresponding counter. At the end of each day the tallies for the day are recorded in the database with a new row of statistics for that day. These daily row counter aggregations can be compiled into a statistical output report. This is available in the Content Manager client, from the Home ribbon, Reports group and from the Statistical drop-down menu, select Event Statistics. The report is a raw set of numbers, the provided column headings show all that statistical items that are available. Can be allocated to multiple Workgroup Servers.
        The counters are grouped into 4 categories:
        • General records management counters (records created, records updated, user logins, some key metadata changes, ...)
        • Document management counters (check in, check out, document printed, ...)
        • Workflow processing counters (action completed, action assigned, activity completed, activity reassigned, ...)
        • General auditing counters (changes to retention schedules, classifications, holds added, security breaches, ...)
      • Document Store Event Handler - should be enabled when you are using a document store of the type Manage in Place or an Amazon S3 compliant to ensure delete requests are processed correctly. Must run on a single Workgroup Server.
      • Auto Classify Records - processes automatic classification jobs for records. Must run on a single Workgroup Server.
      • Inactive Document Storage Optimizer - processes electronic documents made inactive by Inactive Records function, which moves inactive electronic records to lower cost storage. Must run on a single Workgroup Server.
      • Directory Synchronization - synchronizes LDAP-based directory services, in the form of user and group records, to be automatically synchronized to Content Manager. Must run on a single Workgroup Server.
      • Empty Record Recycle Bin - empties the record Recycle Bin as per the System Option - Records - Automatically empty record recycle bin settings. Must run on a single Workgroup Server.
      • Update Exposed Records - enable the event processor to update the contents of Exposed Records.
      • Manage in Place Scan - enable the event processor to perform scan of Manage in Place stores.
    2. Configuration status - the status of each dataset process:
      • Not Processing
      • Enabled - events within this process will be processed when necessary
      • Suspended - temporarily not processing
    3. Run on Workgroup - Workgroup Server running this process.

      Choose a particular Workgroup Server or Any to run this event processor on.

      Changing the Workgroup Server for a processor:

      1. Change the processor's Workgroup Server, click OK
      2. Click Save in the Content Manager Enterprise Studio toolbar.
      3. Click Deploy in the toolbar.

        The Workgroup Server is changed and Content Manager re-allocates the events automatically.

        However, if you suspect that event allocation may not be correct after a Workgroup Server change, use the command Check Allocation.
        See Dataset setup and maintenance.

  4. Custom Processes tab - enables you to define an external application to receive information from user defined Additional Fields.

    See Custom Processes tab.

  5. Options tab - for advanced event processing options like batch size and polling intervals. See Event processing Options tab.
  6. Click OK
  7. If you have made changes to the configuration, click Save in the toolbar
  8. Click Deploy to deploy the new configuration to the Workgroup Servers