These parameters can be used to configure CNV2email.exe and BB2email.exe conversion jobs.
(BB2email.exe only) This parameter has no default value. It can specify either a shortcut, or a fully-qualified path to a folder containing attachment files for imported conversations and emails. The syntax is:
Attachment.Folder=<folder path>
This parameter can specify:
Note: Do not use quote marks around pathnames, even if they contain spaces.
Note: There are no attachment parameters for Cnv2email.exe. This is because any IM attachments will already have been included in the source CNV files by IMFrontEnd.exe.
(BB2email.exe only) Defaults to No. This parameter determines whether subfolders within the Attachment.Folder will be included when BB2email.exe is searching for attachment data files. The syntax is:
Attachment.IncludeSubdirs=<Yes or No>
(BB2email.exe only) Defaults to No. This parameter specifies whether to delete email attachments from the source folder after they have been imported. The syntax is:
Attachment.Delete=<Yes or No>
If set to Yes, attachments are deleted; if set to No, they are not deleted.
Note: Attachment source folders are defined by Attachment.Folder.
(BB2email.exe only) Defaults to No. An attachment file can sometimes fail to be imported, for example if an attachment referenced in the log file being imported cannot be found. The syntax is:
Attachment.RejectOnFailure=<Yes or No>
This parameter specifies whether the BB2email.exe process ignores the attachment and continues with the import process, or fails this log file and moves on to the next. If set to:
BB2email.exe fails the attachment’s log file and moves it to the \Failed subfolder.
BB2email.exe ignores the failed attachment and continues to import the current log file.
(Cnv2email.exe only) This parameter has no default value. It specifies the email address that gets written to the From: field in each EML email. The syntax is:
EML.From=<email address>
This parameter is only needed if you intend to run an Import Policy job in order to apply policy to these converted IM conversations before importing them into the CMS.
Typically, EML.from is set to an email address that corresponds to a custom CA DataMinder user account whose policy has been specifically tailored to process IM conversations. (When you run an Import Policy job, the policy engine uses this From: address to determine which policy to apply. Specifically, it maps the address to an existing CA DataMinder user account and applies outgoing email triggers in that user’s policy to the EML email.)
(BB2email.exe only) This parameter has no default value. It specifies an optional prefix that gets appended in front of the Subject to allow these emails to be easily identified. The syntax is:
EML.SubjectPrefix=Bloomberg EMAIL:
(BB2email.exe only) This parameter has no default value. It specifies a target SMTP email address. The syntax is:
EML.TargetMailbox=<email address>
This parameter is only needed if you intend to forward converted EML emails to an Exchange journal mailbox. If so, this address determines the target mailbox when ingesting the emails into Exchange.
(Cnv2email.exe only) This parameter has no default value. It specifies a target SMTP email address. The syntax is:
EML.To=<email address>
This parameter is only needed if you intend to forward converted EML emails to an Exchange journal mailbox. If so, this address determines the target mailbox when ingesting the emails into Exchange.
(BB2email.exe only) Defaults to No. This paramerter specifies whether to use corporate addresses for the sender and recipient instead of Bloomberg addresses. The syntax is:
EML.UseCorporateAddresses=<Yes or No>
If set to Yes, BB2email.exe uses corporate addresses, if available. If set to No, BB2email.exe uses the Bloomberg address.
If set to Yes but no corporate address is present, BB2email.exe uses the Bloomberg address.
This mandatory parameter has no default value. It specifies a fully-qualified path to the folder containing the source files that you want to convert. The syntax is:
File.Pathspec=<file path>
For Cnv2email.exe, this folder must contain the source CNV files that you want to convert, for example C:\IM_msgs. The folder must correspond to the IM Import output folder, that is, the folder specified by the Import Policy parameter DirFinalDest.
For BB2email.exe, this folder must contain the source XML dump files containing the Bloomberg emails that you want to convert, for example C:\BB_msgs.
Note: You only need to specify a path to the source folder. You do not need to append \*.cnv or \*.xml to the path. Cnv2email.exe will automatically detect CNV files, and BB2email.exe will automatically detect XML files, in the source folder.
Defaults to No. This parameter specifies whether to search for matching CNV or XML files in subfolders below the source folder specified by File.Pathspec. The syntax is:
File.IncludeSubdirs=Yes or No
Defaults to No. This parameter specifies whether to delete the source CNV or XML files after processing. The syntax is:
File.DeleteAfterImport=Yes, No, or Always
If this parameter is set to:
The source CNV or XML file is deleted after it has been successfully processed.
Source CNV or XML files are never deleted. If used with File.ContinuousInput=Yes, then the conversion job will fail to start, because you cannot use these parameters together in such a way.
Source CNV or XML files are always deleted, whether the conversion succeeds or not, and even if File.ContinuousInput=Yes.
Defaults to No. This parameter specifies whether Cnv2email.exe or BB2email.exe repeatedly scans for and converts CNV or XML files specified by File.Pathspec, or whether it shuts down after the input folders and files have been processed. The syntax is:
File.ContinuousInput=Yes or No
If this parameter is set to:
The source folder is continuously monitored and any CNV or XML files written to there are processed automatically. Typically:
Cnv2email.exe: Choose Yes if IM Import is also set to run continuously. That is, the Import Policy parameter RunOnce is set to No.
BB2email.exe: Choose Yes if Event Import is also set to run continuously. That is, the Event Import parameter File.ContinuousInput is set to Yes.
Note also:
After any CNV or XML files in the source folder have been processed, Cnv2email.exe and BB2email.exe quit.
(Cnv2email.exe only) This parameter has no default value. It specifies the target output folder for the EML files. The syntax is:
FileOut.Directory=<folder path>
Event Import or Import Policy can retrieve the EML files from this folder and import them directly into CA DataMinder.
Alternatively, if you want to automate integration with your Exchange-based archive solution, set this parameter to be your Exchange pickup folder. When the EML emails generated by Cnv2email.exe are written to the pickup folder, they are automatically processed by Exchange and forwarded to the mailbox specified by the EML.To parameter.
(BB2email.exe only) This parameter has no default value. It specifies the target output folder for the EML files. The syntax is:
FileOut.Folder=<folder path>
Event Import or Import Policy can retrieve the EML files from this folder and import them directly into CA DataMinder.
Alternatively, if you want to automate integration with your Exchange-based archive solution, set this parameter to be your Exchange pickup folder. When the EML emails generated by BB2email.exe are written to the pickup folder, they are automatically processed by Exchange and forwarded to the mailbox specified by the EML.TargetMailbox parameter.
This optional parameter specifies the maximum number of EML emails that can be written to each output subfolder. The syntax is:
FileOut.MaxFilesPerFolder=<number of emails>
If you include this parameter in your Cnv2email.ini or BB2email.ini configuration file, EML emails are written to a series of subfolders below the output folder specified by FileOut.Directory or FileOut.Folder. When the maximum number of EML emails has been written to the current subfolder, a new subfolder is created (numbered sequentially) and all subsequent EML emails are written to that folder until the maximum is reached once more, when the process repeats. The output subfolders are structured as follows:
1 Set by the FileOut.Directory or FileOut.Folder parameter
2 GUID generated by Cnv2email.exe or BB2email.exe
3 Subfolders numbered sequentially
Important! Do not use FileOut.MaxFilesPerFolder if Cnv2email.exe or BB2email.exe are configured to write EML files to an Exchange pickup folder (see FileOut.Folder or FileOut.Directory). EML files are not retrieved from subfolders below an Exchange pickup folder.
(Cnv2email.exe only) Defaults to 60 minutes. This ‘conversation-splitting’ parameter enables Cnv2email.exe to split IM conversations into separate chapters based on a regular timeout interval, starting from the first message in the first chapter of the conversation. The syntax is:
IM.ChapterTimeoutMins=<number of minutes>
For example, to create a new chapter after every two hours, set this parameter to:
IM.ChapterTimeoutMins=120
Note: A single configuration file can contain both the ‘timeout’ and ‘maximum message count’ conversation‑splitting parameters. Cnv2email.exe monitors both parameters simultaneously and creates a new chapter as soon as either meets its criteria.
(For Cnv2email.exe only) Defaults to 50 messages. This ‘conversation-splitting’ parameter enables Cnv2email.exe to split IM conversations into separate chapters based on the number of messages or comments submitted. The syntax is:
IM.ChapterMaxMessages=<number of messages>
For example, to create a new chapter after every 100 messages, set this parameter to:
IM.ChapterMaxMessages=100
Note: A single configuration file can contain both the ‘timeout’ and ‘maximum message count’ conversation‑splitting parameters. Cnv2email.exe monitors both parameters simultaneously and creates a new chapter as soon as either meets its criteria.
Defaults to 2. This determines the level of logging for the conversion process. For example, you can configure Cnv2email.exe or BB2email.exe to only log errors or important system messages. The syntax is:
Log.Level=<number>
The supported logging levels are:
0 No logging
1 Errors only
2 Errors and warnings
3 Errors and warnings, plus informational messages
4 Errors and warnings, plus informational messages, and trace
Note: Setting Log.Level=4 will cause the log file to grow extremely rapidly. This level of logging is provided for testing purposes only.
Log entries are written to Cnv2email_<date>.log or BB2email_<date>.log, where <date> is the date and time when the log file was created.
Defaults to 100,000. This specifies the maximum size (in bytes) for each log file. The syntax is:
Log.MaxSizeInBytes=<number of bytes>
When the current log file reaches its maximum size, Cnv2email.exe or BB2email.exe creates a new log file.
Defaults to 100. This specifies the maximum number of log files. The syntax is:
Log.MaxNumberFiles=<number of files>
When the maximum number of log files exist, and the most recent log file reaches the maximum log file size (see Log.MaxSizeInBytes), the oldest log file is deleted to enable a new one to be created.
|
Copyright © 2014 CA.
All rights reserved.
|
|