Ir para o conteúdo

Oracle EBS (Beta) connector for Jitterbit Integration Studio

Summary

The Oracle EBS (Beta) connector establishes access to Oracle E-Business Suite (EBS).

The Oracle EBS (Beta) connector provides an interface for creating an Oracle EBS (Beta) connection, the foundation used for generating instances of Oracle EBS (Beta) activities. These activities, once configured, interact with Oracle EBS through the connection.

The Oracle EBS (Beta) connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Note

For beta access and to provide feedback, contact the Jitterbit Product Team.

Connector overview

This connector is used to first configure an Oracle EBS (Beta) connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific Oracle EBS (Beta) connection and its activities are referred to as an Oracle EBS (Beta) endpoint:

Oracle EBS (Beta) activity types

  • Execute Procedure: Executes a procedure in an Oracle EBS database and is intended to be used as a target in an operation.

  • Execute Function: Executes a function in an Oracle EBS database and is intended to be used as a target in an operation.

Note

This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

This connector's license class is Enterprise, available as an add-on to your Harmony iPaaS subscription. To enable it, contact your Customer Success Manager. Endpoints created with this connector are included in endpoint usage reporting and count toward your license.

Prerequisites

The Oracle EBS (Beta) 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.

The Oracle EBS (Beta) connector uses the odjbc8 Oracle JDBC driver to interact with Oracle EBS databases. Oracle EBS version 12.2 is supported, including the 19c and 21c databases offered as part of that version.

If using a private agent group, you must manually download and place the odjbc8 Oracle JDBC driver:

  1. Download the odjbc8 Oracle JDBC driver.
  2. Copy the downloaded odjbc8.jar file to $JITTERBIT_HOME/Connectors/Providers/. By default, $JITTERBIT_HOME points to C:\Program Files\Jitterbit Agent\ on Microsoft Windows and /opt/jitterbit/ on Linux.
  3. Restart all agents in the group.

If the driver is not placed in the expected location, the following error with show when testing the connection:

Error

Error connecting to Oracle EBS instance. Error is: The custom provider JAR file is not present in the Jitterbit Private Agent or it is not in the right location ($JITTERBIT_HOME/Connectors/Providers).

The Oracle EBS (Beta) connection requires an application user with the necessary privileges to view and execute the procedures and functions intended for your use case.

Troubleshooting

If you experience issues with the Oracle EBS (Beta) connector, these troubleshooting steps are recommended:

  1. Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  4. If using private agents, you can enable connector verbose logging for this connector by adding this logger configuration entry to your private agent's logback.xml file:

    <logger name="org.jitterbit.connector.oracle.ebs" level="DEBUG"/>
    

    For more information on connector verbose logging, see Verbose logging for connectors using Jitterbit private agents.

  5. If using private agents, you can check the agent logs for more information.