Integrating Apps 12 Portlets with Third-Party Portals

Here's the latest update on the ever-popular subject of integrating the E-Business Suite Release 12 with third-party portals. 

11i Apps Navigator:

What's Possible in Release 11i Today

You already know that the E-Business Suite Release 11i portlets are written to work exclusively with Oracle Portal.  These portlets can't be plugged into third-party portal solutions.  We don't have any plans to rewrite these portlets for Release 11i, so what you see is what you will get for the foreseeable future for 11i.

Before we look ahead to the future and Release 12, here's a two-word summary of what's possible today in terms of third-party portal integration with Release 11i:  bookmarkable links.

If someone who hasn't logged in attempts to access protected E-Business Suite content, they're automatically redirected to either the E-Business Suite login page or Oracle Single Sign-On, the latter if the environment has been integrated with Oracle Application Server 10g.  Once the user logs in, she's redirected back to the protected E-Business Suite content that she was originally trying to reach.

Links to E-Business Suite content, therefore, can be bookmarked -- either in a browser, or added as links on a third-party portal page.  Admittedly, this might be pretty thin gruel for those of you expecting more, but that's what's available in Release 11i today.

What's Possible in Release 12

The E-Business Suite Release 12.0 ships with WSRP 1.0-compliant versions of the following portlets:
  • Applications Navigator
  • Applications Favorites
  • Applications Worklist
WSRP-compliant versions of other product team portlets (e.g. Balanced Scorecard) have not been released yet.  If you're interested in finding out the status of those product-specific portlets, your best bet would be to log a formal Service Request via Oracle Metalink against the specific Applications product in question.  This has the additional benefit of letting the product team know that you're interested in these upgrades, too.  You'd be amazed the effect that even a few of these Service Requests can have.

Not Supported:  Embedding Page Regions in Third-Party Portals

Many Applications 12 screens are based on the Oracle Applications Framework (OAF).  These screens are displayed in HTML and appear in certified browsers like IE and Firefox. 

It's tempting to assume that it would be possible to take regions of these screens -- or even the entire pages themselves -- and embed them in third-party portals.  More advanced readers will be musing about things like IFRAMES right about now. 

Unfortunately, this is not supported -- either for Release 11i or Release 12.  OA Framework based pages assume that they own the top of the Document Object Model (DOM).  This is not true if the pages are embedded in a third-party portal.  Attempting to do this will cause a range of unpredictable behavior.

This is a known restriction with the versions of OA Framework provided with Apps 11i and 12.  Our OAF team is looking into ways of changing this in future releases.  I don't have details about their plans that can be shared here yet, unfortunately.  As usual, you're welcome to monitor or subscribe to this column for updates on this.


The above is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle. 


Post a Comment:
  • HTML Syntax: NOT allowed


« November 2015