InstallationManual_EDM_1.7_en.pdf - 第10页
Installation Manual SIPLACE EDM 1.7 Edition05/2009 3.2 Forced pull mode In order to have some influence on this situation, SIPLACE Pro provides the “forced pull mode”. This mode allows for the specification of a maximu m…
Installation Manual SIPLACE EDM 1.7 Edition 05/2009
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, 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 66
Installation Manual SIPLACE EDM 1.7 Edition05/2009
3.2 Forced pull mode
In order to have some influence on this situation, SIPLACE Pro provides the “forced pull mode”. This
mode allows for the specification of a maximum time period between two downloads. This should
ensure that the data on the lines is never older than the prescribed time period. If no data is
downloaded from the master server during the time period defined, then the data preparation
engineer is informed of this via a SIPLACE EDM notification and can initiate organizational activities
to ensure the data is downloaded and up-to-date.
Installation Manual SIPLACE EDM 1.7 Edition 05/2009
4 Installation
4.1 Requirements
4.1.1 EDM master server
Minimum Requirements
Hardware Intel Pentium 4, 3 GHz
2 GB RAM
1 GB hard disk space
Network connection
Operating system Windows 2003 Server (SP2), Windows XP Professional SP3 or Windows
Vista SP1
MSMQ runtime must be installed
SIPLACE Pro 7.0 server installation
Microsoft SQL Server Preferred: SQL Server 2008, SQL Server 2008 Express Edition
Supported: SQL2000 SP 4, MSDE 2000 SP4, SQL Server 2005 SP3, SQL
Server 2005 Express SP3
.NET Framework Microsoft .NET 3.5 SP 1
Table 1 EDM master server software requirements
Caution:
When updating to the SQL Server 2005 (Express), the service jobs which are created
manually, can be lost.
11 of 66