You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

On this Page:

Related Pages:

HTTP Protocol with xUML Service Adapters

  • The Bridge comes with many adapters that allow you to access a variety of backends via different interfaces. SOAP, REST and URL adapters use libcurl to provide HTTP headers.
    For more information on specific adapters refer to xUML Service Adapters.

  • Runtime 2019.9 With xUML service adapter calls, the xUML Runtime adds the following outgoing HTTP headers containing correlation information to the request:

    • X-Transaction-Id or xTransactionId (in JMS context)
      This header identifies the transaction the call belongs to. You can set the transaction id manually with setTransactionID. If not set, the Runtime will generate one.
      This header will be passed through the callstack to identify all service calls that belong to a transaction.
    • X-Request-Id
      This header identifies the unique request. The Runtime generates a unique number for each adapter call.
    • X-Sender-Host and X-Sender-Service
      These headers contain the sender host resp. the sender service. They are set by the Runtime automatically.

    Transaction id and request id will be logged to the transaction log on the adapter call. Having this information, you can use this for error analysis or usage metrics.

HTTP Protocol with Service Implementations

The Bridge provides interfaces to act as a variety of services. In general, the Bridge supports HTTP version 1.0 for xUML services. However, the following features of HTTP 1.1 are implemented to the xUML Runtime as well:

  • Expect: 100 Continue
  • Runtime 2018.5 Transfer-Encoding: chunked

  • Runtime 2019.9 Bridge xUML services read the following incoming HTTP headers containing correlation information:

    • X-Transaction-Id or xTransactionId (in JMS context)
      This header identifies the transaction the call belongs to. You can set the transaction id manually with setTransactionID. If not set, the Runtime will generate one.
      This header will be passed through the callstack to identify all service calls that belong to a transaction.
    • X-Request-Id 
      This header should identify the unique request.
    • X-Sender-Host and X-Sender-Service
      These headers should contain the sender host resp. the sender service.

    These headers will be all logged to the transaction log. Having this information, you can use this for error analysis or usage metrics.

For more information on specific service implementations refer to Service Implementations.

  • No labels