Enterprises have applications and databases (on-prem apps) that are deployed within their corporate datacenter that are not accessible (protected via firewalls) to cloud services like Workato for security purposes. There are no differences in how you work with on-prem apps within your recipe, but on-prem app connections do require special configuration. An on-prem app connection needs to point to a on-prem agent and a specific connection profile. The Workato on-premise agent provides a secure way for Workato to selectively access customer authorized on-prem apps without having to open ‘ports’ in the corporate firewall.
Architecture
Workato on-premise connectivity has 2 components
- Agent
- Connector
The on-prem agent, runs within the customer’s data center, and establishes a TLS websocket tunnel with Workato. The on-prem agent runs behind the firewall, and connects out to Workato.
For other apps (like databases that have proprietary protocols), the Workato on-prem connector is required.
Creating recipes
There are no differences in how you work with on-prem apps within your recipe, but on-prem app connections do require special configuration. An on-prem app connection needs to point to a on-prem agent and a specific connection profile.
You can select the right on-prem agent from the pick list. Once you select the on-prem agent, enter the connection profile name as entered in the database.yml configuration file.