e-nspect2000 Configuration

Configuration of e-nspect2000 is undertaken using the Event Sink Administration Module. This is installed as part of the Client Tools. Please refer to the Event Sink Administration Module (ESAM) section for more details.

The first task is to locate the e-nspect sink. The e-nspect2000 event sink is registered within the Transport Events - OnPostCategorize. The Event Sink administration Module Guided tour section details how to navigate through a server's sink structure.

The e-nspect2k installation program installs the e-nspect sink into the Default SMTP Instance. It may be that this location will be incorrect. In this case you can simple delete the sink from this SMTP instance and install it again on the virtual SMTP instance of your choice (refer to the ESAM section for details on how to add new sinks). Of course you can have the e-nspect sink configured to monitor all your virtual SMTP instance. More on this later.

The configurable parameters for the e-nspect2000 event sink are as follows:

• Global Properties
  • Priority - When the sink will "fire" in relation to other sinks. The default value of 24575 should be OK.
  • Sink Name - The name you want to give the sink.
  • Enabled - If enabled the sink will work. If disabled the sink will not work.
• Source Properties - there are no source properties for this sink
• Sink Properties
  • LogFilePath - the directory where e-nspect2000 will hold temporary data (each sink instance needs its own directory).
  • db_host - the name of the database server.
  • username - username for database access.
  • password - the password for the database user.

All these are set during installation, but you can change them at any time if required.

On finding the e-nspect sink you should see this.

Double clicking on the e-nspect sink, or selecting its properties enables you to edit its properties, thus.

 

Some items can not be changed, such as the Sink Class (always "e_report.collect") and GUID (determined by Exchange), but the others can be.

An important configuration point to note is that if you are going to monitor multiple Virtual SMTP instances on the same Exchange server then each virtual smtp instance requires its own (unique) LogFilePath value. in other words, make sure each virtual SMTP instance is configured to use a different temporary directory. There is one other thing to note. If you create a new virtual SMTP instance using the Exchange System Manager then the new instance is a "replica" of the Default instance. So you will have to edit the e-nspect sink properties to provide the new virtual SMTP instance with its own LogFilePath entry.