Main

Release 12 Archives

April 26, 2006

E-Business Suite Release 12 to Include Oracle Application Server 10g

Sharp-eyed readers of my OAUG Collaborate 06 presentation will have noticed some sneak previews of Oracle E-Business Suite Release 12's technology stack buried in an appendix.


The most significant news:  Oracle E-Business Suite Release 12 will use Oracle Application Server 10g for its application tier.  We're officially in the 21st Century now, so it's about time.

This long-awaited configuration will use:
[Cheering is heard from Oracle Applications DBAs worldwide]

Now, a word from Oracle Legal, which I'm obliged to append to all Release 12-related posts:

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.

Related Articles:

Why Use Two ORACLE_HOMEs for Release 12's Application Tier?

Why use two different OracleAS 10g releases in two different ORACLE_HOMEs for the upcoming Oracle E-Business Suite Release 12?  Because you asked for it, of course.  Well, indirectly, perhaps.  You've been asking us when E-Business Suite users can take advantage of the latest Oracle technologies.  So, we're biting the bullet and putting them into our Release technology stack.

Release 12 Application Tier ORACLE_HOMEs:

The latest version of Forms and Reports available today is included in Oracle Application Server 10g 10.1.2.0.2, so that release, at minimum, will be part of the E-Business Suite Release 12.

You've been clamoring for the ability to use Oracle Containers for Java (OC4J), the next-generation successor to JServ.  The latest version of Oracle Containers for Java available today is included in Oracle Application Server 10g 10.1.3, so that release, at minimum, will be part of the E-Business Suite Release 12, too.

The slightly tricky thing is using these two releases together.  In a nutshell, all major services will be started out of the 10.1.3 ORACLE_HOME.  The E-Business Suite modules (packaged in formsapp.eap) will be loaded into the OC4J-Forms instance running out of the 10.1.3 ORACLE_HOME, and frmweb will be invoked out of the 10.1.2 ORACLE_HOME.

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.

Native Sun Plug-In to Replace Jinitiator in E-Business Suite Release 12

E-Business Suite Release 12 will replace Oracle JInitiator with the native Sun Java2 Standard Edition (J2SE).


[More cheering from Oracle Apps DBAs]

As most of you know, Oracle JInitiator is an authorised version of Sun Microsystems' Java2 Standard Edition with some specific fixes required to support Oracle Forms.  JInitiator is currently required to run Oracle Forms in the E-Business Suite Release 11i, although we're running an Early Adopter Program that's evaluating the feasibility of eliminating this requirement for Release 11i.

Oracle JInitiator will no longer be required to run Oracle Forms in E-Business Suite Release 12.  Oracle Forms in Release 12 will run directly in the native Sun Java2 Standard Edition plug-in.  This will be our standard configuration for Release 12.

Related Articles:

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.

April 27, 2006

E-Business Suite Release 12 to include 10gR2 Database

Oracle E-Business Suite Release 12 will include the 10gR2 Database (10.2) as part of its Rapid Install. 


The specific database-tier point release is still undergoing internal review, but it is reasonably certain that the 10gR2 10.2.0.2 Database will be the minimum version included with the Release 12 Rapid Install, given that this database version is already certified with the E-Business Suite Release 11i.  The complementary JDBC 10.2 will be utilitized on the application-tier.

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.

May 4, 2006

Updated User Interface for E-Business Suite Release 12

It's expected that the E-Business Suite Release 12 will feature an updated user interface, codenamed "Project Swan."  Aside from the unfortunate implication that the existing 11i user interface is an ugly duckling, Project Swan has some very appealing new aspects:

Project Swan Overview:
  1. Background pattern for branding
  2. Base font change to Tahoma 9pt
  3. Button style change
  4. Background color change
  5. Tab style sub-tab layout with gradient background
  6. Gradient background for header
  7. Icon change
  8. Table color update
  9. Gradient background for footer
  10. Vertical spacing change

For comparison, here's an existing Release 11i Self-Service Expenses screenshot (OA Framework):

Expenses 11i Screenshot:

And here's a draft version of the Release 12 equivalent:

Expenses R12 Screenshot:

Here's an existing Release 11i Form for the Contacts Center:

Contacts 11i Screenshot:

And here's a draft version of the Release 12 equivalent:

Contacts R12 Screenshot:

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. 

May 5, 2006

Project Swan and Release 12, Redux

I've received a sufficient number of emails on Project Swan, our Release 12 user interface facelift, that we'll take another run at it today.


Just for fun, we'll do a few more before-and-after comparisons.  Here's our Release 11i Login Screen:

11i Login Screenshot:

Here's a draft of the Release 12 equivalent:

R12 Login Screenshot 2:

Here's an existing Release 11i CRM/JTT screenshot for iSupport:

11i iSupport Screenshot:

Here's a draft of the Release 12 equivalent:

R12 iSupport Screenshot:


Converting From Previous Versions

If you've customized or extended Release 11i screens according to our published customization standards, there shouldn't be significant effort involved in getting to the Project Swan look-and-feel.  This is expected to vary a bit by the type of screen.

Oracle Applications Forms

Project Swan changes for Forms are limited to changing the color scheme and using non-boldfaced fonts for field values. These changes will be made in the technology layer, so no changes need to be made by Forms designers. There will be no change to the position or layout of any fields on the forms.

Oracle Applications Framework Screens

In most cases, no code changes will be needed, since the cosmetic changes will be implemented at the OAF technology layer. There may be specific cases where the use of custom stylesheets may require additional tweaks.

CRM/JTT Screens

Like OAF, in most cases, no code changes will be needed, since the cosmetic changes will be implemented at the technology layer. There may be specific cases (e.g. custom renderers, custom stylesheets) that require additional tweaks.

Migration Tools or Documents?

Given that the vast majority of existing screens should automatically be uplifted to the Swan UI, I haven't yet been told whether there will be tools to aid in conversions.  It's likely that we'll provide you with the same internal Swan conversion guidelines that E-Business Suite product teams are using today (albeit with better spell-checking and grammar).

Alternate Colour Schemes

A common question at last month's OAUG conference was whether we would support alternate colour schemes, since many of you distinguish DEV, TEST, and PROD environments with different colours. 

Short answer:  Yes, you'll still be able to customize colour schemes in the new Swan UI.  It isn't clear whether we'll provide you with a preset selection of different schemes, but you'll be able to design your own.

Related Article:

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.

May 16, 2006

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

May 24, 2006

Release 12 and Third-Party Portals

Apr 3, 2007 Update:  Release 12.0 includes WSRP 1.0-compliant versions of the following E-Business Suite portlets:  Applications Navigator, Applications Favorites, Applications Worklist.

I've briefly alluded to our Release 12 plans for portlets, but your feedback suggests that it's worth discussing our plans in more detail.


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 reminder 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.

Release 12, JSR-168, and WSRP

We're still in the process of beefing up our portlet infrastructure for Release 12, so I need to preface what follows with the usual disclaimer:  this is subject to change without notice

JSR-168 Diagram:

With that out of the way, I can say that our plans are to rewrite our existing Oracle Applications Framework Web Provider to JSR-168 and WSRP standards.  This means switching from the existing Java Portlet Development Kit (JPDK 3.0.9) to the new JSR-168 Oracle Java Portlet Container.

If all goes according to plan, this means that you will be able to plug the Release 12 E-Business Suite portlets into any third-party portal that supports the JSR-168 and WSRP standards.

Curves In The Road Ahead

Given the inherent limitations of web-based protocols, it shouldn't come as a surprise to learn that the JSR-168 and WSRP standards aren't quite as feature-rich as the existing JPDK libraries. 

In other words, there are things we can do today with the JPDK that will require considerably more ingenuity to pull off with JSR-168 and WSRP.  For example, dynamic portlet generation and invalidation-based caching have less-powerful equivalents in the new standards.

Until we work through these issues, it's safe to expect that the existing E-Business Suite portlets may look and function a bit differently in Release 12.

Preserving Your Existing Portlets

We're planning to certify and include the latest JPDK 10.1.2 libraries in the Release 12 Rapid Install, too.  If you've invested in building custom JPDK portlets for the E-Business Suite, this means that those portlets will continue to work, providing you with some breathing space during your Release 12 migration. 

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. 

May 26, 2006

Process Management in Release 12

Oracle executives have been justifiably devoting a lot of slides in recent customer briefings to Oracle BPEL Process Manager: it's the cornerstone for our corporate integration strategy.  This begs the obvious question: what's going to be included in Release 12?


Workflow in Release 12

The Rapid Install for Release 12 will include Oracle Workflow out-of-the-box.  At present, we expect that the version included will be Workflow 2.6, but as always, this is subject to change. 

The practical implication of including Workflow in Release 12 is that all of your existing customized workflows will continue to function with minimal disruption and effort if you're upgrading from Release 11i.

Optional R12 Integration with BPEL Process Manager

If you're excited about working with BPEL Process Manager, you'll have the option of doing that, too. 

BPEL Logical Architecture:

Given that the E-Business Suite provides standard SOA web services, all that you'll need to do is to install OracleAS 10g and and BPEL Process Manager on a separate instance and point it to business service endpoints available from the E-Business Suite Release 12. 

Getting Started with BPEL Process Manager and Release 11i

The BPEL Process Manager is considered a standalone tool outside of the E-Business Suite space, so you don't need to wait until Release 12.  You can use BPEL Process Manager and other Oracle Integration connectors with Release 11i today.  That's a good way of getting a headstart if you plan to upgrade to the combination of Release 12 and BPEL Process Manager in the future, or if you'd like to kick the tires and take this for a test drive today.

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. 

June 5, 2006

Java 5 and E-Business Suite Release 12

The E-Business Suite Release 12 Rapid Install is expected to include Java 5 (J2SE) for the application tier.  In addition, given that AutoConfig will be compiled as Java 5 objects, we'll be delivering Java 5 on the database tier, too.


Sun J2SE 5 Download Screenshot:

Release 12's run time components will include Java 5 for the web tier (including JSP compilation), the Concurrent Processing tier, and for the AD utilities.  We're still working out the exact Java version now; feel free to subscribe to this blog if you'd like updates when more details get posted.

Related:

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. 

June 12, 2006

New Secure Sockets Layer Features in Release 12

E-Business Suite Release 12 will include a raft of new SSL-related features, including a new mod_ossl plug-in, use of Oracle Wallet Manager, and optional use of Oracle Certificate Authority for PKI deployments.

Oracle Certificate Authority Screenshot:

The most significant change for Secure Sockets Layer (SSL) support in E-Business Suite Release 12 is expected to be the use of the mod_ossl module for the Oracle HTTP Server.  Like mod_ssl, the mod_ossl plug-in enables strong cryptography for Oracle HTTP Server.  In contrast to the OpenSSL module, mod_ossl is based on the Oracle implementation of SSL, which supports SSL 3, and is based on Certicom and RSA Security technology.

Release 12 SSL certificates will be managed by the Oracle Wallet Manager 10g, which will be accessible via a graphical user interface (GUI) or via a command line interface (CLI), for all of you die-hard purists out there.

Forms Listener Servlet won't need a separate certificate, and will share the same wallet as the Oracle HTTP Server. 

If you're interested in deploying public key infrastructure (PKI) technologies in your organization, you will also have the option of using the Oracle Certificate Authority (OCA) to issue and manage X.509 digital client certificates.  End-users and servers will be able to use these digital certificates to authenticate themselves to Release 12.

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. 

June 13, 2006

Upgrading to E-Business Suite Release 12

Editor Oct 9 Update:  See this article for a small update on upgrade paths.

There's a lot of certification work underway to ensure that it will be straightforward to upgrade to E-Business Suite Release 12.


We plan to support upgrades from any Release 11i version to Release 12.  If your environment is at any level between 11.5.1 to 11.5.10, you should be able to upgrade to Release 12.

Current things that we don't have sufficient information to comment on publicly yet:  the steps and time required to do this upgrade, and the upgrade paths from earlier Oracle Applications releases (e.g. 11.0.3, 10.7). 

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.

June 14, 2006

Using Third-Party Networking Hardware with Oracle Application Server 10g

If you recall, the E-Business Suite isn't explicitly certified with third-party networking components but is expected to work with them. 


Load-balancer with OracleAS 10g Identity Management:

If you're integrating the E-Business Suite with Oracle Application Server 10g, there's another piece that you can add to the puzzle.

Oracle Application Server 10g isn't explicitly certified with third-party networking components, either, but some testing has been performed with specific vendor products.

These tests cover load-balancers, firewalls, and SSL accelerators.  Some of the load-balancer vendors and products include F5's BIG-IP, Foundry, Citrix's NetScaler, Nortel, and Radware.  The firewall and SSL vendors include Check Point, Cisco, Sonic Wall, and Ingrian.

Remember that Oracle testing doesn't equate to certification.  It's the responsibility of the third-party vendor to certify their hardware with Oracle Application Server 10g.  Regardless of that, you might find it reassuring to know that Oracle's tried some of these combinations in the Oracle Application Server 10g labs. 

Even if your networking vendor hasn't certified their hardware explicitly Oracle Application Server (or even the E-Business Suite), it's generally expected that their products will work if they're standards-compliant.

References

June 20, 2006

Virtual Private Database in E-Business Environments

It's interesting how certain questions seem to surge in clusters.  Lately there's been a bountiful harvest of questions about using Virtual Private Database (VPD) functionality in E-Business Suite Release 11i environments.


Virtual Private Database example:

VPD in a Nutshell

Virtual Private Database (VPD) enables programmers and database administrators to enforce security, to a fine level of granularity, directly on tables, views, or synonyms. Because security policies are attached directly to tables, views, or synonyms and automatically applied whenever a user accesses data, there's no way to bypass security.

When a user directly or indirectly accesses an object protected with a VPD policy, the server dynamically modifies the SQL statement of the user. The modification creates a WHERE condition returned by a function implementing the security policy. The statement is modified dynamically, transparently to the user.

In the example diagram above, a customer can only see his orders in the 'orders' table when he is listed in the 'customers' table.

Not a Walk in the Park


Apps makes some use of VPD internally in Release 11i, but enabling your own VPD policies across the E-Business Suite isn't as simple as flipping a switch, unfortunately.

For example, let's say you decide to apply VPD policies to a
particular Workflow or concurrent processing table.  If your custom VPD
policies lock out a set of users, there may be unknown side-effects in
other dependent Apps products that need generic administrative access
to these tables.

Although it's technically possible to use VPD to implement your own data security extensions, there's a decidedly non-trivial amount of custom work involved.  This requires deep understanding of the E-Business Suite data model and is not for the faint-hearted.  Supporting these kind of customizations is outside of our scope here in Apps Development, but there are Oracle Consultants who may have the right expertise for this.

Is It Supported for E-Business Suite Environments?

If you create custom VPD policies for your E-Business Suite environment, Oracle Support will regard these like any other customization or third-party products in your environment, namely:
  • If you report issues that can be reproduced in standard, uncustomized environments, those issues will be resolved via workarounds or patches. 
  • If the issues can't be reproduced in standard environments and are isolated to your custom VPD policies, the outcome will be a recommendation to remove or fix your VPD policies.
Future Plans for Documentation and Release 12

The Applications Technology Group doesn't currently document how VPD extensions should be performed in the E-Business Suite.  There are plans for future documentation that will describe what session context is available for use in VPD policies, but no firm schedules.

In Release 12, VPD will be used as part of the new implementation of Multi-Organization Access Control (MOAC).

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. 

July 14, 2006

Statement of Direction: Oracle E-Business Suite and Content Management

[Editor Update May 21, 2008:  Keith has moved on to another team within Oracle and, sadly, is no longer an active contributor to this blog.  Feel free to direct any questions about his posted articles directly to Steven Chan, instead.]

Oracle has been making big strides in the area of content management. A recent press release touted two new products, Oracle Content Database and Oracle Records Database (or just Content DB and Records DB, for short). In short, Content DB allows you to use a single Oracle database instance as a repository for all kinds of unstructured data, and gives you the ability to use powerful tools like SQL and database privileges to query and manage that data. Records DB offers additional lifecycle management utilities that allow you to apply policies for document auditing, retention, and disposal to meet regulatory compliance obligations.

A Brief History of Content Management at Oracle

If this sounds familiar to you, then you're one of the not-so-many people who's been paying attention to this space over the past few years. Oracle's content management offerings are not entirely new, having undergone several transformations, from iFS, to Oracle Files, to the more recent Oracle Content Services, introduced in Oracle Collaboration Suite 10g. Starting later this summer, this latter incarnation will be rechristened as Oracle Content Database, and will henceforth be available as an option for the Enterprise Edition of Oracle Database 10g.

Oracle Content Database:

This marks the first time that a content management product has moved out of being in its own collaboration offering, and into the head-of-the-class database suite. It makes a strong statement about the importance of having access to the right tools for managing the overwhelming amounts of data companies are juggling today. Hopefully making it easier to obtain and install that technology will be a big step toward easing the burden. (Note that shortly after Oracle made this announcement, Microsoft announced that their perpetually elusive WinFS project was being taken out of the operating system track, and integrated into their SQL Server product. Coincidence? One has to wonder.)

I Want It Now!

