00194585-05_Installation_Manual_EDM_EN.pdf - 第57页
Installation Manual SIPLACE EDM Version 1.1 SP2 Issue 12/2006 Configuration is performed in the same way as for filter configuration (see 5.5 Filter configuration), but is carried out on the master. The configuration opt…
Installation Manual, SIPLACE EDM Version 1.1 SP2 Issue 12/2006
5.4.2.2 Configuring a list
After a distribution list has been selected, the email addresses of the recipients and the object types
or EDM events monitored by the list can be entered. All recipients on the distribution list receive
emails regarding notifications which refer to one of the selected object types. Only those
notifications are taken into account that originate from the line for which the distribution list was
created.
If the recipients are to be notified about "Forced Pull" events, this event must be selected in the
"EDM Events" tab.
5.4.2.3 General distribution list
The general distribution list reacts to notifications from all lines simultaneously, but is otherwise the
same as normal distribution lists.
5.4.3 Direct import of changed objects to the master database
It is possible to bypass the clearing pool and import objects changed on the lines directly into the
master database without the data preparation engineer inspecting the data.
Figure 21 Configuration of notifications to be imported directly
56 of 65
Installation Manual SIPLACE EDM Version 1.1 SP2 Issue 12/2006
Configuration is performed in the same way as for filter configuration (see 5.5 Filter configuration),
but is carried out on the master. The configuration options, however, only allow identification of the
data using the:
• object type
• name of the changed object. This restriction is implemented using regular expressions.
The configuration is stored in the file ClearingPoolImportFilterConfig.xml in the config directory.
5.4.4 Automatic rejection of the changes
It is possible to bypass the clearing pool and automatically reject objects changed on the lines
without the data preparation engineer inspecting the data. The changes are rejected without being
saved.
Figure 22 Configuration of notifications to be rejected automatically
Configuration is performed in the same way as for filter configuration (see 5.5 Filter configuration),
but is carried out on the master. The configuration options, however, only allow identification of the
data using the:
• object type
• name of the changed object. This restriction is implemented using regular expressions.
The configuration is stored in the file ClearingPoolRejectFilterConfig.xml in the config directory.
57 of 65
Installation Manual, SIPLACE EDM Version 1.1 SP2 Issue 12/2006
5.5 Filter configuration
It is not always desirable to inform the data preparation engineer about a data change on a line
server, for example when a reoptimization is being performed on the line. In this case, a number of
internal SIPLACE Pro objects (for example HeadSteps, i.e. individual process steps for a head) are
changed, and these changes would then need to be commented accordingly by the user and put in
the clearing pool, but they do not contain any information. Furthermore, there are customer
processes that imply a selection of change notifications, for example when just the pure product
data (board, components, etc.) are centrally administered and the process-specific data are
recreated on each line. In such a scenario, only changes to the product data are of interest, and
changes to the jobs and recipes are not.
The NotificationFilterConfig.xml file found in the configuration directory is intended to take these
circumstances into account. In the file, you specify the object types and objects for which no change
notifications are to be sent to the master server. The file only affects a line server.
Change notifications can be filtered using a combination of:
• object type
• subobject type
• individual properties of objects/subobjects
• type of change to the object
• name of the changed object. This restriction is implemented using regular expressions.
In the standard installation, a filter configuration is created that captures all irrelevant changes made
during optimization. Changes to NotificationFilterConfig.xml should only be made on the basis of
these default settings.
This part of the system is highly sensitive. In extreme cases, incorrect settings can lead to the loss
of important changes or, on the other hand, the data preparation engineer can be “bombarded” by
notifications regarding irrelevant changes.
58 of 65