Check out our latest tech talk, "JavaScript Supply Chain Security" presented by VP of Security, Adam Baldwin.Watch it here »


2.2.1 • Public • Published

Oracle Database Connector

The Oracle data connector is a plugin for API Builder that can connect to your Oracle database instance and interrogate your schema that will automatically provision Models into to your application, and optionally, automatically generate a rich CRUD API to the underlying tables. The Models can be used programmatically, or can be used within the flow editor to interact with your database.

Minimum requirements

Supported versions

  • Oracle 12c


  • ~25 MB

Disk space

  • ~16 MB

Supported features

  • Automatic generation of Models from SQL tables
  • Automatic generation of API for Models
  • Full CRUD operations on tables via Models


This connector requires Oracle Instant Client installed. To install it, please follow the instructions for your environment here:

The connector also depends on the 'node-oracledb' module. To be able to properly install the connector, please check the prerequisites here:


To install the connector use:

npm install @axway/api-builder-plugin-dc-oracle

A configuration file is generated for you and placed into the conf directory of your API Builder project. You should configure this file before starting your service.


Once the plugin is installed, the configuration file is located <project>/conf/oracle.default.js.

Option name Type Description
connector string Must be: @axway/api-builder-plugin-dc-oracle
connectString string The database instance connection string, e.g. localhost/orcl.
user string The user with which to connect to the database.
password string The user's password with which to connect to the database.
generateModelsFromSchema boolean If enabled, API Builder will automatically interrogate the database and auto-generate Models from SQL tables.
modelAutogen boolean If enabled, API Builder will automatically generate a full and rich CRUD API from the generated Models.


After you configure the connector, you can start up your API Builder project and visit the console (normally found under http://localhost:8080/console). Your connector will be listed under the Connectors section of the console.

Your database tables will be listed under the Models section of the console. You can now click on the gear icon to the right of the table names and generate flow based APIs.

You can also reference the connector in a custom model.

const Account = APIBuilder.Model.extend('Account', {
  fields: {
    Name: { type: String, required: true }
  connector: 'oracle'

If you want to map a specific model to a specific table, use metadata. For example, to map the account model to the table named accounts, set it such as:

const Account = APIBuilder.Model.extend('account', {
  fields: {
    Name: { type: String, required: false, validator: /[a-zA-Z]{3,}/ }
  connector: 'oracle',
  metadata: {
    'oracle': {
      table: 'accounts'

Known issues and limitations

  1. Only supports SQL tables.
  2. Does not support views.
  3. Does not support stored procedures.



  • #5050: Updating license text.


  • #4724: Support for Models based on tables that have no primary key. Previously, there was no way to distinguish between a model with no primary key and a model relying on the default. Now, the models auto-generated by the connectore advertise whether or not they have primary keys.


  • #4532: Data connectors table methods did not display the proper type for the PK Previously, APIs and flows generated for models based created by data connectors assumed a IDs were of type string. Now,the APIs and flows will use the proper type for the primary key.


  • #4871: Breaking Change: Introduce support $in and $nin (IN and NOT IN) operators in where query. Previously, when using Model flow nodes and the auto-generated APIs with the Oracle data connectors, it was not possible to formulate a where clause to return results where the field value is in or not in a list of values. Now the where clause can use $in and $nin to construct these queries, e.g. { "field": { "$in": ["value1", "value2",...]}}.

    For more information on the Model flow node and the methods that accept a where clause please see


  • #4757: Changed SCM repository and associated internal cleanup.
  • #4814: Update the default configuration. Previously the default oracle.default.js configuration file contained hard-coded connection details, now it uses environment variables.


This code is proprietary, closed source software licensed to you by Axway. All Rights Reserved. You may not modify Axway’s code without express written permission of Axway. You are licensed to use and distribute your services developed with the use of this software and dependencies, including distributing reasonable and appropriate portions of the Axway code and dependencies. Except as set forth above, this code MUST not be copied or otherwise redistributed without express written permission of Axway. This module is licensed as part of the Axway Platform and governed under the terms of the Axway license agreement (General Conditions) located here:; EXCEPT THAT IF YOU RECEIVED A FREE SUBSCRIPTION, LICENSE, OR SUPPORT SUBSCRIPTION FOR THIS CODE, NOTWITHSTANDING THE LANGUAGE OF THE GENERAL CONDITIONS, AXWAY HEREBY DISCLAIMS ALL SUPPORT AND MAINTENANCE OBLIGATIONS, AS WELL AS ALL EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED INFRINGEMENT WARRANTIES, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND YOU ACCEPT THE PRODUCT AS-IS AND WITH ALL FAULTS, SOLELY AT YOUR OWN RISK. Your right to use this software is strictly limited to the term (if any) of the license or subscription originally granted to you.


npm i @axway/api-builder-plugin-dc-oracle

Downloadsweekly downloads








last publish


  • avatar
  • avatar
  • avatar
  • avatar
  • avatar
  • avatar
  • avatar
  • avatar
  • avatar
  • avatar
  • avatar
  • avatar
  • avatar
Report a vulnerability