Observe these best practices.
- Thread safety – The admin API client library is not thread safe, so external synchronization is
required when calling the APIs concurrently from multiple threads.
- Performance – When managing multiple SAP Mobile Platform
clusters, for performance considerations, it is best to connect to
SAP Control Center co-located with the managed
SAP Mobile Platform cluster. Although connecting to another
SAP Control Center (as long as they share the same
credentials) to perform management is supported, performance may not be as good
as the former approach.
- Commit configuration – The SUPServerConfiguration,
SUPSecurityConfiguration, and
SUPConfiguration APIs use a local cache and upload
changes later to the SAP Mobile Server. You must perform a commit
to upload changes to the SAP Mobile Server and then refresh.
- Error handling – For error handling, use the error code returned in the exception. Also, by
calling the getErrorCode() method of
SUPAdminException, a string representation of the
structured error code can be retrieved, which can further the centralized error
code handling.