Today, there are a handful of E-Business Suite products that offer optional integration with Oracle Files and/or Oracle Content Services, including Product Lifecycle Management, Internal Controls Manager, and Oracle Tutor.

For instance, Oracle Document Management is an integral component of PLM that allows product designers & engineers to associate large numbers of files and documents that have their own lifecycle policies. It supports features such as check-in/check-out, major/minor revisions & versions, access control, associations (to E-Business Suite objects), and more...all on top of Oracle Content Services. Going forward, we expect that many more products will be enticed to provide support for both Oracle Content DB and Oracle Records DB.

Now in the Bullpen

To aid in this process, the folks here at Techstack Central are looking at how we can make it easier for E-Business Suite teams to offer such support in their products. Content DB and Records DB will be available starting in August, and our evaluation of these products for integration with Release 12 is already well underway.

Our Mail Filters Are Standing By

We will be making a decision at a later time regarding support with Release 11i, but in the meantime, if this combination is deemed critical for your company (and an upgrade to Release 12 is not in the cards), you can always help us out by letting us know about it, either by adding a comment to this blog entry, or by sending me or Steven an email.

Be sure to tell us which specific products you are interested in integrating with our content management solutions.


July 25, 2006

IPv6 and the E-Business Suite

[May 27, 2008 Update:  The E-Business Suite is now certified to be IPv6-compatible; see this announcement for details.]

