User Guide > Publishing Resources > Publishing Resources to a Database Service with OData
 
Publishing Resources to a Database Service with OData
You can use OData to publish resources to a database service.
You can use multiple columns for filtering a published OData resource by creating a unique index for the resource and then selecting two or more columns as index columns.
To publish resources for a database service and define OData options
1. Follow the instructions in Publishing Resources to a Database Service.
2. Open the database service that you created (at the level right below Data Services/Databases).
The database service opens on the OData panel.
Views or tables published through OData require a primary key. If a primary key does not exist, you must create one. For details, see Defining Primary Key for a View or Table in the Indexes Panel.
The list of endpoint Service URLs of the OData producers is exposed. There is one producer endpoint for each data source, catalog, or schema in the published database that contains table links.
3. In the Transport Level Security section of the OData panel, select from the following options.
TLS Option
Description
Enable SSL/TLS
Allows access to OData endpoint through the HTTPS protocol with SSL/TLS to secure data over the network. You must check this option to access either of the next two options. This option is checked and dimmed (unavailable to clear) after Require SSL/TLS and/or Validate Client Certificate is checked.
Require SSL/TLS
When this is checked, HTTP access is disabled, and access to OData endpoints must use HTTPS.
Validate Client Certificate
When this is checked, the client must present a certificate to the server during authentication, and the server must validate it.
4. In the HTTP Authentication Methods section, select one or more of the options listed in the table.
Authentication Options
Description
Basic
Allows users to present plain-text username and password credentials for authentication.
NTLM
Enables NTLM protocol for authentication of username and password credentials.
Digest
Enables a digest-based protocol for authentication of username and password credentials.
Negotiate
Enables client and server to negotiate whether to use NTLM or Kerberos Protocol (thus making Kerberos available).
Bearer
Enables authentication using the access token provided by the Identity Provider.
5. In the Unsupported section, review the list of resources that are not available through OData.
The Reason column explains why resources are unsupported. Determine if you want to fix any issues that caused them to appear on this list. For example, you could add primary keys to resources that do not have them (Defining Primary Key for a View or Table in the Indexes Panel).
6. Save your changes.
7. Optionally to use multiple columns for filtering, specify one or more columns for filtering, see Defining Primary Key for a View or Table in the Indexes Panel.