Deploying Event Loggger
- Create a database to store the reporting data.
Locate the correct setup script for your RDMBS and run it on the database
you created in Step 1.
This script is called eldb_<database_name>.sql, where <database_name> is either db2, mssql, or oracle (for example, eldb_mssql.sql). To locate the script, go to the Script subdirectory of the installation directory of your Interaction Server, then open the subdirectory named after your RDBMS; for example, \InteractionServer_801\Script\Oracle.
- Create a Database Access Point (DAP), filling in the usual mandatory settings on the General and DB Info tabs.
- On the DAP’s Options tab, create a section called logger-settings. This is the only mandatory section; its existence tells Interaction Server to use this DAP for storing reporting events.
- In the logger-settings section, add at least one option (the section must contain at least one option in order to be valid).
Optionally add any of the following section types:
- event-filtering—Contains options filtering out certain classes of event messages
- custom-events—Specifies a custom mapping of the CustomEventId attribute value of EventCustomReporting (the option name) to the Event Logger table to store them in (the option values)
- Custom data sections—Five sections that enable you to map the name of any event onto a custom field in the Logger database.
- On Interaction Server’s Connections tab, add a connection to the DAP. For multiple instances of the Event Logger, run the creation script multiple times, creating multiple databases. Also create a DAP for each database.
This page was last edited on December 17, 2013, at 18:54.