Administrator

Exceptions When Working in a Clustered Server Environment

Keep a few things in mind when working in an clustered server environment.

In an SAP Mobile Platform Server cluster, there is no distinction between master server and secondary server: all nodes are equal and run independently. All nodes share the database. Updates performed in Management Cockpit on any of the nodes in the cluster are saved to the database and therefore automatically synchronized to the other nodes in the cluster. However, there are some exceptions to keep in mind when working in a clustered server environment.

You must perform any tasks that require updating files directly in the file system on each node in the cluster, such as server configuration changes that update the props.ini file or changes to the keystore password that update the local_smp_keystore.jks file.

Updates to Agentry configuration files that are edited outside Management Cockpit and published to the server are not automatically synchronized across the cluster. You must restart each server node for these changes to take effect.

Management Cockpit connects to one server node in the cluster. The following Management Cockpit activities apply only to the server node host to which Management Cockpit is connected. Connect Management Cockpit to another node to perform the activity on that server.
  • Managing server features – server features are enabled only for the node to which Management Cockpit is connected.
  • Viewing server log files – you can view server log files only for the node to which Management Cockpit is connected.
  • Viewing Agentry log files – you can view Agentry log files only for the node to which Management Cockpit is connected.
  • Exporting applications – the exported application ZIP file is created only on the node to which Management Cockpit is connected.