semi合集-English.pdf - 第3155页

SEMI E125.1-0305 © SEMI 2005 9 6.5 Translating UML to WSDL 6.5.1 In general, UML interface classes defined in the abstract specification are translated into WSDL as portType definitions, and each portType defi nition ha …

100%1 / 7923
SEMI E125.1-0305 © SEMI 2005 8
Figure 1
XML Schema Example Diagram
<xsd:element name="Parent">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Child1"/>
<xsd:complexType>
<xsd:sequence minOccurs="0">
<xsd:element name="Child1a"/>
<xsd:element name="Child1b" maxOccurs="unbounded"/>
<xsd:element name="Child1c" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="Child2">
<xsd:complexType>
<xsd:choice maxOccurs="2">
<xsd:element name="Child2a"/>
<xsd:element name="Child2b"/>
<xsd:element name="Child2c"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
<xsd:element name="Child3">
<xsd:complexType>
<xsd:all>
<xsd:element name="Child3a"/>
<xsd:element name="Child3b"/>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Figure 2
XML for Sample
SEMI E125.1-0305 © SEMI 2005 9
6.5 Translating UML to WSDL
6.5.1 In general, UML interface classes defined in the abstract specification are translated into WSDL as portType
definitions, and each portType definition has a corresponding WSDL binding definition. The following tables show
the convention used for documenting the WSDL port type and binding definitions for a given UML interface class.
Table 5 Example Interface WSDL Port Type Table
Class Name <UML interface name from abstract specification>
WSDL Port Type Name <port type name used in WSDL>
SEMI E125 Operation
WSDL Operation
<operation name from UML interface> <WSDL port type operation name>
Table 6 Example Interface WSDL Binding Table
SEMI E125 Class Name <UML interface name from abstract specification>
WSDL Binding Name <binding name used in WSDL>
SOAP Binding Style <RPC or document>
SOAP Transport <transport identifying URI>
6.5.2 Each operation defined for a given UML interface class has a corresponding operation definition and binding.
Operations are described using a table format illustrated by Table 7 and Table 8.
Table 7 Example Operation Binding Table
SOAPAction
<the SOAPAction HTTP header value to be used for this
operation>
Input Headers (WSDL Message, Required)
<the name of the WSDL message providing input headers, and
whether or not the headers are required>
Output Headers (WSDL Message, Required)
<the name of the WSDL message providing output headers,
and whether or not the headers are required>
Table 8 Example PortType Operation Table
Input Message Name <WSDL message name used as input for the WSDL port type operation>
Output Message Name <WSDL message name used as output for the WSDL port type operation>
7 Mapping of SEMI E125 UML to XML Schema and WSDL
7.1 WSDL Organization
7.1.1 Each interface definition in SEMI E125 is mapped to a WSDL portType and binding definition. WSDL
portType definitions are named after the interface and its operations as they appear in SEMI E125. WSDL binding
definitions for each portType are used to specify the SOAP 1.1 envelope contents for each operation, and to define
the corresponding XML encoding styles and HTTP header usage. All SEMI E125 WSDL interfaces use
document/literal encoding, with the complete SOAP header and body contents defined in XML Schema file(s) via
global element definitions.
7.1.2 Figure 1 shows the relationship between the WSDL binding and portType definitions and the XML Schema
types used for each interface. The portType definition imports XML Schema type definitions used in each operation
via the XML Schema “import” statement. The WSDL binding definition imports the portType definition via the
WSDL “import” statement. Figure 2 shows the specific XML Schema and WSDL files defined for SEMI E125.
SEMI E125.1-0305 © SEMI 2005 10
Figure 3
XML Schema and WSDL File Organization
Figure 4
WSDL and XML Schema Files for SEMI E125
7.2 EquipmentMetadataManager
7.2.1 Application of SEMI E132 Sessions
7.2.1.1 This section is provisional, pending the approval of SEMI E132.1 and the SEMI E138.
7.2.1.2 Although no special privileges are specified by SEMI E125 in order to access equipment metadata,
SEMI E125 information is proprietary to the equipment supplier, and should be protected against unauthorized
access within the factory.
7.2.1.3 For this reason, all operations defined by the SEMI E125 EquipmentMetadataManager interface can be
exchanged using the HTTPS transport (HTTP 1.1 over SSL 3.0) by enabling SSL authentication as specified in
SEMI E132.1. Once enabled via SEMI E132.1, the equipment shall require mutual client-server SSL authentication
for all SEMI E125 operations supported by the equipment, and the equipment shall not provide access to any
operations except via the HTTPS transport.
7.2.2 There may be some integration, development, and/or test environments in which it is not practical or feasible
to install equipment and/or client certificates in order to communicate with the equipment. As a practical
consideration for such environments only, the equipment shall support the ability of the user to disable SSL
authentication for the SEMI E125 EquipmentMetadataManager interface, using the equipment configuration
specified by SEMI E132.1. Users should be aware that disabling SSL authentication opens up complete unrestricted
access to SEMI E125 data for any application with network access to the equipment.
7.2.2.1 Regardless of whether or not SSL authentication is enabled, the equipment shall reject all requests from
clients that do not provide a valid SEMI E132 session identifier in the SOAP envelope header provided with the
request. The SEMI E132 session identifier shall be provided via the SEMI E132 Header element, as specified by
SEMI E132.1. If a client does not provide a recognized session identifier, the equipment shall immediately reject
the request using the SEMI Common Error data type, with an error code of ‘6005’ and a source of ‘urn:semi-
org:E132’ as specified in SEMI E132.1. The equipment shall perform no other processing of a SEMI E125 request
if the request is found to include an invalid SEMI E132 session identifier, or if no session identifier is provided.
7.2.3 Use of Common Error Type
7.2.3.1 This section is provisional, pending the approval of SEMI E138.