Strategy ONE

Connect to On-Premise Database Via a Gateway Agent for MCS Environments

Starting in Strategy One (June 2025), access to on-premise data from the Managed Cloud Standard (MCS) Environment is enabled. Data Gateway Server and Data Gateway Client facilitates connectivity to data residing in your on-premise environment behind a firewall. These components work together to establish a secure, bidirectional, persistent command channel. Use this secured channel to connect to your on-premise databases via the Gateway Agent.

Pre-Installation Checks

Before installing the Data Gateway Client, review the following information to ensure smooth deployment.

  • The Client should be able to access the database in the private network that will be connected on Strategy Cloud. The network should be able to make an outbound connection to the internet to access Strategy Cloud.

  • Client sessions are managed by refresh tokens which are generated after a successful sign-in to Managed Cloud Standard from the Data Gateway Agent client. Once the refresh token expires, a new sign-in to Managed Cloud Standard is required.

  • Only one client can be installed on a machine.

Configure the Connection

  1. Contact the Strategy Cloud team to provision a Strategy Cloud environment.

  2. Download and install the Strategy Gateway Agent Client. This client exposes an interface through a task bar icon, allowing users to log in and manage connections to each Strategy Cloud Environment.

  3. Connect the Strategy Go Environment. The Strategy Gateway Agent provides an option for Strategy Cloud Environment users to add an environment and log in.

    • Users can add an environment and log in using Library authentication. Once connected, the Strategy Cloud Environments display on the home page. The supported authentications are Standard, OIDC, and SAML.

    • Users have the option to add new environments or delete existing ones.

  4. Add the whitelist. The Whitelist Data Source is a set of IP/Hostname and Port configurations set by the end user to allow access to an on-premise database using the Gateway Agent client. Only the IP/Port combinations specified in the whitelist can establish a channel, thereby protecting other servers in the on-premise network.

    • The privilege Enable on-premise data access via Gateway Agent is required to add, edit, or delete entries in the Data Source Whitelist.

    • The user must configure at least one data source in the whitelist to enable the Gateway Agent.

  5. Enable the Gateway Agent. After adding a data source to the whitelist, a toggle button displays, allowing the user to enable the Gateway Agent. Once enabled, the Gateway Agent can access the data sources specified in the whitelist.

  6. Connect on-premise data using the Gateway Agent. Once the Gateway Agent is enabled, users can create a new data source using the Gateway Agent. This allows users to connect to on-premise data sources specified in the whitelist from the Strategy Cloud Environment.

  7. Enable network diagnostics for performance troubleshooting. The Strategy Gateway Agent client enables users to enable Realtime Diagnostics, which monitors network speed during the data fetch process.

Best Practices

  1. Install the Gateway Agent Client.

    • Ensure that the machine that you install the Gateway Agent client on is physically close to your warehouse to save on network costs due to reduced data travel distances.

    • It is recommended that you install the Gateway Agent Client on a dedicated machine behind your firewall so that it doesn’t compete with resources from other applications.

    • Supported platforms:

      • Microsoft Windows 10 or later, 64-bit

      • Windows Server 2012 R2 and later versions, including Windows Server 2016, 2019, 2022, and potentially future versions.

  2. Ensure the client machine is on.

    • Continuous operation of the client machine is necessary for the Gateway Agent to function effectively. Make sure it does not go into sleep mode or is shut off unintentionally.

  3. Check the database connection limit.

    • Concurrency for database connections is limited to 100. Plan your operations and database queries accordingly to avoid exceeding this limit.

  4. Check the warehouse type.

    • The Gateway Agent client is only valid for the database type (Driver type) of DBrole. For more information, see Drivers and Connectors.

    • Kerberos and OAUTH requiring third-party interactions are not supported.

  5. Optimize the ODBC/JDBC parameters.

    • Using a Gateway Agent can lead to performance degradation. To mitigate this, fine-tune your ODBC/JDBC parameters.

    • Examples of common parameters to adjust are array size and fetch size, among others.