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

Installation Manu al SIPLACE Engine ering Data Manag er (EDM) Version 1 .9 02/2011 Edition 61 / 65 • individual prop erties of obj ects /subobjects • type of change to the objec t • name of the changed objec t. This rest…

100%1 / 65
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
Installation Manual SIPLACE Engineering Data Manager (EDM) Version 1.9 02/2011 Edition
61 / 65
• 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.
Figure 23 Configuration of the notification filter
The filter configuration comprises a set of ORed rules (see Figure 23 Configuration of the notification filter).
This means that as soon as at least one of the defined conditions applies to the incoming notification, the
notification is rejected (no comment dialog box is opened and the notification is not transferred to the
Master Server). A defined rule is enabled if the associated box is checked.
Installation Manual SIPLACE Engineering Data Manager (EDM) Version 1.9 Issue 02/2009
62
Figure 24 Configuration of a single rule
Every condition checks a subset of the properties of the notification. This set is ANDed, i.e. only when all
the properties checked by the condition have the values specified in the condition is the notification
rejected by this condition.
The following properties can be assessed by a condition:
• Name (regular expression)
• Object type
• Subobject type
• Property of object or subobject
• Deletion of subobjects of a particular object (association delete)
• Type of notification
There is a separate tab for each of these properties. If no value is selected in any of the tabs, this property
is not checked. If one or more values are selected, the value of the property in the notification must match
one of the values for the notification to be filtered.
5.6 Handling incoming change notifications
5.6.1 Saving the changed objects in the Clearing Pool
This is the default handling method for incoming change notifications. It is used for changes to all objects
which