Friday, March 25, 2011

Oracle E-Business Suite and APEX White Paper


The Oracle E-Business Suite and Oracle Application Express teams are proud to announce the release of the Extending Oracle E-Business Suite Release 12 using Oracle Application Express white paper.

Oracle E-Business Suite delivers a wide range of functionality to handle core areas of your business processing needs. However, there are situations where you want to extend your information systems beyond the range of Oracle E-Business Suite. Many times these necessary extensions are meant to handle unique industry conventions, specific customer requirements, or perhaps to offer some other competitive edge. Sometimes these change requests are simple enough, but other times more extensive customizations are needed. In these scenarios, Oracle Application Express, also known as Oracle APEX, provides an easy way to create supplemental applications that are easily integrated with your Oracle E-Business Suite and its data.


This paper outlines how to extend Oracle E-Business Suite 12.1.3 (and up) functionality using Oracle Application Express. Recommended architecture and security considerations are discussed in detail.

You can find the paper on the APEX OTN Site > Learn More > Extending Oracle E-Business Suite Release 12 using Oracle Application Express {Under Technical Information and White Papers}

All the necessary files are also available from My Oracle Support Note: 1306563.1

This document helps customers and partners implement integrated Application Express extensions to the Oracle E-Business Suite Release 12.1.3 and up. The document is complete with a worked example. This solution also requires Oracle E-Business Suite Patch 9659153

10 comments:

Daniel Borgstrom said...

Hi David,

Great post. Very nice to see this getting supported by Oracle.

Some question/comments...my experience with integrating APEX and EBS was done with EBS 11i were I used the cookie solution to authenticate the users (without loging in again) when they clicked on the function in EBS to start the APEX app.

Here I used OWA_UTIL and OWA_COOKIE to solve that. These functions is (what I understand) part of the MOD_PLSQL which is not the recommended solution in R12. How can you solve that the user does not need to login twice if you don’t have any SSO avilable? I’m looking for something that replicates that cookie solution.

Second…in the white paper, the recommended solution is to install APEX in the same instance as EBS. In all of the EBS-APEX projects I have been working on they have not allowed us to install APEX in the EBS-instance. We have done a solution with a standalone instance with APEX and then a DB-link connecting us to EBS with the privileges we need. Can you see any problems to continue with that solution?

I also saw that you need EBS 12.1.3. Is there anyway to get this working with earlier R12-versions?

Regards,
Daniel Borgstrom

Familien Dybvik-Nielsen said...

David,

Im really happy to see an official Oracle paper on this integration.

I have been working in the same scenarios as described by Daniel, and have been trying to persuade my customers to install APEX in the eBusiness Suite database. The database link solution has some drawbacks whick would be nice to avoid.

Will EBS Authentification be a new Authorization scheme in future APEX releases ?

Best regards
Martin Nielsen

Jan Navratil said...
This comment has been removed by the author.
Jan Navratil said...

Congratulations David,

I know how much it means to you :-)

The link to the whitepaper in the post seems to be broken - this one worked for me:

http://www.oracle.com/technetwork/developer-tools/apex/learnmore/apex-ebs-extension-white-paper-345780.pdf

Jan

Hangya said...

Hi,
I could not apply patch 9659153, altough requiered code levels mentioned in the readme have already been superseded; we are on 12.1.3. What am I missing?

The log tells the following:

AutoPatch error:
The following file is missing:

/(...)/apps/apps_st/appl/fnd/12.0.0/admin/driver/fndsub030.drv


AutoPatch error:
Error reading product file driver files [complete; make tapes]

AutoPatch error:
Error determining valid on-site files

Thanks,
Janos

Hangya said...

I can see now that the patch has been classified defective... Hope it will be fixed soon!

Unknown said...

The patch has been replaced and bad links in the paper corrected.

In respect of DB Links with EBS, George Buzsaki, EBS Architect, doesn't recommend using DB Links.

We recommend utilizing Oracle Single Sign-On (OSSO) to prevent the users having to log in again. We do plan to revamp the document in the future to include details on integrating with Oracle Access Manager.

Regards,
David

Mehmood Rehman said...

We have one issue, in our PROD APPS the APEX link is working, but when we clone APPS then from Cloned APPS the APEX link is not working! how can we make it work!

thanks and regards
Mehmood

Unknown said...

Mehmood, I'm not sure what you mean by "cloned APPS". Providing you run the code in the correct places then it should still work (though I have no test environment to attempt this). You may want to log a Service Request with Oracle Support under EBS.

Mastan Ali said...

Extending Oracle E-Business Suite Release 12 using Oracle Application Express (APEX) [ID 1306563.1]

I followed the above document. was able to access apex pages from Main Responsbility pages.

But when i click from Navigator menu. Its just hangs.

We impleted SSO/11G IDM/Weblogic.

Is it working for you from Navigator menu.