JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition System Administration Guide     Oracle Solaris Cluster 4.1
search filter icon
search icon

Document Information


1.  Introduction to Administering the Geographic Edition Software

Geographic Edition Administration

Geographic Edition Administration Tools

Command-Line Interface

Analyzing the Application for Suitability

2.  Before You Begin

3.  Administering the Geographic Edition Infrastructure

4.  Administering Access and Security

5.  Administering Cluster Partnerships

6.  Administering Heartbeats

7.  Administering Protection Groups

8.  Monitoring and Validating the Geographic Edition Software

9.  Customizing Switchover and Takeover Actions

10.  Script-Based Plug-Ins

A.  Standard Geographic Edition Properties

B.  Legal Names and Values of Geographic Edition Entities

C.  Disaster Recovery Administration Example

D.  Takeover Postconditions

E.  Troubleshooting Geographic Edition Software

F.  Deployment Example: Replicating Data With MySQL

G.  Error Return Codes for Script-Based Plug-Ins


Analyzing the Application for Suitability

This section describes the guidelines you must follow in creating applications to be managed by Geographic Edition software.

Before you create an application to be managed by Geographic Edition software, determine whether the application satisfies the following requirements for being made highly available or scalable.

Note - If the application fails to meet all requirements, modify the application source code to make it highly available or scalable.

A scalable service must meet all the preceding conditions for high availability as well as the following additional requirements.

For a scalable service, application characteristics also determine the load-balancing policy. For example, the load-balancing policy Lb_weighted, which allows any instance to respond to client requests, does not work for an application that makes use of an in-memory cache on the server for client connections. In this case, you should specify a load-balancing policy that restricts a given client's traffic to one instance of the application. The load-balancing policies Lb_sticky and Lb_sticky_wild repeatedly send all requests by a client to the same application instance, where they can make use of an in-memory cache. If multiple client requests come in from different clients, the RGM distributes the requests among the instances of the service.

See Chapter 2, Developing a Data Service, in Oracle Solaris Cluster Data Services Developer’s Guide for more information about setting the load-balancing policy for scalable data services.

The application must be able to meet the following data replication requirements: