The Bridge can be used as HTTP server or as HTTP client. In order to access HTTP resources (backends), the URL adapter can be used.
In order to act as server, an HTTP frontend can be defined for a service.
Refer to HTTP Header Support regarding general information on HTTP header support in this context.
Since Runtime 2018.5, the BRIDGE HTTP service supports IPv6.
The HTTP service is defined in the component diagram as <<E2EHTTPService>> component containing one ore many <<E2EHTTPPortType>> classes:
Each <<E2EHTTPService>> contains the following tagged values:
|Name Dialog / Tag||Description||Allowed Values / Examples|
Specifies the machine port number the service is binding to. This port number can be given at the service level only.
Using ports below 1024 may require additional privileges.
|In order to test the HTTP service using the Trace Analyzer, the model compiler generates a SOAP interface for each HTTP service interface. The SOAP service will be listening on this trace port.||any positive integer|
|service port +40000||default|
|Max Request Body Size|
Runtime 2021.2 Specifies the maximum size of the request in KiB (1 KiB = 1024 Bytes). This can be used to prevent DoS or similar attacks. When the payload of the service exceeds the given maximum, incoming request are rejected.
If you have multiple HTTP services in one composite, you can only apply the same value to all. If you specify different values on each of them, the Runtime will pick one and apply them to all.
|any positive integer|
|0||accept unlimited requests|
(default of services compiled with Builder versions < 7.12.0)
|2048||Builder 7.12.0 2MiB, default if not specified|
Defines the authentication mode to be used with this SOAP service.
Independent of the authentication mode, the user is found in the principal object if the authentication succeeded.
|HTTPBasicAuth||HTTP basic authentication|
|HTTPRemoteAuth||HTTP remote authentication|
|Specifies user and password for the use of HTTP Basic authentication.||user/password|
At the moment HTTP is the only supported protocol. If HTTPS is required, use the BRIDGE Apache reverse proxy.
For a list of HTTP port type parameters refer to the reference page at HTTP Service Reference.
Runtime 2019.9 Bridge xUML services read the following incoming HTTP headers containing correlation information: These headers will be all logged to the transaction log. Having this information, you can use this for error analysis or usage metrics.
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.
This header should identify the unique request.
These headers should contain the sender host resp. the sender service.
Runtime 2019.9 Bridge xUML services read the following incoming HTTP headers containing correlation information:
These headers will be all logged to the transaction log. Having this information, you can use this for error analysis or usage metrics.
HTTP Header Roles
Runtime 2020.12 If the standard HTTP header handling does not meet your needs, you can take control of the header handling by defining your own header roles.
Refer to HTTP Header Support > Overwriting the Standard HTTP Headers for a detailed explanation of how to use this feature.