00197193-01_IM_SIPLACE_EDM_2_0_EN.pdf - 第30页
EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition Forced pull mode For this type of data transfer, the time after wh ich the data pre paration enginee r will be notified that no new data has been pull ed for the lin…
EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition
5.3.5.1 General settings
Figure 5-1: General settings for application templates
The general settings include:
● Type of data transfer. Currently, you can only select Pull Mode or Forced Pull Mode.
● Starting Point specifies the object type for which this template can be valid. A template can
only be valid for one object type at a time. However, it is possible to define more than one
template for an object type.
● Objects found in the Default folder and all its subfolders can be subsequently specified by the
line engineer for pulling and pushing from the master.
● An optional comment.
Pull mode
No additional settings can be specified for this type of data transfer between the Master Server and
Line Servers.
29
EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition
Forced pull mode
For this type of data transfer, the time after which the data preparation engineer will be notified that
no new data has been pulled for the line must be specified via Configure. The time is specified in
hours.
Figure 5-2: Forced pull mode configuration
5.3.5.2 Overwriting
Figure 5-3: Settings for overwriting object types
You can select the object types to be overwritten when the data is imported to the line here.
30
EDM V2.0 / Installation Manual Ausgabe 04/2012 Edition
5.3.5.3 Line server
Figure 5-4: Line servers
Here you specify the list of Line Servers for which the application template has to be applied.
● (A list of) Line alias name(s) (as defined in the Lines Settings tab, cf. section 5.3.2) make the
template visible to the specified EDM line(s)
● [All] (the default value) makes EDM present the template to all line servers
5.3.6 Notifications/Filtering…
CAUTION
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" with notifications regarding irrelevant changes.
The Notification Filter section (5.3.6.1) describes the filter system, which determines what
notifications are not sent to the EDM Master. As default behavior, incoming change notifications on
the EDM Master are collected in the clearing pool. A change notification will not be aggregated in
the clearing pool, if it
● is imported directly into the master database as described in section 5.3.6.2, Direct import of
changed objects to the master database.
● is rejected automatically as described in section 5.3.6.3, Automatic rejection of the changes.
● has conflicting settings for “direct import” and “auto-reject” settings
An email notification is sent for all the alternatives as defined in 5.3.6.4, Email configuration.
31