SAP Landscape Management 3.0, Enterprise Edition

Managing SAP Landscape Management

SAP Landscape Management is an add-on to SAP NetWeaver 7.5 installed as an application with the SAP NetWeaver Application Server for Java (SAP NetWeaver AS for Java).

It uses the underlying SAP NetWeaver AS for Java technology. Therefore, to monitor and manage the SAP Landscape Management system, you use the monitoring and managing mechanisms of SAP NetWeaver AS for Java.

Technical System Landscape

The following graphic depicts the main components of SAP Landscape Management:



Main Components of SAP Landscape Management

Technical Configuration

SAP Landscape Management stores its configuration data in the Configuration Manager repository, which is the central storage for technical configurations of all applications deployed on SAP NetWeaver Application Server for Java (SAP NetWeaver AS for Java).

For more information, see the Managing System and Application Configurations sections in the SAP NetWeaver Library documentation in SAP Help Portal.

Starting and Stopping

To start or stop SAP Landscape Management, you must either start or stop the entire SAP NetWeaver AS for Java or use the SAP NetWeaver Administrator to start or stop only the SAP Landscape Management application.

  • For more information about starting and stopping the SAP NetWeaver AS for Java, see the section Starting and Stopping the Application Server Java (AS Java) in the SAP NetWeaver Library documentation in SAP Help Portal.

  • For more information about starting and stopping applications using the SAP NetWeaver Administrator, see the section Starting and Stopping Java Applications in the SAP NetWeaver Library in SAP Help Portal.

User Management

SAP Landscape Management uses the user management functions of SAP NetWeaver AS for Java as provided by the User Management Engine (UME).

For more information, see the section User Management of the Application Server Java in the SAP NetWeaver Library in SAP Help Portal.

Logging and Tracing

Logging and tracing are essential to for analyzing problems. To ensure the stable and error-free operation of the system, the system administrator needs to check the logs regularly for error messages. SAP Landscape Management uses the log mechanisms of the SAP NetWeaver Application Server for Java (SAP NetWeaver AS for Java).

Use

SAP Landscape Management comprises two types of logs:

  • Java Enterprise Edition (Java EE) engine logs and traces

    You can view these logs using the Log Viewer in SAP NetWeaver Administrator.

  • SAP Landscape Management logs

    You can view these logs using the log function in SAP Landscape Management.

Logging and tracing are essential to analyzing problems.

SAP NetWeaver Administrator provides features for viewing and configuring Java EE engine logs and traces.

Java EE Engine Logging and Tracing

Viewing and configuring Java EE engine logging and tracing is integrated with SAP NetWeaver Administrator.

SAP Landscape Management uses the following functions in SAP NetWeaver Administrator for inspecting and configuring Java EE log and trace entries:

  • Log Viewer

    The Log Viewer plug-in helps in viewing information about system problems and displays all log and trace records logged by applications or servers. Careful monitoring of logs and traces can help you predict and identify the sources of problems. You can use predefined perspectives and right filters to speed up the process of gathering required information.

  • Log Configuration

    The Log Configuration plug-in provides functionality for inspecting and modifying the log configuration, changing the severity of log controllers, and resetting the current log configuration to default.

    The logging and tracing functionality is provided by the standard log and trace functionality in SAP NetWeaver Administrator. You do not require any special configuration for this type of logging. However, tracing must be explicitly configured.

In the Log Configuration tool of the SAP NetWeaver Administrator, SAP Landscape Management uses the following locations while creating Java EE log and trace entries:

  • Logging categories

    • ROOT CATEGORY/Applications/LVM

  • Tracing locations

    • ROOT LOCATION/com/sap/nw/lm/aci

    • ROOT LOCATION/com/sap/tc/lm/aci

    • ROOT LOCATION/com/sap/tc/vcm

Backup and Restore

You need to back up your system landscape regularly to ensure that you can restore and recover it in case of failure.

  • To back up your SAP Landscape Management configuration data, you need to export the SAP Landscape Management configurations into an XML file.

    For more information, see Exporting the Configuration Data.
  • You can reuse the XML file containing the exported SAP Landscape Management configuration settings for future configuration tasks or for restoring the configuration data after a system failure.

    For more information, see Importing the Configuration Data.

High Availability

Always have an up-to-date and running backup system on a separate virtual machine. In the case of system errors or down time, you can import the SAP Landscape Management data to this virtual machine and have your application running all the time.

Software Change Management

SAP Landscape Management uses the SAP NetWeaver Development Infrastructure (NWDI) to handle change management.

For more information, see Using the Development and Production Infrastructure.

Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support organization that seamlessly integrates your end-users, internal support employees, partners, and SAP Active Global Support specialists with an efficient problem resolution procedure.

You can raise an incident in component BC-VCM-LVM in the SAP Support Portal at http://support.sap.com/incidentInformation published on SAP site. Incidents assigned to this component are monitored regularly by SAP Landscape Management primary support specialists and are processed immediately.

For more information about attaching technical support information to your incident, see Downloading Support Information.