Downtime and Apache Restricted Mode in Release 12

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.

Enabling Apache in Restricted Mode in Release 12

I. Creation of downtime schedule

1. Login to OAM as administrator and create a downtime schedule as follows.
    1. Click on Sitemap -->  Maintenance --> Maintain downtime schedules
    2. Click on Schedule Downtime link

downtime wizard1:


2. Enter the details in the page and click submit

downtime wizard2:


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.

downtime wizard3:

II. Configuring and starting restricted mode Apache

  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.

  3. Run the command 'txkrun.pl -script=ChangeApacheMode' from the <FND_TOP>/bin directory:
  4. This prompts for the following inputs:
    1. full path for the Applications Context file
    2. Enter the mode for Apache. Type 'Restrict'
    3. Confirmation of whether you have stopped your applications tier services
  5. Once you enter the above details, the configuration script
    1. sets the respective context variables in the context file required to configure the Restricted mode
    2. instantiates the configuration files for the HTTP Server and OC4J in the <INST_TOP>.
  6. Restart the services on the applications tier upon successful completion of the above command.
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.

The URL for the down time page is:

http://host:port/OA_HTML/oam/nonUix/launchMode/restricted/downtime.html

Sample downtime page:

downtime0:


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.

Disabling Restricted Mode of Apache

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.

  3. Run the command 'txkrun.pl -script=ChangeApacheMode' from the <FND_TOP>/bin directory:
  4. This prompts for the following inputs:
    1. full path for the Applications Context file
    2. Enter the mode for Apache. Type 'Normal'
    3. Confirmation of whether you have stopped your applications tier services
  5. Once you enter the above details, the configuration script sets the respective context variables in the context file required to reset the mode back to Normal
  6. Restart the services on the applications tier upon successful completion of the above command.
You are all set for normal user activity now.

References


Comments:

What is the URL to access OAM during maintenance?

Posted by Tianhua Wu on March 25, 2008 at 04:09 AM PDT #

Good to see another update. I look forward to testing it out in the near future.

Posted by NewSunSEO on March 25, 2008 at 06:52 AM PDT #

Too good a functionality to ignore while patching.

Posted by Ram on March 25, 2008 at 09:40 AM PDT #

Click on sitemap-->monitoring-->maintain downtime schedules

--Correct Navigation Path is

Click on sitemap-->Maintenance-->maintain downtime schedules

-Thanks a lot for all your hardwork and keeping us Up-To-Date
Shyamal

Posted by Shyamal on March 26, 2008 at 05:35 AM PDT #

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.

Here is the URL in the book:
http://host:port/servelets/weboamLocal/oam/oamLogin

Actually, I could not find oamLogin.jsp on file system at all. I did find oamLogin.class and oamLogin.uix files.

Posted by Tianhua Wu on March 27, 2008 at 03:55 AM PDT #

Thanks Shyamal for pointing out the correct navigation. Corrected and reposted.

Posted by Prasad Akkiraju on March 27, 2008 at 05:10 PM PDT #

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.

Thank you in advance for you answer,
Regards,
Jurijs

Posted by Yury Velikanov on March 27, 2008 at 09:50 PM PDT #

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.

Posted by Prasad Akkiraju on March 28, 2008 at 03:42 AM PDT #

Sorry Shyamal, I thought you were trying to answer my question.

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

Posted by Tianhua Wu on March 28, 2008 at 06:01 AM PDT #

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.

Posted by Prasad Akkiraju on March 28, 2008 at 03:11 PM PDT #

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

Posted by Steve Parks on April 14, 2010 at 12:57 AM PDT #

For few minutes between shutting down the application and running txkrun.pl to enable restricted apache, the "page not found" is displayed. How can we avoid this, especially on our iRecievables external site.

Posted by Niatti on January 17, 2011 at 11:46 AM PST #

what do you mean by
"instantiates the configuration files for the HTTP Server and OC4J in the <INST_TOP>. " it is 5.2. when enabling restricted access
what actions are expected to be done

regards
Alexander

Posted by guest on April 03, 2013 at 04:16 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
4
5
6
7
8
9
10
11
12
13
14
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today