Oracle Beehive Maximum Availability Architecture: Oracle Maximum Availability Architecture White Paper June 2010 Maximum Availability Architecture Oracle Best Practices For High Availability Oracle White Paper—Oracle Beehive Maximum Availability Architecture Introduction ....................................................................................... 1 Oracle Beehive Architecture .............................................................. 2 Oracle Beehive Tiers ..................................................................... 2 Determining Your Oracle Beehive High Availability Requirements ..... 3 Oracle Beehive High Availability Architectures .................................. 4 Oracle Beehive with Oracle Real Application Clusters ................... 6 Oracle Beehive with a Secondary Disaster Recovery Site ............. 7 Oracle Beehive Disaster Recovery Plus a Local HA Standby ........ 8 Planned and Unplanned Outage Solutions ...................................... 11 Planned Outages ......................................................................... 12 Unplanned Outages ..................................................................... 13 Deploying Oracle Beehive MAA....................................................... 14 Oracle Database MAA ................................................................. 14 Oracle Beehive Application High Availability Deployment ............ 15 Oracle Beehive Site Target in Oracle Enterprise Manager ........... 17 Oracle Beehive Disaster Recovery Site Deployment ................... 17 Local HA Standby Deployment .................................................... 18 Conclusion ...................................................................................... 18 Appendix ......................................................................................... 19 Example Test Environment .......................................................... 19 Install the first Oracle Beehive Instance ....................................... 20 Post-install Verification ................................................................ 20 Port Configuration ........................................................................ 22 Configure TLS and the XMPP Service ......................................... 23 Sanity Test Install ........................................................................ 25 Load Balancer Configuration ....................................................... 26 Sanity Test with Load Balancer ................................................... 28 Oracle White Paper—Oracle Beehive Maximum Availability Architecture Configure ONS ............................................................................ 29 Configure Oracle Beehive Database Services ............................. 30 Clone the Application Tier ............................................................ 33 Oracle Beekeeper Install ............................................................. 38 Oracle Beehive Disaster Recovery Site Setup ............................. 39 Test Role Transitions ................................................................... 48 Oracle Beehive Local HA Standby Setup.................................... 50 Database Configuration Files ...................................................... 52 Create Users Script ..................................................................... 57 Oracle RAC FAN Callout Start Services Script ............................ 60 References ...................................................................................... 63 Oracle White Paper—Oracle Beehive Maximum Availability Architecture Introduction Oracle Maximum Availability Architecture (MAA) is Oracle's best practices blueprint based on proven Oracle high availability technologies and recommendations. The goal of MAA is to achieve the optimal high availability architecture at the lowest cost and complexity. Papers are published on the Oracle Technology Network (OTN) - http://www.otn.oracle.com/goto/maa. This paper describes the Oracle Beehive Maximum Availability Architecture (MAA), a best practice blueprint for achieving an optimal Oracle Beehive high availability deployment using Oracle high availability technologies and recommendations. To achieve Oracle Beehive maximum availability, apply the following high-level recommendations: 1. Deploy the Oracle Beehive database in an Oracle Database MAA configuration. 2. Deploy the Oracle Beehive application in an Oracle Beehive high availability (HA) configuration. 3. Establish a secondary Oracle Beehive site for disaster recovery, testing, and planned maintenance activities. 4. Review the benefits and feasibility of implementing a local HA standby deployment. This white paper describes each recommendation in detail and the solutions that are available for planned and unplanned outages. The Appendix shows a detailed example of deploying an Oracle Beehive MAA configuration. This document was written in the context of Oracle Beehive Version 1.5 running on Oracle Database 11g Release 1 (11.1) and, where necessary, this paper references the documentation for these product releases. In most cases, the recommendations and best practices can be applied to later releases, too. If you are running later product versions refer instead to the appropriate version of the product documentation. 1 Oracle White Paper—Oracle Beehive Maximum Availability Architecture Oracle Beehive Architecture Built on Java 2 Platform Enterprise Edition (J2EE), Oracle Beehive provides a multitier architecture that leverages proven Oracle technologies, such as Oracle Database and Oracle Application Server, as well as other key Oracle and third-party components. Oracle Beehive Tiers The Oracle Beehive architecture is divided into the following logical tiers: ● Client Tier contains Oracle Beehive clients as well as other supported clients and devices, including integration with Microsoft Outlook and a command-line tool for system administration. Oracle Beehive also supports clients and devices that leverage the following standardized protocols: Calendaring Extensions for WebDAV (CalDAV), Extensible Messaging and Presence Protocol (XMPP), File Transfer Protocol (FTP), Internet Message Access Protocol (IMAP), Push Internet Message Access Protocol (P-IMAP), Open Mobile Alliance Data Synchronization (OMA-DS), Simple Mail Transfer Protocol (SMTP), and Web- based Distributed Authoring and Versioning (WebDAV). The open nature of the Oracle Beehive platform also enables developers to build and implement custom clients in the Client Tier using Oracle Beehive Web services. ● Application Tier contains Oracle Beehive services and application server components. The Application Tier is the core of the architecture and includes all Oracle Beehive server components, including interoperable, function-specific services that provide the system's enterprise collaboration features. The Application Tier supports multiple Oracle Beehive server instances. Each Oracle Beehive server instance includes required components of Oracle Application Server 10g, which itself hosts the Oracle Beehive services, including: • Oracle HTTP Server (OHS): The Web server component of Oracle Application Server 10g. Enables connections between supported clients over HyperText Transport Protocol (HTTP) and Secure HyperText Transport Protocol (HTTPS). • Oracle Application Server Containers for J2EE (OC4J): J2EE v1.4 -compliant containers that provide an infrastructure for deploying, un-deploying, and redeploying J2EE-compliant applications and modules. Oracle Beehive services are deployed in OC4J containers. ● Data Tier contains the Oracle Database to store system configuration and collaboration data. The Data Tier provides Oracle Database a layer of separation from the other tiers, ensuring, among other things, optimized security and system performance. Only the Database Access Framework (provided by Oracle Beehive) can access the Data Tier. Oracle Beehive services cannot access the Data Tier directly and must make all connections through the schemas provided by the Database Access Framework. For more information on the Database Access Framework, see the Oracle Beehive Concepts [4] guide. 2 Oracle White Paper—Oracle Beehive Maximum Availability Architecture ● Ancillary Tier, which contains optional Oracle and third-party components that enhance or coexist with certain aspects of the system. Typically, components in this tier are optional because Oracle Beehive already provides many of these capabilities, such as user directories, e- mail, and time management. For a more detailed description of each tier see the Oracle Beehive Concepts4 [4] guide. This paper focuses on the MAA deployment in the Application and Data tiers These tiers are outlined in red in Figure 1. Figure 1 [*Oracle Beehive Concepts]. Oracle Beehive Logical Architecture Determining Your Oracle Beehive High Availability Requirements An analysis of business requirements for high availability combined with an understanding of the level of investment required to implement different high availability solutions enables the development of a high availability architecture that will achieve both business and technical objectives. The Oracle Database High Availability Overview [2] guide has a section on “Determining Your High Availability Requirements” that details an analysis framework for determining your HA requirements. A summary of the framework elements: ● Business Impact Analysis This categorizes the business processes based on the