These parameters are specifically for importing e‑mails from Lotus Notes NSF files. They identify the source Domino server and target NSF files and folders. You can also specify whether source emails are deleted after import operations. NSF import operations can also use Email general parameters) and the File.ContinuousInput parameter.
Note: Before using wgnimp.exe from a command to import .NSF files, you must adjust the logging level for the local Notes client. This suppresses unnecessary progress messages.
This compulsory parameter specifies the name of the Domino Server hosting the NSF file (not the name of the machine hosting the Domino Server). The syntax is:
NSF.DominoServerName=<name of NSF host server>
Server names are not case-sensitive. A single Event Import operation can only include one instance of this parameter. For example, if the Domino Server name is domino-sales/unipraxis, hosted on the machine UNI‑HARDY‑W2K3, set this parameter to:
NSF.DominoServerName=domino-sales/unipraxis
To import a local NSF file, that is, to open import databases from the local data directory (as specified by the Directory variable in notes.ini), set this parameter to:
This compulsory parameter has no default value. It specifies a path to the NSF file relative to the Domino server. The syntax is:
NSF.DominoFileName=<file path>
A single Event Import operation can include multiple instances of this parameter, with each instance specifying a separate NSF file:
NSF.DominoFileName=mail\sales\frankschaeffer.nsf NSF.DominoFileName=mail\sales\spencerrimmel.nsf
You can also use ? and * wildcards.
This optional parameter specifies the password for the Notes user on the Event Import host machine. The password is needed to access the Notes databases that you are importing from. The syntax is:
NSF.ImportPassword=<password>
To avoid a security loophole, you can configure wgncred.exe to securely cache this password; the required component ID is: NotesImport
Note: If the password is not set here or by using wgncred.exe, the importer exits and an incorrect password error is written to the Event Import log file. Find this in the \system\data\log subfolder in the CA DataMinder installation folder.
Defaults to 100. This optional parameter determines how many times Event Import attempts to open an individual note or a Notes database if the Domino server is not responding fast enough. The syntax is:
NSF.OpenRetries=<number of attempts>
Raise this parameter to a higher value if events are failing to import.
This parameter specifies the Notes Mail item (that is, the named property) that contains the unique Archive ID allocated by a third party archive solution. The syntax is:
NSF.RemoteDataLocationDBItem=<named property>
You can also include in this parameter a filter expression to extract the Archive ID from any other information stored in the named property specified. For example, for integration with IBM DB2 CommonStore for Domino, set this parameter to:
NSF.RemoteDataLocationDBItem=CSNDArchiveID, ["DOCID\#{%until(\#)%}"]
This example tells Import Policy that the Archive ID is stored in the CSNDArchiveID property and gives a filter expression to extract the Archive ID from other information stored there.
This parameter specifies the email archive type. The syntax is:
NSF.RemoteDataLocationType=<archive type>
For integration with IBM DB2 CommonStore for Domino, set this parameter to:
NSF.RemoteDataLocationType=CSLD
This optional parameter specifies which folders within the NSF file you want to import. The syntax is:
NSF.FolderName=<name of folder>,Yes or No
A single Event Import operation can include multiple instances of this parameter, with each instance specifying a particular folder:
NSF.FolderName=Internal,no NSF.FolderName=Internal\Memos,no
To import standard folders such as Inbox or Sent, prefix the folder name with a $ character and capitalize the first letter. When identifying subfolders, use backslashes as separators. Add Yes or No after the folder name to indicate whether subfolders are also imported; you must include a comma before the Yes or No option. If you do not specify Yes or No, you do not need a comma and NSF.FolderName defaults to Yes. The following examples illustrate the parameter usage:
NSF.FolderName=Sales,yes
Yes and No options are case‑insensitive.
NSF.FolderName=$Inbox
Subfolders are imported automatically..
NSF.FolderName=Sales\North America,no
Subfolders are not imported.
Note: The NSF.FolderName parameters apply to all NSF.DominoFileName parameters. If a specified folder does not exist within the source NSF file, an error is written to the Event Import log file. Find this in the \system\data\log subfolder in the CA DataMinder installation folder.
Note: This parameter is unable to detect ‘unparented’ emails, that is, emails that have been moved from their original folder within the NSF file.
This parameter specifies the name of the view used by the importer to display failed messages in the Notes Database. The syntax is:
NSF.FailedMessageFolder=<view name>
If an email cannot be imported, the importer creates this view in the Notes Database and then adds the WiganImportStatus property to the email to mark it as ‘failed’. The email is not moved to a separate folder.
Note: If this parameter is not specified, ‘failed’ emails cannot be viewed in the Notes Database.
Defaults to No. This optional parameter specifies whether to delete the source emails (in the specified file or folders) after they have been successfully been imported. The syntax is:
NSF.DeleteAfterImport=Yes or No
If set to:
The source emails are never deleted.
The source emails are deleted after a successful import operation.
Defaults to Yes. This optional parameter specifies whether messages that previously failed to import are retried when the importer is restarted. The syntex is:
NSF.RetryFailedOnStartup=Yes or No
When the importer is restarted, if this parameter is set to:
Event Import does not try to re-import any previously failed messages.
Event Import tries to re-import all messages that previously failed to import. If using continuous import, messages are only retried on their first pass through the database.
Event Import also removes the WiganImportStatus property from ‘failed’ emails to enable it to retry the import process.
If this parameter is not included in the import configuration file, and ‘failed’ messages exist, Event Import assumes a default value of Yes.
Copyright © 2014 CA.
All rights reserved.
|
|