For SAP environments that use Solution Manager
for runtime root-cause analysis, configure a destination System
Landscape Directory (SLD) server. This configuration allows
SAP Mobile Platform to deliver runtime
information to a common SAP SLD repository, keeping information
about your SAP and SAP Mobile Platform mobility
infrastructure complete and current.
To use SAP Mobile Platform data with
an SLD:
- Determine
SAP Mobile Server cluster and data tier
strategy – you can configure SLD in a cluster of two: the primary and
secondary servers perform different activities, and the cluster database
aggregates and holds data. Depending on your schedule and your cluster
design, this might place demands on your cluster database.
- Install dependencies – the installed version of SLD is for SAP NetWeaver 7.0
(2004s) SPS07 or higher. The SLD to which you register must be the latest
Common Information Model version (currently 1.6.30).
- Set
up
the SLD – verify
that
the
SLD
is
available to SAP Mobile Server and configured to receive
data. For more information, see the Post-Installation Guide and
the User Manual for your SAP NetWeaver version on SDN: http://www.sdn.sap.com/irj/sdn/nw-sld.
- Set
connection
properties – collect and deliver to the platform administrator. Determine
the connection values to the SLD server, including its host name, protocol
(HTTP or HTTPS), port, and the SLD user account.
- Encrypt any dependent certificates – if SLD is configured to use HTTPS, ensure that the SLD
server certificate is signed by a known certificate authority. Otherwise,
you must manually import the certificate into the SAP Mobile Server (primary node only) certificate keystore.
See SAP SLD Server Overview in System Administration.