Oracle On Demand

Oracle on Demand, What’s That All About?
Maybe you have worked with Oracle for a long time, maybe you are new, but if you have not worked with Oracle On Demand, here are few things you may want to know.
I have worked with Oracle Applications for over 15 years.  Involved with everything from implementations to production support to integration of 3rd party applications.   Performing both functional and technical type activities.  Nevertheless, when starting to work with Oracle On Demand, new terminology was introduced that was outside of my bailiwick.  Although I had worked at a company which had a project to integrate Oracle’s On Demand offering with their own hardware and application management services, it was not until about a year ago that I was put on the frontline with OOD.
This blog is focused on cutting through some of the red tape of working in an OOD environment.  This first blog post is just a high level overview of the terminology involved with OOD. Future releases will target support activities and other technical concepts.
In a nutshell, OOD is Oracle’s Software as a Service (SaaS) for its Enterprise Business Suite of products.  OOD comes in two flavors:  @Oracle and @Customer.   This just basically represents where the actual servers reside, either at an Oracle location or on-site with the customer.  This will also dictate which party is responsible when it comes to topics like ‘Printing’.  In either scenario, the following principles will still apply.
TERMS- My Oracle Support – Formerly named MetaLink, as it pertains to OOD, this site allows for access to information about the Oracle footprint at the specific customer, and is where you maintain your passwords for the various Oracle servers.
CEMLI – This acronym represents how Oracle categorizes changes to their base application.  C-Configuration, E-Extension, M-Modification, L-Localization, and I-Integration.  Oracle’s support is limited to configurations and localizations.  The customer is responsible for supporting, or separately contracting for support of, extensions and integrations.  What about modifications?  Well, Oracle does not allow these in an OOD environment.
Powerbroker – This software controls how one would gain access past what is granted to their individual user account.  So this will allow a user to have operating system account access like applmgr or oracle given applicable security policies are granted within Powerbroker.  Powerbroker also allows access to the Password Manager Utility which, in short, allows for access to passwords of critical database accounts (i.e. apps, system, bolinf, etc.)
Performance Assessment Tool – Once installed, this tool allows for collecting metrics on CEMLI’s in order to submit to Oracle for approval.  If CEMLI’s do not pass performance standards, exceptions may need to be submitted to Oracle if there are no other options.
Service Delivery Manager (SDM) – This is the contact at Oracle which provides assistance with the various processes needed to setup an id, utilize the performance assessment tool, CEMLI migration process questions, submitting exceptions, etc.
Business Online  (XBOL) – This is the Oracle short name used to represent the application within the OOD environment.  Business Online was the predecessor to Oracle On Demand, and was also known as Oracle Outsourcing.
Business Online Interface (XBIL) – Specifically used for Interfaces/Integrations, XBIL is the short name used for the Business Online Interface application.