http://www.ibm.com/schema/twss/userec/v2_0/local
The writeUsageRecordRequest Complex Type

Write usage record request type.


Local elements (7)
globalTransactionID service eventType recordTime code serviceAttributes serviceValues
Complex Type writeUsageRecordRequest
The writeUsageRecordRequest type does not allow mixed content. There is no restriction on type derivation. 
 CollapseClick here to hide comment XML Instance
<...>
-Begin Sequence [1...1]

The global transaction ID for the Web Service transaction.

<globalTransactionID>xsd:string</globalTransactionID> [1..1]

The service implementation that originated the usage record. The service name is specific to each service implementation and should be chosen to avoid conflicts with other service implementations.

<service>xsd:string</service> [1..1]

The type of event being written. This marks the point in the service implementation where the service usage record is being recorded. This event type is service implementation specific, but should be unique for each service and event type.

<eventType>xsd:string</eventType> [1..1]

The recorded time in milliseconds since the epoch.

<recordTime>xsd:long</recordTime> [1..1]

The service implementation status code. The code used is service implementation specific, but the following status codes are suggested/reserved: 0 - Success, 1 - General failure, 2 - privacy related failure.

<code>xsd:int</code> [1..1]

Service data attribute names.

<serviceAttributes>xsd:string</serviceAttributes> [0..*]

Service data attribute values. Shares the same index as the attribute names and the arrays should be of equal size.

<serviceValues>xsd:string</serviceValues> [0..*]
End Sequence
</...>

 Collapse Attributes

Name Type Summary
No Attributes

 Collapse XML
-<xsd:complexType  name="writeUsageRecordRequest">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>Write usage record request type.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
-<xsd:sequence>
-<xsd:element  name="globalTransactionID"  type="xsd:string">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>The global transaction ID for the Web Service transaction.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  name="service"  type="xsd:string">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>The service implementation that originated the usage record. The service name is specific to each service implementation and should be chosen to avoid conflicts with other service implementations.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  name="eventType"  type="xsd:string">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>The type of event being written. This marks the point in the service implementation where the service usage record is being recorded. This event type is service implementation specific, but should be unique for each service and event type.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  name="recordTime"  type="xsd:long">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>The recorded time in milliseconds since the epoch.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  name="code"  type="xsd:int">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>The service implementation status code. The code used is service implementation specific, but the following status codes are suggested/reserved: 0 - Success, 1 - General failure, 2 - privacy related failure.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  maxOccurs="unbounded"  minOccurs="0"  name="serviceAttributes"  type="xsd:string">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>Service data attribute names.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
-<xsd:element  maxOccurs="unbounded"  minOccurs="0"  name="serviceValues"  type="xsd:string">
-<xsd:annotation>
-<xsd:documentation  xml:lang="en">
<xhtml:p>Service data attribute values. Shares the same index as the attribute names and the arrays should be of equal size.</xhtml:p>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>

 Collapse Uses
 Collapse Type (3)
int  long  string 
 
 Collapse Used-By
 Collapse Element (1)
 
Generated by WSDLdoc ©