00194585-05_Installation_Manual_EDM_EN.pdf - 第43页
Installation Manual SIPLACE EDM Version 1.1 SP2 Issue 12/2006 • the actual process of data flow – the dynamic part – between the central server (EDM master server) and the local clients (EDM line servers), and • the type…
Installation Manual, SIPLACE EDM Version 1.1 SP2 Issue 12/2006
this value set to “false” and use EDM blob handling.
If this option is activated, EDM blob handling must be deactivated with the entry
<add key="UseBlobExtension" value="false"/>.
CompatibilityMode (false)
If true: Allows restricted operation of the EDM line server together with an EDM
master server.
Caution: This mode must not be used for long-term mixed operation, but only
for gradual line-by-line upgrading of the EDM system (see 4.4 Upgrading from
EDM 1.0 to EDM 1.1).
doNotUseDefaultCategoryInCommentDialog (false)
doNotUseDefaultUserInCommentDialog (false)
doNotUseDefaultCommentInCommentDialog (false)
If true: Does not enter default values into the relevant field (category, user
name or comment) when the dialog box for entering a comment for a
notification is opened. This means that the contents must be entered manually
each time.
forceUserEntryInCommentDialog (false)
forceCommentEntryInCommentDialog (false)
forceCategoryEntryInCommentDialog (false)
If true: Forces the user to make an entry in the relevant field (category, user
name or comment) in the dialog box for entering a comment for a notification.
Empty entries are no longer accepted.
EdeUserControlOverride
This class name specifies the control used in place of the Extended Difference
Editor.
5.2.4 Configuration of the VDM blob functions
To use the VDM blob functions, the names of the SPI lines assigned to each line server must be entered
in the line server’s configuration file (see 5.2.3.24 Assigned SPI lines). If this section is left empty, blobs
are accepted for all lines.
5.3 Configuration of the workflow
The production process design is very differently from customer to customer, which means the data
storage process also varies. Two aspects in particular stand out in this regard:
42 of 65
Installation Manual SIPLACE EDM Version 1.1 SP2 Issue 12/2006
• the actual process of data flow – the dynamic part – between the central server (EDM master
server) and the local clients (EDM line servers), and
• the type and amount of data to be transferred – the static part.
Both parts of the process may differ, though, in customer processes. This section deals with the dynamic
part, the actual control of the flow of data. The configuration of the static part – the application templates
– is discussed in 5.4.1 Application templates.
NOTE:
The workflow only needs to be configured if the standard values don’t work in your
environment..
5.3.1 Theory …
The production process of the customer is depicted in a workflow with the help of a finite state
machine. A finite state machine is a concept from theoretical computer science. It helps to know a
little terminology to understand this concept.
A finite state machine generally consists of:
• A set of states. In the following, this set is called Q.
• There is exactly one start state belonging to Q.
• A subset of Q that contains the valid end states.
• A subset of Q that contains the error states.
• A set of Events
1
• A set of state transitions that cause a state q
1
to go to state q
2
when a certain event occurs. A
maximum of one transition can be defined for each state/event pair.
5.3.2 … and application
5.3.2.1 Syntax and options
The theory presented in the previous section must now be implemented in a manageable form for
actual use. This is done in the client workflow configuration file (see also 5.2.3.21 Client workflow
configuration). This file is in XML format. The following text deals with the contents of this file and
how they relate to the theory.
1
This set of events is termed the “input alphabet” in theoretical computer science. For those of you who are
interested!
43 of 65
Installation Manual, SIPLACE EDM Version 1.1 SP2 Issue 12/2006
When starting, you will first need to declare all states, events and transitions. This is necessary so
that the workflow engine operating on the configuration file can more easily verify the finite state
machine.
First, we define the start state:
<state name="clientIdle" isStartState="true" />
In the following state declarations, isStartState=“true” is not allowed to appear any more because a
finite state machine has exactly one start state.
A “normal” state is declared:
<state name="selectObjects" />
This state is marked as an end state:
<state name="done" isEndState="true" />
Error states are declared as follows:
<state name="timedOut" isErrorState="true" />
A state can be an error state and an end state at the same time:
<state name="failed" isErrorState="true" isEndState="true" />
The names of the states must be unique. Next, the events that the workflow engine can react to are
declared in the configuration file:
<event name="pullData" />
The names of the events also need to be unique because they are referenced in the definitions of
the transitions just like the states.
The transitions are the heart of the workflow definition. They are a kind of “building block” that can
be used to model a customer workflow.
44 of 65