This section contains the information that you need to plan your Sun Cluster HA for MaxDB installation and configuration.
Before you begin, consult your MaxDB documentation for configuration restrictions and requirements that are not imposed by Sun Cluster software. For information about restrictions that the Sun Cluster software imposes, see the Sun Cluster documentation.
The configuration requirements in this section apply only to Sun Cluster HA for MaxDB.
If your data service configuration does not conform to these requirements, the data service configuration might not be supported.
For requirements that apply to all data services, see Configuration Guidelines for Sun Cluster Data Services in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Use MaxDB version 7.4 or compatible versions.
Configure Sun Cluster HA for MaxDB as a failover data service. You cannot configure Sun Cluster HA for MaxDB as a scalable data service. For more information, see the following sections:
To enable client applications to access Sun Cluster HA for MaxDB, you must use SAP xserver. Configure SAP xserver as a scalable data service. Do not configure SAP xserver as a failover data service.
Configure SAP xserver so that SAP xserver starts on all nodes to which the MaxDB resource can fail over. To implement this configuration, ensure that the node list of the SAP xserver resource group contains all nodes that are in the node list of the MaxDB resource group. For more information, see How to Register and Configure an SAP xserver Resource.
The Sun Cluster HA for MaxDB data service supports configurations that conform to the requirements in Configuration Requirements.
If you plan to use MaxDB with other highly available SAP applications, you must also configure the Sun Cluster data services for those applications. For more information, see the following table.
SAP Application |
Sun Cluster Data Service |
Associated Document |
---|---|---|
SAP R/3 |
Sun Cluster HA for SAP | |
SAP liveCache |
Sun Cluster HA for SAP liveCache |
Sun Cluster Data Service for SAP liveCache Guide for Solaris OS |
SAP Web Application Server |
Sun Cluster HA for SAP Web Application Server |
Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS |
The examples that follow show these supported configurations of Sun Cluster HA for MaxDB:
Two-node cluster configuration
Four-node cluster configuration with SAP R/3
Four-node cluster configuration with SAP R/3 and SAP liveCache
Sun Cluster HA for MaxDB might support additional configurations. However, you must contact your Sun service provider for information about additional configurations.
This example shows a two-node configuration in which a client application accesses the MaxDB resource through the SAP xserver resource. The characteristics of this configuration are as follows:
The MaxDB resource is configured as a failover data service.
The SAP xserver resource is configured as a scalable data service.
This example shows a four-node configuration in which MaxDB is used with SAP R/3. This configuration uses multiple Advanced Planner & Optimizer (APO) application servers. The characteristics of this configuration are as follows:
The SAP APO Central Instance (CI) resource is configured as a failover data service.
The MaxDB resource is configured as a failover data service.
The SAP xserver resource is configured as a scalable data service.
APO application server (APP) resources are configured as scalable data services.
This example shows a four-node configuration in which MaxDB is used with SAP R/3 and SAP liveCache. This configuration uses multiple APO application servers. The characteristics of this configuration are as follows:
The SAP APO CI resource is configured as a failover data service.
The MaxDB resource is configured as a failover data service.
The SAP xserver resource is configured as a scalable data service.
APP resources are configured as scalable data services.
The SAP liveCache resource is configured as a failover data service.
The configuration considerations in the subsections that follow affect the installation and configuration of Sun Cluster HA for MaxDB.
Ensure that you create a device group for the MaxDB application as follows:
Install MaxDB on its own global device group. For more information, see Installing and Configuring MaxDB. This separate global device group for MaxDB ensures that the MaxDB resource can depend on the HAStoragePlus resource only for MaxDB.
Create an HAStoragePlus resource for the global device group on which MaxDB is installed. For more information, see Configuring the HAStoragePlus Resource Type to Work With Sun Cluster HA for MaxDB.
Ensure that the resource for MaxDB depends on the HAStoragePlus resource for the global device group on which MaxDB is installed. For more information, see Registering and Configuring Sun Cluster HA for MaxDB.
Configure MaxDB so that MaxDB starts only on a node where SAP xserver is running. To implement this configuration, configure resources and resource groups as follows:
Ensure that the resource for MaxDB depends on the resource for SAP xserver.
Create on the MaxDB resource group a strong positive affinity for the SAP xserver resource group.
For more information, see Registering and Configuring Sun Cluster HA for MaxDB.
You might be required to administer SAP xserver as a user other than root. In this situation, you must create and define that user as follows:
You must create that user on all cluster nodes that master SAP xserver.
You must define that user when you register and configure Sun Cluster HA for MaxDB. For more information, see Registering and Configuring Sun Cluster HA for MaxDB.
Answer the questions in this section to plan the installation and configuration of Sun Cluster HA for MaxDB. Write the answers to these questions in the space that is provided on the data service worksheets in Appendix D, Data Service Configuration Worksheets and Examples, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
Which resource group will you use for the MaxDB application resource and for the logical host name for the MaxDB resource?
Use the answer to this question when you perform the procedure How to Enable MaxDB to Run in a Cluster.
What is the logical host name for the MaxDB resource? Clients access the data service through this logical host name.
Use the answer to this question when you perform the following procedures:
Where will the system configuration files reside?
See Sun Cluster Data Services Planning and Administration Guide for Solaris OS for the advantages and disadvantages of using the local file system instead of the cluster file system.