(OpmConfig | pluginConfig)
For
OPM
without attachments, all default values are used if settings are missing from the configuration file. For
OPM
with attachments, the default values listed are optimum values. If optimum values are not provided for OPM
with attachments, then the default values for OPM
without attachments are used, which will cause functionality issues with the OPM
plug-in.XML tag |
Description |
Comments |
|---|---|---|
<subDomain> |
An email domain or sub-domain created and dedicated for OPM use. All outgoing alert email messages are sent from this domain, and all replies to go back this domain. Ensure the domain name does not include “@” sign. For example, <subDomain>alerts.athoc.com</subDomain> |
The DNS MX record needs be added to direct emails that target this sub-domain for the NDS server. |
<responseUrl> |
Indicates the base URL for link-based responses. |
— |
<outQueueThreads> |
The number of threads for processing and signing emails in the outgoing queue.
Default : 4Range : 1 – 20 |
This parameter affects the sent throughput especially when digital signing is turned on. |
<inQueueThreads> |
The number of threads for processing email responses in the incoming queue.
Default : 2Range : 1 – 20 |
This parameter can affect received throughput. |
<dbQueueName> |
The database queue name for incoming emails. The name must match the name specified on the NDS system.
Default : /delivery/opm/emailreply |
Change only when directed by BlackBerry AtHoc Customer Support or Implementation. |
<maxRelayErrorsPerSecAllowed> |
Specifies the threshold to determine if a relay has failed and need human attention.
Default : 10 errors per second |
Occasionally, OPM can experience connection drops, timeouts, and other errors (such as, SMTP 452) from relay servers, which are normal. However, frequent occurrences of these types of errors can indicate that a relay server is unstable or has failed. |
<validateReceivedEmailAddress> |
Species that on receiving emails, OPM validates the sender email address against the recipient email address.
Values :true : Validate email addresses.false (Default): Do not validate the email addresses. |
— |
<engineLaunchTimeout> |
The delay timeout, in seconds, that occurs when launching OpmEngine. At start up, the OPM plug-in launches the OpenEngine.exe and waits the specified number of seconds (default: 5 seconds). OPM tries connect to the OpmEngine. If OPM cannot connect, it retries again.
Default : 5 seconds |
— |
<reuseEngine> |
Specifies whether to reuse or re-launch an instance of OpmEngine, if it is already running.
Values :false (Default): Close the running engine and launch a new instance.true : Connect to the running engine. |
— |
<logTaskLifeCycle> |
Turn on task life cycle logging.
Default : True |
— |
<logPurgeInterval> |
Log purging interval (saving to database) in seconds.
Default : 1 |
— |
<logPurgeBatchSize> |
Purging batch size for records.
Default : 2000Range : 1000-2000 |
— |
<maxTasksPerExecution> |
The maximum number of delivery tasks that OPM can process in a single batch.
Default :
|
Change only when directed by BlackBerry AtHoc Customer Support or Implementation. |
<maxBacklot> |
The maximum number of outstanding delivery tasks that OPM process at any time.
Default :
|
Change only when directed by BlackBerry AtHoc Customer Support or Implementation. |
<minBatchSize> |
The minimum available batch size that OPM can offer to NDS before capacity is available.
Default :
|
Change only when directed by BlackBerry AtHoc Customer Support or Implementation. |
<counterCategery> |
The OPM performance counter category that is registered on Windows Performance Monitor. The category must match the category specified on the NDS system.
Default : AtHoc Delivery OPM |
Change only when directed by BlackBerry AtHoc Customer Support or Implementation. |
<selfTestInterval> |
The OPM performance self test is an in depth health check that runs periodically when OPM is idle. This parameter controls how often the self test runs.
Default : 30 secondsRange : 10 - 180 seconds |
Change only when directed by BlackBerry AtHoc Customer Support or Implementation. |
<selfTestEmail> |
A valid email address used by OPM when running the self test. OPM does not actually send the test email to this address. Instead, OPM uses a separate domain from the relay server to test the relay capability.
Default : test@athocdevo.com |
— |
< selfTestMode> |
The self test modes used for system health checks: Values :PingRelay (Default): Test only the connection to relay.Send : Connect and issue all SMTP commands except DATA.NoRelay : Turn off scheduled relay test. For OPM internal test, only. |
— |