Tuesday Oct 30, 2012

Using Oracle ADF with Oracle E-Business Suite Webcast - Nov 2

If you are using Oracle ADF with Oracle E-Business Suite or ar thinking on embarking on a project with these two technologies - make sure you mark your calendar for this coming Friday, November 2nd at 8.00 a.m. PST. Sara Woodhull, Siva Puthurkattil from Lake County Illinois and I will be having a re-run of the session we delivered at Oracle OpenWorld, but this time on a Webcast.

All the information on how to register and access the dial-in information is available from the Oracle E-Business Suite ATG team blog on the following link: https://blogs.oracle.com/stevenChan/entry/atg_live_webcast_november_2nd

Don't miss this opportunity to learn! 

Tuesday Oct 09, 2012

Couldn't Make It to Oracle OpenWorld? Fear Not! Upcoming: Using the Oracle E-Business Suite SDK for Java in ADF Applications Webcast

For those of you who didn't make it at Oracle OpenWorld, we have good news. The ADF and E-Business Suite teams are well aware that various ADF and Oracle E-Business Suite customers are looking for guidance on how to work with the Oracle E-Business Suite SDK for Java in ADF applications: its capabilities, limitations, etc.

As some of you might know, Sara Woodhull from the Applications Technology Group (ATG) in Oracle E-Business Suite and I delivered a session on the topic at Oracle OpenWorld last week. The good news is that we are already planning to deliver this session again as a webcast, tentatively scheduled for Nov. 2, 2012. 

Stay tuned to this and the Oracle E-Business Suite Technology Stack blog for upcoming information about the webcast.

Friday Jun 29, 2012

Adding a Role to a Responsibility for Use with the Oracle E-Business Suite SDK for Java JAAS Implementation

This new post on the series of ADF integration with Oracle E-Business Suite, was written by Sara Woodhull, Principal Product Manager on the Oracle E-Business Suite Applications Technology team.

Based on a previous post of the series, a reader asked what to do if you have an existing responsibility assigned to lots of users, instead of the UMX role that the Oracle E-Business Suite SDK for Java JAAS Implementation requires.  It would be tedious to assign a new role directly to hundreds or thousands of users, so naturally we’d like to avoid that if possible.

Most people don’t know this, but it’s possible to assign a UMX role to a responsibility in Oracle User Management. Once you do that, users with your responsibility will all inherit your UMX role automatically. You can then proceed with using your UMX role with JAAS for ADF.

Here is how to assign a UMX role to a responsibility in Oracle E-Business Suite:

  1. In the User Management responsibility, go to the Roles & Role Inheritance page.
  2. Search for the responsibility you want.
  3. In the search results table, click the “View In Hierarchy” icon for your responsibility. Note that the codes for responsibilities start with FND_RESP, while the codes for roles start with UMX.
  4. In the Role Inheritance Hierarchy, click on the Add Node icon (green plus + ) for your responsibility.
  5. Now you will see what appears to be the same page again but it is a little different (note the text at the top telling you the role you select will be inherited…).  This time, either search or expand nodes until you find your custom UMX role.  Use the Quick Select to choose that role.
  6. You will be sent back to the first screen, where you should see a confirmation message at the top. On the same page you can verify that the custom UMX role is underneath the responsibility.  You may need to expand one or more nodes to see the UMX role under the responsibility. You might see some other roles that have been inherited as well.
  7. Now that your users have the UMX role, you can test that the UMX role is being passed through to your ADF application through the Oracle E-Business Suite SDK for Java JAAS feature.

Happy coding!

Wednesday May 02, 2012

Debugging ADF Security in JDeveloper 11g

A quick post that can be useful when using ADF security in your application and you use external security providers like Oracle Access Manager, third party LDAP servers or even the Oracle E-Business Suite as shown in a previous post.

Many of you how are ADF developer might already now this first tip. Nonetheless, there is always the chance that it can help someone out there; the following command will enable debugging output to go directly into the server console within JDeveloper, it can be used for any ADF application: In your ViewController project properties, under run/debug/profile options edit the existing deployment profile –> inside Lunch Setting –> under Java Options add

-Djps.auth.debug=true -Djps.auth.debug.verbose=true


The second tip, is associated in particular with debugging security, it will provide information on user credentials and roles every time you interact with the different UI elements from your application: Under your <DOMAIN_HOME>\bin\ open the file setDomainEnv.cmd (sh) –> then add the following line:

set JAVA_OPTIONS=%JAVA_OPTIONS% -Djps.auth.debug=true -Djps.auth.debug.verbose=true


The above output is what you should obtain from an ADF application connecting to Oracle E-Business Suite.

Securing ADF Applications Using the Oracle E-Business Suite SDK JAAS Implementation

In the previous post on the series of ADF integration with Oracle E-Business Suite,  I covered how to setup and use the Oracle E-Business Suite SDK for Java to create a data source for accessing Oracle E-Business Suite data from our ADF applications in read-only form.

