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