Design

Back Next

Native connectors

Native connectors are out-of-the-box connectors that are used to connect to third-party applications.

You can create the following types of native connectors:

Application Connectors

Application Integration

connectors are designed to access data to and from the cloud for each of your applications. You can use the following application connectors:

JDBC: Java Database Connectivity (JDBC) is a Java API that enables Java programs to execute SQL statements and interact with any SQL-compliant database. JDBC makes it possible to write a single database application that can run on different platforms and interact with different DBMS systems. Ensure that you use the latest database driver version that your database supports.
Informatica
provides two JDBC connectors: JDBC and JDBC_IC. Only the JDBC_IC connector is used by
Application Integration
.

OData: Use OData Connector to integrate systems, such as SharePoint and Team Foundation Server that are OData compliant, with other on-premise or cloud applications. It is a standardized protocol for creating and consuming data APIs. OData builds on core protocols, such as HTTP, and commonly accepted methodologies, such as REST.
Salesforce: Use Salesforce Connector to create guides and processes that read information from and write information to Salesforce. Outbound messages from Salesforce can trigger processes that perform background processing of information and write information back to Salesforce.
SAP: Use SAP BAPI Connector to integrate with SAP BAPIs and read, create, change, or delete data in SAP. SAP BAPI Connector is available as a service call in Application Integration. For example, to update the sales order data in SAP, you can configure an SAP BAPI connection to access the BAPI_SALESORDER_CHANGE function.
Workday: Use Workday Connector to integrate data with Workday applications. For example, you can retrieve information about an employee and th employee's dependents or onboard a new hire.

Message-based Connectors

Message-based connectors are designed so you can configure queue-based message brokers, such as ActiveMQ and JMS. You can use the following message-based connectors:

AMQP: Use the AMQP Connects to an AMQP stream to send messages to a queue or delete messages from a queue.
Amazon SQS: Connects to an Amazon SQS stream to send messages to a queue, receive messages from a queue, or delete messages from a queue.

Listener-based Connectors

Listener-based connectors are designed to perform the following tasks:

Monitor file-based systems for files or objects on a file system or other type of storage. You can retrieve files and process the contents of the files or perform file operations, such as moving or reading file metadata. For example, you can parse a comma-delimited file, make the file contents available in a process object as XML, and archive the processed file in another directory. The file or object metadata, such as the number of rows or time stamp, is also available in a process object. The File, FTP, and Amazon S3 connectors belong to this category.

Access event services to perform tasks, such as reading XML from a process object and creating comma-delimited files or reading binary files from a process stream and writing that binary content to the target file system.

You can use the following listener-based connectors:

File: Provides connectivity between Application Integration and file systems to monitor file systems, move files, read and write content from files, and handle processed files.

FTP: Provides connectivity between Application Integration and remote FTP servers.

Amazon S3: Connects to files stored in an Amazon S3 storage system.
Kafka: Connects to a Kafka stream to read data from or write data to a topic.