How To Run A Connector Function in Multiple Environments

Understand how to create test production, testing and development environments for Connectors.

What are Environments?

Connector environments allows you to define seperate target external systems for your connectors to interact with, depending on the lifecycle phase of applications.

Environments allow you to safely develop applications without impacting production databases, and automatically migrate to production databases when applications are published.

Setting Up Multiple Environments

After you create a new SQL or HTTP Connector, you will see a screen like this.

By default, only the "Production" environment will be configured, and the "Development" and "Pre-Production" will be configured to match production.

How Environments are Used

Based on the place where in application is run, and the state of that application, different environments will be used.

Within Developer Mode, the environment can be overwritten (see details here), but within Tulip Player, the environment used will be entirely drive by the phase in the app lifecycle.

Development - When the development version of an application is used (in player or dev mode), the configuration of the Development environment will be used.

Pre-Production - When an application has been submitted for approvals, but has not been approved, the "Pre-Production" environment configuration will be used.

Production - When an application has been published, the production environment will be used.

Further Reading

• How To Write a Connector Function
• How To Call a Connector Function Using Triggers