semi合集-English.pdf - 第3528页

SEMI E134.1-0305 © SEMI 2005 15 7.2.7.5 E134-1-V0305-Schem a.xsd im ports types from the SEMI 3570.1 Specification for XML Semiconductor Common Components XML Schema nam esp ace, specifically the ErrorType type. 7.2.8 WS…

100%1 / 7923
SEMI E134.1-0305 © SEMI 2005 14
7.2.6.3 SEMI E134.1 implements the SEMI E134 Unauthorized Operation Class as the SEMI E132.1
UnauthorizedOperation class and will return the SEMI E132.1 error code “6005” and a source of “urn:semi-
org:E132” Operation not authorized in the Common Components Error structure.
Table 11 SEMI E134 Error Codes
SEMI E134 Error Common Error Code
Operation not authorized. 6005 (as defined in SEMI E132.1)
InvalidPlan 8000
NoSuchPlan. 8001
DCPIsActive. 8002
DCPNotActive. 8003
7.2.7 XML Schema and WSDL Files
7.2.7.1 This section is provisional, pending the approval of SEMI E120.1, SEMI E125.1, and SEMI E132.1.
7.2.7.2 The XML Schema and WSDL defined by this specification for the DataCollectionManager interface is
contained in the following documents:
Table 12 XML Schema
File Name E134-1-V0305-Schema.xsd
Target Namespace urn:semi-org:xsd.E134-1.V0305.DCM
Imported/Referenced
Namespaces
urn:semi-org:xsd.E120-1.V0704.CommonEquipmentModel
http://www.w3.org/2001/XMLSchema
Description
This file defines all of the SEMI E134 data types and elements used by both the
DataCollectionManager and DCPConsumer interfaces.
Table 13 DataCollectionManager PortType Definitions
File Name E134-1-V0305-Equipment-portType.wsdl
Target Namespace urn:semi-org:ws.E134-1.V0305.DCMEqp-portType
Imported/Referenced
Namespaces
urn:semi-org:xsd.E132-1.V0305.auth
urn:semi-org:xsd.E134-1.V0305.DCM
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 DataCollectionManager
interface, based on the data types defined in the SEMI E134 XML Schema.
Table 14 DataCollectionManager Binding Definitions
File Name E134-1-V0305-Equipment-binding.wsdl
Target Namespace urn:semi-org:ws.E134-1.V0305.DCMEqp-binding
Imported/Referenced
Namespaces
urn:semi-org:ws.E134-1.V0305.DCMEqp-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.7.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.7.4 E134-1-V0305-Schema.xsd imports types from the SEMI E132.1 Equipment Client Authentication and
Authorization XML Schema namespace, specifically the E132Header and E132HashHeader types.
SEMI E134.1-0305 © SEMI 2005 15
7.2.7.5 E134-1-V0305-Schema.xsd imports types from the SEMI 3570.1 Specification for XML Semiconductor
Common Components XML Schema namespace, specifically the ErrorType type.
7.2.8 WSDL Port Type Overview
7.2.8.1 The DataCollectionManager WSDL portType definition organizes the SEMI E134.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 DataCollectionManager interface in SEMI E134, ¶9.1. The WSDL portType itself is named after the
SEMI E134 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 E134. Figure 5 illustrates the relationship
between the SEMI E134 UML interface and the WSDL portType definition. The WSDL message and operation
definitions are described in ¶¶7.2.10 through 7.2.20.
Figure 5
Mapping the DataCollectionManager to a WSDL portType
7.2.9 WSDL Binding Overview
7.2.9.1 The WSDL DataCollectionManager binding definition specifies a message and transport protocol to use for
a given portType (SOAP and HTTP for SEMI E134.1), the interface style used (document style for SEMI E134.1).
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.10 through 7.2.20.
7.2.10 WSDL Service Overview
7.2.10.1 This specification does not provide a WSDL service definition. WSDL service definitions define the
address(es) 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 E134 equipment services in the factory
SEMI E134.1-0305 © SEMI 2005 16
7.2.11 DefinePlan
7.2.11.1 WSDL Operation Binding
7.2.11.1.1 See the operation binding for “DefinePlan” in SEMI E134-Equipment-Binding.wsdl. Key information is
shown for convenience in the following table.
Table 15 DefinePlan Operation Binding
SOAPAction
urn:semi-org:ws.E134-1.V0305.DCMEqp-binding:DefinePlan
Input Headers (WSDL Message, Required) E132HeaderMessage, required
Output Headers (WSDL Message, Required) E132HeaderMessage, required
7.2.11.2 WSDL Operation
7.2.11.2.1 See the portType operation definition for “DefinePlan” in E134-Equipment-PortType.wsdl. Key
information is shown for convenience in the following table.
Table 16 DefinePlan PortType Operation
Input Message Name DefinePlanRequest
Output Message Name DefinePlanResponse
7.2.11.3 WSDL Message(s)
7.2.11.3.1 See the message definitions for “E132HeaderMessage”, “DefinePlanRequest”, and
“DefinePlanResponse” in E134-Equipment-PortType.wsdl. Key information is shown for convenience in the
following table.
Table 17 DataCollectionManagement Binding
Message Name
Schema
Element Name
E132HeaderMessage auth:E132Header
DefinePlanRequest dcm:DefinePlanRequestType
DefinePlanResponse dcm:DefinePlanResponseType
7.2.11.4 XML Schema Types
Figure 6
DefinePlanRequest
7.2.11.4.1 DefinePlanRequest - this global element acts as a top-level container entity representing the SOAP body
of a DefinePlan request. As defined in SEMI E134, this operation has one input argument: the new DCP that is
being defined. This argument is modeled as a single element named “NewPlan” of complexType
“DataCollectionPlanType”.