[May 9, 2007 Update:  As of today, this article still represents our latest status on IPv6 certification for the E-Business Suite, for both Release 11i and 12.  We have been briefed on the US Federal requirements for the 2008 changeover.  Aside from those US governmental organizations, if you haven't already contacted us about your IPv6 requirements, please drop me a line.]


A very small number of E-Business Suite customers have expressed interest in Internet Protocol Version 6, otherwise known as IPv6. From the the IPv6 Information Page:

IETF Logo:

IPv6 is the "next generation" protocol designed by the IETF to replace the current version Internet Protocol, IP Version 4 ("IPv4").

Most of today's internet uses IPv4, which is now nearly twenty years old. IPv4 has been remarkably resilient in spite of its age, but it is beginning to have problems. Most importantly, there is a growing shortage of IPv4 addresses, which are needed by all new machines added to the Internet.

IPv6 fixes a number of problems in IPv4, such as the limited number of available IPv4 addresses. It also adds many improvements to IPv4 in areas such as routing and network autoconfiguration. IPv6 is expected to gradually replace IPv4, with the two coexisting for a number of years during a transition period.

Certification Plans for the E-Business Suite

Certification of the E-Business Suite with IPv6 is in the queue for evaluation and feasibility analysis, but we don't have any commitments or timelines that we can share at this point.

Help Influence Our Priorities

If your organization is committed to migrating IPv6, please add a comment to this article or drop me an email with the details, including timelines and how you expect this to affect your E-Business Suite deployments.  Your feedback helps us prioritize this certification for future releases.

July 26, 2006

Release 12 Patch Wizard Improvements

A big part of an Apps DBA's job is patching, so I know the Patch Wizard in Oracle Applications Manager is something about which you have a few opinions.  These opinions are sometimes expressed in energetic and colorful language.  It's clear that some of you feel strongly about this area. 

OAM Patch Wizard screenshot:

Some of you have recently provided feedback on the Patch Wizard, which I forwarded to our development team.  They reviewed your comments and provided some glimpses of functionality to come in future versions such as Release 12.  Here's a sampling of your comments and some selected responses from the team:
  1. Patch Wizard downloads patches which have already been downloaded

    This is by design in the current Release 11i version.  Release 12 will download a patch from Metalink only if it doesn't match an existing patch in your staging directory.
     
  2. Patch Wizard gets some patch prerequisites wrong
     
    This is a known issue, complicated by the interrelationships between patches, Family Packs, and the wide array of bundles that patches can be delivered in.  The issue of handling patch prerequisites more sensibly is being revisited in Release 12.
     
  3. Patch Wizard recommends patches included in already-installed patches
     
    This shouldn't happen for patches that are explicitly included, i.e. patches whose definitions directly include specific sub-patches.  If you encounter this behaviour, file a bug with Oracle Support and we'll investigate this.
     
    If a patch is implicitly included (i.e. all files in a patch are included in an already-applied patch), this can happen.
     
  4. Patch impact analysis doesn't note when a patch is significantly changing your installed patch level, e.g. from Minipack H to Minipack J.
     
    This is true.  This is functionality that is slated to be improved in Release 12.
     
  5. Patch Wizard should show analysis results even when no patches are recommended.
     
    This is a commonly requested enhancement request.  This functionality is slated to be delivered in Release 12.
     
  6. There should be better correlation between analysis runs and concurrent requests.
     
    The technology used for concurrent requests places some restrictions on this; we're looking at what's feasible for future releases.
     
  7. Analysis runs may take some time to complete.
     
    This is true.  Some of the current analysis being performed by the Patch Wizard take some serious computation time.

    It's expected that Release 12 will include some performance gains over earlier releases, partially resulting from avoiding downloads of existing patches, changes in .LDT file packaging, and changes in the logic used by the prerequisite analysis engine.
     
  8. Large patches may trigger "out of memory" errors in some rare cases.
     
    If you encounter this behaviour, please file a bug and we'll investigate this. 
Stay tuned to this website for more patching updates for Release 12.  Thanks for your comments -- keep them coming, and I'll do my best to route them to the right teams.

Related
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. 

July 31, 2006

Identity Management in Release 12

If you've been keeping up with our E-Business Suite Release 12 sneak previews, you know that this release will include Oracle Application Server 10g for the application tier.  Here are a few more details about identity management for this release.

Apps R12 Identity Management:

FND_USER Still The Default

Like Release 11i, Release 12 will use the local E-Business Suite user directory, FND_USER, for user authentication by default.  You may optionally integrate R12 with an external Oracle Application Server 10g instance and delegate user authentication to Single Sign-On 10g and Oracle Internet Directory 10g running externally. 

Integration with Third-Party LDAPs and Single Sign-On Solutions

It's possible to integrate R12 with a third-party LDAP (e.g. Microsoft Active Directory, SunONE/iPlanet) or single sign-on solution (e.g. Microsoft Windows Kerberos, Netegrity SiteMinder).  If you want to do this, you'll need to integrate those third-party solutions via an external Oracle Application Server 10g instance, as shown in the diagram above.

That creates a chain of trust:  R12 delegates user authentication to Oracle Single Sign-On; Oracle Single Sign-On delegates authentication to the third-party single sign-on solution.

Likewise, user information from the third-party LDAP must be synchronized with Oracle Internet Directory 10g, which synchronizes its users with the E-Business Suite's FND_USER directory.  Synchronization is handled by the Oracle Directory Integration Platform.

New Local Login Page

The Release 12 local login page will feature the new Swan look-and-feel, offer multiple languages, and support customizations.

SSO Integration With Portal & Discoverer

As in Release 11i, the R12 Single Sign-On integration allows logged-in E-Business Suite users to access Portal and Discoverer content without having to log in again.

Switch to mod_osso


Under the covers, the R12 Single Sign-On integration switches from the older SSO SDK used in 11i to the latest mod_osso technology available in Oracle Application Server 10g.

From an end-user's perspective, nothing has changed; they're still authenticated by Single Sign-On 10g.  From a security perspective, mod_osso centralizes partner application session management and allows for simpler debugging and administration.

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. 


August 2, 2006

Password Management with Oracle Internet Directory

User password resets - the bane of every sysadmin.  Automating this tedium is a major benefit of integrating your E-Business Suite environment with Oracle Application Server 10g.  By delegating user authentication to Single Sign-On 10g and Oracle Internet Directory 10g, you can take advantage of the latter's automatic password reset capabilities.


But First, Some Basics About Account Management

In a standard E-Business Suite environment, user passwords are stored and encrypted in the user's records in the E-Business Suite's FND_USER directory.  

When an E-Business Suite environment is integrated with Single Sign-On and Oracle Internet Directory, Apps user accounts are linked to Oracle Internet Directory user accounts like this:

Link Apps Account to OID 2:

Where Does The User Log In?

When a user's E-Business Suite account is linked to an account in Oracle Internet Directory,  sysadmins have the option of specifying how the user can log into the E-Business Suite.  This can be specified for each individual user.

Available options are:
  • Users can log in externally via Single Sign-On
  • Users can bypass Single Sign-On and log in locally to the E-Business Suite
  • Users can log in via both of the methods above
E-Business Suite Doesn't Need To Store A Password

In the external scenario, all user authentication is handled by Single Sign-On and Oracle
Internet Directory.  For so-called external users, passwords are stored exclusively in Oracle Internet Directory.  Single Sign-On displays a login screen and collects the user's userid and password, and Oracle Internet Directory checks that those credentials match the user's entry within the Oracle Internet Directory LDAP user directory.

After users successfully log into Single Sign-On, they
receive security tokens that the E-Business Suite recognizes and uses
to establish their E-Business Suite session, based on a chain of trust that looks like this:

SSO OID Apps Trust:

The E-Business Suite uses those Single Sign-On security tokens in place of checking for a password.  So, it doesn't need to store user passwords for external users at all. 

No More Manual Password Changes

So, in a refreshing switch for veteran Apps sysadmins, all external users can reset their own passwords using Oracle Internet Directory's Delegated Administration Service.  This represents the end of the era of manual password resets for Apps users.

Logging Into The E-Business Suite Directly

There are specific users that must always be able to log into the E-Business Suite directly.  These users include Apps DBAs or system administrators, who still need to be able to get into Apps even if the external Single Sign-On and Oracle Internet Directory instances are unavailable due to maintenance windows.

These are considered to be local users, so their passwords are always stored in the E-Business Suite's FND_USER directory, not Oracle Internet Directory.  Passwords for these users still need to be maintained manually using the regular E-Business Suite security forms that you know and love.

A Tricky Case:  "Both"

There might be a subset of users who need to be able to access the E-Business Suite via Single Sign-On as well as locally.  These users would be given access to both login methods, which means that passwords must be stored in both locations:  Oracle Internet Directory and the E-Business Suite's FND_USER directory. 

The password management overhead is higher for these users, so you'll want to use this option very sparingly:
  • Password changes made in the E-Business Suite are automatically sent to Oracle Internet Directory
  • Password changes made in Oracle Internet Directory must be manually repeated in the E-Business Suite using the E-Business Suite security forms
The asymmetry in the tasks above is because of this:  we can decrypt passwords stored in the E-Business Suite, which allows us to send them to Oracle Internet Directory.  Passwords in Oracle Internet Directory, however, are hashed, which prevents us from transmitting a copy to the E-Business Suite.

Password Management With Third-Party Integrations

That's enough for today, but look out for a future article discussing password management when you integrate the E-Business Suite with a third-party LDAP directory or single sign-on solution.  Stay tuned.

Related

Note:  Everything in this article applies equally to both Release 11i and 12 environments.

August 8, 2006

Password Management with Third-Party Solutions

Editor Jan. 12, 2007 Update:  Oracle Identity Management 10g 10.1.4.0.1 is now certified with the E-Business Suite. 

We've now demonstrated that passwords no longer need to be maintained in the E-Business Suite when you've implemented Single Sign-On 10g integration.  What happens to passwords in a configuration that includes a third-party LDAP directory like Microsoft Active Directory, and a third-party single sign-on solution like Microsoft Kerberos?


Third-Party Integration In A Nutshell

Before we get to password management, I'd recommend that you review my earlier article about integrating the E-Business Suite with third-party LDAP and single sign-on solutions

If you're in a hurry, here's a quick recap of the key points:
  • Oracle Internet Directory is a mandatory hub for synchronizing user information between a third-party LDAP directory and the E-Business Suite
     
  • The third-party LDAP directory is usually considered to be the master "source of truth" for user credentials
     
  • Oracle Single Sign-On is a mandatory prerequisite for delegating E-Business Suite's user authentication to a third-party single sign-on solution
Using Oracle Internet Directory As A Hub

Recall that it's possible to integrate your E-Business Suite environment with a third-party LDAP directory using Oracle Internet Directory and its Directory Integration Platform as an intermediary, like this:

Third-Party LDAP Integration 2:

Oracle Internet Directory is a mandatory component in this chain.  Oracle doesn't currently offer any methods of directly integrating a third-party LDAP with the E-Business Suite.

Third-Party LDAP As The Master "Source of Truth"

In the typical configuration, the third-party LDAP directory is the master "source of truth" for the user's credentials.  For example, a change to the user's name would first be made in the third-party LDAP.  The updated user's information would then be sent to Oracle Internet Directory via the Directory Integration Platform.  Once in Oracle Internet Directory, the updated user's information would then be sent to the E-Business Suite via the Directory Integration Platform.

Extending the Chain of Trust

Remember that the E-Business Suite can delegate user authentication to Oracle Single Sign-On, effectively creating a chain of trust between the two components.  When the E-Business Suite is integrated with a third-party single sign-on solution, that chain of trust is extended one level further, like this:

Third-Party SSO Integration:
 
When the user logs on to the third-party single sign-on solution, she gets a set of security tokens that are recognized and trusted by Oracle Single Sign-On.  Oracle Single Sign-On doesn't challenge the user again for her credentials.

In turn, Oracle Single Sign-On issues its own set of security tokens, which are recognized and trusted by the E-Business Suite.  The E-Business Suite doesn't challenge the user again for her credentials.

What About Passwords?

Now that we've got the basics out of the way, understanding how passwords are handled in this scenario should be a bit easier.  In the scenario above, the user is challenged only once for their userid and password.  The third-party single sign-on solution handles that challenge and authenticates the user's credentials against the third-party LDAP.

It stands to reason that if the user is already logged in by the third-party single sign-on solution, and Oracle components never ask for the user's userid and password, there's no reason to keep the user's password anywhere in the Oracle namespaces.

Passwords Stored In Third-Party LDAP:

And, that's true:  when integrated as shown above, users' passwords are not stored locally in either Oracle Internet Directory or the E-Business Suite.  Passwords are stored only in the third-party LDAP directory.

Delegating User Management

Since the third-party LDAP repository is the master source of truth, it handles all user password resets.  Neither Oracle Internet Directory nor the E-Business Suite are interested in -- or even participate in the process -- of password management in this scenario.  It's all delegated to the third-party LDAP.

For Advanced Readers Only

By this point, I've weeded out readers with short attention spans.  For the handful of you who've toughed it out to this point, I should note that the above scenario is only one of many possible starting points.  Other advanced scenarios are technically feasible, including those in which user credentials flow bidirectionally between Oracle Internet Directory and the third-party LDAP. 

These can get pretty involved, so I'll have to leave these as an exercise for you to work out, for now.  More information can be found in our Implementation Guide, which describes more variants on the basic scenario outlined here. 

If you have a burning need to discuss those with someone, drop me a line.  I'll connect you to specialists in our Protected Enterprise Consulting group for more guidance.

Related

Note:  Everything in this article applies equally to both Release 11i and 12 environments.


August 10, 2006

Aliases, Maiden Names and Nicknames

You know, I've never really understood how nicknames are worked out.  It makes sense that Jon can be short for Jonathon.  But how do you get from John to Jack?  And from William to Bill?


Regardless of the mystifying linguistic antecedents, you can accomodate this state of affairs for user management with the combination of Oracle Internet Directory and the E-Business Suite.

Linking Apps Users with OID Users

If you've been following our series of articles on using Single Sign-On and Oracle Internet Directory 10g with the E-Business Suite, you know that we link user accounts in Oracle Internet Directory with their corresponding user accounts in the E-Business Suite, like this:

Link Apps Account to OID 2:

Every user in Oracle Internet Directory has a Global Unique Identifier (GUID).  The E-Business Suite stores this Global Unique Identifier in its own user directory (FND_USER), creating a unique link between the two accounts.

Using Different Names in Apps and OID

Since the users are linked by a numerical Global Unique Identifier, it doesn't matter if their actual userids in the two namespaces don't match exactly.  In addition to accomodating those mystifying nicknames, aliases, and maiden names, this is useful for integrating the E-Business Suite with LDAP directories with different userid naming conventions.

In the example above, the user's ID in Oracle Internet Directory is "john.smith", whereas his userid in Apps is "jsmith".  The user logs on to Single Sign-On using his "john.smith" userid and transparently passes through to Apps with responsibilities tied to his "jsmith" account. 

Assuming Multiple Identities

One of our largest E-Business Suite customers -- one of the world's largest multinationals -- has centralized their global business services.  In this business model, a single purchasing agent acts as the purchaser for different geographic organizations. 

Each of these different organizations have their own business setups, so separate user accounts have been created for each organization.  A given purchasing agent logs into the E-Business Suite using different accounts.

The brute-force approach to handling this is to require the purchasing agent to remember different passwords for each account.  A more elegant solution is to link his Oracle Internet Directory userid to each of the different Apps accounts, like this:

Link Multiple Apps Accounts:

Using this approach, the purchasing agent logs into Single Sign-On using his "john.smith" account.  One of the linked accounts is flagged as the default account, and he can easily switch to the other accounts without having to log out and back in again with a different userid.

Not in the Other Direction

This "one-to-many" link is fully supported with both Release 11i and 12.  In other words, you can link a single Oracle Internet Directory account to multiple Apps accounts.

"Many-to-one" links are not supported, however.  In other words, it's not possible to link multiple Oracle Internet Directory accounts with a single Apps account.

Integration with Third-Party LDAP Directories

You might have a third-party LDAP whose userid naming conventions differ from your E-Business Suite environment.  If so, your best approach is to ensure that Oracle Internet Directory is populated with those third-party userids, like this:

August 11, 2006

COREid, Thor, Xellerate and Others

[Editor:  Apparently there are some unusual packaging and licencing particulars around Oracle Enterprise Single Sign-On and Oracle Web Services Manager.  This article has been updated to reflect these oddities.]

In our recent string of acquisitions, Oracle has made a number of purchases in the identity management space.  These have been rolled into the Oracle Identity and Access Management Suite of products.  The obvious question probably occurs to you:  can you use these with the E-Business Suite?


Oracle Identity Suite Architecture:

What's in Oracle Identity and Access Management?

First, it's important to be very clear about which products are included in this suite.  These are:
Aug 14 Update:  Within minutes of publishing this article, Oracle staff who pay attention to things like licencing excitedly informed me that the following products have "special" licencing terms.  This being a technical blog and not a marketing one, I'm going to blithely sidestep this discussion.  If you really have burning questions about licencing, I'm sure your neighbourhood Oracle account team will be happy to fill you in on these products:

Supported with the E-Business Suite


All of the Oracle Identity and Access Management Suite products are supported for use with the E-Business Suite Release 11i and the upcoming Release 12.  In other words, you may use all of the products above with E-Business Suite environments.

In addition, the E-Business Suite has special certified integrations with Oracle Single Sign-On and Oracle Internet Directory.  The Applications Technology Group has produced specific documentation and patches for these configurations for E-Business Suite customers.

What Happens If You Run Into a Problem?

For an extensive discussion about the distinction between supported vs. certified configurations, see Certification & Support for Third-Party Products.  We support more configurations than we actually certify.

If you run into a problem when using any of the products above with E-Business Suite environments, you have two options for getting support:
  1. Log a Service Request against the E-Business Suite

    Applications Support Engineers will attempt to isolate the problem. 

    If the problem's root cause lies in the E-Business Suite, such as Oracle Financials, then the Service Request will be handled by an Applications Support Engineer.

    If the problem is isolated to a product in the Identity and Access Management Suite, then the Service Request will be routed to an Identity Management Support Engineer.
     
  2. Log a Service Request against the Identity and Access Management Suite
     
    Identity Management Support Engineers will attempt to isolate the problem.
     
    If the problem's root cause lies in an Identity and Access Management Suite product, such as Oracle Identity Manager, then the Service Request will be handled by an Identity Management Support Engineer.
     
    If the problem is isolated to the E-Business Suite, then the Service Request will be routed to an Applications Support Engineer. 
Passing the Buck

All Oracle products should work together.  If you find yourself in a situation where your Service Request is being bounced around, don't just suffer through it.  Call Oracle Support and escalate to a Duty Manager, who can ensure that your SR isn't treated like the proverbial buck that no one wants to handle.

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. 

August 23, 2006

Virtualization & E-Business Suite

[Editor Sep 8 Update:  Added section to discuss virtualization recommendations for client/server Apps components]

I don't know if VMware has launched a new marketing campaign recently, but there's been a notable surge in questions lately about support for their virtualization software with the E-Business Suite.

VMWare ESX Architecture:

Our standard support policy for third-party products applies to E-Business Suite application and database servers running on virtualization software such as VMware, Microsoft Virtual Server, and Citrix, namely: 
  • Oracle will triage and attempt to diagnose issues reported for these configurations. 
  • Specific problems isolated to virtualization software that cannot be reproduced in standard Oracle environments -- i.e. environments without virtualization software -- may need to be referred to the third-party vendor for advanced debugging and resolution.
Use in Production Environments

I've heard a number of anecdotal reports from Apps customers using VMware and Citrix, but the Applications Technology Group doesn't have formal recommendations or guidelines for this configuration. 

If you plan to use virtualization software for your application and database servers in a production environment, the usual advice applies:  conduct thorough functional tests, perform peak load-testing, and have detailed fallback plans in case of issues with production environments.

Special Case:  Use with Client/Server Apps Modules

The information above applies to the E-Business Suite's application and database servers.  There is a special case for E-Business Suite client/server modules, which make direct connections to the E-Business Suite database.  These should be deployed on servers rather than end-user desktops, so remote server configurations are recommended for the following products:
  • Account Hierarchy Manager
  • Applications Desktop Integrator
  • Balanced Scorecard
  • Configurator Developer
  • Discoverer Administrator
  • Financial Analyzer
  • Financial Dimension Hierarchy Manager
  • Financial Services Suite
  • Sales Analyzer
  • Warehouse Builder
  • Workflow Builder
  • XML Gateway Client
Related

October 9, 2006

Update: Upgrading to Release 12

I am buried under email following an unexpected multi-week absence.  Combined with OpenWorld preparations, it may be a while before I get scaled up to a regular publishing cycle again.

However, I'll squeeze in a small but important update to a previous article:

That article stated that, "We plan to support upgrades from any Release 11i version to Release 12.  If your environment is at any level between 11.5.1 to 11.5.10, you should be able to upgrade to Release 12."

This is still technically correct.  But there's one more thing.  Our release engineering team has stated that it is expected that 11.5.10 will be a prerequisite for desupported E-Business Suite versions (11.5.6 or earlier) for the Release 12 upgrade. 

So, if you're on an earlier desupported release, say, 11.5.3, you will need to upgrade to 11.5.10 first.  Once you're on 11.5.10, you'll be able to upgrade to Release 12.

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. 

October 17, 2006

New Application Management Packs Coming for Oracle Enterprise Manager 10g

[Editor Oct 18, 2007 Update:  Changed link to detailed information; there's more coming, including the presentation with detailed features and screenshots, during OpenWorld.]

Our hard-working Oracle Enterprise Manager 10g team has just announced that a new set of Application Management Packs will soon be released for Oracle E-Business Suite, PeopleSoft Enterprise, and Siebel.

Enterprise Manager Screenshot:

For the E-Business Suite, this new Application Management Pack will support both Release 11i and 12.  Some interesting new features:
  • Automated discovery
  • Service Level Management
  • Out of box service models & beacon transactions
  • Configuration Management
  • Topology views
  • Integration with Application Server & Database diagnostics
  • Cloning automation for production to test environments
  • Customized beacon for Forms components
A bit more information about the new application management, monitoring, and service level capabilities can be found here:
The official press release is characteristically light on specific release dates for the E-Business Suite Application Management Pack.  Stay tuned; I'll post updates as they become available.

Related

November 7, 2006

Diving Deep Into the Release 12 Techstack

Ivo Dujmovic is an architect in our hard-working Applications Technology Integration team.  We were lucky to get some of his time at OpenWorld 2006 this year, where he discussed the deep innards of the Release 12 technology stack. 

Release 12 Techstack Overview: Overview of three-tier logical architecture for E-Business Suite Release 12, including the database, application server, and desktop tiers. 

For the most comprehensive preview released so far on how the Release 12 technology stack will be architected and work, take a look at his presentation.  He covers:
  • Highlights of new R12 techstack components
  • New Application Server 10g (10.1.2 & 10.1.3) ORACLE_HOMEs replacing the 9iAS 1.0.2.2.2 O_HOMEs from 11i
  • Switch from JServ to Oracle Containers for J2EE (OC4J) for running servlets, Java Server Pages (JSP), and Enterprise Java Beans (EJB)
  • OC4J Deployment details, including replacements for jserv.conf and jserv.properties configuration files
  • New R12 filesystem layout, including the introduction of an Instance Home (INST_TOP)
  • New use of Oracle Process Manager & Notification Server (OPMN)
  • New Forms 10g deployment
  • Comparison of 11i and R12 environment variables
  • Discussion of relative benefits of Forms Servlet vs. Server (socket) mode deployments
  • Disabled mod_plsql in R12 (more about this in a later article)
  • Things you can do today to prepare for R12
Related
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. 

November 8, 2006

Mod_plsql Not Supported in E-Business Suite Release 12

[June 4, 2008 Update:  It should be stressed that the Oracle E-Business Suite is distinct from Oracle Application Server.  Oracle E-Business Suite Development chooses to use specific Oracle Application Server components in the E-Business Suite technology stack.  These decisions by E-Business Suite Development should not be interpreted to represent the release policies or plans for Oracle Application Server. 

It must be emphasized that Oracle is fully committed to supporting
mod_plsql as part of Oracle Application Server and as part of the Oracle Database distribution into the indefinite future.]

One of my degrees is in psychology -- cognitive science, to be exact -- so it's interesting when that world intersects with my present work in the IT industry.  A landmark text in grief counseling is Elizabeth Kubler-Ross' On Death and Dying, in which she described the general grieving process as proceeding in roughly five stages:

  • Denial and isolation
  • Anger
  • Bargaining
  • Depression
  • Acceptance
Floyd Teter has astutely pointed out that OpenWorld's news of mod_plsql's demise in Oracle E-Business Suite Release 12 may trigger this process for some of you.  So, to help you through the first stage of denial, on behalf of the Applications Technology Group, I'll officially reiterate that here:
  • Release 12 will not support the use mod_plsql
Switching to Oracle Application Framework in Release 12

If you're planning on upgrading to R12 and you currently have Release 11i customizations that depend on mod_plsql, you would be well-advised to do the following things immediately:
  1. Inform your management about this upcoming change
     
  2. Prepare a comprehensive inventory of all of your existing 11i mod_plsql customizations and dependencies
     
  3. Review R12 capabilities with your business users and stakeholders, to see if your customizations are still needed
     
  4. If yes, budget time in your R12 upgrade cycle for:
  • A test install of an R12 demonstration environment to support a functional review with your business users, to see if the customizations can be further weeded out by relying on native R12 functionality
     
  • Training yourself and your developers in the Oracle Application Framework (OAF)
     
  • Doing the actual conversion from mod_plsql to the OA Framework model
For obvious reasons, the Release 12 Oracle Application Framework documentation is not available publicly yet.  In the meantime, it can't hurt to review the existing OA Framework
documentation for Release 11i, which will help you get a general sense
of the migration process. 

We plan to release some specific technical guidance on preparing your custom development for R12 soon; watch this space for that announcement.

Related
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. 

November 13, 2006

New Systems Management Capabilities for Release 12

The latest details about the upcoming Release 12 Oracle Application Management Pack for Oracle Enterprise Manager 10g were unveiled at OpenWorld.  This new product replaces the older "Grid Control Plug-in for E-Business Suite," and many of the new features are backwards-compatible with Release 11i, too.

OAM R12 screenshot:

This latest plug-in will extend the Enterprise Manager 10g Grid Control capabilities for monitoring and managing E-Business Suite environments.  It will include a number of cool new features, including:
  • User interface enhancements, including an enhanced Home and Topology views
     
  • Automatic discovery of E-Business Suite environments
     
  • New configuration management capabilities, including views, comparisons, and searchs of configuration information across multiple Apps systems
     
  • Application Service Level management for Concurrent Porcessing, Forms, Workflow, and Self-Service, with configurable service level alerts
     
  • JVM usage monitoring, including monitoring of the Application Module pool, locked AOL/J connections, and OA Framework cache components
     
  • Enhanced cloning and data scrambling capabilities
For a more in-depth discussion of these new features and capabilities -- and lots of screenshots -- check out Biju Mohan's OpenWorld presentation:
Related
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.

November 14, 2006

Summary of Oracle E-Business Suite Technology Updates

If you're a regular of this site, you might be wondering how to convey all of the latest Apps techstack news to your management.  If so, you'll find Lisa Parekh's OpenWorld 2006 presentation useful. 

Release 12 ORACLE_HOMEs:

I report to Lisa, so her presentation covers all of the breaking news reported here on this site, and more, including:
  • Release 12 technology stack changes, such as the use of Oracle Application Server 10g 10.1.2 and 10.1.3 in different ORACLE_HOMEs and the latest 10gR2 database
  • Release 12 user interface screenshots
  • Release 12 supported browsers, including IE 6.0, Firefox 1.5, and Safari 2.0
  • OA Framework Personalization enhancements
  • Oracle Portal and WSRP support for E-Business Suite portlets
  • XML Publisher enhancements in Release 12, including the new Data Extraction Engine, Bursting Engine, and other new RTF template features
  • Workflow enhancements, including Workflow Flexfields and Workflow Bulk Interface
  • Release 12 Integration Repository previews
  • Upcoming technology stack certifications for the E-Business Suite Release 11i application and database tiers, such as:
You can download her presentation here:
Related
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. 

November 17, 2006

Partitioning and Purging Best Practices for Oracle E-Business Suite

For my last post prior to a Thanksgiving holiday, here's a treat for DBAs looking to squeeze some additional performance out of existing database hardware. 

Partitioning Example GL Balances Table:

Ahmed Alomari and Mohsin Sameen put together an excellent OpenWorld 2006 session on optimizing the performance of E-Business Suite environments via partitioning and purging.  Starting with a quick survey of how partitioning has changed from the Oracle 8 database release all the way up to Oracle 10g, Ahmed and Mohsin then dive into:
  • Overview of partitioning benefits and some Apps modules that take advantage of this out-of-the-box, and custom partitioning
  • Technical advantages, such as backup, index rebuild, and Cost Based Optimization (CBO ) implications
  • Integration with Information Lifecycle Management (ILM) for data storage on lower-cost storage devices
  • Techniques and relative merits of range, list, hash, and composite partitioning
  • In-depth discussion of index partitioning methods, including the new Global Hash Partitioned (prefixed) capabilities in 10g
  • Useful data dictionary views for partitioning
  • Before and after comparisons, and actual customer case studies with real statistics
  • Review of purging and archiving programs shipped out-of-the-box with the E-Business Suite
  • Samples of typical customer purging runs
  • Review of the latest Purge Portal released with the E-Business Suite 11.5.10
  • Sneak previews of Release 12 enhancements to the Purge Portal, like this (I can't resist a screenshot):
Release 12 Purge Portal Screenshot:

Related
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. 

December 5, 2006

Distinguishing Release 12 from Fusion Applications

With so many Apps releases in the pipeline, it isn't surprising to hear that at least one of our readers might need a
hand sorting them out.   Earlier this year, I committed to keeping this website free of marketing rhetoric.  Confusion over marketing statements, however, can sometimes drown out other signals, so I'm going to take a short detour today to clarify how upcoming Apps releases relate to each other, and point you to some additional resources if you want more details. 

John Wookey, SVP of Application Development, included this slide in his OpenWorld 2006 keynote address:

Oracle Apps Release Roadmap:

To summarize what this means to E-Business Suite customers:

  • Oracle E-Business Suite Release 12 is the next major release after Release 11i
     
  • Release 12 is expected to have its own stream of updates, such as 12.1 and 12.x
     
  • Oracle Fusion is our next-generation enterprise applications suite, bringing together the best functionality and technology from of all Oracle applications. 
     
  • Oracle Fusion Applications will be released after Release 12. 
    Fusion Applications is not the same as Release 12.
     
  • Under the Applications Unlimited support policy, Oracle E-Business Suite customers have the choice of staying with their current release or migrating to another one.  There are no forced migrations.
Our E-Business Suite executives have devoted a fair bit of time to covering the Applications roadmap, with particular emphasis on Fusion Applications.  In particular, I'd suggest these OpenWorld sessions:
Technical articles discussing Release 12's technology stack can be found here:
Related
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. 

December 15, 2006

Patch-Related Enhancements in Release 12

Patching is an integral part of an Apps DBA's operational duties, and I've previously written about some of the things we're working on to improve the whole Lifecycle Management experience. 

R12 Apps Dashboard File History Screenshot:

In his OpenWorld 2006 session, Kenneth Baxter took the wraps off some of the new patching and maintenance features coming in Release 12.  His crisp presentation is full of interesting details about the changes to the maintenance capabilities in R12's Oracle Applications Manager, notably:
  • New Patch Wizard functionality, improving the process of identifying, downloading, and analyzing recommended patches
  • Registering flagged files to understand a patch's impact on customizations
  • Improvements in determining whether given patches have been applied
  • Manual Steps Infrastructure (MSI) functionality, reducing the number and complexity of manual steps
  • Support for checking codelevels and baselines, reducing the risk of a patch "breaking" other functionality
  • Patch filters to tailor patch searches to your specific environment
  • Central access point for all patch details, including applied patch reports, timing reports, and log files
As an added bonus, his presentation is packed with R12 screenshots; you can download it here:
Related
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. 

January 8, 2007

Launch Event for E-Business Suite Release 12

Editor Jan 26 2007 Update:  Revised article to point to latest release information.



Happy New Year, everyone.  I see that the blogosphere is starting to buzz with anticipation over the New York launch event for the E-Business Suite Release 12.

R12 Launch Event:

We're pretty excited about this launch event, too.  Please see this article about Release 12 availability:



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. 

January 16, 2007

Four Critical Changes for Customizations in Release 12

If you're planning to upgrade from the E-Business Suite Release 11i to Release 12, one of your most important preparatory tasks is to catalog all of the customizations you've deployed in production. 


You may have built customizations or extensions to Apps 11i using any of the following technologies:
  1. mod_plsql

  2. Oracle Reports Server
     
  3. Oracle Graphics Integration with Oracle Forms
     
  4. Oracle Applications Framework pages in the AK Repository (AK mode)
If so, you should review the following Metalink Note to evaluate the implications of Release 12's new technology stack on your deployment:
If you're looking for a bit of guidance on how to tackle this task, I've outlined a general business approach in this article:
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. 

January 25, 2007

E-Business Suite Release 12 is Generally Available

The waiting is over, and that sound you hear is cheering from Oracle Apps Development teams around the world. 

R12 Launch Event:

I am very pleased to announce that Oracle Applications E-Business Suite Release 12 -- the Global Business Release -- is now available for new and upgrading customers on all supported languages.  It's available from the Oracle Store and for download from  Oracle Electronic Product Delivery.

Enhanced Documentation in Release 12

Significant strides have been made to improve the amount of Release 12
information via MetaLink. The About Documents that accompanied releases
in the past have been replaced with a single comprehensive roadmap document:
The Documentation
Roadmap provides a landing pad to help you navigate through the wealth of material available, and highlights individual documentation
roadmaps at the product and product family level too.

What's New in Release 12?


There are over 1,500 new features in Release 12, with significant new functionality in the Financials area.  Release 12 includes the latest in Oracle technology, including the 10gR2 Database and Oracle Application Server 10g.

For links to the published Release Content Documents for Oracle Applications, E-Business Suite Release 12, see the following document:
Release Content Documents (RCD) highlight new or changed functionality only.  Existing functionality from prior point releases is not described.  You can use the Release Content Note as a central launchpad for individual Release Content Documents for all of the E-Business Suite product families, including:
  • E-Business Suite (General)
  • Applications Technology Stack
  • Intelligence Family
  • Customer Relationship Management Family
  • Marketing & Sales Family
  • Logistics    
  • Supply Chain Management Family
  • Advanced Planning
  • Procurement Family
  • Process Manufacturing
  • Discrete Manufacturing
  • Maintenance Management
  • Customer Service Family
  • Service Execution
  • Projects Family
  • HRMS Family
  • Financials Family
  • Customer Data Management    
  • Property Manager
  • Product Lifecycle Management    
  • Order Management    
  • Student Systems
Regular readers of this website will likely be most interested in the Applications Technology Stack RCD, which covers new features for the following areas:
  • Technology Components
  • New Look and Feel - "Swan" User Interface
  • Identity Management Integration
  • Security
  • Oracle User Management
  • Functional Administration
  • Concurrent Processing
  • Oracle Applications Tablespace Model (OATM)
  • Oracle Application Framework (OAF)
  • Workflow, Messaging, and Integration
  • Oracle Applications Manager and Grid Control Plug-in for the E-Business Suite
  • Applications Installation and Configuration Management 
  • Oracle XML Publisher
  • Oracle Web Applications Desktop Integrator
  • Oracle Report Manager
  • Oracle iSetup
  • Oracle Tutor
Platform Availability

You can check the Oracle Electronic Product Delivery site for media packs for available operating system platforms.  If your specific platform isn't available yet, keep checking the site for updates.  If you plan to download this yourself, be prepared to put aside some time for the task -- there are over 70 disk images in the media pack!

Tune Into Our Launch Event

Don't forget that our launch event is still lined up for January 31st.  If you can't join us in New York, you can still reserve a virtual seat for the online event now.

Now, you'll have to excuse me.  I need to brush the confetti out of my hair...

February 6, 2007

Getting Started with the Release 12 Technology Stack

The sheer amount of available Release 12 documentation can be intimidating.  The R12 Online Documentation Library is over 400 MB.  On top of that, a great deal of information needed by R12 Apps DBAs can only be found in standalone Metalink Notes.  If you're feeling overwhelmed, don't panic:  this is the first of a series of articles highlighting the key documentation that you'll need to get up to speed.

Release 12 Documentation Library Screenshot:

Starting at the Very Beginning

With a tip of the hat to Julie Andrews, the first stop for all system administrators is the Oracle Applications Concepts Guide (Part No. B31450).  Even if you're familiar with Release 11i, this guide is worth scanning for updates specific to Release 12.  It covers the general technology stack components, the new R12 filesystem structure, database organization, new 10gR2 database features, and operational topics such as cloning, high availability, user authentication with OracleAS 10g, load-balancing, and other advanced topics.

A Roadmap for Techstack Metalink Notes

The E-Business Suite's technology stack is regularly updated with new supported configurations and certifications.  Given that procedures and specific patch numbers change on a regular basis, the Applications Technology Group publishes this class of documentation via Metalink Notes. 

Finding the right Metalink Note can be difficult sometimes, so a new Release 12 Note roadmap has been assembled.  The Oracle E-Business Suite Release 12 Technology Stack Documentation Roadmap (Metalink Note 380482.1) lists the key Metalink Notes that you'll need to implement and manage your environment, covering areas such as:
  • Installation & Configuration (including AutoConfig, cloning, shared filesystem, load-balancers, and Forms socket mode)
  • Database & High Availability
  • Application Server (including both internal and external OracleAS 10g services such as Oracle Internet Directory, Single Sign-On, Portal, and Discoverer)
  • Java (including the use of the native Sun J2SE plug-in instead of Jinitiator)
  • Security (including SSL, demilitarized zones, and Wallet Manager)
Stay tuned -- I'll be covering some of these topics in more detail in future articles.

February 9, 2007

JDeveloper 10g with OA Extension Now Available

If you're planning on extending your E-Business Suite Release 12 OA Framework-based  Oracle Applications pages, you'll be pleased to hear that the Oracle JDeveloper 10g with OA Extension (Patch 5856648) is now available for download from Oracle MetaLink.

Full details on Oracle standards for personalizing and extending OA Framework-based applications in E-Business Suite Release 12 can be found in this documentation roadmap:

Related

February 15, 2007

Choosing Between Release 12 or 11i

One of the most frequently asked questions at OpenWorld was, "Should I upgrade to 11.5.10 or Release 12?"  Release 12 wasn't available at that time, and we couldn't even discuss possible release dates, so the answer was further complicated by the uncertainty of when an upgrade could actually be started.  Now that Release 12 is available, the answer is a bit simpler. 

Release 12 website screenshot:

Not About the Technology Stack

First, I should emphasize that even though you're reading a website dedicated to technology stack topics, the answer to this question is not about the relative merits about the technology stack for the respective E-Business Suite releases.  At the heart of the choice between Release 11i and 12 is a hierarchy of business decisions, decisions that require broad and deep input from the stakeholders in your end-user community.

Assessing the Business Benefits

Back in the days when I was a management consultant, a system selection project could run for months (if not years).  As with all business decisions in large organizations, your costs and benefits will likely be weighted by qualitative and political considerations, too.  With that in mind, I should emphasize that a comprehensive system selection framework is far beyond the scope of this article. At minimum, if you're deliberating between a Release 11i (11.5.10) or 12 upgrade, I would recommend checking that your existing system selection framework includes variants of the following questions:
  1. What's the prioritized list of applications that your business users use today?  What are the differences in Release 11i and Release 12 functionality for those applications?
     
  2. What business advantages, process improvements, and new organizational capabilities will be possible with the new Release 12 features?
     
  3. What are the new architectural or deployment capabilities in Release 12?  How will these new capabilities improve system performance, scalability, availability, manageability, and security?
     
  4. What investments have you made in adapting your organization to Release 11i, and vice versa?  This might include:
    • Employee, partner, vendor, and supplier training
    • Customizations and personalizations, including custom Forms, OA Framework screens, workflows, concurrent programs, and reports
    • Integrations with third-party systems
       
  5. Which of your customizations, extensions, and personalizations can be replaced with new Release 12 features?  What savings will these represent?  How much of those investments will carry over to Release 12? 
     
  6. How will Release 12 help reduce your operational costs?  What are the incremental costs of Release 12 infrastructure, relative to your current Release 11i infrastructure costs?  These costs might include server, storage, and networking hardware and licencing
Getting Help from Oracle

This might seem like a daunting task, but you're not on your own.  Remember that Oracle has field specialists who can help you work through these questions.  If you haven't already done so, you shouldn't hesitate to contact your Oracle account manager for help.  He or she can bring in specialists to describe the new features for your key applications, and even engage Development in those discussions, if  necessary.

References

February 19, 2007

Personalizing and Extending Release 12

The JDeveloper 10g with OA Extension was recently released for use with the E-Business Suite Release 12.  Following on that theme of extending and personalizing Release 12, you might find it useful to review Sara Woodhull's excellent presentation on this topic from OpenWorld 2006.


Release 12 Personalization Screenshot:

Sara's OOW presentation covers the E-Business Suite Release 12's Oracle Applications Framework (OAF) architecture, which is designed to provide rich and upgradable personalization and extensibility capabilities in a declarative, object oriented model.  This allows Release 12 to be extended and customized without the overhead of traditional development projects.  Topics included in this presentation are:
  • OA Framework Model-View-Controller architecture and key features
  • Personalizations features, including:
    • The ability to hide and show page items and regions, reordering page items, adding new items, adding corporate branding
    • Importing and exporting personalizations with the Personalization Document Manager
    • New user interface for creating personalizations
    • Matching the Release 12 colors and fonts to match your corporate website
    • Using simple expression (SPEL) bindings for more control over fields, items, and regions
  •  Extensibility features, including:
    • The ability to add new business logic to existing screens
    • Durability of extensions, allowing them to be preserved across upgrades
    • Use of Oracle JDeveloper 10g with OA Extension to support J2EE development and integration with Release 12
    • Support for service interfaces, standalone components that can be deployed as web services, EJB session beans, or as co-located Java APIs
You can download her presentation here:
Related

February 20, 2007

FAQ: Using Oracle Application Server 10g with E-Business Suite Release 12

I've noticed a curious effect over the years of working in the Applications Technology Group:  the volume of incoming questions about the E-Business Suite's technology stack is inversely proportional to the quality and availability of our formally published documentation. 

Release 12 Techstack Overview: Overview of three-tier logical architecture for E-Business Suite Release 12, including the database, application server, and desktop tiers. 

Questions about the Release 12 technology stack are starting to mount, so we've updated one of our more-popular FAQs for this latest release:
This FAQ covers the Release 12 topics such as:
  • General configuration & installation with Oracle Application Server 10g
  • Discoverer 10g integration
  • Portal 10g integration
  • Single Sign-On & Oracle Internet Directory 10g integration
  • Integration with third-party authentication systems and LDAP directories
  • Security
Here are some examples of the frequently asked questions covered in this document:
  • How is Oracle Application Server 10g integrated with Oracle E-Business Suite Release 12?
  • What versions of Oracle Application Server 10g can be used with Oracle E-Business Suite Release 12?
  • What are the certified configurations of Oracle Application Server 10g with Oracle E-Business Suite Release 12?
  • Can E-Business Suite Release 12 be integrated with third-party authentication systems?
  • Can E-Business Suite Release 12 be integrated with third-party LDAP directories?
  • Can Oracle E-Business Suite Release 12 be integrated with third-party portals?
  • What is the latest Discoverer version that works with Release 12?
  • Does the Release 12 Rapid Install include an OracleAS 10g Infrastructure?

February 22, 2007

Additional Configuration and Deployment Options in Release 12

The AutoConfig utility provided with E-Business Suite Release 12 automates a wide variety of deployment options. However, there are a number of optional configurations that AutoConfig doesn't automate yet.  In this initial release, implementation of some of these optional configurations requires additional manual steps or the installation of additional patches.


Release 12 Techstack Overview: Overview of three-tier logical architecture for E-Business Suite Release 12, including the database, application server, and desktop tiers. 

If you plan to use any of the following deployment options, you may need to perform some additional manual steps:
For a brief discussion about these configurations, see Oracle E-Business Suite Release 12 Support for Additional
Configuration & Deployment Options
(Metalink Note 380483.1).

Related

February 23, 2007

Application Management Pack for Oracle E-Business Suite Now Available

Editor May 7, 2006 Update:  It's been pointed out that the relative positioning between Oracle Application Manager and the Oracle Application Management Pack could stand to use some elaboration.  Oracle Application Manager is still present and bundled with both Apps 11i and 12.  The Oracle Application Management Pack is a purchased add-on for Oracle Enterprise Manager.  They're related but distinct products.

If you've used previous versions of Oracle Applications Manager (OAM), you'll be pleased to hear that the latest generation of systems management tools has just been released:  the Application Management Pack for Oracle E-Business Suite is now available.  This new product plugs into Oracle Enterprise Manager Grid Control 10gR3, and is available for Linux platforms in its initial release.


Enterprise Manager Screenshot:

Application Management Pack for Oracle E-Business Suite extends Enterprise Manager 10g Grid Control to help you monitor and manage Oracle E-Business Suite system environments. The Pack can be used to manage the following Apps releases:
The pack integrates Oracle Applications Manager with Enterprise Manager Grid Control, allowing you to drill down from Enterprise Manager's server monitoring level to specific E-Business Suite technology stack components.  Some of the key new capabilities include:
  • Automated cloning: Using the pack, Enterprise Manager Grid Control can be used to clone an Oracle E-Business Suite system (both 11.5.10 and Release 12) automatically.
  • Service Level Management (SLM):  Monitor the E-Business suite infrastructure and application service's availability and performance, and capture activity and performance metrics for trend analysis.  
  • Configuration Reports:  Over a hundred reports on E-Business suite configuration details.  Reports can be viewed, searched, and compared from within Enterprise Manager Grid control.
Free downloads for Oracle Enterprise Manager 10g Grid Control are available, but it's important to note that the Application Management Pack for Oracle E-Business Suite is a separately licensed product.  If you'd like to do a hands-on evaluation of this latest release, you should give your Oracle account team a call.

Related

February 26, 2007

Mixed Platform Architectures for Release 12

Editor Mar 15 Update:  There are a number of mixed platform architectures that are supported for Release 12 today, although certification of additional platforms is still pending.  More details added below.

Editor Update:  It turns out that our official nomenclature for these types of configurations has evolved between releases.  In Release 11i, these were called "split configurations."  In Release 12, these are now called "mixed platform architectures."


Here's a quick update for those of you who might be interested in "mixed platform architectures," where the E-Business Suite's database and application servers are deployed on different operating system platforms. 


Itanium Chip:

R12 Fully Certified Platforms

As of March 15, 2007, the following are the fully certified platforms (application and database tiers) for the E-Business Suite Release 12. See Oracle Certify for exact versions and platforms certified with E-Business Suite:
  • HP-UX Itanium
  • HP-UX PA-RISC
  • IBM AIX
  • Linux x86 and x86-64 (32-bit OS)
  • Linux x86-64 (64-bit OS)
  • Microsoft Windows Server 2003
  • Sun Solaris Operating System (SPARC)
These platforms can be mixed together, i.e. the database tier can use any one of these platforms, and the application tier can use any one of these platforms.  So, this would be a certified combination:  database tier on HP-UX Itanium, and application tier on Linux x86-64 (32-bit OS).

Not Certified Yet... For Use on the Database Tier Only

Certifications for the following additional platforms are underway for
the database tier only:
  • IBM System z Linux
  • Linux Itanium
  • Microsoft Windows Server 2003 x64
  • Microsoft Windows Server 2003 Itanium
In other words, you can't use any of these four operating system platforms for your database tier yet, but these certifications are forthcoming.  When they're certified, you'll be able to deploy any of these four platforms on your database tier only.  At that time, you will be able to mix any of these four database tiers with application tiers running on any of the existing fully certified platforms in the first list.

The certifications of the four database tier only platforms are underway now, and are expected to be released in conjunction with the R12 certification for the 10.2.0.3 Database.  Firm schedules aren't available yet, but feel free to monitor or subscribe to this site for updates, which I'll post as soon as they're available.

Still Confused?

Don't worry -- you're not the only one.  As you can infer from the changes to this article, we've been working through the nomenclature around these mixed platform architectures ourselves.  If you're still struggling to get a handle on this, either log a Service Request or contact your Oracle account manager to get some help with your specific target platform architecture.

Related

March 5, 2007

Security Best Practices for Release 12

If you're working with Release 12, you'll be pleased to hear that our Applications Technology Group Security team has just published a new document detailing our best practices security recommendations for this release.

Like its Release 11i cousin, this document covers the following topics for Release 12:

  • A framework for securing different segments of your E-Business Suite deployment, starting with the operating system
  • Pointers to essential Apps security reference materials, security alerts to monitor, and recommended patches
  • Guidance
    for securing internal deployments, including the database at the schema
    level and for database net access, the Apps web tier, and end-user PCs
  • Tips for hardening your EBS security setup
  • Monitoring security through Oracle Applications Manager (OAM)
  • Guidance
    for securing externally-facing deployments in DMZs, including the use
    of Responsibility filters, URL filters via the URL firewall, noise
    filters via mod_security
For details, see:
Related

March 8, 2007

AppCast: Release 12 Technology Highlights in 10 Minutes

If you're looking for something to listen to on your iPod for your commute, I'd recommend dropping into our Oracle E-Business Suite AppCasts center, which has a range of podcasts about Oracle Applications.  These podcasts are hosted by Cliff Godwin, senior vice president of the Applications Technology Group, who manages to pack a lot of information into these interviews with his guests.

Release 12 Techstack Overview: Overview of three-tier logical architecture for E-Business Suite Release 12, including the database, application server, and desktop tiers. 

Lisa Parekh, vice president of our Application Technology Integration team, recently recorded a short podcast with Cliff that touches on the major technology stack advances and highlights in Release 12.  She touches on most of the key new R12 technology stack components and their associated benefits, including:
  • Oracle 10gR2 Database
  • Oracle Application Server 10g (10.1.2 for Forms & Reports, 10.1.3 for HTML & Java)
  • OA Framework and the new user interface
  • Oracle Containers for Java (OC4J)
  • Oracle Personalization
  • Extending R12 with JDeveloper 10.1.3
  • Integration Repository
  • XML Publisher
If you have ten minutes to spare, this is a quick way of getting a high-level summary of some of the most interesting new aspects of our new Release 12 technology stack:

March 14, 2007

Loopbacks, Virtual IPs & the E-Business Suite

[Editor Mar 27 , 2007Update:  Updated with more information about loopback requirements for internal and external applications.]

[Editor Mar 16 , 2007 Update:  Added loopback diagram and updated test section with additional comments.
]

An area that seems to be perennially troublesome for E-Business Suite architects and sysadmins is that of multiple domain names, virtual IPs and loopback issues.  Here's a quick primer on some of the key concepts that you should be familiar with.


What's a Virtual IP?

Let's say that you'd like to set up an E-Business Suite environment with two different domain names, following Metalink Note 287176.1 (for Release 11i) or Note 380489.1 (for Release 12):
  • partners.company.com for external users
  • employees.company.com for internal users
If you've got a generous networking budget, one approach would be to set up a physical architecture shown below.  This architecture uses two different physical load-balancers, one dedicated for external users (LBR1), and another dedicated for internal users (LBR2):

Physically Separate Load-Balancers:

Note that in the architecture above, the reverse proxy server acts as the "web-entry point" -- that is, the primary point from which all end-user traffic gets dispatched -- for external users.  That's the gold-plated approach. 

However, many customers have big, sophisticated load-balancers that can handle the combined traffic for both domains.  In these situations, the single physical device can be assigned two virtual domain names, each with their own virtual IP address, like this:

Virtual IPs for a Single Load-balancer:

In this architecture, the load-balancer has two virtual domain names, each of which serves as the "web-entry point" for the respective domains:
  • Traffic from User 1 for partners.company.com goes to the external pool of application servers, either Node 1 or 2
  • Traffic from User 4 for employees.company.com goes to the internal pool of application servers, either Node 3 or 4
Technical Requirements for E-Business Suite Environments

Virtual IPs and multiple domain names are supported for E-Business Suite, for both Release 11i and Release 12.  A number of basic requirements need to be met:
  1. Each virtual domain name must have its own virtual IP address, and your end-users should be able to access those IPs in your DNS. 
     
  2. E-Business Suite technology stack components need to be able to access the load-balancer's virtual IPs, too, due to loopback requirements (see below).
If your load-balancer is capable of it, you should enable additional features such as resource monitoring, fail-over, and immediate returns of failed traffic.  For more details about our recommendations for those features, see the Metalink Notes below.

What are Loopbacks?

For reasons too arcane to delve into here, some components in the E-Business Suite technology stack sometimes need to call other techstack components (or themselves) at various times.  They do so by sending those calls to the web-entry point -- the load-balancer or reverse proxy for their domain -- which forwards those calls to the requested technology stack component, as shown in the following diagram:

Revised Loopback Example:

Loopbacks in Internal and External Applications

Some E-Business Suite modules can be deployed for external use.  These include iSupplier Portal, Oracle Sourcing, iRecruitment, iStore, iSupport, and others listed in Appendix A of Metalink Note 287176.1.  These applications do not require loopbacks.

Applications that aren't on this list are intended for internal deployments.  These applications may require loopbacks.  In some internal architectures, the internal web-entry point is separated from the actual application tier server node by a firewall.  In the diagram above, E-Business Suite techstack components in the application server pool used by internal users will send their loopback requests to the HTTP LBR2 device.  It's not shown in the diagram, but one can envision an architecture where a firewall exists between HTTP LBR2 and Web Nodes 3 and 4.  If this firewall blocks outbound loopback traffic from the Web Nodes to the load-balancer, then the techstack services for internal applications that depend on those loopback connections will start to fail... sometimes in puzzling ways.

Firewall Rules & Production Rollouts

This is a major source of problems that I see reported when moving from testbeds to production rollouts.  Testbeds usually include only one or two machines and they're never separated by firewalls.  However, production systems are usually spread across multiple physical servers, each separated by firewalls. 

Making the situation even more entertaining, networking, security, and E-Business Suite administrators are often in different groups.  Invariably, one team forgets to fill in the other team on their networking requirements.  The E-Business Suite (which worked fine in the testbed environment) seems cranky and unstable in pre-production.  The production rollout gets hung up until the problem is diagnosed and appropriate firewall rules are tweaked.

Don't let that happen to you.  Identifying a loopback problem is really simple:  on each of your application servers in each of your domains, use either ping or telnet to hit each domain's web-entry point.  Likewise, from both an internal and external end-user desktop, ping the respective internal or external E-Business Suite domain name.  If you get a response in all cases, then your firewall rules are
configured correctly.  If not, then give your network and security
teams a call.

Update:  It's been pointed out that the ping test alone is a necessary but not sufficient test, since it doesn't prove whether a given port is accessible to the calling client or application tier service.  Additional tests such as using wget or telnet (the latter documented in the latest updates to Metalink Note 217368.1) may also required to demonstrate that a particular port is accessible through one or more firewalls.

Related

[Unrelated postscript:  Possibly due to sunspots, the lunar cycle, or global warming, any emails you sent me on March 11 or March 12, 2007 may be delayed, possibly indefinitely.  If you sent me anything in that time, I'd recommend resending it.]

March 19, 2007

Update #2 on Vista Certification for the E-Business Suite

[Nov 8, 2007 Update:  Vista is now certified with IE 7 for E-Business Suite Release 11i and 12.  See this article for full details.]

[Oct 11, 2007:  See the latest
Update #5: Vista Certification with the E-Business Suite]

We haven't received a lot of responses to our informal survey about your plans for upgrading to Microsoft Windows Vista.  However, the requests for updates on our pending Vista certification are gradually becoming more commonplace, so here's a quick summary of where we are today for Release 11i and 12 certification of that desktop client.

Microsoft Windows Vista Logo 2:

As of today, we're still working on certifying both Release 11i and 12 with Vista.  This configuration is expected to require the use of Sun's J2SE 6.0 plug-in, but we're also evaluating the use of the J2SE 5.0 plug-ins, too.  At this stage, I suspect that it's unlikely that we'll be certifying JInitiator with E-Business Suite clients running on Vista, but that's also still under investigation.

In the process of our testing, we've identified a Sun J2SE bug that affects E-Business Suite environments for Vista deployments.  This is a critical issue, unfortunately, and we're working with Sun to get this into a future J2SE release.  As of today, we don't have a firm schedule for the next J2SE release containing this fix.  As a result, we don't have a firm schedule for the completion of our Vista certifications for either Apps 11i or 12 right now, either.

I'll continue to post updates on this certification and the configurations that we expect to support as soon as I have more details that I can share here.  Stay tuned...

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. 

March 27, 2007

DB Sizing Examples for Release 12 Upgrades

Database sizing for the E-Business Suite can be a tricky business.  Doing sizing estimates for major upgrades, like moving from Apps 11i to 12 can be even tricker, given the degree of data model changes involved.

R12 Upgrade Sizing Screenshot:

Our Applications Performance Group has released an informative white paper with sample data from one of their internal benchmark environments, which they upgraded from Release 11i (11.5.10.CU2) to Release 12.  Interesting findings:  they tested two upgrade scenarios, one with three years of historical data, and the other with twelve years of data.  The large Apps database with 12 years of data went from 6.6 TB to 7.2 TB, an increase of ~8%. 

This white paper covers contains:
  • Tablespace and schema sizing information
  • Information on required post upgrade concurrent jobs
  • Upgrade timing
  • Some best practices to manage the upgrade of Release 12
For complete details, see:
Your Mileage Will Vary

Naturally, these results won't map directly to your own upgrade, since your transactional mix (and level of master-detail complexity) will be unique to your own organization.  However, this paper is useful in that it shows the general ballpark. 

If you have data on your upgrade tests, by the way, we'd be delighted to hear from you.  Feel free to post a comment to this story or drop me a private email.  I'll be sure to pass on your comments to our Apps Performance team for you.

Related

April 4, 2007

Fully Automated Cloning for Release 11i and 12

Cloning is the process of creating an identical copy of an already existing Oracle Applications system.  Cloning is a regular part of an Apps DBA's responsibilities, so you're probably already familiar with the latest Rapid Clone utility and its predecessor,  adclone.pl, the original AD Clone Utility.  If you've used those tools in the past, you likely also know that overall cloning process requires some user intervention for things like the APPS password and so on. 

Enterprise Manager Screenshot:

A customer recently asked whether the following cloning process can be fully automated, so that no user intervention is required at all:
  1. Shut down the PROD environment for both the application server and database tier
  2. Do an offline preclone of both tiers
  3. Copy both tiers to another server (the sandbox environment)
  4. Restart the PROD environment
  5. Do an offline postclone of both tiers for the sandbox environment
  6. Start the sandbox environment
In researching that, I was pleased to learn that this kind of automation is a new feature in the latest Application Management Pack for Oracle E-Business Suite for Enterprise Manager Grid Control 10gR3. 

The management pack automates the cloning of both Release 11i (11.5.10 with ATG RUP4) as well as Release 12 environments.  You go through a step-by-step interview process to configure the clone routine once, and then you can reuse the cloning routine as many times as you wish.  In addition, the cloning routing can send out a notification if it failed.

Very slick.  If you've had a chance to try this, I'd be interested in hearing about your experiences with this new feature.

References

April 11, 2007

Getting Personal with OA Framework Pages

I often receive questions similar to the following, regarding personalization of E-Business Suite (EBS) HTML-based pages:

"How can we quickly determine if particular E-Biz pages support personalizations?"

First of all, I assume we're talking about the Oracle Application Framework (OAF) Administrator personalization, not Personalized Views (Saved Searches).

All pages built using OA Framework are personalizable by default--the page developer has to do something specific to make the page be non-personalizable.  One thing a developer can do to make a page (usually just a region or field) non-personalizable is to set a specific property to false during development.  The other is to create regions or fields programmatically (so they don't exist in the page definition that is stored for using with personalizations).  These are generally the exception cases.

Some HTML Products Don't Support OAF Personalization

In 11.5.10 (11i), many E-Business Suite CRM products and some other products were built using a different technology stack (JTT/JTF), so they couldn't use OAF personalization.  In EBS Release 12, most of these have been rebuilt using OAF. 

EBS Business Intelligence products have their own version of personalization, and they do not use the OA Framework feature even though they are built with OAF.  Business Intelligence products have somewhat different implementations of their personalization depending on whether you are looking at a dashboard or a report page.  But the way to tell if it's a BI page is to look in the upper corners.  If you see an Actions dropdown, it's a BI page.

BI Page screenshot:

But Which Ones Are Built Using OA Framework?

Sometimes people have trouble telling which pages are created using OA Framework.  Here are several ways I use to tell if a page is built using OAF:

The best and easiest way I know of is to look for "OA.jsp" in the URL of the page.

Is OA.jsp in the URL screenshot:

You can also use the About this Page feature to confirm if a page is an OA Framework page.  If you don't have it already, you'll need the FND: Diagnostics profile option set to Yes (you may need your administrator to set this).  Go to a product page (I'm using iProcurement here) and click on the About this Page link:

About this page screenshot:

If you see that the first line of the page definition is "pageLayout", it's an OAF page.

Page definition starts with pageLayout screenshot:

Beyond looking at each page individually, you can use the About this Page feature to get a whole list of pages built with OAF, all at once.  Since you're already there, simply go look at the page context (menu), as follows:

About this Page > Page Context > Menu (Expand All)

Most of the functions in the menu display a URL, so you can see at a glance which ones start with "OA.jsp":

Lots of OA Framework Pages screenshot:

Another way to check for a single page is to use View Page Source in the browser.  Early in the source, you will see the following for an OAF page:

<!-- METADATA_SOURCE - JRAD -->

You can also list the pages (and more) using the JDR_UTILS package.  It is described in the "Inspecting the MDS Repository Content" chapter of the Oracle Application Framework Developer's Guide for your release version (available on MetaLink).

Finally, you can set the "Personalize Self-Service Defn" profile option to Yes to allow personalization, and then look for the Personalize Page link on the top of each page.  Of course you can also use the link to see the personalization hierarchy page (or the context page if you are using 11.5.9 up to 11.5.10 CU1--it changed in 11.5.10 CU2).

Note that all of this applies to both Release 11.5.10 and Release 12 of the E-Business Suite.  It also applies to EBS 11.5.9 if you applied OAF 11.5.10 to it as part of a patch.

To learn more about OA Framework Personalization, see the Oracle Application Framework Personalization Guide in the Oracle Applications Online Documentation Library.

Here's an Extra Tip: Hidden Fields Between the Fields 

Some product teams build features into their pages that are hidden by default because they expect most customers won't use them.  These include extra fields for special purposes, hidden Additional Information regions containing descriptive flexfields, and so on.  We recommend to product teams that they explicitly document places in their applications where customers are expected to personalize the pages.  Check your product's documentation for such updates.  I know that iProcurement, at least, mentions such hidden fields directly in the text of their implementation manual.  I found one on page 2-17 of the Oracle iProcurement Implementation and Administration Guide, Release 12, Part No. B31402-01.  Also, the Oracle Workflow Administrator's Guide and Oracle Workflow User's Guide both have appendices highlighting some of the personalizations for Workflow pages that customers may be most interested in using.

Happy personalizing!

Related


April 12, 2007

New Rapid Install StartCD (12.0.0.22) for Release 12

A new Rapid Install startCD, patch 5885627, for E-Business Suite Release 12 is now available for download from Metalink.  This new Rapid Install startCD (Version 12.0.0.22) fixes a dozen installation-related issues for Release 12.

Release 12 Rapid Install screenshot: Screenshot of E-Business Suite Release 12 Rapid Install Wizard

This patch can be uncompressed on top of any previous R12 startCD under the main staging area.  Following our standard support policies, this is the only startCD version supported at this point.  If you report problems with prior R12 startCDs, it's likely that you'll be asked to apply this version before advanced debugging can proceed.

What's New?

This new startCD has two high-priority fixes:
  • 5939781 : INVALID ORACLE HOME NAME FORMAT (HYPHEN)
  • 5947071 : CONVERT
    CHARACTER SET (ADDCCNV.SQL) FAILS WITH ORA-600
The first fix resolves a problem where the registration of the ORACLE_HOME fails if the machine name has a hyphen (e.g.
atg-sun.us.oracle.com).  The second fix resolves a problem where the database conversion fails with ORA-600 on Windows platforms.

In addition, the new startCD also fixes the following bugs:
  • 5757402 : EDIT PATHS FORM NOT RETAINING PATHS IF YOU NAVIGATE
    BACKWARDS
  • 5769619 : ADAUTOSTG.PL MENU ENHANCEMENT
  • 5735127 : CURRENT
    INSTALL MECHANISM DOES NOT SUPPORT FOR NEW OS VERSIONS
  • 5754396 : RI.RIW:
    RAPIDWIZ DOES NOT PRESERVE VALUES ON TRAVERSING
  • 5860525 : UNINSTANTIATED
    VARIABLES TEST FAILS
  • 5916075 : SILENT INSTALL IS FAILING ON
    WINDOWS
  • 5893147 : POST CHECKS FAIL AFTER USING RAPID INSTALL TO UPDATE
    CONFIGURATION
  • 5922016 : JDBC CONNECTION TEXT SHOULD BE GENERIC
  • 5893659 :
    SILENT INSTALL IS FAILING WITH JAVA EXCEPTION
  • 5934198 : AT RAPIDWIZ SESSION, ADDBCCNV.SQL
    : ORA-01012: NOT LOGGED ON
Related

April 13, 2007

OracleAS 10g + E-Business Suite Statement of Direction

[Aug 9, 2007 Update:  Integration of the E-Business Suite with Single Sign-On 10g is a prerequisite for the use of Oracle Access Manager.  This is elaborated upon in the Statement of Direction, as well.]

Our certification matrix is constantly being updated as we certify new product releases with the E-Business Suite.  The Certify database on Metalink is always the definitive authority for certification questions.  However, the Certify database can be tricky to navigate and doesn't always reflect our directions or planned certifications.  That's where Statement of Direction documents come in handy.

Certification matrix: Certification matrix for E-Business Suite Release 11i and 12 with various Oracle Application Server 10g products

Our Statement of Direction for Oracle Application Server certifications with the E-Business Suite has just been updated with the latest summary information about the use of:
  • Single Sign-On and Oracle Internet Directory
  • Oracle Access Manager and Oracle Identity Manager
  • Portal
  • Discoverer and Business Intelligence Enterprise Edition (formerly Siebel Analytics)
  • Oracle Integration
  • Web Cache
It also contains a few tantalizing glimpses of certifications that we're working on, for both Release 11i and 12.  I'll post more detailed statements about these upcoming certifications here, as soon as I have more concrete information that I can share.

References

April 25, 2007

Critical Patch Update for April 2007 Now Available

I was startled by the results of an informal survey taken in an Apps security-related session at Collaborate 07 last week.  The majority of session attendees indicated that they were two or more Critical Patch Updates (CPU) behind the latest release.


I'll just underline the obvious:  Critical Patch Updates deliver critical security-related fixes for all of your Oracle technology stack components, including patches for E-Business Suite Release 11i and 12. 

It's also important to note that Critical Patch Updates for the E-Business Suite are generally not cumulative.  Apps sysadmins need to apply all of the released CPUs to their E-Business Suite environment to get all of the latest security-related fixes.

I would strongly recommend adding these patches to your regular E-Business Suite maintenance cycle.  The CPU release dates are published in advance, which should help you schedule their application proactively.

Critical Patch Update for April 2007 now available

The Critical Patch Update Advisory is the starting point for relevant information. It includes the list of products affected, pointers to obtain the patches, a summary of the security vulnerabilities for each product suite, and links to other important documents. Supported products that are not listed in the "Supported Products and Components Affected" section of the advisory do not require new patches to be applied.

Also, it is essential to review the Critical Patch Update supporting documentation referenced in the Advisory before applying patches, as this is where you can find important pertinent information.

The next four Critical Patch Update release dates are:
  • July 17, 2007
  • October 16, 2007
  • January 15, 2008
  • April 15, 2008

April 26, 2007

Apps 12.0.1 Release Update Pack Now Available

The first major update for Apps Release 12 is now available for download from Metalink:

A RUP by Any Other Name...

A short word about terminology is needed before I go much further.  In Release 11i, we have these things called Rollup Patches, which inexplicably became known as "RUPs."  Release 11i Rollup Patches contain patches for a single product family (e.g. ATG Family Pack H Rollup 4).

In Release 12, we're now shipping these things called Release Update Packs.  Given the way that neologisms form, it's inevitable that these will be called "RUPs" too.  The difference is that the R12 Release Update Packs combine patches created across several E-Business Suite product families. 

If you're paying attention, it should be dawning on you about now that "Release Update Packs" in Release 12 are the equivalent of "Consolidated Updates" in Release 11i.  These are big, important patches.

What's New in Release Update Pack 1?

Regardless of what it's called, the first Release Update Pack for Release 12 contains fixes for the following areas, with details in the listed Metalink Notes:
Drilling down into the areas updated for Applications Technology, you'll find updates for the following techstack components:
  • Oracle Alert - R12.ALR.A.Delta.1  
  • Oracle Application Object Library, which includes:
    • Oracle Applications Manager
    • Oracle Application Framework
    • Oracle CRM Technology Foundation
    • Oracle Workflow
  • Oracle Applications Technology Stack
  • Oracle e-Commerce Gateway
  • Oracle Common Application Components
  • Oracle Common Modules
  • Oracle iSetup
  • Oracle Report Manager
  • Oracle User Management
  • Oracle Web Applications Desktop Integrator
  • Oracle XML Publisher
Includes April 2007 Critical Patch Updates

There's a little gem buried in all of this:  This Release Update Patch includes all of the security fixes released in the April 2007 Critical Update Patch (CPUApr2007). 
 
Related

April 27, 2007

Using Port Pools in Release 12

[Editor Update May 21, 2008:  Nilesh has moved on to another team within Oracle and, sadly, is no longer an
active contributor to this blog.  Feel free to direct any questions
about his posted articles directly to Steven Chan, instead.]


Oracle E-Business Suite Release 12 integrates many technology stack components with each other.  These components communicate with each other via a large number of ports, and preventing conflicts between port settings for various components can be a major deployment and management task.  For E-Business Suite sysadmins, this task is simplified by the use of port pools.  Understanding how port pools work is a key part of managing multiple E-Business Suite instances on the same physical server.


Port-pool-1: Rapid install wizard port pool selection screen
 
What's a Port Pool?

Oracle Applications uses the concept of a port pool.  A port pool is a preconfigured set of unique port assignments for every E-Business Suite technology stack component that requires network connectivity. 

If you have multiple Release 12 environments on the same machine, you can configure each of them to use a different port pool, ensuring that these two environments can coexist without conflicts.  The screenshot above shows a scenario where the sysadmin is selecting Port Pool 14.

How are Port Pools Created?

At the time of installation the Rapid Install Wizard allows sysadmins to select the port pool that the environment will use.  Underlying the use of port pools is a mechanism for:
  • Determining a default base value for each type of port
  • Handling formatted values, which often contain multiple ports or a range of ports
  • Determining a unique value for each pool
The net result of this is that there are 100 different port pools which are guaranteed to contain non-overlapping values.  Port starting values are preset, but you can specify the increment by selecting a number from the pull-down list. This increment will be added to each pre-set port number.

Selecting a Port Pool

The default value of the Port Pool set is zero, but you can customize it by selecting another value from the drop-down list in the Port Pool field.  For example, there are 100 port pool selections (0 TO 99).  If you select an increment of 3, the default values will increase by that value. The Database Port (1521) becomes 1524, the RPC Port (1626) becomes 1629, and so on.

Preventing Conflicts with Other Software

You also can add an extra level of sophistication by specifying individual port values to meet particular site-specific requirements, over and above the basic use of the Port Pool mechanism described above. For example, you might wish to avoid using a particular port for some reason, perhaps because it's already assigned to other software already installed on the server. 

 Port-pool-2: Manual port modification after selecting port pool.

Comparing Port Assignments from Two Different Port Pools

The table below lists ports required for different components, comparing the default ports assigned using Port Pool 0 with new port numbers assigned after selecting Port Pool 4.

 
































































































































































Sr. No


Components used this port


Default port (Port Pool 0)


New port value with Port Pool=4


1


Database Port


1521


1525


2


RPC Port


1626


1630


3


Web SSL Port


4443


4447


4


ONS Local Port


6100


6104


5


ONS Remote Port


6200


6204


6


ONS Request Port


6500


6504


7


Web Listener Port


8000


8004


8


Active Port


8000


8004


9


Forms Port


9000


9004


10


Metrics Server Port


9100


9104


11


Metrics Server Request Port


9200


9204


12


JTF Fulfillment Port


9300


9304


13


MCSA Server Port


10200-10205


10224-10229


14


MCSA Telnet Server Port


10200,10202,10204


10224,10226,10228


15


MCSA Dispatcher Port


10800


10812


16


Java Object Cache Port


12345


12349


17


OC4J JMS Port Range for Oacore


23000-23004


23020-23024


18


OC4J JMS Port Range for Forms


23500-23504


23520-23524


19


OC4J JMS Port Range for Home


24000-24004


24020-24024


20


OC4J JMS Port Range for Home


24500-24504


24520-24524


21


OC4J AJP Port Range for Oacore


21500-21504


21520-21524


22


OC4J AJP Port Range for Forms


22000-22004


22020-22024


23


OC4J AJP Port Range for Home


22500-22504


22520-22524


24


OC4J AJP Port Range for Home


25000-25004


25020-25024


25


OC4J RMI Port Range for Oacore


20000-20004


20020-20024


26


OC4J RMI Port Range for Forms


20500-20504


20520-20524


27


OC4J RMI Port Range for Home


21000-21004


21020-21024


28


OC4J RMI Port Range for Home


25000-25504


25520-25524


29


DB ONS Local Port


6300


6304


30


DB ONS Remote Port


6400


6404


 


 


 

April 30, 2007

What Does "DMZ Certification" Mean?

Depending on whom you ask, the E-Business Suite has somewhere around 200 functional applications products, clustered into larger product families such as Oracle Financials.  A subset of those products are specifically certified for deployment in an externally-facing configuration via demilitarized zones (DMZ).  For example, products certified for these types of "external" deployments include iRecruitment, iStore, and iSupplier Portal.

DMZ Reverse Proxy:

The diagram above shows a common DMZ configuration for the E-Business Suite Release 11i.  All of the points I'll make in this article apply equally to Release 11i and 12.

Loopbacks are Incompatible with DMZs

Some E-Business Suite products use loopbacks, which I've discussed in a previous article.  Apps products certified for external use in demilitarized zone configurations are tested to ensure that they don't use loopbacks. 

In fact, we turn off loopback support completely as part of the DMZ certification process for externally-facing products.  If a particular product breaks during testing in these environments, this means that their code must be upgraded to eliminate the use of loopbacks.

Which Products are Certified for DMZs?

Products certified for external deployment are listed in:
Not all Apps products are appropriate for use in demilitarized zones, so product testing in these configurations isn't comprehensive across all product families.  For example, regardless of security measures, no sane Apps architect would consider allowing their Chart of Accounts to be modified via the Internet.  So, there's no point in certifying that particular product with in a DMZ configuration.

If a product isn't in listed in the appendices of the Notes listed above, it could mean one of two things:
  1. It uses loopbacks and is not certified for external use in a DMZ configuration
  2. It hasn't been tested in a DMZ configuration, and may or may not use loopbacks
What If a Product Isn't Certified?

Here's a hypothetical situation:

You'd like to deploy a particular application externally in a DMZ configuration. It's not listed in either of the referenced Metalink Notes.  What do you do?

The answer:  log a Service Request against the specific application via Metalink stating your requirement.  It always helps to include a network diagram of your proposed topology, by the way.  If all goes as planned, the Development team for the product will be notified of your requirement and will respond with an update on their plans for that certification.

Related

Lease Management Modules Supported for DMZs

[Editor Apr 30 Update:  Overloaded acronyms... >sigh<   Corrected entry from Oracle Learning Management to Oracle Lease Management.  Support is only for Release 11i presently.]

Two new Oracle Lease Management (OKL) modules in the Financials product family are now certified for external use in demilitarized zone (DMZ) configurations:

  • Customer Self-Service
  • Vendor Self-Service
These certifications apply to E-Business Suite Release 11i and are available for immediate deployment for production Apps environments.  For more details, see the DMZ documentation below.

Related

May 3, 2007

Will the Real JRE Please Stand Up?

Unlike Release 11i, E-Business Suite Release 12 no longer requires Oracle Jinitiator for its Forms-based content.  In theory, it will be possible to use any version of the native Sun J2SE Runtime Engine (JRE) plug-in to access Forms-based content in this Applications release.

Java Console Screenshot:

The present reality is that you need to use a specific version of the Sun JRE with Release 12.  I know some of you have been interested in going deep on this, so strap on your helmets; we're goin' in.

A Problem of Focus

When you have multiple windows for different programs open in WinXP (say, Outlook and Firefox), the one you're working in actively has the focus.  So, if you're working in Outlook and then click on the Firefox window, the focus changes to Firefox.

Here's the complicating factor:  current releases of the native Sun JRE plug-in may lose focus from Forms-based content in a few situations.  This behavior occurs in all Sun JRE versions released publicly to date, including 1.5.0_11.

We've been working closely with Sun on this issue.  Sun has committed to including the fix for this issue in an upcoming JRE release.  In the meantime, Sun has provided Oracle with a specially-patched version of 1.5.0_10 that includes the fix for this bug.  This version is informally called 1.5.0_10-erdist and is included as part of the Release 12 Rapid Install.

Checking Your JRE Version

To check which version you have installed:
  1. Enable the Java Console on your PC through the 'Java Control Panel' by clicking on the 'Java' icon within your desktop's 'Control Panel'.
     
  2. Select the 'Advanced' Tab and expand the 'Java Console' field, then ensure the 'Show Console' option is selected.
     
  3. Select the 'General' Tab and click the 'About' button.
If the version displayed is:
  • Version 1.5.0 (build 1.5.0_10-erdist-b20061221)

    You have the special version that includes the focus fix required for use with Release 12.
     
  • Version 1.5.0 (build 1.5.0_10-b03)
     
    You have the standard version of 1.5.0_10 that does not include the focus fix.  If you wish to use Forms-based content in Release 12, you need to uninstall this version and install the special 1.5.0_10-erdist version included with Release 12.
A Word About Upgrading Your JRE

It's important to remember that JRE 1.5.0_10-erdist is the only version available today that includes this focus fix.  If you or your end-users use (or upgrade to) 1.5.0_11, they may encounter issues with accessing Forms-based content in E-Business Suite Release 12.

Later JRE versions that include the focus fix will be certified with Release 12, of course. At present, I don't have any information that I can share about either their release dates or their certification schedules with the E-Business Suite.  I'll post updates here as soon as they're available.

Related

May 9, 2007

Reducing Patching Downtimes via Shared Apps File Systems

I had a chance conversation with an Apps sysadmin late in the evening at the Collaborate conference.  He wearily noted that he had to somehow cover increasing maintenance costs with reduced levels of staffing.  The conversation suggested that our support for shared E-Business Suite application tier file systems may be one of our better-kept secrets.  If you haven't come across this yet, here's a way of reducing the amount of time that you spend patching.


Scaling Up with Load-Balancers

When your E-Business Suite user base grows beyond a certain size, it's likely that you'll look into deploying multiple application servers in a load-balanced pool of nodes.  Your deployment topology might look like this:

Generic Apps Load-balancing:

Regardless of whether you're running Release 11i or 12, each of these
nodes would need its own disk space and would to be maintained and
patched separately.  What a pain.

Different File System Structures in Release 11i and 12

In Release 11i, the Applications tier file system includes the APPL_TOP, the COMMON_TOP, and the Applications technology stack (8.0.6 and iAS ORACLE_HOMEs).  In a traditional deployment, each one of these application servers would have its own Applications file system, like this:

Distributed Application Tier Filesystem:

In Release 12, the Applications tier file system includes the APPL_TOP, the COMMON_TOP, and the Applications technology stack (10.1.2 and 10.1.3 ORACLE_HOMEs), plus a new INST_TOP.  Each node would have the following:

Release 12 application tier structure 2:

Enter the Shared Application Tier File System

For Release 11i, starting with 11.5.10, it's possible to put the Applications tier file system on a shared disk resource mounted to each Application tier server node in the system, like this:

Shared Application tier file system:

Similarly, in Release 12, you could put the Applications tier file system on a shared disk resource mounted to each Application tier server node, like this:

Release 12 shared filesystem:

Migrating to Shared File Systems

There are a few prerequisites:
  • Different nodes must be running the same operating system and the same O/S patches
  • You must be on a UNIX platform (Windows doesn't support shared file systems)
Certification of Shared File System Solutions

If you've gotten to this point, you're probably wondering, "Is my _____ SAN/NAS shared file system software certified with the E-Business Suite?"  File system solutions that customers have recently asked about include:
Supported but not Certified

The short answer is that your shared file system solution is supported but not certified with the E-Business Suite, for either Release 11i or 12.  Remember that there's a key distinction between support and certification, which I've covered in detail in this article:
The complexities of whatever shared disk resource management solution that you're using must be transparent to the E-Business Suite.  Aside from that, there aren't any special requirements for shared disk resources.  They can be local to the server or on a standalone disk array.

Almost Irresistible

Regardless of which E-Business Suite release you're running, the main advantage of using an Application shared file system is simplicity and ease of patching:  when
you apply patches or changes to the shared disk resource,
they're immediately visible on all application tier server nodes.  You
patch in a single place and deploy those changes across multiple
servers.  You save disk space for each additional application node you
deploy, and it's easier to deploy additional nodes, too.

If you've been wondering how to squeeze more productivity out a packed roster of administration activities, I'd recommend setting up a testbed to try this out.  Feel free to post a comment with your experiences with this; I'll make sure your feedback gets back our team.

Related

May 17, 2007

Performance Tuning the Apps Database Layer

Performance tuning is an art that should be executed systematically.  I assume almost everyone has heard this from others talking about tuning, but it's often repeated because of its fundamental truth.

Whenever there's a response time issue for the E-Business Suite, it is initially treated as a performance problem.  I would go a step further and say that poor performance is not a problem by itself.  It is a result of a root cause which lies somewhere else.

Let's dig into each of the possible places for this root cause in the E-Business Suite's technology stack.  Oracle Applications has the following layers:

  • Operating system
  • Database
  • Techstack components (Concurrent tier, Forms tier and iAS techstack)
  • Application code (Forms, Jsp etc)

This article will touch on performance-related issues for the database layer. 

Possible Causes for Database Layer Performance Issues

Possible issues include:

  • Core optimizer issues
  • Known performance-related database bugs
  • Incorrect statistics to the cost-based optimizer (CBO), which is responsible for SQL optimization
  • Incorrect System Global Area or Program Global Area sizing

Other areas like locking and latching affect performance, too.  For the limited purposes of this article, we'll focus on these four setup-related areas.

Core Optimizer Issues

Most of the E-Business Suite database's recommended parameters are listed in:

Setting the values of memory-related parameters as is not a one-time job.  We recommend that you periodically review your Statspack and AWR reports to find if the your current settings meet your current load requirements.

For recommended database init.ora parameters, refer to Note 216205.1.  Pay attention to mandatory parameters.  Based on our benchmarks, we recommend that your Apps setup adhere to the init.ora parameters listed in the note.
 
Known Performance-Related Database Bugs

For issues with the Oracle optimizer and database, most of the known performance-related bugs and their recommended patches for E-Business Suite environments are listed in:

Incorrect Statistics to the Cost-Based Optimizer (CBO)

Now comes the most complex -- and paradoxically, the easiest to solve -- area:  ensuring that the cost-based optimizer works with accurate metadata.

Before going into the details, I'll remind you that the rule-based optimizer (RBO) is no longer supported.  Don't use it in your E-Business Suite environments.  If you have an optimizer-related issue that appears in the cost-based optimizer but not the rule-based optimizer, log a Service Request with Oracle Support.

Maximizing the Benefits of Cost-Based Optimization

The cost-based optimizer is not infallible, but it's a DBA's responsibility to ensure that correct metadata is available to the optimizer.  There are two things that system administrators should do:

    1. Set all of the optimizer-related parameters, following Note 216205.1
    2. Gather statistics for all database objects

Gathering Statistics for Database Objects

There are many different ways of gathering statistics:

  • Use the Analyze command
  • Use Dbms_stats
  • Use Fnd_stats

For Oracle E-Business Suite environments, we recommend using fnd_stats.

A Short Digression:  What is fnd_stats?

Fnd_stats is a wrapper around dbms_stats that suits most of the E-Business Suite's requirements.

We recommend using fnd_stats over dbms_stats for Apps environments because of the former's support for restarts.  Starting with the 10g version of the database, dbms_stats has also this feature.

If the Gather Schema Statistics concurrent program is used, fnd_stats does the bookkeeping for the run.  Should the run fail for any reason, the next run of the program starts from where the previous run was stopped. This saves lot of time.

We also recommend  fnd_stats because of its support for histograms.  Histograms are useful when:

  1. A table's column is used in an equality or equi-join predicate AND there are  skews in the column.
  2. A table's column is used in a range or like predicate AND there are  skews in the column.

Oracle Applications' data distribution is dependent on the functionality of the specific product modules.  Based on our benchmarks, a number of columns are useful for histograms.  These columns are listed in the FND_HISTOGRAM_COLS table.

When Gather Schema Statistics is executed, it reads FND_HISTOGRAM_COLS and builds the histograms.  

gather schema/table statistics:

Back to Gathering Database Statistics

When gathering the statistics for the entire applications database, we must use the Gather Schema Statistics concurrent program.  Only the Gather Schema Statistics and Gather Table Statistics should be used. Do not use the Gather Column Statistics program.

When Should You Gather Statistics?

There is again no hard and fast rule for the interval between gathering statistics.  A general rule-of-thumb is is to run the statistics collection after a 10% increase in the database size. 

Having said that, other factors may come into play.  From 11.5.10 onwards, fnd_stats was enhanced to gather only the statistics for those objects, which have undergone a predefined percentage of data increase, or for objects that have no statistics.  The latest versions of fnd_stats identifies STALE and EMPTY statistics and gather the statistics for those objects only.  This saves lot of time and allows sysadmins to set flexible statistics gathering intervals. 

gather auto:

Although there are a number of options that you can set, we recommend selecting  the GATHER AUTO option.

Incorrect System Global Area and Program Global Area Sizing

SGA_TARGET sets the maximum size of the System Global Area (SGA) for your E-Business Suite instance.  Parameters like db_cache_size and shared_pool_size affect the database buffer cache and shared pool for that instance.   PGA_AGGREGATE_TARGET determines the maximum value for the Program Global Area (PGA) for the instance.

Note 216205.1 lists the minimum values for these parameters. These values might need to be varied depending on the actual load on your environment.  In the same way.  If these are values are:

  • Set too high:   memory on the server is not utilised to the maximum
  • Set too low:  there will be performance issues

To find out whether these parameters are set properly on your system, you can run a Statspack or AWR report.

Interpreting Statspack or AWR Reports

Covering this area comprehensively is beyond the scope of this article, but here's some things to remember about interpreting your Statspack report:

Total Response time = Service time + Wait time

Service Time is generally the amount of "CPU used by this session".  From the 9.2 database version and upwards, this is reported in the Statspack.  You can use this to derive the Wait Time.

For example:

Using a Statspack report with a 9.2 or higher database, examine the figures reported for CPU time.  If it's 70% of the total time, then the wait time is 100-70=30%.

Total Response time = 70% CPU time + 30% wait time

Once we have identified the time taking component, look into the specific component.  For memory-related areas, look at the Advisory Statistics section.  This shows details about the sizing of SGA (cache and shared pool) and PGA (M-pass executes should be as small as possible for a optimal PGA). 

Based on this type of analysis, you can vary your SGA and PGA settings accordingly.

Getting Support for Performance Issues

As you can see, investigating performance issues can be tricky, especially if you find the topics briefly described here to be daunting.  Take heart:  you're not on your own.  We have teams that specialize in these areas, so if you run into any performance-related issues, log a Service Request via Metalink and we'll jump in to help.

In Summary

A quick recap of database setup-related issues and recommendations for tracking down performance-related issues:

  • Database Parameters:  Refer to Note 216205.1 for mandatory settings, and then check your Statspack/AWR reports periodically to see whether your memory-related parameters are set correctly.
     
  • Apply the Recommend Performance-Related Database Patches:    Refer to note 244040.1
     
  • Keep Your Statistics Fresh: Use the Gather Schema/Table Statistics concurrent program regularly.  The GATHER AUTO option can be of great help here.

It's possible to dive much deeper into database or instance tuning topics.  If you'd like me to go into more details, feel free to post a comment here.

Related

 

May 18, 2007

Debugging General Performance Issues with Oracle Apps

Identifying performance bottlenecks can sometimes be a black art with any distributed computing system.  It is sometimes difficult to know where to start.  This article gives some high-level guidance on the sort of information you may need to gather in order for Oracle Support to assist you with this task for the E-Business Suite.

Performance issues can potentially occur across any or several different areas of the Technology Stack, or may be restricted within Functional Code. For example (but not restricted to)

  • Architecture issue (e.g. high latency WAN, firewall)
  • Operating System problem or resource constraint
  • SQL or general RDBMS configuration issue
  • Database Deadlock
  • Apache Listener

mzPerfIssues:

Types of Performance Issues

"Simpler" Problems

These issues will hopefully be relatively straightforward to define and investigate.  For example: -
Single report consistently slow, SQL trace discovers one or more SQL statement(s) taking the majority of the elapsed time

More complex issues

These can take more work to be able to confidently define the real issue and often involve complex investigations involving different parties and much data gathering and analysis

For example :-
Any intermittent issue, System wide issues, Issues where SQL trace time represents only a small proportion of the elapsed time

Gathering Data for Performance Issues

It's helpful to follow a systematic process for investigating performance issues.  First steps include identify the nature, scope and extent of the problem. 

1. Identify the Extent of the Problem

Determine whether the extent of the problem is:

  • System Wide
  • Confined to one Technology Are. For example does it only happen in one of the Self Service, Forms or Reports areas
  • For a specific Product Area(s) For example, were it to only occur in HR, GL or iStore
  • Single Report/Form/Page
  • Which Instance or instances is the problem observed. Can it be reproduced in UAT/TEST instances
2. Narrow the Scope Further

Determine whether the problem occurs for:

  • All users
  • Only one geographic location
  • Only for users with certain Browser/type of PC
  • Only during peak periods
3. Qualify the Nature of the Problem
  • Is the problem intermittent or reproducible?
  • Is the problem due to slow performance or a process hanging or spinning?
  • When was the last time the process was completed without experiencing poor performance?  Document any changes since then.
  • Is there a workaround available?   For example, restarting Browser or restarting Apache.
  • What is the frequency of occurrence?
4.  Capture Additional Clues
  • Document and differentiate factual information from user perceptions. Example - users may say "it's always slow" but reality may be that it takes 10 seconds most of the time, but 40 seconds between 10am and 11am (peak load).
  • How long does it take for the process to complete when running slowly?  How long did it previously take (before having the performance issue)?  What is the expected performance for this process?
  • What is load on server(s) when issue occurs (CPU/Memory/Network)?  Is there any unusual activity when problems occur?  For example, memory used suddenly growing or CPU at 100%.
  • Is the problem reproducible with other browsers, such as Firefox, as well as with Internet Explorer?

5.  Identify likely causes and eliminate other possible causes

  • Are there any customizations?  If so, can they be eliminated for testing purposes?
  • If the problem only occured since patches have been applied or any configuration changes have been made, can these be reverted?
  • Do you have any Resource Limits enabled on the database that may be effecting the Applications users runtime or Concurrent Manager?
  • Does the number or frequency of certain Concurrent Requests correlate to performance issues occurring?
  • Have the database parameters been configured as per the current recommendations in Database Initialization Parameters and Configuration for Oracle Applications 11i (Metalink Note 216205.1)?
  • Does AWR or Statspack show anything unusual for Top waits, Top buffer gets, etc?
  • Have you searched Metalink generally, but specifically reviewed Recommended Performance Patches for Oracle E-Business Suite (Metalink Note 244040.1) for any known performance issues, tuning guidelines and/or patches?

Getting Help from Oracle Support

Once you understand the issue and reach the point where you need Oracle Support involved, it may be useful for you to review the "Performance Tuning" section of:

The first key decision you need to make is selecting a product code for your Service Request (SR): 

  1. If the issue is with an individual Form/Report/Page or only in one product area then log the SR for that particular product support team
  2. If issue seems to be with the Technology Area or System wide then log the SR with the AOL team (Oracle Application Object Library)

It is very important to provide a good problem definition (nature, scope, extent) so be as verbose as needed to give a good description of the issue.

It is also very important to reproduce the issue on a non-Production instance. If you are able to reproduce the problem outside of your Production instance, then any recomended patches or changes can be quickly assessed for their impact and any detailed debug or tracing required to identify the issue can be easily implemented.

A Quick Aside:  One issue per Service Request

You may need several issues investigated simultaneously and may be reluctant to raise different SRs or have different people investigating. Unfortunately, even similar-looking issues can have different root causes, which means they will need to go to different support teams or have different SR statuses. This is why it is important to ensure each issue is raised as a separate SR.

Performance Issues with Specific Forms, Reports, or Pages

For these "simpler" types of issues, we can generally track down the issue with the following information:

  • Form, Report or Page name, version and navigation path
  • Full versions of Forms, Reports or Framework as well as the iAS and Database versions, including rollup or interop patches applied
  • Relevant Family Packs or Maintenance Packs applied
  • Description of symptoms, what have you tried, your investigations, conclusions and/or thoughts/ideas
  • Does it reproduce constantly, in other environments as well?
  • When did you last run "Gather Schema Statistics" and at what percentage?
  • When did you last run any relevant purging processes?
  • SQL trace with binds and waits (raw file and TKPROF output)
  • Wall clock time elapsed from user perspective
  • What are the target and acceptable times for this process?

Performance Issues for Other Areas

These are the more complex issues and will normally require additional information (and patience) to resolve.  We will need the same information as listed above, but also:

  • Description of your System Architecture and network diagram
  • Technology Stack configuration files (Apache, Forms, Reports and Database, as relevant to the problem)
  • List of any Metalink notes or product documentation you have reviewed already, and what steps you implemented from this documentation
  • List of any patches applied specifically to try to address this issue
  • Details of profile options or configuration settings you have tried changing, explaining why you tried these settings and what effect they had (if any)
  • AWR or Statspack output for "good" and "bad" performing time periods
  • Details about your pinning, purging and gather schema statistics strategy
  • Relevant Log files
  • Debug and trace files

Good starting points for collating all this information are:

Additional Tips for Troubleshooting for Apache / JVM problems

Additional Tips for OA Framework-related issues

  • It is often useful to enable "STATEMENT" level logging (for ONE user only!) using the FND:Debug% profile options if you have a reproducible test case

Conclusion

Performance issues can sometimes be tricky to isolate, particularly those having more than one root cause.  This article has presented some ideas about the approach to take, in addition to the sort of information Oracle Support would likely be asking for if you need to log a Service Request.

If there is sufficient demand, I can write further articles in future, expanding on the topics introduced here.

Related

May 24, 2007

Virtualization & the E-Business Suite, Redux

Operating system vendors such as Hewlett Packard, IBM and Sun are increasingly promoting the use of their own virtualization solutions for reasons primarily related to the need for IT consolidation and better hardware utilization.


For instance, Solaris Containers is a feature of Solaris 10 that allows partitioning of an existing operating system into separate virtual hosts:

Sun Solaris Containers:

IBM promotes the use of its Dynamic Logical Partitioning (LPAR) technology that enables the virtualization of hardware resources which can be shared by multiple operating systems:
 
IBM LPAR overview:

HP's virtualization solution -- Virtual Server Environment -- includes various technologies such as nPartitions, vPars and Integrity VM that allow running multiple instances of HP-UX on the same server:

HP Virtual Server Environment:

Additionally other vendor-neutral solutions such as VMware, Microsoft Virtual Server, and Citrix allow different operating systems to run as guest operating systems on a single physical machine.  I've briefly discussed our support for these types of virtualization solutions in a previous article, with a special case for E-Business Suite client/server modules which make direct connections to the E-Business Suite database.

The use of operating system vendors' virtualization technologies to host E-Business Suite falls under the same 'not explicitly certified, but supported' category. These technologies are covered by Oracle's standard policy for third-party product support
  • Oracle will triage and attempt to diagnose issues reported for these configurations. 
  • Specific
    problems isolated to virtualization software that cannot be reproduced
    in standard Oracle environments -- i.e. environments without
    virtualization software -- may need to be referred to the third-party
    vendor for advanced debugging and resolution.
Use in Production Environments

If you
plan to use virtualization software for your application and database
servers in a production environment, the usual advice applies:  conduct
thorough functional tests, perform peak load-testing, and have detailed
fallback plans in case of issues with production environments.

References

May 25, 2007

Release 12 Upgrade Forum Now Open

A group of users at the recent OAUG Collaborate conference in Las Vegas pooled business cards after a Release 12-related session.  Their goal:  "to share their thoughts, upgrade feedback, and driving forces for moving to R12." 


We'd like to help that group -- and you, of course -- collaborate and share experiences on this upgrade.  You're not alone.  As of early April, over 225 customers were actively working with Release 12, and almost a thousand downloads had been logged (at 41 GB, not a task for the only-mildly-curious).  Those numbers have certainly increased since then.


We've created a new discussion forum on the Oracle Technology Network:
I'm not an upgrade specialist, but I've (rather nervously) volunteered to monitor that forum and jump in where I can.  I suspect I'll be acting like a human router between forum participants and Oracle development.  This is in addition to my regular responsibilities (like this blog), so I'm bracing myself...

May 29, 2007

Pinning Objects to Improve Apps Performance

Keeping database packages in the Oracle database's System Global Area (SGA) shared pool is a common practice.  This is also called pinning.  One common misconception is that pinning is not useful or needed in later Oracle database versions such as 10g and above, since those releases offer automatic shared memory management.  This isn't completely accurate for all cases, for reasons which I'll discuss below.

An Introduction to the System Global Area (SGA)

The Oracle database's System Global Area contains various pools of memory used to satisfy particular classes of memory allocation requests:

System Global Area (SGA) Pools:

  • Shared pool:  used for caching shared cursors, stored procedures, dictionary caches, etc.
  • Buffer cache:  cache of disk data
  • Large pool:  large allocations
  • Java pool:  Java allocations and for caching java objects
  • Log buffer:  in-memory buffer for redo generation
  • Streams Pool:  new in 10g, for buffering inbound and outbound logical change records
  • Fixed SGA:  bootstrap section of the SGA


SGA memory is allocated in units of contiguous memory chunks called granulesThe size of a granule depends on your operating system platform and the SGA's total size. On most platforms, if the estimated SGA size is:

  • Less than or equal to 1GB, the granule size is 4 MB
  • Greater than 1GB, the granule size is 16 MB
A Primer on Space Allocations in the Shared Pool

One of the important components of the SGA is the shared pool.  The
shared pool was introduced as a feature of the Oracle Database in
Version 7, primarily as a repository for shared SQL and PL/SQL.  The
shared pool has come a long way since its original release.

The Oracle database requires contiguous space.  For example, if a request for 4 K of memory is made, the database cannot allocate separate 3 K and 1 K chunks.  It must allocate a 4 K block of contiguous free memory to satisfy the request.  If there is no free memory, it will scan the Least Recently Used list to free some memory.  The heap manager will try to free as many objects as possible before giving up.  If the shared pool has no space to satisfy the request for memory, an ORA-4031 error is thrown.

With the advent of automatic shared memory management, we need not configure the size of the shared pool via the shared_pool_size parameter.  Automatic shared memory management requires one parameter to be set:  sga_target.  The Oracle database's automatic memory allocation is superior to manual memory management. This prevents ORA-4031 errors in most cases.


When Large Objects Jump in the Shared Pool


Imagine a large package (or any object) has to be loaded into the shared pool.  Large PL/SQL objects present particular challenges.  The database has to search for free space for the object.  If it cannot get enough contiguous space, it will free many small objects to satisfy the request.  If several large objects need to be loaded, the database has to throw out many small objects in the shared pool. 

Finding candidate objects and freeing memory is very costly.  These tasks will impact CPU resources.


One approach to avoiding performance overhead and memory allocation errors is to keep large PL/SQL objects in the shared pool at startup time.  This process is known as pinning.  This loads the objects into the shared pool and ensures that the objects are never aged out of the shared pool.  If the objects are never aged out, then that avoids problems with insufficient memory when trying to reload them.

What's in Your Shared Pool Now?

Objects are 'kept' in the shared pool using the dbms_shared_pool package that is defined in the dbmspool.sql file. 


For example:


execute dbms_shared_pool.keep('owner.object');

To view a list of all objects that are kept in the shared pool, one can query the v$db_object_cache:


select owner,name,type,sharable_mem from v$db_object_cache where kept='YES';

The SQL query above will list all of the objects that are 'kept' in the shared pool using dbms_shared_pool.keep.

Identifying Candidate Objects for Keeping in the Shared Pool


To identify candidates that should be kept in the shared pool, first run the following query:


select substr(owner,1,10)||'.'||substr(name,1,35) "ObjectName", type, sharable_mem,loads, executions, kept from v$db_object_cache where type in ('TRIGGER','PROCEDURE','PACKAGE BODY','PACKAGE') and executions >0 order by executions desc,loads desc,sharable_mem desc


The query above will return something like this:

SQL output to identity candidates:


Next, query the x$ksmlru table, using:

select * from x$ksmlru;

The x$ksmlru table keeps track of the current shared pool objects and the corresponding number of objects flushed out of the shared pool to allocate space for the load.  These objects are stored and flushed out based on the Least Recently Used (LRU) algorithm.  Here's what the table looks like:

describe x$ksmlru       

Table or View x$ksmlru         

     Name           Null?    Type                       
     -------------- -------- --------------             
     ADDR                    RAW(4)
     INDX                    NUMBER                      
     KSMLRCOM                VARCHAR2(20)                
     KSMLRSIZ                NUMBER                      
     KSMLRNUM                NUMBER  

  • KSMLRNUM  shows the number of objects that were flushed to load the large object
  • KSMLRISZ shows the size of the object that was loaded (contiguous memory allocated)

Note:  This is a fixed table: once you query the table, the database will
automatically reset the table.  Make sure that you spool the output to
a file so you can capture it for analysis.

Analyze the x$ksmlru output to determine if there are any large allocations that are flushing other objects.  If this is the case, analyze the v$db_object_cache to identify the objects with high loads or executions.  These should be kept in the shared pool.

Keeping Objects in Oracle Applications Databases


All E-Business Suite DBAs should do some analysis to assess whether pinning can improve the performance of your Apps environment.  Arriving at the objects to be pinned varies from setup to setup.  Objects have to be pinned after each instance startup, and ideally immediately after the startup.

The $AD_TOP/sql/ADXGNPIN.sql script is provided to pin the packages in Oracle Applications.   This script pins all Oracle Applications objects, which is generally not completely necessary or advisable.  You should modify this script based on your analyses of v$db_object_cache and x$ksmlru to identify the right objects to be pinned for your environment. 

For more information about this script (and the related ADXCKPIN.sql script, used for listing objects in the shared pool), see the appropriate manual for your Apps release:

Related


June 5, 2007

Comparing Bandwidth Requirements between Release 11i and 12

[June 8, 2007 Update:  Clarified background on the second set of benchmarks]

A few questions have been raised in our new Release 12 Upgrade Forum about the differences in network bandwidth requirements between Release 11i and 12.


The usual disclaimers apply:  benchmark tests are conducted by the Applications Performance Group on reference E-Business Suite environments.  These environments and the selected transactions will not necessarily match up with your own transaction mix, so your mileage will vary.  If you're in need of precise benchmarks, it's always best if you perform your own tests with your own mix of transactional data.

Differences Between JInitiator and the native Sun JRE Plug-in

Release 11i currently requires Jinitiator to display Oracle Forms-based content.  Release 12 requires the native Sun Java Runtime Engine (JRE) to display Forms-based content. 

Our Applications Performance Group has published a full whitepaper comparing bandwidth requirements between these two configurations:
Differences in Page Sizes

As for our web-based applications, many of the products changed their pages and flows in Release 12.  There are actually two comparison points: 
  1. 11.5.10.CU2 vs. 11.5.10.CU2 with on the Release 12 ATG Rollup
  2. 11.5.10.CU2 vs. Release 12
Here's the first comparison of page loads:

Comparison of page load sizes - Part 1: Comparison of page load sizes between Release 11i 11.5.10.CU2 vs. 11.5.10.CU2 with the Release 12 ATG Rollup applied

[June 8, 2007 Update:  The section above is generating a lot of similar questions, perhaps understandably.  Here's the scoop:  the comparison above shows the additional overhead associated with the
new R12 technology stack running the same Applications code.  This
would be the equivalent of running the 11i versions of these screens in
Release 12.  Our Applications Performance team is very meticulous about comparing equivalent things.  No "apples to oranges" comparisons for them.


They deemed it important to distinguish between added network bandwidth overhead in Release 12 due to new code at the Apps layer vs. new R12 technology stack requirements.

So, their baseline for network bandwidth was the Release 11i.5.10.CU2 environment.  They then ran benchmark tests with the same Applications code and the new Release 12 ATG components.  Important note:  this configuration isn't documented, supported, or recommended -- it was strictly a Development-only configuration used for benchmarking purposes.  You cannot apply the Release 12 techstack to an E-Business Suite Release 11i environment, and we don't provide any patches to do so.]

Here's a thumbnail of the second comparison (click on it to see the full-size version, which is admittedly low resolution):

Thumbnail - Full page load comparison: Thumbnail of table comparing Release 11i and 12 page load sizes

The table above compares a Release 11i environment with a full E-Business Suite Release 12 environment.  The Release 12 environment includes not only the ATG changes but also all of the Apps code changes.  You'll see that the page sizes did increase, but these increases were mainly due to Apps code changes and user interface changes.  The new OA Framework (Swan) changes accounted for less than 4%.

New Functionality Trumps All

As Apps technologists, it's tempting for us to get caught up in these types of discussions.  "Look -- the login page is X bytes larger!" 

It's always worth remembering that your end-users don't really care much about such things, however.  They're more likely to remark on the fact that the login page now has two new capabilities:  reminding them of their password, and reminding them of their userid, too. 

It's been my experience that new functionality trumps all, at least in the eyes of your users.  My recommendation:  go ahead and consider these benchmarks as part of your Release 12 evaluations, but more meaningful comparisons will come from spending some quality time with your end-users in assessing and prioritizing the new functional benefits in R12.

Related

June 7, 2007

Top 5 Myths About Patching Apps Environments

When I was younger, I thought I could change this world.  Now I no longer think so but for emotional reasons I must keep on fighting a holding action.

~ Robert Anson Heinlein

A rational person might contend that actions follow attitudes which follow beliefs.  Bad news:  there's a substantial amount of psychological literature that suggests that this isn't how we really tick.

There's an equally large body of empirical data that suggest that beliefs are relatively intractable.  Once established, certain beliefs don't change, regardless of the best data, clear reasoning, and eloquence that can brought to bear on the subject.  Recent fMRI studies suggest that brain structures may develop in such a way that people with strongly-held beliefs are actually unable to process new information that contradicts those beliefs.

The broader implications of this are kind of depressing to contemplate.  But I digress.

For the narrow purposes of this discussion, I'm compelled to make an admittedly-quixotic attempt to persuade you that the benefits of keeping your E-Business Suite environment up-to-date far outweigh the costs.

"We Can't Upgrade Because..."


  1. It requires too much downtime
  2. Testing is too expensive for end-users

  3. It's too complicated
  4. We don't have enough staff
  5. It ain't broken; why fix it?
Myth #1:  It Requires Too Much Downtime

This seems rational on the surface.  After all, a downtime for patching seems worse than no downtimes.  

Remember that we issue patches for four major reasons: 


  1. To add new functionality
  2. To improve stability
  3. To improve performance

  4. To improve security
The corollary is that an unpatched system may have fewer or less-sophisticated features, and be slower, less stable, and less secure than a fully-patched one.  Questions to consider if you believe this myth:


  • How much downtime is currently caused by unplanned outages due to unpatched stability bugs?
  • How much downtime is needed to bounce your application servers due to unpatched JVM memory leaks?
  • How much downtime would be required if an attacker takes advantage of an unpatched security risk?
There are a number of key ways to reduce downtimes.  One of these is to use shared filesystems in environments with multiple application servers.  There are a number of other ways, too.  These are beyond the scope of this article, so I've covered the top seven way of reducing downtimes in this article.

Myth #2:  Testing is Too Expensive For End-Users

Many organizations recruit business users to participate in User Acceptance Tests for patches.  If you do this, it's true that this may reduce participants' productivity for the duration of your testing phase. 

If you don't keep your environment up-to-date, the key consideration are: 


  • How much productivity is lost for all end-users -- not just the testers -- due to unpatched performance, stability, or security bugs?
  • How much could productivity be improved by new features?
Myth #3:  It's Too Complicated

All DBAs know the drill:  before patching, print all patch READMEs and spread them in neat piles across a big surface.  Read them, highlight them, then reread them.  Download more patches.  Repeat. 

Every patch has some set of prerequisites.  These prerequisites lead to other prerequisites.  The key thing to remember is that it's always easier to patch an up-to-date system than something that's much older.  The bigger the gap between your current system and target patch level, the more complex the upgrade will be. 

The best way of reducing the complexity of upgrades is to keep your system up-to-date.

Myth #4:  We Don't Have Enough Staff

I need to be candid here:  there's a kernel of truth in this one.  This is a direct outcome of believing Myth #3.  If you haven't patched your E-Business Suite Release 11i environment since it was installed in 2001, then you may have a big and complex upgrade project on your hands.  This might take more staff than you have.

So, the best way of avoiding the truth of this one is to keep up-to-date with your patching.  If you're up-to-date, applying a given patch is less complex and requires fewer staff.

Myth #5:   It Ain't Broken; Why Fix It?

With apologies to English teachers everywhere, that old axiom has a seductive ring of truth to it.  After all, your system seems to be running just fine, thank you.  Why bother potentially destabilizing something that everyone's happy with?

Repeating the key points made in Myth #1:  new releases are issued to provide new functionality and improve stability, performance, and security.  If you're running an older release, it has -- by definition -- issues in these areas that you may not have noticed yet.

The Worst-Case Scenario

If I were an IT manager running an older E-Business Suite release, say 11.5.2, this would be the nightmare scenario that would keep me awake at night:


My business requirements changes due to an acquisition or a change in business practices.  These changes trigger a different load or usage profile on my E-Business Suite environment.  This triggers a Severity 1 outage.  My production system is down.

I call Oracle Support for help.  Good news: they can reproduce the problem on 11.5.10.CU2.  Bad news: due to technical dependencies (and supported by the fact that 11.5.2 is out of Premier Support status), they can only issue patches on top of 11.5.10.CU2.  There's no way of getting that patch backported to 11.5.2.

Now I'm faced with a huge upgrade from 11.5.2 to 11.5.10.CU2.  My production system is still down, and it will be down for the duration.  Users are burning me in effigy in the parking lot.  Business impact analysis, user acceptance testing, load-testing, fail-over testing -- all of those activities are jettisoned in my panicked attempts to get my environment running again.

It's Never Too Late

At this point, I suspect I've lost most of my readers.  By now, they've clicked on the latest YouTube video or something more cheerful. 

For the handful of my remaining readers:  if you're in a hole, it's never too late to stop digging.  Less metaphorically:  just because you're behind in patching doesn't mean that you should just give up entirely. 

We can help you put together a strategy for getting up-to-date.  Your first call should be to your Oracle account manager.  He or she can engage specialists in Sales Consulting or Consulting to help.  There are also excellent groups in our Advanced Customer Services organization (a.k.a. Field Support, On-Site Support, Premium Support) who offer a number of of packaged and customizable support offerings in the patching realm. Alternately, there are a number of excellent third-party consultants who can help you with this.  Or, if you're really intent on doing it yourself, there are forums on the Oracle Technology Network and elsewhere where you can brainstorm possible upgrade strategies.

Whatever path you choose:  start now.  It's never too late.

Related

June 13, 2007

Fusion Intelligence Now Available for Apps 11i & 12

[June 14 update:  Fusion Intelligence displays its analytic content based on the responsibilities assigned to each user.  This applies regardless of whether Oracle Single Sign-On is installed or not.  Rearranged existing points to avoid confusion about this.]

Oracle Fusion Intelligence for the E-Business Suite is now available for both Release 11i and 12.  Sorting out what this means for Apps sysadmins and architects might be a bit entertaining.  You need to know three things to before I jump into the details about Fusion Intelligence:

What's Oracle Fusion Intelligence?

Oracle Fusion Intelligence delivers prebuilt analytic dashboards on top of the Daily Business Intelligence products (i.e. the DBI materialized views and and base summaries).  These dashboards run on Oracle Business Intelligence Suite Enterprise Edition.  Fusion Intelligence users only see reports and data permitted by their existing E-Business Suite responsibilities.  Users can drill across from Oracle Fusion Intelligence dashboards into the underlying transactional data in the E-Business Suite.

Its logical architecture looks like this:

Fusion Intelligence Logical Architecture: Diagram shows the E-Business Suite layer, the DBI Repository, and the Oracle BI Administration and Presentation Services layers

Fusion Intelligence analytic content covers the following areas:
  • Financials
  • Governance, Risk,
    and Compliance
  • Human Capital Management
  • Procurement
  • Service
  • Supply Chain
  • Order Management
  • Sales
Integration with Oracle Application Server 10g and Apps

Regular blog readers know that you can integrate your E-Business Suite environment with OracleAS 10g.  There are a number of good reasons to do this, primarily the use of Single Sign-On and Oracle Internet Directory 10g.  If you've implemented Single Sign-On for your Apps environment, you'll be pleased to hear that Fusion Intelligence plugs into that existing infrastructure. 

Fusion Intelligence's Relationship to Discoverer

Fusion Intelligence is distinct from Discoverer 10g, which we continue to offer.  Both of these products meet different and complementary functional requirements, so you may end up choosing either one -- or even both -- to meet your end-users' reporting and analytic needs.  I'm in the Applications Integration team, so I'm not a Business Intelligence specialist.  If you'd like to contrast and compare these products in more detail, a chat with your Oracle account team might be in order.

References

June 15, 2007

Update #3 on Vista Certification for the E-Business Suite

[Nov 8, 2007 Update:  Vista is now certified with IE 7 for E-Business Suite Release 11i and 12.  See this article for full details.]

[Oct 11, 2007:  See the latest
Update #5: Vista Certification with the E-Business Suite]

I've been receiving questions from a relatively small number of large enterprise customers who are planning Vista upgrades for their end-users.  Unfortunately, I have no information that I can share about certification dates, either publicly or off-the-record, for reasons I've discussed in the past.  But I can give you an update on our progress.

Microsoft Vista Logo:

What Does Certification Mean?

The deceptively-simple phrase, "Certification of the E-Business Suite on Vista" actually hides a great deal of complexity.  This certification covers two major E-Business Suite releases -- Versions 11i and 12.  Depending on who's counting, there are between 200 to 240 products to be tested.  In additional to base functional testing, additional tests are required for MLS languages, including right-to-left multi-byte / Unicode character sets.  Each set of tests performed need to be duplicated for both Internet Explorer and Firefox.
 
Each of these releases have three parts that need to be tested:
  1. Oracle Forms-based components of the E-Business Suite running in Sun's Java Runtime Environment (JRE) plug-in on Vista, for both IE7 & Firefox
  2. HTML/Javascript-based components of the E-Business Suite running in IE7/Firefox
  3. Client/server administration components of the E-Business Suite running on Vista
Iterative Testing Cycles

It's very important to remember that all technology certifications are inherently iterative. 
Any issues found and fixed in the course of testing may cause some or all of these activities to restart from the very beginning.  For example, a Vista compatibility issue discovered and fixed downstream in Release 12 may require fixes to be backported to 11i.  Such fixes will trigger retesting in both releases.

The iterative nature of these types of certifications makes it extremely difficult to predict certification dates accurately.

Progress Report:  Where We Are Today

I can fill you in on some background on what we've done so far:
  • We had conducted early pre-certification tests with Vista release candidates last year.  These went well, for the most part.
  • Our Vista certification was hung up when we discovered that a serious focus-related issue in Sun's JRE occurs in Vista, too.
  • Sun has just released JRE 1.5.0_12.  This appears to contain the fix we've been waiting for.
Our Vista certifications have now restarted in earnest.  We have passed the first two of approximately five