OAM/OID integration with r12.2

[Sri]

Dear erman,

What is recommended way of provisioning OID with ebs r12.2?Is it BiDirectional Provisioning (-provisiontype=1)?

Thank you,
Satish.

[ErmanArslansOracleBlog]

This is the default registration type.
This type is to be used when you want a bidirectional provisioning between OID and EBS.
It is highly customizable though.
You can customize it using the  oidprovtool utility.
So it is according to your needs and there is no specific recommendation about it.
If you need a bidirectional provisioning then use it.
If you need bidirectonial provisioning , but also need to modify this, modify it according to your needs.
If you don't need a bidirectional provisioning, then don't use it and use the other registration types, such as  InBound Provisioning, OutBound Provisioning and BiDiNoCreation Provisioning.
In the projects that we implement, we don't use bidirectional provisioning most of the time. We just synchronize AD to OID and then provision EBS users from OID and that 's it.
I recommend you the discuss this with your EBS functional teams and decide..

[Sri]

Thanks for the information.

When will OIM come into picture?Is this required for EBS?

[ErmanArslansOracleBlog]

You know that OAM, OID and OIM are different things, right?

OIM does life cycle management of a user or any similar entity.

OAM is the access manager, where we have abilities such as Single Sign On (SSO),Authentication
Authorization,Real time session management,Auditing and Policy Administration

OID is a LDAP implementation like Active Directory/AD.

So please tell me what you need to do, so I can adress the required solutions for you.

[Sri]

Thanks for providing an update.

In my colleagues project,they have SSO with oam and oid.What he said they also have OIM and each user who needs access to ebs will raise a request in oim.This made me confused to understand.
Will oim uses the same oid database which our OAM also uses?

Thank you

[ErmanArslansOracleBlog]

You may use OIM to provision the users.
So basically it serves user management and reconcilation activities.
I mean, if you have OIM, you can provision accounts to EBS or reconcile users from EBS to OIM...
It is a matter of choice.
It is not required to be used in OAM+OID implementation projects.
It makes the user management easy.

For ex: when an employee is joined to your organization, you just create his user in  OIM and then reflect the necessary user/account definitions to the EBS .. FND_USER account, PERSON definitions etc..
So you manage it from a single place..
I hope you understand what I mean.