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.
Example File (Builder project Basic Modeling/Frontend):
 | <your example path>\Basic Modeling\Frontend\uml\simpleHttpService.xml <your example path>\Basic Modeling\Frontend\uml\simpleRESTSupportManager.xml |
Since Runtime 2018.5, the E2E HTTP service supports IPv6.
HTTP Components
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:
| Tagged Value | Description | Allowed Values | |||||
|---|---|---|---|---|---|---|---|
| port | MultiExcerpt named port was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro | any number Using ports below 1024 may require additional privileges. | |||||
| tracePort | 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 number | |||||
| service port +40000 | default | ||||||
| authenticationMode | MultiExcerpt named authenticationMode was not found -- Please check the page name and MultiExcerpt name used in the MultiExcerpt-Include macro | none | no authentication | ||||
| HTTPBasicAuth | HTTP basic authentication | ||||||
| HTTPRemoteAuth | HTTP remote authentication | ||||||
| user | Specifies user and password for the use of HTTP Basic authentication. | Example: user/password | |||||
At the moment HTTP is the only supported protocol. If HTTPS is required, use the E2E Apache reverse proxy.
HTTP Port Type Operation Parameters
Each operation of an <<E2EHTTPPortType>> may contain the following parameters - all of them being optional:
| Name | Type | Direction | Description | Values |
|---|---|---|---|---|
| method | String | in | HTTP method. | get, post, put, patch, delete, ... |
| uri | String | in | complete URI. | |
| inputContent | Blob | in | content send by POST or PUT. | |
| getParameters | Array of Parameter | in | all GET parameters encoded in the URL as an array of Parameter classes containing name/value pairs. | |
| postParameters | Array of Parameter | in | all form parameters posted by the client. | |
| inputHeaderParameters | HeaderField | in | all header fields as an array of HeaderField classes containing name/value pairs. | |
| pathParameters | Map | in | for RESTful service calls: all parameters derived from the path as a Map of name/value pairs. | |
| outputContent | Blob | out | the content sent back. | |
| outputHeaderParameters | HeaderField | out | if necessary, HTTP output header can be set using this object. | |
| httpStatusDescription | String | out | the resulting HTTP status description. If not set explicitly using this object, the service returns OK if no exception occurred or Internal Error otherwise. | |
| httpStatusCode | Integer | out | the resulting HTTP status code. If not set explicitly using this object, the service returns 200 if no exception occurred or 500 otherwise. |
Overview
Content Tools