Skip to content

Sage 100 Setup

Sage 100 (formerly MAS 90 and MAS 200) is an on-premises Windows ERP with no public API. superglue reaches it through the Secure Gateway, a small program that runs on a Windows machine in the client’s network. On that machine, the gateway runs short scripts that use the supported Sage 100 Business Object Interface. The agent reads customers, vendors, items, orders, and other Sage 100 data this way.

This guide walks you through the setup. Most of the time goes to the steps that the client’s IT must do on the Sage machine.

  • No inbound firewall rules. The gateway opens one outbound encrypted connection to superglue. Nothing on the client’s network is exposed to the internet.
  • Runs as one Sage user. Every script logs on to Sage 100 as the user that you enter in superglue. The agent can only see and change what that user’s role allows.
  • One license seat per run. Each script uses one Sage 100 user license while it runs and signs out at the end.
  • Approval before writes. The agent reads freely. In the default Ask for permission mode, it asks before any script that writes to Sage 100.

The client’s IT and Sage administrator do these steps. They are made in Windows and in the Sage 100 desktop programs on the client’s network, so the agent cannot do them in its own browser.

  • A Windows machine with Sage 100. The gateway must run on a Windows machine where Sage 100 Workstation Setup is complete, for example the Sage server or a terminal server. The Business Object Interface exists only on such a machine.
  • Administrator rights on that machine, once. The gateway installs as a Windows service. Windows asks for administrator rights during the installation.
  • Outbound internet access. The machine must reach superglue over port 443. No inbound port is needed.
  • A dedicated Sage 100 user. Ask the Sage administrator to create a Sage user for superglue with access to the modules in scope. Do not use a person’s own Sage user.
  • The company code. The code of each Sage 100 company that the project needs, for example ABC for the Sage demo company.
  • The path to the Sage 100 home folder. The full path to the MAS90\Home folder on that machine, for example C:\Sage\Sage100\MAS90\Home. Use the Home folder, not the MAS90 folder.
  1. Ask the agent to connect Sage 100

    1. Start a session from the task, or click New session.
    2. Tell the agent: “Connect the client’s Sage 100 server.”
    3. The agent can install the Sage 100 integration. It adds a setup playbook and a connection test. Accept it.
  2. Set up the gateway on the Sage machine

    1. The agent shows the gateway setup in the chat. It turns on the script runner, which Sage 100 needs, and names the gateway, for example after the client or the site. To use another name, tell the agent. It shows a new setup.
    2. On the Sage machine, select Download for Windows, or use Copy link and open the link there.
    3. Open the downloaded superglue-gateway-windows.exe. It opens a page in the browser.
    4. Paste the one-time code from the chat and select Connect. Windows asks once for administrator rights.
    5. Keep the chat open. The setup shows when the gateway is connected and the agent continues. It attaches the gateway to the Sage 100 connection.

    If the client’s IT prefers a script, turn on Install with a command and give them the PowerShell command. The code and the command contain a secret. Use them only on the Sage machine.

  3. Enter the Sage 100 values

    1. The agent opens the secure connection form.
    2. Enter the path to the MAS90\Home folder, the company code, and the name and password of the Sage user. The values go directly to the connection. They do not appear in the chat.
  4. Test the connection

    1. The agent runs the connection test. It logs on to Sage 100, opens the company, and reads the first customer.
    2. To test it yourself, tell the agent: “List five A/R customers from Sage 100.” If you get customers back, the setup works.

If the client cannot install the gateway, superglue can work with exports. Ask the client to export the data from Sage 100, for example as Excel or CSV files, and attach them in the chat. The agent reads them like any other upload.

Exports are a copy at one point in time. superglue cannot write back to Sage 100 from an export, and you need new exports to get later changes.

Sage 100 Premium keeps its data in a Microsoft SQL Server database. superglue can also read that database through the gateway. In that case, the gateway machine needs network access to the SQL Server, and the client’s database administrator creates a SQL Server login for superglue with read access to the company database.

The gateway forwards one TCP port. If SQL Server runs as a named instance, it must listen on a fixed TCP port. The agent cannot reach a named instance through SQL Server Browser.

  • Windows only. The script runner works only on Windows. The gateway must run on the Sage 100 machine itself, not on another server in the network.
  • License seats. Each run uses one Sage 100 user license while it runs. If all seats are in use, the test reports that no license is available. Ask users to sign out, or run the task later.
  • Record locks. A write fails when the record is open in the Sage 100 desktop or held by another session. The agent reports the lock and does not retry.
  • Run time. A script stops when the step time limit is reached. Large reads go in several smaller runs.

To remove access right away, do one of these steps:

  • In the Sage 100 desktop, make the superglue user inactive or delete it.
  • In superglue, open the Sage 100 connection on the Connections page. Under Secure Gateway in its advanced settings, select Remove gateway. This disconnects the gateway and deletes the API keys that you select.

To remove the gateway from the machine, open PowerShell as administrator and run:

Terminal window
& "C:\Program Files\superglue Gateway\superglue-gateway.exe" uninstall

You can delete the Sage 100 connection in its connection panel on the Connections page.

Why must the gateway run on the Sage 100 machine?

Section titled “Why must the gateway run on the Sage 100 machine?”

The Business Object Interface is a local Windows component that Sage 100 Workstation Setup installs. A gateway on another machine cannot use it. If the test reports COM error 0x80040154, the gateway runs on a machine without Sage 100 Workstation Setup.

Sage 100 returns the reason with the error, for example a wrong password, a missing role permission, or a wrong company code. The agent shows that reason. Check the value in the connection, then ask the Sage administrator to check the user’s role.

Yes. The agent writes through the Sage 100 business objects. It asks for your approval before each script that writes. Try writes in a test company first.

How do I connect several Sage 100 companies?

Section titled “How do I connect several Sage 100 companies?”

The company code is part of the connection. Add one connection for each company and name it after the company. The connections can use the same gateway.

Does the client have to keep a person signed in to Sage 100?

Section titled “Does the client have to keep a person signed in to Sage 100?”

No. Each script logs on as the superglue user and signs out at the end. The gateway runs as a Windows service and starts with the machine.