semi合集-English.pdf - 第3157页

SEMI E125.1-0305 © SEMI 2005 11 7.2.3.2 Th is specification does not define any SEMI E125-speci fic error codes, but reserves the comm on error type “source” name of “urn:sem i- org:E125” for future use. 7.2.4 XML Schema…

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.

SEMI E125.1-0305 © SEMI 2005 11

7.2.3.2 This specification does not define any SEMI E125-specific error codes, but reserves the common error type

“source” name of “urn:semi-org:E125” for future use.

7.2.4 XML Schema and WSDL Files

7.2.4.1 This section is provisional, pending the approval of SEMI E132.1 and SEMI E120.1.

7.2.4.2 The XML Schema and WSDL defined by this specification for the EquipmentMetadataManager interface is

contained in the following documents:

Table 9 XML Schema

File Name E125-1-V0305-Schema.xsd

Target Namespace urn:semi-org:xsd.E125-1.V0305.esd

Imported/Referenced

Namespaces

urn:semi-org:xsd.E120-1.V1104.CommonEquipmentModel

urn:semi-org:xsd.CommonComponents.V0305.ccs

http://www.w3.org/2001/XMLSchema

Description

This file defines all of the E125 data types and elements used by both the

EquipmentMetadataManager and MetadataClient interfaces.

Table 10 EquipmentMetadataManager PortType Definitions

File Name E125-1-V0305-EqpMetadataMgr-PortType.wsdl

Target Namespace urn:semi-org:ws.E125-1.V0305.esdMetaEqp-portType

Imported/Referenced

Namespaces

urn:semi-org:xsd.E132-1.V0305.auth

urn:semi-org:xsd.E125-1.V0305.esd

http://schemas.xmlsoap.org/wsdl/

http://www.w3.org/2001/XMLSchema

Description

This file defines all of the input/output messages and operations for the

EquipmentMetadataManager interface, based on the data types defined in the SEMI

E125 XML Schema.

Table 11 EquipmentMetadataManager Binding Definitions

File Name E125-1-V0305-EqpMetadataMgr-Binding.wsdl

Target Namespace urn:semi-org:ws.E125-1.V0305.esdMetaEqp-binding

Imported/Referenced

Namespaces

urn:semi-org:ws.E125-1.V0305.esdMetaEqp-portType

http://schemas.xmlsoap.org/wsdl/soap/

http://schemas.xmlsoap.org/wsdl/

Description

This file binds the abstract portType definition to HTTP and SOAP, specifying

required SOAP and HTTP headers for each operation and the XML encoding style.

7.2.4.3 These documents are a part of this specification and should accompany this document. The contents of

these documents constitute the core part of this specification.

7.2.4.4 E125-1-V0305-Schema.xsd imports types from the SEMI E120.1 Common Equipment Model XML

Schema namespace

7.2.5 WSDL Port Type Overview

7.2.5.1 The EquipmentMetadataManager WSDL portType definition organizes the SEMI E125.1 XML Schema

data types into a collection of named operations with inputs and outputs that correspond to the UML operations that

are defined for the EquipmentMetadataManager interface in SEMI E125. The WSDL portType itself is named after

the SEMI E125 interface, and each WSDL portType operation is named after the corresponding UML operation

defined for the interface. Each WSDL operation consists of two WSDL message definitions corresponding to the

input and output (request and response) for the UML operation defined in SEMI E125. Figure 3 illustrates the

relationship between the SEMI E125 UML interface and the WSDL portType definition; Table 12 describes this in

tabular form. The WSDL message and operation definitions are described in ¶¶7.2.8 through 7.2.16 .

Figure 5

Mapping the EquipmentMetadataManager to a WSDL portType

Table 12 EquipmentMetadataManager Port Type

SEMI E125 Class Name EquipmentMetadataManager

WSDL Port Type Name EquipmentMetadataManager

SEMI E125 Operation



WSDL Operation

GetUnits  GetUnits

GetTypeDefinitions  GetTypeDefinitions

GetStateMachines  GetStateMachines

GetSEMIObjTypes  GetSEMIObjTypes

GetExceptions  GetExceptions

GetEquipmentStructure  GetEquipmentStructure

GetEquipmentNodeDescriptions  GetEquipmentNodeDescriptions

GetLatestRevision  GetLatestRevision

NotifyOnRevisions  NotifyOnRevisions

7.2.6 WSDL Binding Overview

7.2.6.1 The WSDL EquipmentMetadataManager binding definition specifies a message and transport protocol to

use for a given portType (SOAP and HTTP for SEMI E125.1), the interface style used (document style for

SEMI E125.1). These setting are shown in Table 13. For each WSDL portType operation, the binding defines any

SOAP headers used and whether or not they are required, the HTTP SOAPAction header value to use for that

operation, and the XML encoding to use (literal). The binding definitions for each portType operation are described

in ¶¶7.2.8 through 7.2.16.

Table 13 EquipmentMetadataManager Binding

E125 Class Name EquipmentMetadataManager

WSDL Binding Name EquipmentMetadataManagerBinding

SOAP Binding Style document

SOAP Transport http://schemas.xmlsoap.org/soap/http

7.2.7 WSDL Service Overview

7.2.7.1 This specification does not provide a WSDL service definition. WSDL service definitions provide one way

to define and locate the endpoint(s) at which a given interface can be accessed by a client. Such information cannot

be determined until the equipment has been installed on a factory network, and therefore is out of scope for this

specification. Users are responsible for defining the mechanisms by which clients locate SEMI E125 equipment

services in the factory.