IDM Driver for Oracle Applications aka eBusiness Suite

mbluteau

By: mbluteau

May 3, 2011 10:57 am

Reads: 287

Comments:0

Rating:0

This step-by-step guide for setting up a simple, triggerless JDBC driver for Oracle eBusiness Suite foundation tables, will allow you to test drive your driver in a lab environment, without requiring access to the real thing.

Installing Oracle eBusiness Suite involves dealing with many steps and dozens of ISO files(for CDs or DVDs) and before you get to an actual lab environment, it may be useful to testdrive a driver on your test system.

The only requirement is access to an Oracle database installation. Then you can download the sql script at the bottom of this article to create the fake table and a view.

The table we will be looking at is FND_USER, under the APPLSYS schema. The FND_USER table stores application user account. Other tables may also contribute information.

Let’s build a simple triggerless driver for FND_USER.

Click to view.

Figure 1: Select Oracle in the driver palette, and drop it onto the project.

Click to view.

Figure 2: Select the JDBC driver template.

Click to view.

Figure 3: Select Oracle as the database.

Click to view.

Figure 4: Select the database version.

Click to view.

Figure 5: Select Direct and which 3rd party JDBC driver you want to use. You will need to download and copy the JDBC driver archives to your IdM server, for example /opt/Novell/eDirectory/lib/dirxml/classes for Linux and restart eDirectory.

Click to view.

Figure 6: Specify authentication parameters.

Click to view.

Figure 7: Specify triggerless, and browse your vault to select destination OUs.

Click to view.

Figure 8: Configure driver, don’t forget to set password for Oracle account.

Click to view.

Figure 9: Modify driver options.

Click to view.

Figure 10: Modify Subscriber options.

Click to view.

Figure 11: Modify Publisher options..

Click to view.

Figure 12: Modify Schema Mapping.

Click to view.

Figure 13: Modify Filter.

Click to view.

Figure 14: Modify Publisher Matching Rule. Modify Publisher Matching Rule.

Click to view.

Figure 15: Modify Publisher Create Rule.

Click to view.

Figure 16: Publisher Placement Rules.

Click to view.

Figure 17: After deploying/starting your driver, you should see accounts from Oracle.

Click to view.

Figure 18: Account from Oracle.

After you have a basic driver up and running, you can add support for additional attributes/tables, configure the Subscriber Channel if you want a bi-directional driver.

As for password sync/reset on the Subscriber Channel(from Vault to Oracle) it is possible to leverage utilities like FNDCPASS from Oracle.

I will provide an example of enabling Password support in an upcoming article:

http://www.novell.com/communities/node/12924/oracle-ebusiness-suite-password-sync-subscriber-channel

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Categories: Uncategorized

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Comment