SAP J2EE (+PO) Monitoring

Background

Process Orchestration (PO) is described by SAP as an integrated tool infrastructure to model and design business processes. It is often confused with the terms Exchange Infrastructure (XI) and Process Integration (PI) but they are relatively the same thing with additional functionalities as SAP evolved over time.  

The performance monitoring of SAP PO/PI/XI has gotten more and more complex as PO evolved into a full standalone SAP J2EE application on top of Netweaver Java AS, comprising of PI (AEX - Advanced Adapter Engine Extended) and BPM.


On This Page

IT-Conductor Streamlines PO Monitoring

SAP J2EE Environment is notoriously complex. It has grown organically and through acquisitions but has retained a disjointed approach to management and monitoring.

Unlike SAP CCMS that serves as a unified instrumentation and monitoring tool, the J2EE Environment has NWA (NetWeaver Administrator) which is a collection of disparate monitoring tools and monitoring data is spread over a number of tables, specific for each area.

SAP PO adds even more complexity as it introduces more screens and tables, thus making the task of monitoring the SAP J2EE Environment even more daunting.

SAP Solution Manager was introduced by SAP with the aim to bring monitoring of SAP infrastructure under control. However, given its complexity, heft, and rigidity, several organizations have been reluctant to go this route and we cannot blame them.

Features

IT-Conductor™ introduced SAP PO Monitoring in addition to SAP J2EE Infrastructure Monitoring.

Unlike native SAP J2EE monitoring and Solution Manager, IIT-Conductor™ delivers a highly functional, logical, and flexible way to monitor and manage SAP J2EE Infrastructure with PO and BPM add-ons.

PI/PO Service Grid

Once the SAP Netweaver Java AS system has been added to SAP Java monitoring via a Wizard, IT-Conductor™ discovers the SAP Java Cluster Nodes. Then the PO/PI/XI components are associated including:

  • Java Server Nodes
  • Integration Server (AEX)
    • Adapter Framework:
      • Caches
      • Communication Channels
      • Jobs
      • Messages
      • Queues

Figure 1: Sample J2EE and PO/PI/XI Components View


Each of these components covers statuses, performance metrics, and workloads that aids the performance monitoring for the Advanced Adapter Engine alongside the SAP J2EE server.

Time-Synchronized Troubleshooting Context

IT-Conductor™ introduced the standard time-synchronized context approach to this environment, enabling unparalleled visibility into performance bottlenecks and making troubleshooting easy and fast.

Figure 2: Sample Pop-out Charts for Average Processing Time

Events and Performance

Historical and interval-based collectors allow you to drill down into the errors and have the whole context at your fingertips.  This allows you to perform analysis from a single console.

Figure 3: Sample Historical and Interval-based View of Error Messages

More Information



Do you have a question about the content on this page? E-mail us at support@itconductor.com.