00197193-02_IM_SIPLACE_EDM_2.1_EN - 第47页

EDM V2.1 / I nstallat ion Ma nual Ausgabe 11/2012 E dition 47 6.3.2 Machine Configura tion The Machin e Conf iguration consists of a “< machines >” sec tion containi ng a list of “ < host > ” entries. Eac h e…

100%1 / 73
EDM V2.1 / Installation Manual Ausgabe 11/2012 Edition
46
6.3.1 Configuration Sets
An EDM Configuration Set has a configuration type of
Siemens.SiplacePro.EDM.Common.Configuration.ConfigurationSet” and contains a
list of configuration files associated with the configuration set. EDM uses 15 standard entries,
custom configuration files (e.g. used in workflows) may be added as needed. All files referenced in
the configuration set must be stored in the EDM configuration directory (or any sub-folder except
“_cache”). The default configuration set (used by the configuration server or in local mode) is
named “EdmConfiguration.xml” and has to reside in the EDM Configuration folder.
Name Default Type
1
MachineConfig
global\MachineConfig.xml .Common.Configuration.MachineConfig
RoleConfig
global\RoleConfig.xml .Common.Configuration.RoleConfig
SystemConfig
default\SystemConfig.xml .Common.Configuration.SystemConfig
CommentConfig
default\CommentConfig.xml .Common.Configuration.CommentConfig
CustomConfig
default\CustomConfig.xml .Common.Configuration.CustomConfig
RequestConfig
default\RequestConfig.xml .Common.Configuration.RequestConfig
DataTransferConfig
default\DataTransferConfig.xml ....DataTransferExtension.PushModeConfig
Rules
default\NotificationFilterConfig.xml ...Common.NotificationFilterConfig
Rules_DirectImport
default\ClearingPoolImportFilterConfig.xml ....Common.NotificationFilterConfig
Rules_AutoReject
default\ClearingPoolRejectFilterConfig.xml ….Common.NotificationFilterConfig
EmailFilter
default\EmailNotificationFilterConfig.xml ….Common.NotificationFilterConfig
EmailSettings
default\EmailConfig.xml (EDM EmailConfig)
DisplayConversionConfig
default\DisplayConversionConfig.xml (Generic XML)
Log4Net
default\log4net_debug.config (Log4Net)
NotificationDisplay notifications\NotificationDisplayTemplates.r
esx
EDM User Language customized messages
ClientWorkflow
workflows\clientWorkflow.xml (EDM Workflow)
Table 6-8: Standard EDM Configuration Set entries
1
“…”: refers to „Siemens.SiplacePro.EDM“
NOTICE
The paths to the configuration files are relative to the location of the configuration set!
EDM V2.1 / Installation Manual Ausgabe 11/2012 Edition
47
6.3.2 Machine Configuration
The Machine Configuration consists of a “<machines>” section containing a list of<host>
entries. Each entry has the following attributes:
id (DNS-Name),
alias (EDM-Display-Name)
serverType (the type of the EDM installation, generally “LINE”)
xmlHandling Flag
(See 6.3.6.29 for a description of the possible values. The default is “-1” which means
ByServerType” and results in 1” for Lines and “9” for the Master)
Each host entry may also contain a list of <spiLine> child elements with the ‘path’ attribute
specifying the SIPLACE Pro path of the associated Line. The special values “[ALL]” and “[NONE]”
may also be used to indicate, that a host shall be assigned to all or no line. If no entry is found,
EDM assumes, that it is assigned to all lines found in the local SIPLACE Pro installation.
Please remember, that an EDM Line Alias must meet the following criteria:
1. It must be unique
2. It must not be equal to the “id” of another entry (it may be equal to it’s own id though)
3. It may not be empty or consist of only whitespace characters (spaces tabs etc.)
4. It should not contain new lines.
The “id” (hostname) has to fulfil these criteria:
1. It must be unique
2. It must not be equal to the “alias” of another entry (it may be equal to it’s own alias though)
3. It may not be empty or consist of only whitespace characters (spaces tabs etc.)
4. It cannot contain new lines.
5. Only hostnames are allowed (EDM will not resolve IP-Addresses)
A sample Machine-Config file:
<configuration>
<configurationInfo name="Demo" version="2.0.0.0" comment="Sample Configuration"
type="Siemens.SiplacePro.EDM.Common.Configuration.MachineConfig"/>
<machines>
<host id="PC4711" alias="Line_01" serverType="LINE" xmlHandling="-1">
<spiLine path="System\Line1_A" />
<spiLine path="System\Line1_B" />
</host>
</machines>
</configuration>
EDM V2.1 / Installation Manual Ausgabe 11/2012 Edition
48
6.3.3 Comment Categories
All entries consist of a value and an optional index (used to determine the display order)
A comment category entry has to fulfil these criteria:
1. It must be unique
2. It should not be empty or consist of only whitespace characters (spaces tabs etc.)
3. It’s value should not contain new lines.
A sample Comment-Config file:
<configuration>
<configurationInfo name="Comment categories" comment="Sample" version="2.0.0.0"
type="Siemens.SiplacePro.EDM.Common.Configuration.CommentConfig" />
<commentCategories>
<category value="Production" index="0" />
<category value="Important change" index="1" />
<category value="Test" index="2" />
<category value="Filter" index="3" />
</commentCategories>
</configuration>
6.3.4 Request Configuration
All entries consist of a name (key) and a value:
<add key="[request]" value="[Class]"/>
There is one entry for each of the services provided by the Master Server. These settings should
only be changed by the developer since they depend on the implementation of the Master Server,
and improper settings can affect the integrity and operation of the system as a whole.
A request command entry has to fulfil these criteria:
1. The key must be unique
2. The key cannot be empty or consist of only whitespace characters (spaces tabs etc.)
3. The key cannot contain new lines
4. The value should point to an existing class
5. The value has to point to a class that can be loaded by EDM (.Net Framework 4.0; x86)
Sample excerpt from a Request-Config file:
<configuration>
<configurationInfo name="Request Sample" comment="Demo" version="2.0.0.0"
type="Siemens.SiplacePro.EDM.Common.Configuration.RequestConfig" />
<requestCommandConfig>
<add key="objectData"
value="Siemens.SiplacePro.EDM.DataExchange.Commands.RequestDataCommand,DataExchange" />
</requestCommandConfig>
<!-- ... -->
</configuration>