These parameters specify the earliest and latest events to be included in the import operation and the location for any EVF files generated when an event cannot be imported for any reason. Other parameters specify the maximum number of events in each batch returned to Event Import for processing and whether or not the import job runs in continuous mode.
Important! This parameter is mandatory for remote CMS import operations!
Defaults to zero (see below). This mandatory parameter defines a ‘job start date’. The syntax is:
SQL.JobStartTime=<year:month:day:hour:min:sec>
The job start date is the earliest capture date for imported events. That is, the import job only includes events captured after this start date; events captured before this date are not imported. This example imports events captured after midnight on 11 July 2007:
SQL.JobStartTime=2007:07:11:00:00:00
If set to zero
This parameter can also be set to zero. This means the import job has no start date; all events are imported, providing their capture date falls before the ‘job end date’ (if specified).
SQL.JobStartTime=0
Defaults to zero (see below). This parameter optionally defines a ‘job end date’. The syntax is:
SQL.JobEndTime=<year:month:day:hour:min:sec>
The job end date is the latest capture date for imported events. That is, the import job only includes events captured before this end date; events captured after this date are not imported. This example imports events captured before midnight on 12 July 2007:
SQL.JobEndTime=2007:07:12:23:59:59
Note: If an import job runs before the specified ‘job end date’, then the job end date is automatically set to the current time.
If set to zero
This parameter can also be set to zero. This means the import job has no end date; all events are imported, regardless of capture date:
SQL.JobEndTime=0
Important! This parameter is mandatory for remote CMS import operations!
This parameter specifies the folder used to store events that could not be imported. The syntax is:
SQL.FailedEVFDirectory=<Path>
These import failures can occur, for example, if a policy engine fails to process an imported event. Events that fail to be imported are written to the specified folder as EVF files (see below). For example:
SQL.FailedEVFDirectory="C:\Import Failures"
You must enclose the folder path in double quotes if it includes spaces.
Import failures saved as EVL files if unable to generate EVF files
If Event Import fails to generate an EVF file (for example, because the connection to a policy engine is lost), it will save an EVL file to this folder. EVLs are ‘event link’ files that point to the associated email events on the primary CMS.
Reprocessing import failures
To retry importing these failed events, you must run a EVF import job. That is, the Import.Type parameter is set to EVF; see .
This parameter enables scheduled import jobs to resume from the point at which it was stopped. The syntax is:
SQL.RunViaScheduledTask=Yes or No
You can schedule remote CMS import jobs (based on wgnimp.exe) by using Windows Scheduled Tasks. This enables you to schedule import jobs to run at fixed times for a fixed duration.
If a scheduling time slot expires before an import jobs has completed, this parameter, SQL.RunViaScheduledTask, enables the import job to resume (during the next scheduled time slot) from the point at which it was stopped. If this parameter is set to:
An interrupted remote CMS import job will resume from the point that it was stopped. That is, it ignores events returned by the database query that have already been imported. If you run scheduled import jobs, you typically also set SQL.JobEndTime to zero.
Important! Be aware that if you change any of the following parameters while an import job is running, the job will restart from the beginning (see the ‘No’ description below for details):
SQL.RunViaScheduledTask SQL.JobStartTime SQL.JobEndTime SQL.EventType
An interrupted import job will restart from the beginning. That is, it will attempt to import all events returned by the database query, including events already imported. This mode is appropriate for batch import jobs.
Defaults to 4000. This parameter specifies the maximum number of events in each import batch. The syntax is:
SQL.RecordSetSize=<Number>
You do not normally need to change this number. When a database query searches a remote CMS database, it returns matching events to Event Import in batches. Each batch is based on event timestamps. Grouping the query results in this way ensures optimized import performance and avoids potential problems that can occur when very large results sets are transferred across a network.
If your CMS database is very large, and the CMS host server is sufficiently powerful, you may want to increase the batch size to enable faster importing.
Defaults to Yes. This parameter specifies the date for the event timestamp. The syntax is:
SQL.EventDateFromSource=Yes or No
If set to:
The timestamp is set to the original timestamp from the CMS database.
The timestamp is set to the date when the event was actually imported.
Note: This parameter is primarily used for diagnostic or testing purposes.
|
Copyright © 2014 CA.
All rights reserved.
|
|