11gR1 How to Use OIM Request Service APIs in Your Custom SOA Composite
(Doc ID 2189842.1)
Last updated on OCTOBER 08, 2021
Applies to:Identity Manager - Version 184.108.40.206.0 to 220.127.116.11.11 [Release 11g]
Information in this document applies to any platform.
This note describes how to make the OIM request service APIs available to your OIM SOA approval composite as detailed in the Developers Guides referenced below.
Developer's Guide for Oracle Identity Manager (18.104.22.168.0)
22 Using Oracle Identity Manager APIs from SOA Composites
Developer's Guide for Oracle Identity Manager (22.214.171.124.0)
26 Using Oracle Identity Manager APIs in SOA Composites
This is because such callouts would internally involve the use of datasources and as such are not thread safe with respect to transaction handling. The exposed request service methods detailed in the Developers Guide above do not cause such issues.
This document is specific to 126.96.36.199 and 188.8.131.52 OIM ONLY!!
From OIM version 184.108.40.206.x and up, any additional Request, User, Resource or Catalog Data that is needed in the approval process must either be passed as a user defined field object when the request is created or it can be obtained using the exposed methods from OIMs Request Service. Steps to configure the Partnerlink Adapter to connect to the Request Service can be found in the Developers Guides under the section like:Developing Workflows for Approval and Manual Provisioning > Making Request and Catalog Data Available to the BPEL Process.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!