The Autonomous REST Connector maps JSON responses to a relational model, exposing your REST data to relational, SQL-based applications. To map the responses to the relational model, the driver employs a Model file that defines endpoints and table mapping. The Model file is also capable of configuring a number of driver behaviors, such as paging, custom authentication, and HTTP response code processing. After creating a model file, you specify the location of the file using the Config (REST Config File) property to sample endpoints and begin accessing data.

The Model file is a simple text file that uses the file_name.rest naming convention. You can configure the file using either or both of the following methods:
  • The Autonomous REST Composer: Using the included REST management tool, the Autonomous REST Composer, you can generate and edit REST model files. See "Generating a Model file with the Autonomous REST Composer."
  • Text editor: Using a text editor, you can configure the relational map by populating the contents of the Model file with a list of comma-separated endpoints and requests using the formats described in "Model file syntax."

The following example demonstrates the basic format used in the Model file when mapping a table to the schema: 

{
          "<table_name1>":"<endpoint1>",
          "<table_name2>":"<endpoint2>",
          "<table_name3>":"<endpoint3>"
          }
A sample Model file, named example.rest, is installed in the install_dir\restfiles directory. For additional examples, see "Example Model file."
Note: The driver also offers a number of prebuilt Model files for publicly available data sources. See "Getting started using prebuilt Model files" for details.