Affects Version/s: 6.2.0
Fix Version/s: 6.2.x
The Dynamic ESDL document should explain the process of configuring ESDL binding methods with Request Context information for Roxie query consumption.
There are 3 instances where the current document discusses the configuration of Methods. All three of those instances should illustrate
- Section "Publish the ESDL Service Definitions and Bind the ESDL Service" subsection 2
- Section "esdl bind-service"
- Section "esdl bind-method"
- there might be other sections
We need to explain that DESDL methods can provide context information to roxie (this includes things such as gateway information, urls, credentials, etc.).
The way this information is configured, is by appending children elements to the Methods/Method portion of the ESDL Binding. For example, in the document we provide the following XML as a ESDL Binding example:
If the method AddThis needs to provide context information to roxie it would be added as follows:
The DESDL ESP does not pose any restrictions on the layout of this information (as long as it is valid XML). This gives the product owner the flexibility to provide the information in any xml format the wish. This means the roxie query ECL developer needs to decide what information they will need from the ESP request and it is their responsibility to design how that information is to be laid-out in the ESP request and ESDL binding configuration.
In this example, every "AddThis" request processed by the ESP and sent to roxie would contain the sample gateways information in the request context. Example:
The ECL query consumes this information and is free to do whatever it needs to do with it. In some instances, if the query decides it needs to send a request to a gateway in order to properly process the current request, it can interrogate the context information for the appropriate gateway's connection information, and use that information to create the actual gateway request connection.