These settings configure the local policy engine. Before running a policy engine, you need to specify, for example, how many policies it can hold at one time and how many events it can process simultaneously:
Settings to Determine Which User Policy Gets Applied
These settings determine how the policy engine handles events when it does not recognize the associated user or when user information is unavailable.
Important! For all of these settings, you must restart the policy engine any changes to take effect!
Policy engines use this setting to apply policy to e-mails sent from unrecognized users within your organization. For example, this can happen if a new recruit has an account in Active Directory but no CA DataMinder account has been created for them yet.
The setting specifies the name of a CA DataMinder user. It defaults to UnknownInternalSender; this account is created automatically when you install a CMS. The policy engine applies this user’s policy if the sender’s address is internal (that is, it matches an Internal E-mail Address Pattern—see below) but no corresponding CA DataMinder user account exists.
Policy engines use this setting to apply policy to external e-mails. That is, e-mails sent from someone outside your organization.
The setting specifies the name of a CA DataMinder user. It defaults to ExternalSender. This account is created automatically when you install a CMS. The policy engine applies this user’s policy if the sender’s address is external (that is, it does not match an Internal E-mail Address Pattern—see below).
Policy engines use this setting to detect e-mails sent by users within your organization.
This setting specifies a list of internal e-mail address patterns. Policy is only applied to the e-mail if the sender’s e-mail address matches an internal address pattern. Similarly, Address Book (MAPI) lookup operations are only performed for recipients with internal addresses.
This setting specifies the name of a CA DataMinder user. It defaults to DefaultFileUser. This user account is created automatically when you install a CMS.
Policy engines use this setting to apply policy to files if no other means are available to determine the policy participant. For example, if an FSA scanning job specifies a ser account that does not exist, the policy engine applies the Default Policy for Files to the scanned file.
The setting specifies the name of a CA DataMinder user. It defaults to DefaultClassificationUser. This account is created automatically when you install the CA DataMinder Content Classification Service (CCS).
Policy engines use this setting to classify documents forwarded to the CCS from external applications such as CA SiteMinder.
Other Settings
You can optionally define the maximum number of user policies that the policy engine can hold in its memory at one time. Because each policy requires a significant amount of memory, this setting can prevent excessive memory usage.
You can optionally define the maximum number of e-mails that can be processed simultaneously by a policy engine. This can prevent a performance slowdown on heavily loaded policy engines.
This setting is provided for diagnostic purposes only. It specifies whether the policy engine can retrieve e-mail address details and distribution list members from an LDAP directory.
Important! We strongly recommend that you do not change this setting!
This setting defines the frequency of policy timeouts. That is, the amount of time a policy engine retains a policy that has not been used. After this period of time, the policy is unloaded.
This setting is designed to maintain processing capacity. It specifies how long a thread must be inactive before the policy engine considers the thread to have stalled and creates a new processing thread.
This setting enables policy engines to detect 'embedded content' e-mails (that is, EML e-mails contained embedded IM conversations, Bloomberg messages or other communications such as eFaxes). It enables policy engines to set the event type as 'embedded IM', 'Bloomberg' or 'eFax' and, for IM conversations, to extract or set the IM network.
This setting defines the frequency of policy timeouts. That is, the amount of time a policy engine retains a policy that has not been used. After this period of time, the policy is unloaded.
This setting is designed to maintain processing capacity. It specifies how long a thread must be inactive before the policy engine considers the thread to have stalled and creates a new processing thread.
|
Copyright © 2014 CA.
All rights reserved.
|
|