Configuration Steps for SAP NetWeaver Administrator (NWA)

As of SAP NetWeaver 04 SP Stack 12, the SAP NetWeaver Administrator (NWA) is also available to you for landscape-wide administration and central monitoring.

The NWA runs as an application on the J2EE Engine and is called using the URL :
http://host:port/nwa

To use the NWA for central monitoring, install a Java Add-In for your CEN, if it does not already have one. Since you can use the NWA not only for central monitoring, but also for central administration, the corresponding double-stack system is referred to as the central administration and monitoring system. This system is also abbreviated to CEN

If you want to use the NWA to monitor your system landscape, you need a System Landscape Directory (SLD), since information about the monitored systems is stored in the SLD for this application. We recommend that you set up an SLD on the J2EE Engine of CEN for this purpose. This SLD is known as the administrative SLD.

• You need to configure and start the administrative SLD; you also need to enter all ABAP and Java systems in your system landscape into this SLD.
• CEN must be able to write data about the agents of the monitored systems to the administrative SLD. You need to create special connections and authorizations for this.
• You also need to set up a special RFC connection between the ABAP and the Java stacks of CEN.
• If you want to use the NWA to administer multiple Java systems, we recommend that you store the corresponding logon data in the NWA's J2EE Engine, so that you do not need to log on with a user name and password every time.

To simplify this step, the Template Installer is available in the NWA. You can use it to perform the above configuration steps more easily.


More can be found @ http://service.sap.com/nwa

Prerequisites:
1) Monitored ABAP systems must be entered in transaction RZ21;
2) A CCMSPING availability agent must be installed and registered with CEN;
3) Monitored Java systems must be registered with CEN using the CCMS agent SAPCCMSR;
4) It is recommended to register the monitored ABAP instances with CEN using the CCMS agent
SAPCCM4X;

More Information can be found from the link below.

http://help.sap.com/saphelp_nw04s/helpdata/en/3d/b5f9c2ea65c242957ee504ca4a37a9/frameset.htm

SAP Netweaver 2004s - Components of Monitoring - Global Workload Monitor

The Global Workload Monitor (transaction ST03G) displays statistical records for entire landscapes and therefore allows the analysis of statistical data from ABAP and non-ABAP systems. You can use this data to analyze the workload of the monitored components in great detail.

While statistics records for an ABAP system can only trace actions that are processed by ABAP components, you can use Distributed Statistics Records (DSRs) to trace actions that are processed by, for example, the J2EE Engine, ITS, and TREX. You can even do so across component boundaries.

SAP Netweaver 2004s - Components of Monitoring - Standalone Log Viewer

With the standalone log viewer, you can monitor any J2EE Engine or Java application log files, even if the J2EE Engine is not functioning correctly, cannot be started, or is not available on the system to be monitored. The standalone log viewer contains any number of servers and one client:

• 
  The server of the standalone log viewer monitors log files that are registered with this server. It must be installed on every host of the J2EE system landscape. The various servers function independently of each other.
• 
  The client of the standalone log viewer connects to one or more servers of the standalone log viewer and displays the contents of the log files. You only need to install the client once in the J2EE system landscape.

For general information about the standalone log viewer, see the SAP NetWeaver Library
under SAP NetWeaver -> SAP NetWeaver by Key Capability -> Application Platform by Key Capability -> Java Technology in SAP Web Application Server -> Administration Manual -> Supportability and Performance Management -> Logging -> Log Viewer -> Standalone Log Viewer.

SAP Netweaver 2004s - Components of Monitoring - Operating System Collector SAPOSCOL

The operating system collector SAPOSCOL is an independent program that runs in the
operating system background. It functions independently of the SAP instances, exactly once per monitored host. SAPOSCOL collects data about operating system resources, including:

* Usage of virtual and physical memory
* CPU utilization
* Utilization of physical hard disks and file systems
* Resource usage of running processes

