Integrate Sage 300 with External Services using SnapLogic

SnapLogic is an integration platform-as-a-service (iPaaS) that allows users to create data integration flows with no code. When paired with the CData JDBC Drivers, users get access to live data from more than 250+ SaaS, Big Data and NoSQL sources, including Sage 300, in their SnapLogic workflows.

With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live Sage 300 data. When platforms issue complex SQL queries to Sage 300, the driver pushes supported SQL operations, like filters and aggregations, directly to Sage 300 and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying lets you work with Sage 300 data using native data types.

Connect to Sage 300 in SnapLogic

To connect to Sage 300 data in SnapLogic, download and install the CData Sage 300 JDBC Driver. Follow the installation dialog. When the installation is complete, the JAR file can be found in the installation directory (C:/Program Files/CData/CData JDBC Driver for Sage 300/lib by default).

Upload the Sage 300 JDBC Driver

After installation, upload the JDBC JAR file to a location in SnapLogic (for example, projects/Jerod Johnson) from the Manager tab.

Configure the Connection

Once the JDBC Driver is uploaded, we can create the connection to Sage 300.

1. Navigate to the Designer tab
2. Expand "JDBC" from Snaps and drag a "Generic JDBC - Select" snap onto the designer 👁 Adding a Generic JDBC snap onto the designer
   
3. Click Add Account (or select an existing one) and click "Continue"
4. In the next form, configure the JDBC connection properties:
   • Under JDBC JARs, add the JAR file we previously uploaded
   • Set JDBC Driver Class to cdata.jdbc.sage300.Sage300Driver

   • Set JDBC URL to a JDBC connection string for the Sage 300 JDBC Driver, for example:

     jdbc:sage300:User=SAMPLE;Password=password;URL=http://127.0.0.1/Sage300WebApi/v1/-/;Company=SAMINC;RTK=XXXXXX;

     NOTE: RTK is a trial or full key. Contact our Support team for more information. 👁 Configuring a connection (Salesforce is shown)
     

     Built-In Connection String Designer

     For assistance in constructing the JDBC URL, use the connection string designer built into the Sage 300 JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

     java -jar cdata.jdbc.sage300.jar

     Fill in the connection properties and copy the connection string to the clipboard.

     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
     • 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.
     👁 Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
     
5. After entering the connection properties, click "Validate" and "Apply"

Read Sage 300 Data

In the form that opens after validating and applying the connection, configure your query.

• Set Schema name to "Sage300"
• Set Table name to a table for Sage 300 using the schema name, for example: "Sage300"."OEInvoices" (use the drop-down to see the full list of available tables)
• Add Output fields for each item you wish to work with from the table

Save the Generic JDBC - Select snap.

With connection and query configured, click the end of the snap to preview the data (highlighted below).

Once you confirm the results are what you expect, you can add additional snaps to funnel your Sage 300 data to another endpoint.

Piping Sage 300 Data to External Services

For this article, we will load data in a Google Spreadsheet. You can use any of the supported snaps, or even use a Generic JDBC snap with another CData JDBC Driver, to move data into an external service.

1. Start by dropping a "Worksheet Writer" snap onto the end of the "Generic JDBC - Select" snap.
2. Add an account to connect to Google Sheets 👁 Connecting to Google
   
3. Configure the Worksheet Writer snap to write your Sage 300 data to a Google Spreadsheet 👁 Writing to a Google Spreadsheet
   

You can now execute the fully configured pipeline to extract data from Sage 300 and push it into a Google Spreadsheet.

More Information & Free Trial

Using the CData JDBC Driver for Sage 300 you can create a pipeline in SnapLogic for integrating Sage 300 data with external services. For more information about connecting to Sage 300, check at our CData JDBC Driver for Sage 300 page. Download a free, 30 day trial of the CData JDBC Driver for Sage 300 and get started today.