This blog provides general guidelines and deployment configuration recommendations to migrate your existing application deployments to the Oracle Exalogic environment.

Your existing environments may vary based on the following:

  • Number of applications in the domain
  • Number of clusters and size of the clusters
  • Number of servers in the domain

You might migrate multiple domains, each of which may be different from each other. Given the differences in existing deployments, there is no set series of steps recommended by Oracle to follow when migrating to the Oracle Exalogic environment.

Migration Process

To migrate your existing environment, Oracle recommends the following steps:

  • Review the domain configuration and apply the specific application deployment configuration guidelines.
  • Determine the domains that will be migrated to the Oracle Exalogic environment.
  • Determine the High Availability requirements for each application in the domain.
  • Define the topology for the new Oracle Exalogic environment based on each domain’s CPU and High Availability requirements.
  • Migrate each domain, updating the domain configuration to reflect the new file system, recommended topology guidelines, and application deployment configuration changes.

Recommended Topology

Oracle recommends the following topology for the Exalogic environments:

  • A domain spans at least two compute nodes.
  • Each cluster spans at least two compute nodes.
  • Each Managed Server is located on a server core.
  • A node manager resides on each compute node.
  • Domains, applications, and binaries are located on shared storage.

Application Deployment Configuration Guidelines

In general, applications can be migrated to the Exalogic environment with minimal changes. Oracle recommends considering the following regarding application deployment configuration to the Exalogic environment:

  • Shared File System Considerations
  • Staging Model Considerations

Shared File System

The Oracle Exalogic environment contains a shared file system available to all servers. When migrating your application, Oracle recommends that the application archives and domain directories to be located on the shared file system. In an Oracle WebLogic Server domain, each individual server can either share a domain directory or have its own domain directory. In the Exalogic environment, Oracle recommends that one domain directory be shared among all servers.

Staging Model

Oracle WebLogic Server supports three types of deployment staging modes for deployed applications. For more information, refer to section “Controlling Deployment File Copying with Staging Modes” in the Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server guide. http://docs.oracle.com/cd/E11035_01/wls100/deployment/deploy.html

In the Oracle Exalogic environment, application archives are located on the shared storage and one physical copy of the application is available to all servers. Because of this, Oracle recommends using the nostage staging mode for applications.

Migration Considerations for Oracle Exalogic