How Your Adapters Differ from Oracle Adapters
Oracle adapters and non-Oracle adapters offer nearly identical experiences to integration developers. For example, the type of information that integration developers specify when creating connections is the same, and the monitoring capabilities are the same. However, be aware of some key differences.
Area | Oracle adapters | Non-Oracle adapters |
---|---|---|
Functionality |
Oracle adapters offer a rich experience with complete functionality. They cater to a wide breadth of use cases and are generally suitable for most audiences. |
Non-Oracle adapters typically offer a more targeted functionality for specific use cases. |
User experience for endpoint configuration |
The wizard that an integration developer uses to configure an endpoint has three or more sections, depending on the adapter's complexity and supported functionality. |
The wizard that an integration developer uses to configure an endpoint always has three sections: Basic Information, Configuration, and Summary. |
Version numbers |
The version numbers for Oracle adapters correspond to the version numbers of functional releases. For example, 23.12 or 24.02. |
The version numbers for non-Oracle adapters follow semantic versioning rules. Version number typically have 3 places, such as 1.2.3. Note: Currently, the Rapid Adapter Builder doesn't allow a major version change. |
Backward compatibility |
Adapter updates are backward compatible. |
Adapter updates are backward compatible. Note: Although the Rapid Adapter Builder attempts to detect violation of backward compatibility by analyzing the adapter definition document's updates (such as, changes to set of actions, triggers, their contracts, and the security-policy definitions), the updates are not guaranteed to be backward compatible. |
Maintenance and support |
Oracle maintains and supports its own adapters. |
Oracle does not maintain or support non-Oracle adapters. |