Loading Apps User to OID

Hello everyone!!!

I have been out of blogging for couple of months due to hefty work schedule and couple of long vacations. I am back to applications DBA arena. I hope you will enjoy the series of articles coming. As usual most are going to be related to R12.

This is in continuation with the article I have published earlier(Integrating R12 with 10g AS OID)
http://applicationsdba.blogspot.com/2007/06/ssooid-integration-in-r12.html

This article is all about loading Apps User to OID.

Assumptions:

Fresh implementation, where OID was installed and integrated with R12 & No users present in OID.

Steps involved in this migrations are given here:

Step1: Create Intermediate LDIF file

1) Login to Appl top owner account, Source the environemnt (check classpath points appropirately)

2) Use AppsUserExport to extract user information --> exported information will be stored as intermediate LDIF file (LDIF -- LDAP Data Interchange Format)

java oracle.apps.fnd.oid.AppsUserExport \ [-v]
–dbc \
-o \
-pwd \
-g
[-l ]

3) Check the logfile for any errors.

4) Users will not uploaded to intermediate LDIF can be identified by
select user_name from FND_USER where user_id<10;
(Those users who have set as 'LOCAL' for the profile APPS_SSO_LOCAL_LOGIN or 'N' for the profile APPS_SSO_LDAP_SYNC, will not be migrated. )

in R12 Above query returns

ANONYMOUS
SYSADMIN
INITIAL SETUP
FEEDER SYSTEM
CONCURRENT MANAGER
APPSMGR
GUEST
WIZARD
INDUSTRY DATA


Step2: Converting Intermediate LDIF File to Final LDIF File

1) Login in as AS 10g Infra Tier owner, and Transfer the file created by the step 1 to AS instance infra tier file system

2) User LDIF migrator utility to migrate intermediate LDIF file to final LDIF file.

ldifmigrator "input_file=data.txt" \
"output_file=data.ldif" \
"s_UserContainerDN=cn=users,dc=us,dc=oracle,dc=com" \
"s_UserNicknameAttribute=uid"

Step 3: Loading Final LDIF file into Oracle Internet Directory

1) Make sure OID processes are down. Use opmn process to bring down the services.

$ORACLE_HOME/opmn/bin/opmnctl stopall

2) Run the bulkload utility with the –check and –generate options to verify that
there are no duplicate users.

For example:
bulkload.sh –connect -check –generate qualified path to LDIF file>

3) If the log file indicates duplicate users, manually remove these users from the LDIF
file. Run the step 2 after removing duplicate entries.

4) Use OID bulk Load utility to load the user information to OID.

bulkload.sh –connect –load path to LDIF file>

Its pretty simple and straight forward. You can migrate the users from Apps to OID easily.

Once Loading done, bring up the services and check the login using the users loaded newly to OID. Add users using OID DAS and check newly added user in OID getting propagated to APPS (if you have implemented Bi-Directional provisioning) by checking in FND_USER table. If users not getting propagated check DIP log file.

Another implementation scenario that could arise is already OID is in place, newly APPS is implemented. in this scenario you have to load the data the other way around. I am leaving this scenario to the users.(You can prepare cookbook from the doc http://download.oracle.com/docs/cd/B34956_01/current/acrobat/120sasg.pdf)

I hope you enjoyed reading this article. Happy Learning!!!