How to set up an HTTP server for OData operations

This topic has been updated for build 1823.

There are two ways to set up an OData Server.

Embedded HTTP server set up

The OData Server utility initiates an instance of the embedded HTTP server and automatically loads OData Producers as Java Servlets.

The embedded HTTP server cannot be manually configured or used to serve other non-OData content, such as HTML files. However, some HTTP server options can be specified in the OData Server configuration file.

The following steps are required to set up and launch the embedded HTTP server:

Create an OData Server configuration file that contains the settings for the OData Producers and the embedded HTTP server.
Store the configuration file on the computer to act as the HTTP server, and then load the configuration file when you run the OData Server utility at a command prompt.

Alternative HTTP server set up

To use OData Producers with an alternative HTTP server, you must deploy the OData Producers to the server. OData Producers must be run as Java Servlets that can be loaded into an HTTP server. For example, Tomcat can be used as a Java Servlet container and paired with an Apache HTTP server.

Note

IIS cannot execute Java Servlets, but it is possible to configure a connector that redirects Servlet requests from an IIS server to another server that is able to run them.

The process of deploying OData Producers differs depending on your HTTP server. For more information, see your HTTP server documentation.

The following steps are required to deploy OData Producers:

Create an OData Server configuration file.

Any configuration options that are specific to the embedded HTTP server, including security considerations, are not applied to the alternative HTTP server.

OData Producers respect the logging configuration of the HTTP server. For more information about HTTP server logging, see your HTTP server documentation.
Deploy the OData Server configuration file, along with the following file, located in the %SQLANY16%\Java directory:
- dbodata.jar
Deploy the JDBC client. This includes the JDBC 4.0 driver and supporting files.
Load the SAPSybaseODataServlet class, which implements the Java EE HttpServlet interface, into the HTTP server.