Part II describes recommendations and steps you need to take to create a high availability environment.

This part contains the following topics:

• Using Shared Storage
  Oracle recommends locating specific artifacts in shared storage for a high availability environment.
• Database Considerations
  As you configure database connections for Oracle Fusion Middleware in a high availability setup, you must make decisions about Oracle Real Application Clusters (Oracle RAC).
• Scaling Out a Topology (Machine Scale Out)
  Steps to scale out a topology (machine scale-out) are similar for all Fusion Middleware products that are a part of a WebLogic Server domain. To enable high availability, it is important to provide failover capabilities to another host computer. When you do so, your environment can continue to serve your application consumers if a computer goes down.
• Using Dynamic Clusters
  A dynamic cluster is a cluster that contains one or more dynamic servers. A dynamic server is a server instance that gets its configuration from a server template. This is in contrast to Managed Servers, which require you to configure each server individually.
• JMS and JTA High Availability
  To configure JMS services and Java Transaction API (JTA) services for high availability, you deploy them to migratable targets that can migrate from one server in a cluster to another server.
• Administration Server High Availability
  The Administration Server plays a unique role in domains. To set up high availability, you configure the Administration Server on a virtual host.