Oracle E-Business Suite Technology

Looks like another good week for certification announcements. Close on the heels of announcing Database 11gR1 certification,  we are announcing the certification of Oracle Single Sign-On and Oracle Internet Directory 10g 10.1.4.2 with Oracle E-Business Suite Release 11i. Existing 11i environments using earlier version of SSO & OID can be upgraded to the 10.1.4.2 Patch Set. Customers on 10.1.2.0.2 version of SSO & OID must first upgrade to 10.1.4.0.1 and then apply the 10.1.4.2 Patch Set.

Certified Operating System Platforms

• Linux x86-32
  
• Sun Sparc Solaris
• HP-UX PARisc
• IBM AIX
• Microsoft Windows 2003

The latest certified configuration is documented in:

• Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i (OracleMetalink Note 233436.1)
  

Related Articles

• Oracle Identity Management Fixed Bugs and Workarounds 10g Release 3 Patch Set 1 (10.1.4.2)
• Oracle Identity Management 10g (10.1.4.2) Online Documentation Library
• In-Depth: Using Single Sign-On 10g with E-Business Suite Release 11i

As soon as we announced Database 11gR1 (11.1.0.6.0) certification with EBS Release 11i, questions have started pouring in - when it would be certified with EBS Release 12?. For the curious support and customer community, I would like to inform that the 11gR1 certification project for Release 12 is in progress and we will update you as soon as the effort is complete. However, we would not be able to give firm timelines for completion and announcement of this certification.

As I started writing down the steps for my recent post Downtime and Apache Restricted Mode in Release 12,  Steven and I exchanged some conversations which made me realize that there would be questions about the availability of the same feature Release 11i. And, it turns out to be fairly accurate realization. So, this one is for those enthusiastic pals of mine on this community. I will try to do this differently, hence making it relatively shorter in content.

Is this feature available in 11i?

Yes. Check out the documentation in the References section.

Is the procedure to configure the same?

Yes. As you might have understood already, there are two pieces in this puzzle.

1. Creation of downtime
2. Managing Apache in Restricted Mode

Answering the question based on these two tasks,

• Step '1' is pretty much the same in 11i and Release 12. Hence, I am not recreating the screen shots for you here. Check out the steps in the table below.
  
• Step '2' is automated in Release using the perl script where as in Release 11i, the administrator has to go through some manual steps and run Autoconfig.
  

What are the exact steps in Release 11i?.

Thanks to our OAM team, these are well documented. And, they work like charm. Below are the sequence of steps for my DBA friends.

Note: Navigation in 11i for the downtime page creation is slightly different than Release 12.

S.No	Task	How to?
1.	Schedule System Downtime and warn your end users of an impending downtime	Use OAM to schedule downtime: ( Navigation: Sitemap=>Maintenance=>Patching and utilities=>Schedule Downtime)
2.	Complete the required one-time setups to monitor patch in progress	Use OAM Autoconfig editor to edit the variable < s_trusted_admin_client_nodes > to include the list of hosts that can access OAM in restricted mode. Run autoconfig to ensure that the new settings take effect. Ensure that you have enabled the the monitoring user account by unlocking the ad_monitor user account and setting the password by using the following commands: alter user ad_monitor account unlock; Login to SQL*Plus as user ad_monitor. Default password is lizard. Reset the password.
3.	Shutdown all Applications services	Use the standard ad script from $COMMON_TOP/admin/scripts/<context_name> directory: adstpall.sh <apps user>/<password>
4.	Enable maintenance mode for your Applications system	Run adadmin, and: Select option 5 'Change Maintenance Mode' Select option 1 'Enable Maintenance Mode'
5.	Start OAM in restricted mode to monitor patching in progress	From the $COMMON_TOP/admin/scripts/<context_name> directory, run: adaprstctl.sh start
6.	Begin applying patch	Run adpatch (hotpatch=n)
7.	Monitor patching in progress	Access OAM in restricted mode from the following URL : http://host:port/servlets/weboamLocal/oam/oamLogin Login into OAM using the ad_monitor user Navigation: Sitemap=>Maintenance=>Patching and utilities=>Timing Reports
8.	Confirm the end of scheduled downtime upon patch completion	From within OAM in restricted mode: Navigation: Sitemap=>Maintenance=>Patching and utilities=>Manage Downtime Schedules=>Select "Complete" button.
9.	Bring your Applications System to normal mode.	Run adadmin, and: Select option 5 'Change Maintenance Mode' Select option 2 'Disable Maintenance Mode'
10.	Shutdown Apache in restricted mode and Restart all services	From the $COMMON_TOP/admin/scripts/<context_name> directory, run: adaprstctl.sh stop adstrtall.sh <apps user>/<password>

References

1. About Oracle Applications Manager Mini-pack 11i.OAM.H
2. Chapter 6, Section 'Managing Downtime in Restricted Mode' of Oracle Applications System Administrator's Guide - Maintenance - Release 11i (Part No B13924-04)