If errors occur during an OData request, Intrexx tries to identify the error
messages from the response of the service, and display them in the browser.
This is not possible in all cases. For a more detailed error analysis, it is
therefore possible to enable OData Request Tracing in the Intrexx
Portal Server. This is described below.
1.2. Request tracing and error logging
When Request Tracing is activated, both the OData requests and the responses
are written in detail to the Intrexx portal log file. For requests, an entry
consists of the HTTP action, the URL, the query option, the request headers
and XML body. For responses, the HTTP headers and XML body of the response
will be recorded.
While Intrexx offers support for all major functions of the OData
specification version 2.0, there may be circumstances when a service does not
support certain features. In this case, there will either be a failure, or a
query will not deliver the expected result. Since the OData specification of
the services implemented provides considerable flexibility, in terms of
support of features, in such a case, only the Intrexx application can be
adjusted so that only the functions supported by the service are used.
Examples of such cases are filter definitions, site navigation (pagination) or
sorting. Using the corresponding
problematic OData features can be deactivated. If certain filter definitions
are not supported, the filter must be adjusted accordingly in Intrexx, or
2.1. SSL connections
For SSL connections between the Intrexx portal server and an OData service,
the certificate of the Certificate Authority that issued the service
certificate, must have been added to the certificate store of the Intrexx
Portal server. An exception applies to self-signed certificates, which were
not issued by a recognized Certificate Authority. To enable SSL connections
to services with self-signed certificates, the testing of the
"Certificate Chain" in the Intrexx server must be disabled in this case. This
is possible at service level through a system property. Open the "portal.cfg"
file in the
portal directory /internal/cfg/
with a text editor, and in the <environment> section, add a new
<systemProperty> entry, as follows:
<systemProperty name = "de.uplanet.lucy.server.odata.consumer.ssl.allowSelfSignedCerts.<SERVICE_GUID>;" value="true"/>
The placeholder <SERVICE_GUID> should be replaced with the
GUID of the OData services. The GUID
can be found in the service configuration file
portal directory internal/cfg/odata.
After saving the "portal.cfg" file, the Intrexx
portal service must be
restarted for the changes to take effect.
2.2. OData specification
A description of the OData protocol and the OData specification is available at the following URL: http://www.odata.org/
2.3. OData tools
The following tools have been found to be helpful for the creation of applications, and problem analysis:
This Firefox plugin
allows OData requests to be run and analyzed within the browser. This is
useful, especially for error analysis. Thus, with Request Tracing enabled,
the OData HTTP request may be copied from the Intrexx portal.log and
executed in the REST client, and in cases of failure, can be adjusted
to avoid unsupported functions.