Context Document
The contents of the context document are described by the following XSD:
<?xml version="1.0" encoding="UTF-8" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:c="http://www.tibco.com/schemas/asg/context" targetNamespace="http://www.tibco.com/schemas/asg/context" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="context">
<xs:complexType>
<xs:sequence>
<xs:element ref="c:entry" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="entry">
<xs:complexType>
<xs:sequence>
<xs:any namespace="##any" processContents="lax" />
</xs:sequence>
<xs:attribute name="key" type="xs:string" />
</xs:complexType>
</xs:element>
<xs:simpleType name="key">
<xs:restriction base="xs:string" />
</xs:simpleType>
</xs:schema>
If the incoming request is received from an HTTP server, the contents of the request context document are described by the following XSD:
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.tibco.com/asg/protocols/http" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="request">
<xs:complexType>
<xs:sequence>
<xs:element name="request-id" type="xs:short" minOccurs="0"/>
<xs:element name="server-ip" type="xs:string" minOccurs="0"/>
<xs:element name="server-port" type="xs:short" minOccurs="0"/>
<xs:element name="client-ip" type="xs:string" minOccurs="0"/>
<xs:element name="client-port" type="xs:byte" minOccurs="0"/>
<xs:element name="scheme" type="xs:string" minOccurs="0"/>
<xs:element name="method" type="xs:string" minOccurs="0"/>
<xs:element name="request-uri" type="xs:string" minOccurs="0"/>
<xs:element name="protocol-version" type="xs:string" minOccurs="0"/>
<xs:element name="query-string" type="xs:string" minOccurs="0"/>
<xs:element name="header" maxOccurs="unbounded" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="name" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="payloadSize" type="xs:short" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
The following is an HTTP Request Context sample:
<?xml version="1.0" encoding="utf-8"?>
<ctx:context xmlns:ctx="http://www.tibco.com/schemas/asg/context">
<!--Context doc href: context.0.xml-->
<c:entry xmlns:c="http://www.tibco.com/schemas/asg/context" key="asg:httpRequest">
<c:origin>i_http</c:origin>
<h:request xmlns:h="http://www.tibco.com/asg/protocols/http">
<h:request-id>2192</h:request-id>
<h:server-ip>localhost</h:server-ip>
<h:server-port>9222</h:server-port>
<h:client-ip>127.0.0.1</h:client-ip>
<h:client-port>0</h:client-port>
<h:scheme>http</h:scheme>
<h:method>POST</h:method>
<h:request-uri>/TerminalLocationService/services/TerminalLocation</h:request-uri>
<h:protocol-version>HTTP/1.1</h:protocol-version>
<h:query-string/>
<h:header name="content-type">text/xml; charset="utf-8"</h:header>
<h:header name="soapaction">"/getLocation"</h:header>
<h:header name="connection">close</h:header>
<h:header name="user-agent">Jakarta Commons-HttpClient/3.0.1</h:header>
<h:header name="host">localhost:9222</h:header>
<h:header name="content-length">489</h:header>
<h:payloadSize>489</h:payloadSize>
</h:request>
</c:entry>
</ctx:context>
The contents of HTTP Response Context document are described by the following XSD:
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.tibco.com/asg/protocols/http" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="response">
<xs:complexType>
<xs:sequence>
<xs:element name="status-code" type="xs:short" minOccurs="0"/>
<xs:element name="all_headers" type="xs:string" minOccurs="0"/>
<xs:element name="header" maxOccurs="unbounded" minOccurs="0">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="name" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="payloadSize" type="xs:short" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
The following is an HTTP Response Context sample:
<?xml version="1.0" encoding="utf-8"?>
<ctx:context xmlns:ctx="http://www.tibco.com/schemas/asg/context">
<!--Context doc href: context.0.xml-->
<c:entry xmlns:c="http://www.tibco.com/schemas/asg/context" key="asg:sbHttpResponse">
<h:response xmlns:h="http://www.tibco.com/asg/protocols/http">
<h:status-code>200</h:status-code>
<h:all_headers>Date: Fri, 29 Apr 2016 00:15:16 GMT
Content-Length: 486
Content-Type: text/xml;charset=utf-8
Server: Apache-Coyote/1.1
</h:all_headers>
<h:header name="Date">Fri, 29 Apr 2016 00:15:16 GMT</h:header>
<h:header name="Content-Length">486</h:header>
<h:header name="Content-Type">text/xml;charset=utf-8</h:header>
<h:header name="Server">Apache-Coyote/1.1</h:header>
<h:payloadSize>486</h:payloadSize>
</h:response>
</c:entry>
</ctx:context>
If the incoming request is received from a JMS server, the contents of the request context document are described by the following XSD:
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.tibco.com/asg/protocols/jms" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="request">
<xs:complexType>
<xs:sequence>
<xs:element name="request-id" type="xs:int" minOccurs="0"/>
<xs:element name="JMSCorrelationID" type="xs:string" minOccurs="0"/>
<xs:element name="JMSReplyTo" type="xs:string" minOccurs="0"/>
<xs:element name="body" type="xs:string" minOccurs="0"/>
<xs:element name="payloadSize" type="xs:short" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
The following is a JMS Request Context sample:
<?xml version="1.0" encoding="utf-8"?>
<c:context xmlns:c="http://www.tibco.com/schemas/asg/context">
<c:entry key="asg:jmsRequest">
<j:request xmlns:j="http://www.tibco.com/asg/protocols/jms">
<j:request-id>40709</j:request-id>
<j:JMSCorrelationID>GetLocation_118009</j:JMSCorrelationID>
<j:JMSReplyTo>asg.out.request.reply.0.0</j:JMSReplyTo>
<j:body>40709req</j:body>
<j:payloadSize>397</j:payloadSize>
</j:request>
</c:entry>
</c:context>
The contents of JMS Response Context document are described by the following XSD:
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.tibco.com/asg/protocols/jms" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="message">
<xs:complexType>
<xs:sequence>
<xs:element name="JMSCorrelationID" type="xs:int" minOccurs="0"/>
<xs:element name="Service" type="xs:string" minOccurs="0"/>
<xs:element name="ServiceInstance" type="xs:string" minOccurs="0"/>
<xs:element name="Operation" type="xs:string" minOccurs="0"/>
<xs:element name="JMSExpiration" type="xs:byte" minOccurs="0"/>
<xs:element name="body">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="size" type="xs:short"/>
<xs:attribute name="isBinary" type="xs:string"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
The following is a JMS Response Context sample:
<?xml version="1.0" encoding="utf-8"?>
<c:context xmlns:c="http://www.tibco.com/schemas/asg/context">
<c:entry key="asg:sbJMSResponse" xmlns:c="http://www.tibco.com/schemas/asg/context">
<k:message xmlns:k="http://www.tibco.com/asg/protocols/jms">
<k:JMSCorrelationID>40724</k:JMSCorrelationID>
<k:Service/>
<k:ServiceInstance/>
<k:Operation/>
<k:JMSExpiration>0</k:JMSExpiration>
<k:body size="371" isBinary="false"></k:body>
</k:message>
</c:entry>
</c:context>
Copyright © 2021. Cloud Software Group, Inc. All Rights Reserved.