Automated Continuous Sage 300 Replication to Google Cloud SQL

Always-on applications rely on automatic failover capabilities and real-time data access. CData Sync integrates live Sage 300 data into your Google Cloud SQL instance, allowing you to consolidate all of your data into a single location for archiving, reporting, analytics, machine learning, artificial intelligence and more.

Configure Google Cloud SQL as a Replication Destination

Using CData Sync, you can replicate Sage 300 data to Google Cloud SQL. To add a replication destination, navigate to the Connections tab. Then select the appropriate destination based on your Google Cloud SQL service (MySQL, PostgreSQL, or SQL Server).

MySQL

1. Click Add Connection.
2. Select MySQL as a destination.
3. Enter the necessary connection properties. To connect to MySQL, set the following:
   • Server: The IP address or domain name of the server you want to connect to.
   • Port: The port where the server is running.
   • User: The username of a user with read/write access to the database.
   • Password: The password of a user with read/write access to the database.
   • Database: The name of the database.
4. Click Test Connection to ensure that the connection is configured properly.
5. Click Save Changes.

Jump to configuring the Sage 300 connection.

PostgreSQL

1. Click Add Connection.
2. Select PostgreSQL as a destination.
3. Enter the necessary connection properties. To connect to PostgreSQL, set the following connection properties (CData Sync ships with the Npgsql ADO.NET Provider for PostgreSQL):
   • Server: The address of the server hosting the PostgreSQL database.
   • Port: The port used to connect to the server hosting the PostgreSQL database.
   • User: The user ID provided for authentication with the PostgreSQL database.
   • Password: The password provided for authentication with the PostgreSQL database.
   • Database: The name of the database.
4. Click Test Connection to ensure that the connection is configured properly.
5. Click Save Changes.

Jump to configuring the Sage 300 connection.

SQL Server

1. Click Add Connection.
2. Select SQL Server as a destination.
3. Enter the necessary connection properties. To connect to SQL Server, set the following:
   • Server: The name or network address of the computer running SQL Server.
   • User: The username provided for authentication with SQL Server, if using forms authentication.
   • Password: The password provided for authentication with SQL Server, if using forms authentication.
   • Database: The name of the SQL Server database.

   Java Edition

   The Java version requires the Microsoft SQL Server JDBC Driver, which can be downloaded from the Microsoft Download Center. Copy the JDBC driver to the lib folder of your Java Web server to make a connection.

4. Click Test Connection to ensure that the connection is configured properly.
5. Click Save Changes.

Jump to configuring the Sage 300 connection.

Configure the Sage 300 Connection

You can configure a connection to Sage 300 from the Connections tab. To add a connection to your Sage 300 account, navigate to the Connections tab.

1. Click Add Connection.
2. Select a source (Sage 300).
3. Configure the connection properties.
   
   

   Sage 300 requires some initial setup in order to communicate over the Sage 300 Web API.

   • Set up the security groups for the Sage 300 user. Give the Sage 300 user access to the option under Security Groups (per each module required).
   • Edit both web.config files in the /Online/Web and /Online/WebApi folders; change the key AllowWebApiAccessForAdmin to true. Restart the webAPI app-pool for the settings to take.
   • Once the user access is configured, click https://server/Sage300WebApi/ to ensure access to the web API.

   Authenticate to Sage 300 using Basic authentication.

   Connect Using Basic Authentication

   You must provide values for the following properties to successfully authenticate to Sage 300. Note that the provider reuses the session opened by Sage 300 using cookies. This means that your credentials are used only on the first request to open the session. After that, cookies returned from Sage 300 are used for authentication.

   • Url: Set this to the url of the server hosting Sage 300. Construct a URL for the Sage 300 Web API as follows: {protocol}://{host-application-path}/v{version}/{tenant}/ For example, http://localhost/Sage300WebApi/v1.0/-/.
   • User: Set this to the username of your account.
   • Password: Set this to the password of your account.
4. Click Connect to ensure that the connection is configured properly.
5. Click Save Changes.

Configure Replication Queries

CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.

Replicate Entire Tables

To replicate an entire table, click Add Tables in the Tables section, choose the table(s) you wish to replicate, and click Add Selected Tables.

Customize Your Replication

You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication.

Schedule Your Replication

In the Schedule section, you can schedule a job to run automatically, configuring the job to run after specified intervals ranging from once every 10 minutes to once every month.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Sage 300 data to Google Cloud SQL.