semi合集-English.pdf - 第7902页

SEMI T13.2-1104 © SEMI 2004 22 RELATED INFORMATION 1 IPC MESSAGING MECHAN ISM AND STRUCTURE NOTICE : This related information i s not an official part of SEMI T13.2 and was derived from the Japanese Traceability Committe…

100%1 / 7923
SEMI T13.2-1104 © SEMI 2004 21
<xsd:complexType name="NamedValueType">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="Value" type="xsd:anyType"/>
</xsd:sequence>
</xsd:complexType>
<!-- Service Status Type - - - - - Service Status Type - - -->
<xsd:complexType name="ServiceStatusType">
<xsd:sequence>
<xsd:element name="SvcAck" type="jit:SvcAckType"/>
<xsd:element name="SvcErr" type="SvcErrType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="SvcAckType">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="Successful"/>
<xsd:enumeration value="Wrong Service"/>
<xsd:enumeration value="Refused"/>
<xsd:enumeration value="Invalid Parameter"/>
<xsd:enumeration value="Has started"/>
<xsd:enumeration value="Unsuccessful"/>
<xsd:enumeration value="Wrong object"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="SvcErrType">
<xsd:sequence>
<xsd:element name="SvcErrCode" type="xsd:integer"/>
<xsd:element name="SvcErrText" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<!-- Attributes - - - - - Attributes - - - - - - Attributes - - -->
<xsd:attributeGroup name="RegRequestAttr">
<xsd:attribute name="dateTime" type="xsd:dateTime" use="required"/>
<xsd:attribute name="sessionRef" type="xsd:string" use="required"/>
<xsd:attribute name="requestId" type="xsd:string" use="required"/>
</xsd:attributeGroup>
<xsd:attributeGroup name="RegResponseAttr">
<xsd:attribute name="dateTime" type="xsd:dateTime" use="required"/>
<xsd:attribute name="sessionRef" type="xsd:string" use="required"/>
<xsd:attribute name="requestRef" type="xsd:string" use="required"/>
<xsd:attribute name="status" type="RspStatus" use="required"/>
<xsd:attribute name="authority" type="xsd:string" use="optional"/>
<xsd:attribute name="linkId" type="xsd:string" use="optional"/>
<xsd:attribute name="linkCnt" type="xsd:integer" use="optional"/>
<xsd:attribute name="linkExp" type="xsd:duration" use="optional"/>
</xsd:attributeGroup>
<xsd:simpleType name="RspStatus">
<xsd:restriction base="xsd:string">
<xsd:enumeration value="GRANTED"/>
<xsd:enumeration value="REFUSED"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
SEMI T13.2-1104 © SEMI 2004 22
RELATED INFORMATION 1
IPC MESSAGING MECHANISM AND STRUCTURE
NOTICE: This related information is not an official part of SEMI T13.2 and was derived from the Japanese
Traceability Committee. This related information was approved for publication by full letter ballot on July 23,
2004.
R1-1 HTTP and SOAP Envelope
R1-1.1 The following diagram illustrates HTTP message border and SOAP Envelope structure. SOAP Header
contains information of the message and SOAP body just contains SOAP Faults to make sure what happens when
something wrong. Intended message service and its parameters are contained in second MIME Block to make it
possible to allow mixture of non-XML data.
R1-2 Communication with Message Broker
R1-2.1 The following diagrams show client-server communications with Message Broker.
HTTP 1.1
SOAP with MIME Envelope
MIME Block
MIME Block
Mess age Name a nd Parameters
SOAP Envelope
SOAP Body
SOAP Header
SOAP Faults
Me s s ag e I n f o r ma t i on
Figure R1-1
SOAP Envelope and MIME Blocks
SEMI T13.2-1104 © SEMI 2004 23
Client
(HTT P Clien t)
Broker
(HTT P Se rver)
HTTP POST <MessageC1>
HTTP 200 <Acknowledge>
Client
(HTTP Client)
Broker
(HTT P Serve r)
HTT P POST < getM essag e>
HTTP 200 <MessageB1>
Client
(HTTP Client)
Br oker
(HTTP Serve r)
HTTP POST <g etMessage >
HTTP 200 <empty>
HTTP POST <Ack nowledge>
HTTP 200 <empty>
Client
(HTT P Clien t)
Broker
(HTT P Serve r)
HTTP POST <M essa geC2>
HTTP 200 <Ackno wledge>
Client
(HTTP Client)
HTTP POST <getMessage>
HTTP 200 <MessageC2>
HTTP P OST <Ackn owledge>
HTTP 200 <empty>
Message from Client to Broker
Message from Broker to Client
No Message from Broker to Client
Messa
g
e between Client
s
Figure R1-2
Communication with Message Broker
NOTICE: SEMI makes no warranties or representations as to the suitability of the standards set forth herein for any
particular application. The determination of the suitability of the standard is solely the responsibility of the user.
Users are cautioned to refer to manufacturer's instructions, product labels, product data sheets, and other relevant
literature, respecting any materials or equipment mentioned herein. These standards are subject to change without
notice.
By publication of this standard, Semiconductor Equipment and Materials International (SEMI) takes no position
respecting the validity of any patent rights or copyrights asserted in connection with any items mentioned in this
standard. Users of this standard are expressly advised that determination of any such patent rights or copyrights, and
the risk of infringement of such rights are entirely their own responsibility.
Copyright by SEMI® (Semiconductor Equipment and Materials
International), 3081 Zanker Road, San Jose, CA 95134. Reproduction of
the contents in whole or in part is forbidden without express written
consent of SEMI.