00196806-01_IM_EDM_1.9_EN.pdf - 第59页

Installation Manu al SIPLACE Engine ering Data Manag er (EDM) Version 1 .9 02/2011 Edition 59 / 65 If the recipients are to be n otified about "Forced Pu ll" events, th is event m ust be selected in the "E…

100%1 / 65
Installation Manual SIPLACE Engineering Data Manager (EDM) Version 1.9 Issue 02/2009
58
Figure 20 Configuration of email distribution lists
The storage location of the configuration file should be specified for informational purposes and must not
be changed. Direct manipulation of the configuration file should also be avoided.
5.4.2.1 Setting up a new list
A line must be selected before a new distribution list can be added. A name and a comment are assigned
to each new list.
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.
Installation Manual SIPLACE Engineering Data Manager (EDM) Version 1.9 02/2011 Edition
59 / 65
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
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 folder.
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.
Installation Manual SIPLACE Engineering Data Manager (EDM) Version 1.9 Issue 02/2009
60
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 folder.
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 folder 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