00194585-05_Installation_Manual_EDM_EN.pdf - 第8页
Installation Manual, SIPLACE EDM Version 1.1 SP2 Issue 12/2006 It also allows you to enter comments for new notif ications. The EDM Tool is installed on the line server. Comments can also be entered on a computer other t…
Installation Manual SIPLACE EDM Version 1.1 SP2 Issue 12/2006
2.5 EDM notifications
The EDM notifications subsystem converts the change notifications received from the lines into a
readable form and distributes these to the appropriate locations. The type of messages sent and the
recipients of the messages can be configured. This will be explained in more detail later on (see
5.4
EDM configuration and 5.5 Filter configuration).
2.6 EDM configuration
The EDM configuration is the central location for configuring the customized settings. There you will
find the functionality to
• create and administer application templates
• configure email notifications on incoming notifications
The configuration options and the user interface are described in section
5.4.1 EDM configuration
Application templates and 5.4.2 Email configuration.
2.7 EDM filter configuration
EDM filter configuration allows you to configure the EDM notifications. The configuration options and
the user interface are described in section 5.5, Filter configuration.
2.8 EDM line server
The EDM line service is the counterpart to the EDM master service. It monitors the changes made
by users to the local SIPLACE Pro database, documents the changes and sends them to the master
service for entry in the clearing pool.
2.9 EDM Tool
The EDM Tool is a utility under which the master server and line server run and which monitors the
status of the EDM services (master service and line service) and the integrity of the EDM
configuration files.
7 of 65
Installation Manual, SIPLACE EDM Version 1.1 SP2 Issue 12/2006
It also allows you to enter comments for new notifications. The EDM Tool is installed on the line
server.
Comments can also be entered on a computer other than the line server. To do this, the EDM Tool
must be installed on this computer and an entry in the configuration file of the line server must be
adapted accordingly (5.2.3.14 EDM tool endpoint).
8 of 65
Installation Manual SIPLACE EDM Version 1.1 SP2 Issue 12/2006
3 Data transfer
The main motivation and goal behind the development of SIPLACE EDM was to make it possible to
store SIPLACE Pro data on a decentralized basis. One requirement to fulfill to reach this goal is to
guarantee an efficient, selective data transfer from the master server to the line servers. Changes
made at the local level are integrated into the central database so that it contains data that is valid –
i.e. as up-to-date as possible – throughout production.
Technically speaking, both directions of data transfer are based on the SIPLACE Pro XML import
and export data model already known from SIPLACE Pro Desk. The transfer can also be initiated
manually there.
This technical solution must be integrated into a process-based solution for the data transfer that
controls and monitors precisely this transfer. This process-based solution, as implemented in
SIPLACE Pro EDM V1.0, provides two ways to control and monitor the flow of data:
• The Pull Mode and
• The Forced Pull Mode.
3.1 Pull mode
On the one hand, the pull mode represents a stand-alone process controller for the data transfer,
and on the other hand, it serves as the basis for the forced pull mode. For this reason, this section
will only discuss the aspects common to both modes, and the following section will only deal with the
aspects specific to the forced pull mode.
The basic idea behind the forced pull mode as well as the “simple” pull mode is that the line
engineer is basically responsible for the production data and for the decision regarding which data
applies to the line since the line engineer is responsible for ensuring that the line produces.
To do this, the line engineer manually starts the “pull mode” via the SIPLACE EDM client. He selects
the data to be transferred. The data preparation engineer, though, is provided with configuration
options he can use to actively intervene in the process (the application templates, see also 5.4). This
control capability arises from the fact that the data preparation engineer specifies which object types
are to be overwritten during the download to the line. In general, the following can be stated: the
data preparation engineer is responsible for the correctness of the object types overwritten during
the download, and the line engineer is responsible for the object types that are not overwritten.
The data preparation engineer, however, has no influence on whether or not the line engineer pulls
new data from the master server, nor when this data is pulled.
9 of 65