My Oracle Support Banner

ODI 12c Toolbox - OdiInvokeRESTfulService is not Allowing Empty Context Property (Doc ID 2628981.1)

Last updated on MARCH 12, 2021

Applies to:

Oracle Data Integrator - Version 12.2.1.2.6 to 12.2.1.4.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

In Oracle Data Integrator (ODI) 12c, using OdiInvokeRESTfulService does not allow "empty" context when a logical schema is set.

According to the description documentation an empty context should be possible, in which case the execution context should be used. However, the context always defaults to the global context.

See simulation mode below:

Target Context Code:
<CONTEXT CODE>
Target Command:
OdiInvokeRESTfulService "-CONTEXT=GLOBAL" "-LSCHEMA=<LOGICAL SCHEMA NAME>"

Even though the context code is set to <CONTEXT CODE> the OdiInvokeRESTfulService is command is always executed with "-CONTEXT=GLOBAL"

To reproduce the behavior:

  1. Create a Logical Schema for RESTfull service (physical one isn't necessary).
  2. Create a Package.
  3. Create an OdiInvokeRESTfulService step in the Package.
  4. Choose Logical Schema in the Properties.
  5. Set Context to <Empty> isn't possible and "Global" is automatically set instead.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.