Archive Integration Guide › Event Import › Running an Event Import Operation › Multiple Import Operations

Multiple Import Operations

You can run different types of import operations concurrently on the same host machine by running wgnimpsv.exe from a command line. Note also:

• All service instances share the same set of CMS logon credentials, so you do not need to rerun the wgnimpsv -setcredentials command.
• You must ensure all instances have been manually deleted before uninstalling Event Import, otherwise orphaned services will remain on the host machine.
• Each instance must import from a separate source.

Important! Import each service instance from a separate source. You cannot improve import performance by using multiple service instances to import data from a single Exchange mailbox or a single source folder. Indeed, this approach causes misleading 'import failure' messages to be written to the logfile.

The command syntax for configuring multiple service instances is shown below.

To create a non-default service instance

Each configuration file can specify a separate set of import parameters that apply only to that service instance. This example command creates a new service called wgnimpsv_lsteel, and the new service looks for a configuration file called import_lsteel.ini.

Wgnimpsv -instance lsteel ‑service

Note: The -instance parameter must come before the -service parameter

To start or stop a service instance

These example commands start and stop the new service.

net start wgnimpsv_lsteel

net stop wgnimpsv_lsteel

To delete a non-default service instance

This example command deletes the new service, provided it is not set as the default.

wgnimpsv -instance lsteel ‑unregserver

Note: The -instance parameter must come before the -unregserver parameter.