Home
Connectors
This documentation describes the connectors and how they are used.
Schema mapping
Certain applications that use Link require that connectors define a schema mapping.

Connectors
This documentation describes the connectors and how they are used.
- Introduction to the connector wizard
  The Link connector wizard provides an easy way to create REST-based adapters, or connectors, within the user interface, without having to write code or use additional tooling.
- Service based adapters
  Service based adapters are created by referencing a service definition that defines REST endpoints. Endpoints defined in the service become operations of the adapter, and the parameters of the service and its endpoints become the properties of the adapter.
- Flow based connectors
  Flow based connectors are created by referencing a project that contains Link flows.
- Flow and service based connectors
  Connectors that use both flows and services are created by referencing a project that contains Link flows, and a service defiition that defines REST endpoints.
- Hand coded adapters
  Link adapters can be implemented in Java or C/C++. The connector wizard can be used to create the adapter descriptor that is required to expose the properties and operation of the adapter to Link.
- Connector wizard functionality
  The connector wizard provides capabilities from the connectors page of the user interface.
- Connector properties
  Connector properties allow you to configure a connector.
- Operations
  Operations provide a convenient way for you to set the properties of a connector. Selecting an operation automatically configures one or more properties to simplify your experience.
- Schema mapping
  Certain applications that use Link require that connectors define a schema mapping.

Schema mapping

Certain applications that use Link require that connectors define a schema mapping.

The mapping provides a way for Link to get the field definitions that a connector is expecting for a given operation. These field definitions are used in the mapping page of the embedded Link user interface.

Fields can either be static or dynamic. Statically defined fields are fixed in the schema definition. Dynamic fields are obtained by calling an endpoint that produces a list of fields.

A schema mapping definition consists of:

Name – only serves to identify a schema mapping definition.
Condition – conditions can be specified so that alternate schema mappings can be used based for different conditions. The condition specifies an expression which if it evaluates to true will result in the mapping being utilized. Expressions are of the same form as defined for property enablement.
Static Fields – these additional fields, that should always be present in the schema, are defined in a table of static field definitions.
Dynamic Field Endpoint – specifies an endpoint that is called to obtain fields dynamically. Only endpoints that define schema field responses are shown in the list of available endpoints.