Beruflich Dokumente
Kultur Dokumente
Sign In
BLOGS PRODUCTS &
INDUSTRIESSUPPORTPARTNERSCOMMUNITIESABOUT
HOME SERVICES
E-Business Suite Release 12 provides a useful mechanism for the Applications administrators to start the
Apache on the applications tier during down time. Applications administrator can start the apache in a
mode called restricted mode. Down time tasks like patching can continue to be performed while the
Apache is in restricted mode. Restricted access to Oracle Applications Manager (OAM) is available in this
mode. This allows the system administrator to monitor tasks like patching from OAM. When the Apache
is started in restricted mode, normal users are redirected to a downtime URL containing downtime details.
The above step creates a downtime.html page that will be used as redirect page when apache is started in
restricted mode
3. The downtime schedule can be viewed, edited, or cancelled from the wizard.
1. Login to your applications tier and source the environment file so that all the environment variables
are set
2. Stop your application tier services by running adstpall.sh from $ADMIN_SCRIPTS_HOME
directory.
During the configuration, the utility makes a copy of your context file in case you hit any issues. This
backup file can always be restored and autoconfig be run to restore to the original state.
Now, you are ready to use the restricted mode of Apache and plan your downtime activities!!.
When the users try to access the Applications home page, they get redirected to the downtime page
generated when you schedule downtime.
http://host:port/OA_HTML/oam/nonUix/launchMode/restricted/downtime.html
Access to OAM
For system administrators, a user named ad_monitor is available to access OAM during the restricted
mode. Login from this user provides access to the maintenance wizards and status pages in the Oracle
Applications Manager.
Once you are done with your downtime activities, Restricted mode of Apache can be disabled i.e.,
switching back to NORMAL mode by running the following steps:
1. Login to your applications tier and source the environment file so that all the environment variables
are set
2. Stop your application tier services by running adstpall.sh from $ADMIN_SCRIPTS_HOME
directory.
References
● Chapter 6 'Patching and Maintenance with Oracle Applications Manager', Section 'Managing
downtime in Restricted Mode' of Oracle Applications System Administrator's Guide -
Maintenance, Release 12 (Part Number B31454-01)
Tags:
● EBS 12
● Prasad Akkiraju
● best practices
● maintenance
Comments (11)
Tianhua Wu:
NewSunSEO:
Good to see another update. I look forward to testing it out in the near future.
Ram:
Shyamal:
Tianhua Wu:
But I am sorry, Shyamal, you will be redirected to downtime.html when you try to login. The reason I
asked is that the URL provided in "Oracle Applications System Administrator's Guide - Maintenance,
Release 12" did not work for me.
Actually, I could not find oamLogin.jsp on file system at all. I did find oamLogin.class and oamLogin.uix
files.
Prasad Akkiraju:
Thanks Shyamal for pointing out the correct navigation. Corrected and reposted.
Yury Velikanov:
Hi,
Just a short question: What is the difference in that functionality comparing with 11i?
Are there any improvements? IMHO 11i was a bit buggy and kind of beta release for that.
Prasad Akkiraju:
In 11i, there is no utility to configure Apache in restricted mode. It has to be done by editing the context
file and running autoconfig. The wizard is pretty much the same for downtime scheduling. I will be
writing up the procedure for 11i soon.
Tianhua Wu:
Prasad, since you mention OAM can be accessed via ad_monitor user during the restricted mode, could
you please let me know what the URL should be? The one in my previous post does work.
Thanks,
T Wu
Prasad Akkiraju:
Remember in Release 12, there is a single entry point for apps. HEnce, login through the main login page
as ad_monitor. This works for me.
Steve Parks:
Hello,
I'm wondering if there's a simple workaround for allowing a select group of applications users to still log
into the E-Business Suite and use their responsibilities during a scheduled downtime, whether Apache is
started in restricted mode or not. I'd like to avoid using the FND_USER_PKG API to temporarily end-date
users from List A while allowing users from List B to still access the system during a cut-over period.
Thanks,
SBP
Post a comment
(If you haven't left a comment here before, you may need to be approved by the site owner before your
comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)
Name:
Email Address:
URL:
Comments:
Preview Post
Google Search
Categories
● Focus Areas
● Business Intelligence
● Configuration Management
● Database
● Desktop Clients
● Extending Apps
● Networking + Architectures
● Optimizing Performance
● Patching
● Portal
● Security
● Third-Party Integration
● User + Identity Management
● News
● Desupport Notices
● Events + Conferences
● General
● Hottest Articles
● New Certifications
Archives
Select a Month...
Links
● All Oracle Blogs
● Related Blogs & Other Sites
● Apps Podcasts (AppCasts)
● Oracle Apps Product Center
● EBS R12 Upgrade Forum
Subscribe to Updates
Recent Comments
Comments Feed
Powered by
Movable Type and Oracle
The views expressed on this blog are my own and do not necessarily reflect the views of Oracle. Terms of
Use