SAP Netweaver 2004s - Components of Monitoring - CCMS Agents

CCMS agents are independent processes with an interface using RFC to a central monitoring system and an interface to the shared memory. These agents have the following properties:

• A connection to CEN using RFC, to ensure greater downtime security and general availability
• Use of the push technology to optimize performance when reading and writing monitoring attributes and alerts
• Inclusion of the operating system collector SAPOSCOL to monitor processes at operating system level.
• Connection to systems with no SAP NetWeaver Application Server
• Monitoring of any log files

There are various CCMS agents, including:

SAPCCMSR - Monitoring of components on which no SAP ABAP instance is active, such as the J2EE Engine or SAP IPC
SAPCCM4X - Monitoring of SAP ABAP systems as of SAP Basis 4.X

SAP Netweaver 2004s - Components of Monitoring - SAP NetWeaver Administrator (NWA)

The SAP NetWeaver Administrator (NWA) unifies the most important administration and monitoring tools both for Java and for ABAP systems in a new, browser-based user interface. The most important advantages of the NWA are:

• You no longer need to switch between different tools for administration, troubleshooting, and problem analysis of your entire SAP NetWeaver system landscape.
• There is now a central administration tool available to you landscape-wide for both Java and ABAP systems for starting and stopping instances, checking configuration settings and logs, and monitoring error-free functioning of components.
• The interface follows the current guidelines for interface design, is easy-to-use, task-oriented, and complete. By using Web Dynpro, it runs in a normal browser.
• The interface allows seamless navigation to other SAP NetWeaver administration tools (User Management Engine, in the future also System Landscape Directory, Adaptive Computing).
• For Java, the NWA represents the crossover from various expert tools to an integrated, simple, and clear solution. The NWA also completes the integration of the data sources for monitoring.
• For ABAP, the NWA represents the crossover from many different expert transactions, some of which are difficult to use, to integrated, centrally available information.

The NWA is delivered for the first time for SAP NetWeaver 04 SP Stack 12. A more advanced version is delivered with SAP NetWeaver 2004s. It is intended to deliver an advanced version with SAP NetWeaver 2004s. The NWA will also be continually further developed in later releases, and extended with additional administration and monitoring functions.

SAP Netweaver 2004s - Components of Monitoring - System Landscape Directory (SLD)

The SAP System Landscape Directory (SLD) is the central information provider in a system landscape. The SLD contains two types of information:

• Component information: all available SAP products and components and their versions. If appropriate, external products are also registered here.
• Landscape description: all installed systems in a system landscape.

SAP Netweaver 2004s - Components of Monitoring - Visual Administrator

The J2EE Engine Visual Administrator is a graphical user interface for administering entire clusters, all cluster elements, and all modules that are running on the J2EE Engine.

Among other things, it includes the following functions in a single user interface:

• Obtaining general information about a service, a manager, and interface, or a library
• Administration and changing of the properties for services and managers
• Configuration of global properties
• Administration and monitoring at runtime
• Performing deployments of applications

SAP Netweaver 2004s - Components of Monitoring - Alert Monitor

The alert monitor is the central tool with which you can efficiently administer and monitor distributed SAP solutions or client-server systems. The alert monitor displays problems quickly and reliably. The alert monitor has, among other things, the following properties:

􀁸 You can use the alert monitor to monitor all SAP and non-SAP systems, the host systems and the database completely and in detail.

􀁸 All errors generate alerts that are displayed in a tree structure; the most significant error is reported upward in the display hierarchy.

􀁸 You can assign analysis and auto-reaction methods to the individual nodes. These methods contribute to quicker processing of the error.

􀁸 You can adjust all settings individually and configure your own monitors.

For general information about the alert monitor, see the SAP NetWeaver Library under
SAP NetWeaver -> Solution Life Cycle Management -> Solution Monitoring -> Monitoring in CCMS -> Alert Monitor.