About using Fusion Middleware Control to manage multiple machines

6-4 Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer availability, see Oracle Fusion Middleware Administrators Guide for Oracle Web Cache. ■ Non-load balanced: This configuration is essentially several unconnected Discoverer middle-tier machines that operate independently. In other words, you have a different Discoverer URL for each machine. When you deploy Discoverer, you cannot configure components separately Discoverer Plus, Viewer, and Portlet Provider. You must configure all the components, but you can choose to disable certain components. For example, you might enable Discoverer Plus only on one machine and Discoverer Viewer only on another machine. ■ Hardware load balancer: This configuration distributes Discoverer Web traffic to multiple Discoverer middle tier machines. ■ When you configure Discoverer across multiple machines or multiple instances with load balancing, you also provide load balancing for other Oracle Fusion Middleware components on those machines or instances. For example, you can also configure Oracle Portal with load balancing. ■ To provide a consistent Discoverer interface to end users, when you configure Discoverer across multiple machines or multiple instances with load balancing, ensure that each machine has the same configuration settings for example, user interface customizations and timeouts.

6.2.2 About using Fusion Middleware Control to manage multiple machines

When you install Discoverer on more than one machine, you can link instances together in a domain. Consider a scenario in which you have installed the following: ■ Oracle Internet Directory, and the PStore and Portlet Provider database schemas on host 1 for example, in d:\classicdisc1\asinst_disc18 ■ Standalone installation on host 1 for example, in d:\classicdisc1\asinst_ 19 ■ Oracle Internet Directory and the PStore and Portlet Provider database schemas on host 2 for example, in d:\classicdisc2\asinst_19a You can manage the above scenario by using Fusion Middleware Control. Each machine would be represented as an instance in Fusion Middleware Control, displayed in the WebLogic Domain folder. Managing Discoverer in a Multi-Machine or Multi-Instance Environment 6-5 Notes ■ For more information about using Fusion Middleware Control, see Fusion Middleware Control Help. ■ When Discoverer is installed on multiple machines or in multiple instances, the Discoverer Preference Server component can be configured in the following ways: – One Discoverer Preference server component when there is a single instance. – One Discoverer Preferences server component in one instance on one machine to which other Discoverer instances on the same or different machines point. For more information, see Section 1.9.2.2, What is the Discoverer Preferences server component? and Section 6.6, About the Discoverer Preferences component in a multiple-machine environment . 6.3 What are the prerequisites for using Oracle Web Cache to provide load balancing for Oracle BI Discoverer? Before you can configure Oracle BI Discoverer for load balancing using Oracle Web Cache, you must have the following installed: ■ Two or more Discoverer installations on multiple machines or in multiple instances ■ Oracle Web Cache installed in at least one instance Note : Oracle Web Cache is included in both a Discoverer installation and an Oracle Java EE and Web Cache type installation. Notes ■ Include the Discoverer installations to load balance in the same domain. 6-6 Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer ■ When load balancing between multiple installations, either all or none of the installations must be associated with the Oracle Internet Directory. Also note that multiple installations can be on the same machine or on different machines.

6.4 About using Oracle Web Cache to configure load balancing for Discoverer