Managing Environments and Agents

Managing Environments and Agents

Audience: Administrators, IT teams

Applies to: All environments (Cloud and On-Premise)

Last reviewed: 2026

1. Cloud vs. On-Premise Agent

Factor Cloud Agent vs. On-Premise Agent
Provisioned by APPSeCONNECT automatically | You (installed on your Windows server)
Best for Cloud apps: Shopify, WooCommerce, Salesforce, HubSpot, Zoho | On-Premise apps: SAP B1, Dynamics NAV, SQL Server, on-site ERPs
Requires server No | Yes — Windows Server 2016+ or Windows 10+
Network APPSeCONNECT connects outbound to cloud apps | Your server connects to your local app (SAP DI Server, SQL, etc.)
Maintenance Zero (managed by APPSeCONNECT) | You manage Windows updates, restarts, and InSync Service health
Real-time support Yes | Yes (if InSync Service is running)

2. Installing the On-Premise Agent

  1. Download the APPSeCONNECT On-Premise Agent installer from your portal under Environments.

  2. Run the installer on your Windows server as Administrator.

  3. During installation, enter your APPSeCONNECT Organisation credentials to link the agent to your account.

  4. After installation, the APPSeCONNECT InSync Service starts automatically.

  5. In the portal, go to Environments — your server should appear with status Online.

NOTE: The On-Premise Agent must be installed on the same network as your on-premise application. It must be able to reach the application server by hostname or IP.

3. SAP Business One Prerequisites

SAP B1 integrations require these services running on your SAP server:

Requirement Details
SAP DI Server Must be running on port 30000 (default). APPSeCONNECT uses this to read/write SAP data.
SLD (Software Landscape Directory) Required for SAP B1 connector validation. If SLD is stopped, connector validation fails.
SBOeConnect Add-On Must be registered in SAP B1 at the correct version for your SAP B1 patch level.
User permissions The SAP user must have full authorisation for all object types being synced.

WARNING: The most common SAP B1 error is ‘Cannot connect to DI Server’ — either the DI Server service is stopped, or the firewall is blocking port 30000. Check both before raising a ticket.

SAP DI Server restart steps: (1) Log in to SAP B1 server. (2) Open services.msc. (3) Find ‘SAP Business One DI Server’ and Restart. (4) Also restart SLD if visible. (5) Re-validate the SAP B1 connector in APPSeCONNECT.

4. On-Premise Agent: InSync Service Management

The InSync Service must be running for all ProcessFlow executions and real-time flows.

InSync Service won’t start: (1) Open services.msc. (2) Locate ‘APPSeCONNECT InSync Service’. (3) Check Log On tab — service account needs ‘Log on as a service’ rights. (4) Check Windows Event Viewer for details. Common causes: .NET 4.7.2+ missing, insufficient disk space, or corrupted files. Clear old logs from C:\Program Files (x86)\APPSeCONNECT\ or reinstall the agent.

Real-Time flow shows ‘Service Not Available’: (1) Confirm InSync Service is running. (2) Check agent status in Environments. (3) If Offline, restart InSync Service and wait 60 seconds. (4) If Online but failing, undeploy and redeploy the ProcessFlow. (5) Verify the real-time webhook URL still points to APPSeCONNECT.

5. Credential and Token Management

Always update APPSeCONNECT immediately when: an API token is regenerated, a password changes, an OAuth token expires, or an SSL/TLS certificate is renewed.

Amazon LWA Credential Rotation: When you receive an Amazon LWA rotation email, act within the deadline. Go to Amazon Seller Central → Apps & Services → Manage Your Apps → generate new LWA credentials (Client ID, Client Secret). Update in APPSeCONNECT under Apps → My Apps → Amazon. Validate before the deadline. The error ‘invalid_client’ in Snapshot confirms expired LWA credentials.

HubSpot Token Expiry: Go to HubSpot → Settings → Integrations → Private Apps. Generate a new token with the same scopes. Update in APPSeCONNECT under Apps → My Apps → HubSpot. Validate and redeploy affected ProcessFlows.

6. Environment Health Monitoring

  • Set up email alerts: Settings → Notifications for sync failure and agent offline events.

  • Review the Sync Info dashboard daily — error spikes indicate connection or data quality issues.

  • For critical integrations, configure a scheduled health check ProcessFlow that sends a test record hourly.

  • Keep your On-Premise Agent updated for bug fixes and API compatibility.

TIP: A green agent status means ProcessFlows can execute. Orange or red means immediate attention is required.

    • Related Articles

    • Product Features & How-Tos

      Audience: All users Applies to: All plans Last reviewed: 2026 This article explains how to use APPSeCONNECT's core features and walks through common how-to tasks. Use it as a reference guide for day-to-day operation. 1. ProcessFlow — Core Concepts A ...

    • Billing & Account Management

      Audience: Account administrators and billing contacts Applies to: All plans Last reviewed: 2026 This article covers billing, subscription management, plan changes, invoicing, and account administration for APPSeCONNECT. 1. Plans and Pricing Overview ...

    • APPSeCONNECT Troubleshooting Guide

      Audience: All users — customers and CS/support teams Applies to: All integrations and environments Last reviewed: 2026 This guide covers the most frequent issues reported by APPSeCONNECT customers, organized by category. For each issue you will find: ...