Outlining New Capabilities in SP23

The SUSE Pacemaker cluster is an often used cluster resource manager for high availability environments. To ensure that SAP systems managed by Pacemaker work with SAP Landscape Management, enterprise edition, SAP Landscape Management integrates with SUSE Pacemaker cluster since Support Package 21 (SP21). With SP21, basic functions for handling the Pacemaker cluster were delivered. For example, the ability to switch maintenance mode on and off via SAP Landscape Management. With SP23, integration with SUSE Pacemaker Cluster has been extended, giving you more possibilities and flexibility for dealing with your Pacemaker-managed SAP systems running on SAP HANA databases.

Among other things, all operations have been optimized and you can now see details about your cluster at the instance and host level.

However, SAP Landscape Management is not cluster-aware from the start. For this, you must first enable the cluster integration. In this e-learning, you first learn how to prepare the system, which includes making SAP Landscape Management cluster-aware. Then you find out where you can see the details of your cluster and what is displayed. Finally, you learn what has been optimized in the operations and what opportunities are now open to you for your custom processes.

What preparations must you make so that SAP Landscape Management is cluster-aware and can deal with SAP systems managed by Pacemaker?

1. First, update your SAP Landscape Management, enterprise edition system to the SP23 release.
2. Next, check if you've already installed SAP Adaptive Extensions Patch 69 or higher. If not, then install it.
3. For SAP Landscape Management to recognize and manage SAP systems running within SUSE Linux Enterprise high availability extension cluster managed by Pacemaker, you must also enable cluster integration in the settings. By default, cluster integration is disabled.

Next, you see where you can select the checkbox to enable the cluster integration to make SAP Landscape Management cluster-aware.

For SAP Landscape Management to recognize and manage SAP systems managed by Pacemaker, you must first enable cluster integration for your system. To do this, follow these six steps:

1. Log in to your SAP Landscape Management system.

2. Choose Setup → Settings.

3. Make sure you are on the Engine tab.

4. Choose Edit.

5. If you want to enable cluster integration, select the Enable Cluster Integration checkbox. If you want to disable it, clear the checkbox.

6. Save your changes.

When the cluster integration is enabled, SAP Landscape Management recognizes SAP systems managed by Pacemaker and prohibits or adapts operations and custom processes for the cluster. You can do the following:

• Run Cluster Manager Operations operations.
• View cluster details in the Operations view when opening the general instance or host details.
• Use cluster validations.

When the cluster integration is deselected, SAP Landscape Management treats all SAP systems as if there is no cluster. Therefore, if you already have your own scripts for SUSE Pacemaker, you can continue to use them without hesitation.

You can find instructions on how to enable and disable the cluster integration also here: Managing Cluster Integration

Congratulations. Now, you know where to check the box to enable cluster integration.

Next, you see where the details of your cluster are displayed.

Here, you learn where you can see the details of your cluster at the instance and host level:

1. Choose Operations → Systems.

2. Select a system managed by Pacemaker.

3. Choose an instance. For example, your central services instance.

4. Here you can now see the cluster details of your instance. If the resource is part of a group, you can also see the group ID.

5. If you want to see the cluster details of a specific host, switch to the Hosts tab.

6. Choose a corresponding host.

7. Here you can now see the cluster details of your host.

Congratulations. Now, you know where you can find the details of your cluster at the instance and host level.

Next, you find out what has been optimized in the operations and what opportunities are now open to you for your custom processes.

With SP23, we have optimized all operations of SAP Landscape Management. Each operation can now be classified into one of the following categories:

1. The operations of the first category are not affected by the cluster. No changes have been made to these operations. You can continue to use them as they are. For example, set note.
2. The operations belonging to the second category are disabled for systems managed by Pacemaker, since their execution could cause conflicts with the cluster solution. Therefore, these operations are not displayed, but can be found under Non-Executable Operations, including the reason why they are not available. This category currently also contains all provisioning activities. If you don't want this, because you want to execute an unsupported operation, you can deactivate the Enable Cluster Integration checkbox. By deactivating, everything is as before, so all operations, such as Enable System Replication, are available again.
3. The operations of the third category can be applied only while the corresponding entity is in maintenance mode. Therefore, as long as the entity is in maintenance mode, you see the operations that belong to this category and you can safely apply those operations. When the maintenance mode is not enabled, these operations are not directly visible, but are displayed under Non-Executable Operations. Example: Stopping the secondary SAP HANA database. So, if you want to apply this standalone operation, you must enable the maintenance mode for the SAP HANA database first. However, it is different for processes, as you learn in the following sections.

New operations have been added to the custom processes defined by SAP, to ensure that the processes can interact correctly with the cluster solution. You can see an example in the What Has Changed for Custom Processes? screenshot. The operation Enable Cluster Resource Maintenance Mode (Optional) is such an operation. These new process steps are only applied when the checkbox Enable Cluster Integration is selected and the process is to be applied for a system managed by Pacemaker. The verification is done via new constraints. In addition to these constraints, there are other new constraints to deal with systems managed by Pacemaker. All these new constraints can also be integrated into your own custom processes. A list of all constraints, including the new constraints, can be found here: Static and Dynamic Constraints

With SP23, there is also the new operation, Start Pacemaker, which starts the Pacemaker service. This operation can only be used within a custom process.

If you don't want to use the optimized operations and custom processes, you can clear the checkbox Enable Cluster Integration at any time.

A full list of all operations and custom processes affected by this checkbox can be found here: Managing Cluster Integration

Congratulations. Now, you know what has changed in operations and custom processes and that some new constraints are available for creating or modifying your own custom processes.

You now know:

• How to prepare the system, which includes making SAP Landscape Management cluster-aware.
• Where you can see the details of your cluster and what is displayed.
• What has been optimized in the operations and what opportunities are now open to you for your custom processes.