Sage 200 Connector¶
The Jitterbit Harmony Sage 200 Connector establishes access to Sage 200.
The Sage 200 connector provides an interface for creating a Sage 200 connection, the foundation used for generating instances of Sage 200 activities. Activities interact with Sage 200 through the connection and are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).
The Sage 200 connector is accessed from the design component palette's Connectivity tab (see Connectors in Design Component Palette).
This connector can be used only with Private Agents. In addition, it is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.
See Jitterbit's comprehensive Sage 200 connection documentation, which is provided at a dedicated website. Configuration details such as these are included:
- Getting Started: Initial steps for establishing a connection.
- Advanced Features: User-defined views and SSL configuration.
- Data Model: The data model that the connector uses to represent the endpoint.
- Connection String Options: Properties that can be defined to configure the connection for both basic and advanced configurations.
Together, a specific Sage 200 connection and its activities are referred to as a Sage 200 endpoint:
- Query: Retrieves records from a table at Sage 200 and is intended to be used as a source in an operation. (Generically documented in Query Activities.)
Prerequisites and Supported API Versions¶
The Sage 200 connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.
This connector requires the use of a Private Agent.
Refer to the documentation for information on the schema nodes and fields.
3-legged OAuth Authentication¶
3-legged OAuth authentication is supported as described on Connections under three-legged OAuth authentication.
Verbose logging can be enabled for this connector. See Verbose Logging for Connectors for details.
Invoke verbose logging for this connector using this configuration entry:
<logger name="org.jitterbit.connector.verbose.logging.Sage200" level="TRACE"/>