Skip to main content

Siteline + Sage 300 CRE - Setup

One-time setup for the Siteline + Sage 300 CRE integration

Written by Bradley LaFave

Intended audience: technical user. This page covers the one-time installation and server configuration required to keep the Sage 300 CRE connector online. Day-to-day billing workflows are covered on the Usage page.

The Sage 300 CRE integration connects Siteline to your on-prem Sage environment through a connector that runs on the Sage server. The connector must be running at all times for the integration to work. Because the connector is a desktop application, simply closing the server session closes the app and takes the integration offline.

To prevent this, configure the connector as a background task so it stays running independently of whether a user is signed in to the server.

Recommended: run the connector as a scheduled task

Follow Agave's step-by-step guide:

Below are Siteline's additional notes on specific steps in that guide.

Step 3: run whether the user is logged in or not

Even if the user who configured the task is not logged in, you want the task to keep running β€” this is what keeps the Agave connector open. Otherwise, if the user is not logged in (usually the IT person who set this up), the task scheduler will not continue to run.

Task scheduler: run whether user is logged on or not

Step 5: do not stop the task after a set number of days

Ensure that the task does not stop running if it runs longer than a specific amount of days, otherwise the connector will eventually go offline.

Task scheduler: do not stop the task

Step 7: point at the actual executable, not the desktop shortcut

Do not use the desktop file path β€” use the actual file path to the Agave Connector executable. By using the actual file path, the task will execute and start the Agave connector as a background process. You want to ensure you're running the local program as opposed to the Desktop application itself.

Task scheduler: use the actual executable path

Step 8: task settings and retry behavior

The task settings should match the screenshot below. You also want to select if the task fails, restart every 10 minutes up to 3 times.

Task scheduler: settings and retry behavior

Step 10: confirm the task is running, not just ready

Many times folks will have the task in a "ready" state rather than a run state. After configuring, confirm the task shows as Running.

Task scheduler: running state

Step 11: close the desktop application

We recommend you close out of the desktop application at this point by clicking the X for the Agave connector. The scheduled task will keep the background process running.

Did this answer your question?