Design

Back Next

Using the OData Provider

OData is a REST-based and standardized protocol that provides access to data over the Web. You can use the OData protocol to access data services from the Cloud, including internal data sources like those available with a JDBC connection.

OASIS has standardized on OData V4. Informatica recommends that you use version to use OData V4, and it is the default version.

Your organization can expose OData feeds on an endpoint such as:

https://[host].rt.informaticacloud.com/active-bpel/odata/[version]/[connection name]/[data source name]

For example, these two endpoints expose the sampleparts
table:

OData Version 2
: https://[host].rt.informaticacloud.com/active-bpel/odata/v2/Parts/sampleparts

~or~

OData Version 4
: https://[host].rt.informaticacloud.com/active-bpel/odata/v4/Parts/sampleparts

Data is available in Atom XML format or JSON, including support for the XML content-type.

When the OData schema is generated, note the following:

The IID fields are excluded.

The key fields are added to the OData Key definition.

The schema uses the same type as the native data type for each field.

You can enable OData in connections configured to run on Secure Agents. The Secure Agent, rather than opening a port, opens up an outbound connection to the Informatica Cloud servers through which all communication occurs. The Secure Agent then has access to any on-premises applications or data sources.

If you publish an OData enabled connection to a Secure Agent, the OData URL on the

Connection

page is an Informatica Cloud URL.

You do not see a Secure Agent URL. To construct the Secure Agent URL, replace all text

odata/v4/Oracle

in the Informatica Cloud URL with

https://<host>:<port>/process-engine/

For example, if the Informatica Cloud URL is

https://ps1w2.rt.informaticacloud.com/active-bpel/odata/v4/Oracle

, the Secure Agent URL is

https://localhost:7443/process-engine/odata/v4/Oracle

System Services, Listeners and Connectors