semi合集-English.pdf - 第7775页

SEMI T12.2-0704 © SEMI 2004 4 7.2 Service Parameter Ma pping — Service parameter type mapping is shown in th e following table. Table 2 Serv ice Parameter Type Mapping Parameter Name Attribute/Element Type Remarks Action…

SEMI T12.2-0704 © SEMI 2004 3

Service Message Name Supporting Class Service Message Element

Name Base

Remarks

fluctuate HistoryRecord Fluctuate

install Inventory Install

listEvent HistoryRecord ListEvent

listRecords HistoryDB ListRecords

listUp Inventory ListUp

receiveInvoice JitMachine ReceiveInvoice

reset HistoryDB Reset

setReleaseCondition HistoryBuffer SetReleaseCondition

showAction Expiry ShowAction

showAttachment HistoryBuffer ShowAttachment

showAttachments Invoice, JitMachine, PublicLocation ShowAttachments

showAvailableSpace PublicLocation ShowAvailableSpace

showCapacity PublicLocation ShowCapacity

showCategory Exception ShowCategory

showCode Exception ShowCode

showData Inventory ShowData

showDescription Exception, Expiry ShowDescription

showEvent HistoryRecord ShowEvent

showExeptions JitMachine ShowExeptions

showExpiration Expiry ShowExpiration

showHistory Attachment, HistoryBuffer, HistoryDB,

HistoryRecord, Invoice

ShowHistory

showId Attachment, Exception, Expiry, Invoice,

JitMachine, PublicLocation, Secondment

ShowId

showLoadports Invoice ShowLoadports

showLocationType PublicLocation ShowLocationType

showName Attachment, JitMachine, PublicLocation,

Secondment

ShowName

showNamespace Inventory ShowNamespace

showOccupancy PublicLocation ShowOccupancy

showPossibleType PublicLocation ShowPossibleType

showReleaseCondition HistoryBuffer ShowReleaseCondition

showState Exception, Expiry, HistoryBuffer,

PublicLocation, Secondment

ShowState

showSubject Exception, Expiry ShowSubject

showType Attachment, JitMachine, Secondment ShowType

showTypes Invoice ShowTypes

uninstall Inventory Uninstall

update HistoryDB, Inventory Update

updateHistory Attachment, Exception, HistoryBuffer UpdateHistory

updateState PublicLocation UpdateState

SEMI T12.2-0704 © SEMI 2004 4

7.2 Service Parameter Mapping — Service parameter type mapping is shown in the following table.

Table 2 Service Parameter Type Mapping

Parameter Name Attribute/Element Type Remarks

Action Element string

AttachmentId Element string

AttachmentInfo Element string

AttachmentName Element string

AttachmentType Element anyType Some Enumeration

Capacity Element unsignedInt

Category Element string

Code Element string

Condition Element string

DataName Element string

DataValue Element anyType Usually integer or float

Description Element string

EventCaption Element anyType Formatted Text

ExceptionId Element string

Expiration Element string

ExpiryId Element string

GroupName Element string

Handle Element string

History Element anyType Formatted Text

HistoryDifference Element anyType Formatted Text

InvoiceId Element string

Item Element string maybe enumerated

LoadportId Element string Usually small integer

Location Element string

LocationId Element string

LocationName Element string

LocationType Element string

MachineId Element string

MachineName Element string

MachineType Element string

Operation Element string Enumerated

Occupancy Element int Positive or Nagative

Restriction Element string regular expression or any

ServiceStatus Element complexType status+ Rejection

Space Element unsignedInt Usually small integer

State Element string Class dependent

SEMI T12.2-0704 © SEMI 2004 5

7.3 Additional Parameters for Service Messages — Because this protocol mapping works for asynchronous HTTP

server-client communication on message broker, such additional parameters to give complementary information as

issued time and transaction identification are required to be attached to each message. The information may be

dependent to the role of the message. Type mapping of them are shown in the following table.

Table 3 Type Mapping of Additional Parameters

Parameter Name Attribute/Element Type Remarks

dateTime Attribute dateTime

sessionId Attribute string

sessionRef Attribute string

requestId Attribute string

requestRef Attribute string

linkId Attribute string extended for delayed response

linkCnt Attribute integer extended for delayed response

linkExp Attribute duration extended for delayed response

7.4 Example XML Message Fragments — The following subsections give examples of some fragments of service

messages in XML. A full message is given with envelopes and headers.

7.4.1 addEvent Request — The following XML description is an example of the principal part of service request

message for addEvent provided by HistoryRecord objects. Because the structure of parameter ‘History’ is dependent

to event, attachment type and equipment, the standard doesn’t define it. Suppliers are required to define the structure

or negotiate with specific user. Users need to discuss with suppliers or interpret their structures.

<AddEventRequest dateTime=”2004-03-29T13:05:25.000-08:00”

SessionRef=”SemiJitQs-9876543210” RequestId=”123456”>

</ HistoryIndex>

<Event>

<EventClass>Milestone</EventClass>

</NamedValue>

<Event>

</History>

</AddEventRequest>

7.4.2 showTypes Response — The following XML description is an example of the principal part of service

response message for showTypes provided by Invoice objects.

<ShowTypesResponse dateTime=”2004-03-29T09:07:59.000-08:00”

SessionRef=”SemiJitQs-9876543123” RequestRef=”123443” status=”GRANTED”>

<SvcAck>Successful</SvcAck>

</ServiceStstus>

</ShowTypesResponse>