00197458-01_UG_EDM_V2.2_en.pdf - 第66页

EDM V2.2 / U ser Guid e Ausgabe 10/2013 E dition 66 6.2.3 Comment Categorie s All entries consist of a valu e and an opt ional index (used to determ ine the disp lay order) A comm ent categor y entry has to fulfil thes e…

100%1 / 94
EDM V2.2 / User Guide Ausgabe 10/2013 Edition
65
6.2.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.2.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 its 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 its 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.2 / User Guide Ausgabe 10/2013 Edition
66
6.2.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. Its 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.2.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>
EDM V2.2 / User Guide Ausgabe 10/2013 Edition
67
6.2.5 Role Configuration
The Role Configuration consists of a "<roles>" section containing a list of "<role>" entries. Each
entry has the following attributes:
id: Id of the role
line: Pattern to match against the 'Line-Alias' (or the Host-Name if no alias is configured)
application: Pattern to match against the name of the EDM Application (e.g. EdmClient))
spiUser: Pattern to match against the SIPLACE user name (currently always "System" as EDM
does not support any User Management).
windowsUser: Pattern to match against the Windows user name running the EDM Application
(Note: the EDM service normally runs as "SYSTEM" user).
lineServerRole: Pattern to match against the "server type" of the EDM Application
(e.g. "LINE")
edmVersion: Pattern to match against the EDM version
pattern: Specified the pattern matching algorithm to use. Supported values:
"regex" (or "regularexpression") to use Regular-Expressions.
"" (or omitting the attribute) to use simple case insensitive string comparison.
index: used to define the priority of the roles (highest index => lowest priority).
The following rules apply:
1. The "id" of each entry must be unique.
2. Currently the recognized pattern value is "regex" (otherwise a case insensitive string
comparison is used).
3. The "pattern" attribute changes the comparison of all values.
4. The first match (by index) is used. This implies the "default" configuration has to have the
highest "index" otherwise all following entries are ignored.
5. If no matching entry is found the standard EDM Configuration
[ConfigDir]\EdmConfiguration.xml will be used.
6. The referenced configuration file has to exist and has to be a valid EdmConfigurationSet
(Otherwise the default EDM configuration file (see above) will be used - which could lead to
unexpected behaviour).
7. The path of the configuration file is relative to the EDM configuration directory (not to the
location of the role configuration file).
Sample Role-Config file:
<configuration>
<configurationInfo name=" Role mapping" version="2.0.0.0" comment="Sample"
type="Siemens.SiplacePro.EDM.Common.Configuration.RoleConfig" />
<roles>
<!-- Role using regular expression to match the line server name -->
<role id="NPI"
line="NPI-Line_.*"
application=""
configuration="Edm-NPI-Configuration.xml"
spiUser=""
windowsUser="EdmNpi"
lineServerRole=""
pattern="regex"
index="0" />
<!—- Fallback configuration for all other lines -->
<role id="Default" application="" line="" spiUser="" windowsUser=""
configuration="EdmConfiguration.xml" index="1" />
</roles>
</configuration>