Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Use the CData ODBC Driver for Sage 300 in MicroStrategy
Connect to Sage 300 data in MicroStrategy Developer using the CData ODBC Driver for Sage 300.
MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for Sage 300, you gain database-like access to live Sage 300 data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through creating a database instance for Sage 300 in MicroStrategy Developer and creating a Warehouse Catalog based on Sage 300 data.
The CData ODBC driver offers unmatched performance for interacting with live Sage 300 data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy 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 (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze Sage 300 data using native MicroStrategy data types.
Connect to Sage 300 as an ODBC Data Source
Information for connecting to Sage 300 follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Sage 300 must be installed on the machine hosting the connected MicroStrategy Intelligence Server).
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 DSN, 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.
Windows
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
Linux
If you are installing the CData ODBC Driver for Sage 300 in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.
/etc/odbc.ini
[CData Sage300 Sys]
Driver = CData ODBC Driver for Sage 300
Description = My Description
User = SAMPLE
Password = password
URL = http://127.0.0.1/Sage300WebApi/v1/-/
Company = SAMINC
For specific information on using these configuration files, please refer to the help documentation (installed and found online).
Create a Sage 300 Database Instance in MicroStrategy Developer
You can connect to Sage 300 in MicroStrategy Developer by adding a database instance based on the CData ODBC Driver for Sage 300.*
- Open MicroStrategy Developer and select a Project Source.
- Navigate to Administration -> Configuration Managers -> Database Instances and right-click to add a new instance.
- Name the instance, select Generic DBMS as the database connection type, and create a new database connection.
- In the database connection wizard, name the connection and create a new Database Login name, using filler values for the user and password.
- Select the DSN that you configured earlier as the ODBC data source (i.e., CData Sage300 Sys).
- Select the newly created database connection.
- In the Project Source, right-click the project and open the Project configuration.
- Navigate to Database Instances and select the newly created database instance.
- Close MicroStrategy Developer and restart the connected MicroStrategy Intelligence Server to complete the database instance creation.
With the database instance configured, you will now be able to connect to Sage 300 data from the Warehouse Catalog and Data Import.
Connect to Sage 300 Data from the Warehouse Catalog
Once you have created a database instance based on the ODBC Driver for Sage 300, you can connect to data from the Warehouse Catalog.
- Select your project and click Schema -> Warehouse Catalog.
- In the Read Settings for the Catalog, click Settings and set the queries to retrieve the schema:
- To retrieve the list of tables, use the following query:
SELECT CatalogName NAME_SPACE, TableName TAB_NAME FROM SYS_TABLES
- To retrieve the list of columns for selected tables, use the following query:
SELECT DISTINCT CatalogName NAME_SPACE, TableName TAB_NAME, ColumnName COL_NAME, DataTypeName DATA_TYPE, Length DATA_LEN, NumericPrecision DATA_PREC, NumericScale DATA_SCALE FROM SYS_TABLECOLUMNS WHERE TableName IN (#TABLE_LIST#) ORDER BY 1,2,3
- To retrieve the list of tables, use the following query:
- Select tables to be used in the project.
If you are interested in connecting to Sage 300 from other MicroStrategy products, you can read about connecting from MicroStrategy Web and connecting from MicroStrategy Desktop.
Note: connecting using a ODBC driver requires a 3- or 4-tier architecture.