Access Sage 300 Data as OData Feeds in Tableau

The CData API Server, when paired with the ADO.NET Provider for Sage 300 (or any of 200+ other ADO.NET Providers), provides Sage 300 data as OData Web services. This article will explain how to use the API Server to provide the underlying connectivity to Sage 300 data in Tableau's business intelligence tool.

Set Up the API Server

Follow the steps below to begin producing secure Sage 300 OData services:

Deploy

The API Server runs on your own server. On Windows, you can deploy using the stand-alone server or IIS. On a Java servlet container, drop in the API Server WAR file. See the help documentation for more information and how-tos.

The API Server is also easy to deploy on Microsoft Azure, Amazon EC2, and Heroku.

Connect to Sage 300

After you deploy the API Server and the ADO.NET Provider for Sage 300, provide authentication values and other connection properties needed to connect to Sage 300 by clicking Settings -> Connections and adding a new connection in the API Server administration console.

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.

When you configure the connection, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

You can then choose the Sage 300 entities you want to allow the API Server to access by clicking Settings -> Resources.

Additionally, click Settings -> Server and set the Default Format to XML (Atom) for compatibility with Tableau.

Authorize API Server Users

After determining the OData services you want to produce, authorize users by clicking Settings -> Users. The API Server uses authtoken-based authentication and supports the major authentication schemes. Access can also be restricted based on IP address; by default only connections to the local machine are allowed. You can authenticate as well as encrypt connections with SSL.

Create Real-Time Sage 300 Data Visualizations

Follow the steps below to create data visualizations based on the remote Sage 300 data:

1. In Tableau, select 'Connect to data'. In the 'On a server' section, click OData.

   

2. In the resulting wizard, enter the URL of the OData endpoint for the API Server. Append the name of the table you want to access to the OData entry URL. For example:

   https://your-server/api.rsc/OEInvoices
3. Select the 'Use a Username and Password' option and enter the username and password of a user who has access to the API Server.

4. Tableau uses the table metadata exposed by the API Server to detect dimension and measure columns.

   

5. To view the Sage 300 data, right-click under the table name in the Data section of the dashboard and select the View Data option. The Sage 300 data will appear in Tableau.