In this post we are going to explore another feature of the Oracle E-Business Suite SDK for Java, the implementation of JAAS (Java Authentication and Authorization Services). Using this implementation we can use E-Business Suite users and roles to restrict access to specific parts of external Java EE applications. You can find a very nice explanation about this feature on the following post from the Oracle E-Business Suite Technology Team blog.

You will need to setup your runtime environment (WebLogic Server) and afterwards configure you ADF application to point to the right resources. Both steps are well explained in My Oracle Support Knowledge Document 974949.1. In this article I will provide a high level overview of the steps that are provided on the document, highlighting areas where it’s easy to make mistakes and hopefully these can help you to get everything working successfully.


First you need to set up the AppsDataSource on your WebLogic Server server in order establish the communication channel with the Oracle E-Business Suite instance. Follow the instructions from the document in the section Configuring AppsDataSource and Configuring AppsDataSource on Oracle WebLogic Server (WLS):


The second step is to create and setup a default realm on WebLogic that enables users and roles provisioning directly from E-Business Suite. In E-Business Suite users and roles are stored in specific database tables, so the new realm will make use of the AppsDataSource defined on the first step. All of the steps are described on the note in the section: JAAS Configuration for Oracle WebLogic Server When setting the realm you need to pay attention to the following steps; if not executed correctly they could cause problems later on:

  • External Authenticator: By default, WebLogic server doesn’t provide the external authenticator which is used to authenticate against E-Business Suite. During the AppDataSource setup you are going to use the fndtext.jar that comes with the patch from My Oracle Support, and you recompile it using the following command:

java -classpath /tmp/mysrc:$CLASSPATH -DMJF=/tmp/mysrc/fndext.jar -Dfiles=/tmp/mysrc weblogic.management.commo.WebLogicMBeanMaker

If the command is executed correctly and doesn’t throw any errors, on creating the new realm you will be able to select ExternalAuthenticator from the list of authentication providers.

  • DataSource: Another area where you  need to be careful  is at the time of specifying which datasource to use for the realm. Make sure the JNDI name that you have given the your AppsDataSource matches the one to be used by the realm.


After completing all the steps you should have 2 realms on your WLS, having the newest one as the default one.


ADF Application

An interesting aspect of the integration is that you can leverage ADF Security to use the E-Business Suite JAAS implementation without manually editing configuration files as is the case with Java EE applications.

Please be clear that all the E-Business Suite roles to be used in the ADF application need to be defined as Enterprise Roles. Also, you do not need to create users for the application given that all them would come from Oracle E-Business Suite. However, you could define application-specific roles, but those roles need to map one of the enterprise roles.

When you are ready to deploy make sure you uncheck all the options related to users and groups. You don’t need those.


Now your application should be working and authenticating against E-Business Suite.

Here is a video that shows an ADF Application using the E-Business Suite SDK for Java JAAS implementation.

Securing ADF Application using the JAAS Implementation of the Oracle E-Business Suite SDK for Java

Related Articles:
AppsDataSource and Java Authentication and Authorization Service for Oracle E-Business Suite

Friday Mar 09, 2012

Using the Oracle E-Business Suite SDK for Java on ADF Applications - The AppsDataSource

In my previous post we covered how to create an ADF UI that displays data from the EBS database in read-only form. In this article we will explore how you could use the Oracle E-Business Suite SDK AppsDataSource to enable access to the data from Oracle E-Business Suite to the ADF applications deployed on WLS.

The following sample uses the Oracle E-Business Suite database Vision Demo that is available from the EBS installation media.

Creating the E-Business Suite data source in WLS

The first step that we need to do is to create a data source that will be in charge of connecting the ADF applications with the E-Business suite database schema.

The E-Business Suite team has a Java SDK that has been available for some time now. Among its components are the AppsDataSource and AppsXADataSource which we can be use to enable access to the EBS APPS database schema through a much cleaner approach.

The instructions to access the Oracle E-Business Suite SDK for Java and to set up the AppsDataSource on WLS are well documented on My Oracle Support Knowledge Document 974949.1.

Once you are finished, you will have a new data source defined on WLS.


Setting up the data source  on your ADF application and deploying it to WLS

In order to make use of the data source, we need to edit the configuration of the Application Module so instead of using a JDBC URL it uses a the JDBC Data Source in WLS.


Now, before deploying the application to the WLS Server we need to make sure the EAR file doesn’t include direct reference to the project’s DB connection. For that we uncheck the option on the application deployment profile options.


And with that we can deploy and now our application will use AppsDataSource from the EBS SDK for Java to access the DB. This way E-Business Suite administrators don’t need to give away the APPS password to development teams, nor the ADF application have a reference to it.

Here a video that summarizes the entry.

Using Oracle E-Business Suite SDK for Java AppsDataSource on ADF

A blog that explores features, tips and tricks of ADF and JDeveloper by Juan Camilo Ruiz, Product Manager on the ADF and JDeveloper team
Follow me:

« July 2016