- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Releasing a SQL Connector
Once the new version of the SQL connector is ready for production, it can be marked as a release in Git. Then the connector can be moved to production. This page describes how to release a SQL connector from a development environment to a production environment.
It is assumed that the standard setup is used, as described in Separate development and production environments.
If any changes were made to the data extraction, you must first update the extractor on the production environment.
When you are using CData Sync, this means that you must update the CData Sync job of the SQL connector.
The connection used for the extraction must point to the production source system.
The released connector content can be checked out on the production environment.
config.json
file in the scripts\
directory points to the job name on the production server. It should be overwritten when updating the connector contents.
This happens automatically when GitHub is used because the file is ignored by Git.
profiles.yml
file contains connection information that should be different for the production environment. Make sure your profiles.yml
is located outside of the connector directory.
The next time the connector is run, the new data extraction and transformation are used to generate data.
Running a SQL connector on how to run a SQL connector manually.
It is also possible to set up a scheduled task for data extraction. See Scheduling data extraction for more information.