Integration Repository for the E-Business Suite

There are many ways of getting information into and out of the E-Business Suite.  Until recently, however, these have been documented in a wild assortment of different places, including product-specific Apps manuals, the Electronic Technical Reference Manual (eTRM), and other unlikely sources.  If you've been subjected to the dubious pleasure of sifting through
our documentation in search of APIs and web services, this article should come as welcome news.


Integration Repository 11i Screenshot:

The new Oracle Integration Repository for the E-Business Suite pulls all of those sources into a single place... at last.  Initially intended to catalog service endpoints available via our service-oriented architecture, this repository has since grown into a comprehensive reference for all of the E-Business Suite's business service interfaces. 

You can browse the repository by product family, drilling down into specific modules:

Integration Repository 11i Menu:

Once you drill into a specific API, there's a concise list of the details you'd expect, including function names, parameters, rules, and so on:

Integration Repository 11i API Screenshot:

Looking Ahead to Release 12

The Release 11i version of the repository is available online only.  In Release 12, it's expected that the Integration Repository will be part of your Rapid Install.  As your instance is patched, the repository will automatically be updated with content appropriate for the precise revisions of interfaces in your environment.

July 13 Update:  We will also host an online version of the Integration Repository for Release 12, as well.

Related

Comments (12)

Thanks for the link it will be a wonderful resource

Hi
I am developing my own applet that will be used in conjunction with Oracle e-Business Suite. I want to ensure that when the applet is launched it executes using the existing install of Jinitiator on the client PC. What would be the correct way to launch this applet? It does not seem to be possible to make Jinitiator the default JVM for the browser. I am playing around with urlē—“ like http://server.com:port/dev60cgi/f60cgi?&appletmode=nonforms&HTMLpageTitle=Test&HTMLpreApplet=Test&code=appletname&width=400&height=300&archive=folder/appletname.jar. But I want to ensure that I get it correct. Can you point me to the correct documentation? I am struggling to find a good source of information.

Steven Chan:

Hi, Shaun,I've done a bit of research on this but am drawing a blank, ultimately, on recommendations.In general, no applets or extensions within the E-Business Suite should be attempting to force invocations of any specific JVM/Jinitiator release.   Whatever Java invocation takes place on the mid-tier should simply trigger the default Java desktop client configured for the overall E-Business Suite environment.  If the sysadmin has configured their E-Business Suite environment to use the native JRE, then that should be triggered by your extension, too.I don't have any pointers to official documentation on these types of extensions, unfortunately.  If you're really interested in investigating this further, our Oracle Consulting group may be better able to assist than us in Development.Sorry -- I wish had a better answer for you.  Good luck with your project.Regards,Steven 

MDT:

Hi Steve, great blog.

Had a chance to look into the Integration repository in V12 from the perspective of data integration across an enterprise. Is is possible to interrogate the repository from an outside program using APIs? Or is the repository only meant to to be a browser within the Oracle Apps environment? It would be very useful to have the API capability so that the discovery, import and mapping activities to the V12 integration objects [example, interface tables, stored procedures, business views,..] can be performed from an integration program.

Steven Chan:

Hi, MDT,Thanks for the feedback on the blog.  Sorry for the delay in responding.Good question!  I've passed it on to our Integration Repository team and will post their reply as soon as possible.Regards,Steven 

MDT:

Thanks Steven, will await the response.

Follow on question - if the repository is strictly a browser and does not expose a queryable API (as I suspect), is there an export facility so that one could export a whole set of interface metadata and import that into an external integration application?

Steven Chan:

Hi, MDT:Sorry for the delay in getting back to you on this.  My post-pneumonia backlog has been formidable.There are no facilities presently to do bulk interface metadata exports.  For you previous question, here's an excerpt from the reply from our Integration Repository team:Current Solution:===========We have EBS Adapter (10.1.3.3) today which
provides the introspection capability for IREP for most of the integration
interfaces, and can be directly used either in a ESB or BPEL as a pure
Web-Service.We also have a native Service Bean in IREP which allows
interogation on the Service Bean's deployed in the IREP. This can be called from
any WS Client.They also dropped some interesting hints about their product roadmap.  They still putting together some formal communications around this now, so I can't share those quite yet.  Stay tuned:  I'll post some updates on this as soon as possible.Regards,Steven

MDT:

Steven,
Thank you for the info and best wishes. Will await further updates..

Qing:

Hi Steven,

You mentioned "We have EBS Adapter (10.1.3.3) today which provides the introspection capability for IREP for most of the integration interfaces, and can be directly used either in a ESB or BPEL as a pure Web-Service." in you last post. My understand is the EBS Adapter provided the Web-Service, from which user can get most of the integration interfaces showing in the IREP. Do I understand this correctly? If it's correct. Are those WSDL files of web-services published in somewhere?

Thanks,
Qing

Steven Chan:

Hi, Qing,My understanding is that this is correct:  the EBS Adapter has the same seed data for the published web service endpoints for the E-Business Suite. However, I don't know whether the actual WSDL files are published somewhere.  I'd recommend logging a Service Request against the EBS Adapter to get some guidance with more hands-on experience with that than I.Regards,Steven

felix:

Hi fooks:
Are there any API and method can be used by public to import the IREP metadata which can be used to construct the interface tree?
Hopefully your suggestions!

Steven Chan:

Hi, Felix,

No, I'm not aware of any way of exporting the IREP metadata into another tool.

Regards,
Steven

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Google Search

Archives

Subscribe to Updates

Powered by
Movable Type and Oracle