SCAN Run Time Implications and Limitations

4-14 Oracle Fusion Middleware High Availability Guide

4.4.1 SCAN Run Time Implications and Limitations

There are three possible supported scenarios when you configure against RAC: Table 4–6 SCAN Run Time Implications and Limitations Scenario Description High Availability Run time Outcome and Limitations 1. Non Scan Multi DS with each subordinate DS pointing to a separate RAC instance Gives run time High Availability of the database connections, which the WLS Multi Datasource implementation manages. Limitation : Even if you reference a SCAN address, you are using the limited High Availability features of the WLS Multi Datasource. 2. SCAN Multi DS with each subordinate DS pointing to the SCAN address Gives run time High Availability of the database connections, which the WLS Multi Datasource implementation manages. Limitation : Even if you reference a SCAN address, you are using the limited High Availability features of the WLS Multi Datasource. 3. SCAN A single Data Source pointing to the SCAN address. Does not give runtime High Availability of the database Connections. Limitation : A SCAN address virtualizes the entry point to the RAC instances, however, if you specify a single Data Source on WLS, doing so does not provide High Availability. The reason for this is that each server is effectively bound to a single RAC instance. 5 Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-1 5 Configuring High Availability for Oracle Fusion Middleware SOA Suite Oracle Fusion Middleware SOA Suite provides a complete set of service infrastructure components for designing, deploying, and managing composite applications. Oracle Fusion Middleware SOA Suite enables services to be created, managed, and orchestrated into composite applications and business processes. Composites enable you to easily assemble multiple technology components into one SOA composite application. Oracle Fusion Middleware SOA Suite plugs into heterogeneous IT infrastructures and enables enterprises to incrementally adopt SOA. This chapter provides a description of Oracle SOA Suite components from a high availability perspective. This chapter also includes sections that outline the single-instance concepts for SOA components that are important for designing a high availability deployment. This chapter includes the following topics: ■ Section 5.1, Introduction to Oracle Fusion Middleware SOA Suite ■ Section 5.2, Oracle SOA Service Infrastructure High Availability ■ Section 5.3, Oracle BPEL Process Manager and High Availability Concepts ■ Section 5.4, Oracle BPM Suite and High Availability Concepts ■ Section 5.5, Oracle Mediator and High Availability Concepts ■ Section 5.6, Oracle Human Workflow and High Availability Concepts ■ Section 5.7, Oracle B2B and High Availability Concepts ■ Section 5.8, Oracle Web Services Manager and High Availability Concepts ■ Section 5.9, Oracle User Messaging Service and High Availability Concepts ■ Section 5.10, Oracle JCA Adapters and High Availability Concepts ■ Section 5.11, Oracle Business Activity Monitoring and High Availability Concepts ■ Section 5.12, Oracle Service Bus and High Availability Concepts ■ Section 5.13, Configuring High Availability for Oracle SOA Service Infrastructure and Component Service Engines ■ Section 5.14, Configuring High Availability for Oracle Service Bus, with SOA Service Infrastructure and Component Service Engines ■ Section 5.15, Configuring High Availability for Oracle BAM 5-2 Oracle Fusion Middleware High Availability Guide

5.1 Introduction to Oracle Fusion Middleware SOA Suite