SData Installation
SData Setup & Communication Ports:
Sage 100 SData, a standard Web Service API provided by Sage itself, is essential to configure your Salesforce Org. The GUMU™ Integration uses a Sage 100 SData URL to fetch records from Sage 100 and synchronize them to Salesforce. The SData Web Service URL must be mapped to a domain or subdomain accessible over the web. Salesforce is a cloud-based system and cannot connect to an on-premise system, i.e. Sage 100, without the data port exposed through a static IP. The domain or subdomain will be connected/mapped using Secure Sockets Layer (SSL). This ensures a secured connection to the port of a system that connects to the Sage 100 ERP SData Web Service.
For installing SData, you need the following components:
Pre-installed Sage 100 application
IIS application
SSL certificate
Note: The minimum requirement for installation of SData is the installation of the Sage 100 Application server. The data server and Sage 100 Application server can also be on different servers if it allows us to connect the Sage 100 ERP System with the GUMU™ Integration.
*SData installation is typically done by your Sage consultant or IT team, however if you prefer that we do the SData install for you let us know and we can build it in to your package.
Once you have pre-installed the Sage 100 SData application, the IIS application and SSL certificate you can follow the steps below to install SData on your system:
Navigate to the Sage 100 ERP folder located on your system.
Click on autorun and select your Sage 100 option (Standard, Advance & Premium) to proceed.
Next, select Productivity Applications.
Select Install the Native SData Provider Adapter from the Sage 100 installation setup.
Navigate to IIS Manager, expand the Site folder, and then SData Folder.
Click on MasApp in the Connections Pane.
Click on Basic Settings in the Actions Pane on the right side of the screen.
Click on Connect as, select Specific user and click Set (it will ask for credentials and Windows domain), fill in User name and Password and then click OK.
Click on Advanced Settings in the Actions pane on the right side of the screen.
Check Application Pool Name, Virtual Path & Physical Path Credentials (it should be defined as Windows Domain\Username entered in the Basic Settings).
If the SSL certificate is installed the Enabled Protocols should be set to https (or http if no SSL certificate is installed) and click OK.
Click on Application Pools in the Connections pane.
Select SData App Pool, set Enable 32-Bit Applications to TRUE.
Once the SData provider is installed, login to Sage 100.
Navigate to the Library Master > Setup > System Configuration and check the Enable Native SData Provider and Access within Role Maintenance checkbox.
Once the above checkbox is checked, the Security tab gets enabled in Sage’s Role Maintenance, provide rights to the corresponding resources you wish to access through SData.
To access Sage 100 data externally through SData, navigate to Library Master > Main > Company Maintenance > Preferences tab and check the Allow External Access checkbox (these settings will allow the GUMU™ to access the Sage 100 data).
To check whether the SData URL is working, navigate back to IIS Manager, go to MasApp, and click on Browse*:80(http).
Once everything is set up, you should be able to access the Sage data using the web service URL
http://localhost/SData/MasApp/MasContract/ABC/AR_Customer, where ABC is your Company Code.
Last updated
