This post shows an example of a post process event handler in OIM. The example is simple and it shows how the user profile can be updated from the event handler based on the information that is provided by OIM to the event handler.
Use case description: a UDF is created in the user profile and it will hold the user's 'Director'. To simplify the use case, the 'Director' will be the 'manager's manager'. In other words, the UDF will be populated with the information from two levels up in the management chain, the value to be used is the director's login.
The first step is to create the UDF that will hold the data. An authorization policy is also needed, otherwise it will not be possible to update the UDF using the APIs. All the steps below must be done in OIM logged as system administrator.
Creating the UDF:
Showing posts with label oracle identity manager. Show all posts
Showing posts with label oracle identity manager. Show all posts
Wednesday, September 28, 2011
Thursday, April 21, 2011
Developing Workflows to OIM 11g - the basics
OIM & BPEL Working together?
OIM 11g release brought us the powerful world of Oracle BPEL based workflows: from this release on, Oracle BPEL is the workflow engine to be used by OIM in all sorts of requests and their related approval processes. While this integration makes OIM workflows way more powerful and flexible when compared to OIM 9.x, the development process is quite different. The idea for this article is to provide tips for making the development process more straightforward.
First let’s take a look in the main development steps for having a new workflow:
1. Generating basic workflow: OIM provides an utility that can be used to generate a JDeveloper project that contains a basic BPEL Workflow process:
‘ant -f new_project.xml -f new_project.xml’
The ‘new_project.xml’ is located at $OIM_HOME/server/workflows/new-workflow.
You have to provide the application name (which will become the JDeveloper Applciation Name), the project name (which will become the JDeveloper project in the application) and the process name (which needs to be unique across applications and will be the BPEL process name).
The command line will generate a JDeveloper application and you can copy it to wherever your JDeveloper is installed and start working on your customizations.
OIM 11g release brought us the powerful world of Oracle BPEL based workflows: from this release on, Oracle BPEL is the workflow engine to be used by OIM in all sorts of requests and their related approval processes. While this integration makes OIM workflows way more powerful and flexible when compared to OIM 9.x, the development process is quite different. The idea for this article is to provide tips for making the development process more straightforward.
First let’s take a look in the main development steps for having a new workflow:
1. Generating basic workflow: OIM provides an utility that can be used to generate a JDeveloper project that contains a basic BPEL Workflow process:
‘ant -f new_project.xml -f new_project.xml’
The ‘new_project.xml’ is located at $OIM_HOME/server/workflows/new-workflow.
You have to provide the application name (which will become the JDeveloper Applciation Name), the project name (which will become the JDeveloper project in the application) and the process name (which needs to be unique across applications and will be the BPEL process name).
The command line will generate a JDeveloper application and you can copy it to wherever your JDeveloper is installed and start working on your customizations.
Labels:
11g,
BPEL,
deployment,
OIM,
oracle identity manager,
soa,
workflow
Subscribe to:
Posts (Atom)
