Skip to Content

SOA Management

Frequently Asked Questions

Applies to:

  • SAP NetWeaver Process Integration 7.1
  • SAP NetWeaver CE
  • SAP NetWeaver 7.0 > SPS13
  • SAP Solution Manager 7.0, SPS15

General

Configuration

Monitoring

Search-Based Monitoring

Alerting

Testing


General

What is SOA management?

SOA management is a solution which enables the effective management of an SOA implementation during the deployment and runtime phases. It provides the capabilities to safeguard, operate, and evolve your SOA deployment so that you can fully leverage the benefits of service orientation for the business.
SOA Management is best viewed as a solution, not a product by itself. It may utilize the capabilities of several infrastructure products to synergistically address the SOA runtime management challenges.

A SOA management solution - also referred to as runtime governance solution - will cover a wide range of capabilities to ensure a successful SOA deployment. Capabilities belonging to SOA management include, but are not limited to, configuration, monitoring - for availability, performance, and overall Quality of Service, policy enforcement - to ensure the right behavior of services, Service Level Agreements (SLA) - to ensure the contracted level of service is provided, auditing and logging, alerts and notifications, deployment and upgrades, report generation, and facilitation of root cause analysis

Why do I need SOA management?

As organizations begin to mature in their uptake of SOA, they typically start to find a number of challenges in the management of their SOA environment that comprises a fast-growing number of loosely coupled, connected services spanning a variety of IT platforms, infrastructure technologies and communication protocols. An unmanaged and ungoverned SOA implementation is likely to lead to a "Shelfware SOA" of hundreds of services that are deployed but are not actually used, or are reused little, or offer duplicate functionality (a state also often referred to as "service sprawl").

The challenges in managing the SOA environment will invite some typical questions: What services are running in my landscape and how are they inter-related? Are the services providing the agreed-on level of service? Are the policies I enforced on the services violated? If my CreditCheck service goes down, which processes and which customers are affected? Who uses the services? The list of "SOA management questions" can grow immensely.

A SOA management solution addresses these challenges by:

Providing IT

  • Greater visibility into the multi-platform and multi-protocol SOA landscape
  • Control over the distributed and loosely coupled SOA assets
  • Reduced complexity of the SOA entities running in a diverse set of applications, systems, and IT infrastructure

Offering the business

  • Accountability of the way the SOA-based business processes and services operate to achieve the KPIs of the enterprise in support of the corporate strategy.

Ultimately, the primary goal of SOA management is to provide the means to reduce the operational risk of your SOA landscape and ensure SOA runtime governance over the operations of the SOA landscape aligned with the strategic goals of the enterprise. SOA management can be seen as the realization and execution of SOA runtime governance.

What is SOA governance?

SOA governance refers to the processes, policies and associated control mechanisms which a company establishes to steer the adoption, implementation and evolution of SOA in line with business needs. These governance principles provide SOA initiatives with risk-mitigating and controlled structures that lead to predictable and reusable SOA assets and ensure a successful SOA adoption.
SOA governance is part of the broader domain of IT governance. IT governance, in turn, falls into the realm of corporate governance. In this way, SOA governance extends IT governance to address the specific challenges of SOA. SOA governance is essentially a key component of the overall corporate governance strategy.

Integrated SOA governance pervades both the design-time and runtime aspects of the SOA implementation. A holistic and evolutionary approach to SOA governance encompasses people, processes, and technologies. You will need more than just tools for effective SOA governance. SAP sees four key ingredients of effective SOA governance:

  • Organizational governance
    The organizational structures, skill sets, and procedures that are aligned with the specific needs of the company
  • Tool-sets and lifecycle management
    All the tools required to support good governance and to achieve the ultimate goal of automated governance
  • Design and modeling methodology
    A methodology that spans all phases of service design, harmonization, and implementation.
  • Community
    Continually sharing ideas and best practices, inside and outside of the company, for faster time to value and sustained success.


Additionally, the SAP Enterprise Application Framework (EAF) is a methodology with its roots in TOGAF whose principles can be mapped to all the aspects of SOA governance. Many organizations today require a cohesive approach to understanding and adopting SOA across their enterprise landscape. SAP has developed a SOA Domain Model which highlights the key activities organizations should focus on and establish competencies in - designed in a logical way to support the typical IT life cycle. This is then used in conjunction with the SAP SOA Reference Architecture - which allows customers to create a blue print of their "as is" and "to be" architectures. Highlighting the areas where they have strengths, gaps and possible problems moving forward in relation to their SOA adoption. The SOA Reference Architecture can be taken from a conceptual view, to a functional view and can even be mapped onto a specific Enterprise Architecture of a customer - highlighting IT projects, future road maps and changes that may need to happen in the architecture to support the Business. This overall approach supports the SAP governance model and methodologies.

Is SOA governance really so important, why do I need it? When do I need to start worrying about it?

There is a direct correlation between the amount of governance control mechanisms an organization adopts to manage SOA complexity and the benefits it will reap from its SOA initiatives. There is common agreement within the analysts' community that the lack of SOA governance in mid- to large-size SOA projects (greater than 50 services) is the most common reason for project failure. Without an effective, holistic and integrated SOA governance strategy facilitated by the right SOA management solution, organizations run the risk of ending up with few or no reusable SOA assets, and a vulnerable, fragile SOA deployment with unpredictable performance.

To safeguard SOA success, evolutionary SOA governance needs to be a factor at the early stages of your SOA projects. You should consider a SOA governance strategy when you initially deploy SOA to avoid roadblocks as you try to advance your SOA initiatives.

What does SAP offer for SOA management and runtime governance?

SAP aims to offer the very best SOA Governance solutions to our customers to ensure a successful SOA adoption. As part of this strategy, SAP in tandem with the SOA partner ecosystem offer our customer base a selection of options. These options range from the solutions provided by SAP to hybrid solutions integrating partner capabilities as well as specialty SOA appliances for very demanding scenarios.

SAP's strategy is to bring high quality packaged enterprises services with built-in design time governance that can be deployed in both intra and extranet scenarios. Customers reap the benefits of SAP's proven top-down SOA methodology that guarantees alignment of the SOA infrastructure and services with the business objectives while providing the agility demanded by today's fast moving business climate.

SAP Solution Manager is aligned with ITIL to provide a first-class platform for the management of the entire SAP solution landscape. It helps companies reduce TCO throughout the solution life cycle, manage their core business processes and link business processes to the underlying IT infrastructure. SAP Solution Manager adopts these concepts also to SOA Management and plans to extend the functionality to address the management challenges and opportunities of SOA landscapes while at the same time ensure low TCO through a consistent management across SOA and non-SOA based business processes and application of proven IT management practices.

In addition to the SOA Management capabilities provided in SAP Solution Manager and SAP NetWeaver Administrator, SAP works closely with leading SOA vendors in the SOA management space to ensure the overall operational health (deploy-time) as well as providing closed loop governance scenarios. The cooperation between SAP and SOA Management vendors gives customers the freedom to choose which solution for SOA Management fits best their needs or integrates best with their existing infrastructure helping customers to protect their investments. In order to ensure that seamless integration of partner products with SAP's own offering is possible, SAP co-operates with leading SOA Management vendors in various ways: In the SAP CO-Innovation Labs (COIL) SAP and partners jointly build proof-of-concepts and develop best-practices in real-world customer scenarios (For more information, check COIL's Kevin Liu blog SOA Management - Solutions from SAP Co-Innovation Lab). In addition SAP plans to work jointly with partners to develop open interfaces that will simplify the integration between SAP and partner products.

In February 2010 Oracle acquired AmberPoint. How does this impact SAP’s offering in the SOA management and runtime governance space?

SAP is committed to enabling customers to deploy a holistic SOA governance solution that helps them manage their SOA landscape in the context of their IT landscape. In order for our customers to have a choice of technology providers, SAP's CO-Innovation Lab (COIL) has cooperated with an ecosystem of leading SOA management vendors to ensure that best-in-class SOA management capabilities are available to complement the IT management capabilities of SAP Solution Manager.

The ecosystem of SOA management vendors currently includes Progress Actional, SOA Software, and Sonoa Systems whose SOA management offerings provide customers with a rich set of capabilities and the ability to protect existing SOA management investments. Detailed solution descriptions and reports from the PoCs with Progress Actional, SOA Software, Sonoa Systems made in COIL are available in COIL's Kevin Liu blog SOA Management - Solutions from SAP Co-Innovation Lab.

AmberPoint - a formerly independent SOA management vendor recently acquired by Oracle - has previously offered its agent-technology for SAP NetWeaver and planned further releases. Following the acquisition, the decision whether to keep the offering going forward lies with AmberPoint, now Oracle.

Our strategic direction is to provide customers with the ability to select an integrated SOA governance solution that best fits their needs and ensures a closed loop between design-, run-, and change-time of their SOA and business process assets in the unified lifecycle management of their IT landscape.

Configuration

Can I centrally configure point-to-point and mediated communication in SAP NetWeaver Process Integration 7.1?

Yes, you can centrally configure your scenarios - both point-to-point and mediated - through the Integration Directory of SAP NetWeaver Process Integration (PI). In PI 7.1, the Integration Directory offers a new configuration object, direct connection, which enables you to centrally configure point-to-point connections. The benefits of the central point-to-point configuration in the Integration Directory are extended by the central monitoring capabilities, which are offered in the SAP NetWeaver Administrator for PI, for those point-to-point connections.

Additionally, you can use the Integration Directory to configure both application-to-application and business-to-business processes and to configure communication between Web service consumers and Web service providers. The same fundamental procedures are used in all cases.

More information: Integration Directory

What is the relationship between the Enterprise Services Repository and the Integration Directory?

All information about a scenario, such as process models, interfaces and other content objects, is stored in the Enterprise Services Repository (ESR). This information describes the scenario on an abstract level independent of any system landscape. When you configure a mediated scenario, you reuse the information and the objects from the ESR, and you specify how the scenario should run within an actual system landscape. For example, by adding specific routing conditions for messages, and technical connectivity for message exchange between senders and receivers, you specify how messages in the scenario should be exchanged between the systems of your actual system landscape.

Configuration of a mediated scenario is performed in the Integration Directory, and the individual configuration settings are structured in configuration objects.

What are the most important configuration tasks which I need to perform in the Integration Directory?

  • Specifying the potential senders and receivers of messages
    To specify the involved back-end systems that act as sender or receiver of messages, you create communication components and parties. A communication component is an umbrella term for a sender or receiver of messages, for example a business system or an integration process, previously known as "business service". More information: Communication component.
  • Configuring routing
    To specify the receivers of a message, you define a receiver determination. To specify the inbound interface at the receivers' side and the mapping that has to be performed, you define an interface determination.
    Apart from having fixed recipients of messages, you can also have receivers determined dynamically at runtime as well as determined based on the content of the messages (content-based routing).
  • Configuring connectivity to the back-end systems
    To specify the details of the connectivity for a sender or receiver of a message, you define a communication channel. A communication channel contains the details of the used adapter and is assigned to a communication component.
  • Specifying which communication channel has to be used and security settings
    To specify which communication channel has to be used and which security settings should apply, you have to define a collaboration agreement.
    When you configure the message exchange to be processed via the Advanced Adapter Engine (to bypass the Integration Server), you have to use the separate configuration object called integrated configuration, which is a new object in the PI 7.1.


To facilitate the configuration process, you can use the following tools:

  • Model configurator
    If the scenario is modeled as process integration scenario in the Enterprise Services Repository, you can use the process integration scenario as configuration template.
  • Configuration wizard
    To configure a single communication step between a sender and a receiver, you can use the configuration wizard.
  • Integrated configuration
    Integrated configuration is a separate Integration Directory object coming with PI 7.1. It enables the straightforward configuration of message exchange which goes through the Advanced Adapter Engine instead of the Integration Server as message broker: you only have to define one configuration object and there you can specify all necessary details.


Are there any quick or automated ways to configure processes modeled in the Enterprise Services Repository?

Yes, for the purpose, SAP NetWeaver Process Integration provides the so called template-based configuration. You can quickly configure a scenario based on a Process Component Interaction Model from the Enterprise Services Repository by using the model configurator. It automates most of the configuration steps in the Ingeneration Directory and allows you to interactively configure the modeled process for your actual system landscape.

An additional option for template-based configuration is the communication channel template. Within a communication channel template you can already specify details of the connectivity configuration in the ES Repository and assign it to a Process Component Interaction Model. When configuring the scenario in the Integration Directory, you can create a communication channel based on the communication channel template.

Apart from the central configuration tool Integration Directory, are there tools for local configuration?

In addition to the Integration Directory, there are the following local tools for configuring Web service communication:

SOA Manager
With the help of the SOA Manager (transaction SOAMANAGER), you can administer and configure Web services and Web service consumers for the local AS ABAP.

SAP NetWeaver Administrator
The SAP NetWeaver Administrator (available at :/nwa) is a Web Dynpro-based tool which you can use for the configuration Web services and Web service clients running on the local AS Java.

In addition to the tools for local Web service configuration mentioned above, SAP NetWeaver Process Integration 7.1 offers the SAP NetWeaver Administrator for PI (available at :/nwapi) which allows you to centrally configure Web services and Web service clients (both ABAP and Java) across your PI landscape.

I have 50 Web services provided in my landscape and several composite applications each consuming about 3-5 Web services. Is there any automated way for configuring the service providers consumers, or I have to configure them one by one?

SAP offers a set of capabilities for automated configuration which allow you to quickly configure multiple Web services and Web service consumers at one go in a uniform and an easy to use way. These capabilities automate most of the steps required to configure multiple service connections at one go. At the same time, they give the administrator control over the policies that need to be enforced on the service-consumer communication.

This framework for automated configuration is available in both the ABAP and Java worlds and can be used to configure the provisioning as well as the consumption side of the Web service communication.

What are the benefits from using the capabilities for automated configuration?

As SOA projects move to maturity, the number of services and consumers in the SOA landscape is expected to grow. The automated configuration of these artifacts offers some clear benefits in handling the challenge:

  • Lower TCO
    You can enforce runtime configuration settings for multiple Web services and consumers at one go which allows you to dramatically minimize the configuration overhead in the face of proliferating services and consumers. In addition, the framework automates the enforcement of communication policies and thus facilitates an error-free runtime configuration of services and consumers.
  • Unified approach
    The same configuration steps apply no matter whether you configure in ABAP or Java, or whether your consumer is a composite business process, or a Visual Composer, Web Dynpro, a Composite Application Framework (CAF), or a Java EE5 application.
  • Improved efficiency
    The framework offers a role-based approach to automated configuration. It enables a policy Administrator to define the communication policies for service communication in compliance with the policies of the enterprise. The policy Administrator can define policies independently from the service, or application Administrator, who then applies the right policies to the right services and consumers. By facilitating the division of labor, the role-based approach to configuration lowers the total cost of understanding and simplifies the configuration tasks.


More Information: The New SOA Configuration Approach

By using the capabilities for automated configuration of Web services and consumers, can I…

Configure Web services which are not provided by non-SAP platforms or external to my landscape?
No, currently there are no standards which would allow for this type of configuration.

Configure Web services centrally for my landscape?
Currently, you can configure only Web services and Web service clients running on the local SAP Application server ABAP or Java.

Which tools do I have to use to automate the configuration of Web services and consumers?

For ABAP Web services and consumers, you use the SOA Manager (transaction SOAMANAGER). For Java Web services and consumers, you use the SOA Management work center of the SAP NetWeaver Administrator available at the following URL: :/nwa.

In which versions of SAP NetWeaver PI 7.1 and SAP NetWeaver CE 7.1 are the capabilities that enable automated configuration available?

Please refer to the table below:

Product

Smart SOA Configuration for...

SAP NetWeaver Process Integration 7.1

  • ABAP Web service consumers and providers
  • Java Web service providers

SAP NetWeaver Process Integration 7.1, Enhancement Package 1

  • ABAP and Java Web service consumers and providers

SAP NetWeaver Composition Environment 7.1, SP3

  • Java Web service providers

SAP NetWeaver Composition Environment 7.1 Enhancement Package 1

  • Java Web service consumers and providers


I am still exploring SOA in a small pilot project and I have only two Web services with one Web service consumer in my landscape. Can I configure them one by one, or I still need to use Smart SOA configuration?

The framework for automated configuration of Web services and consumers does not replace the capabilities which are currently available for the configuration of individual Web services and Web service consumers; it enhances them. You can still configure Web services and Web service clients one by one. This functionality is available as follows:

  • Local configuration of individual ABAP Web services and Web service consumers:
    SOA Manager (transaction SOAMANAGER)
  • Local configuration of individual Java Web services and Web service consumers:
    SOA Management work center of the SAP NetWeaver Administrator available at the following URL: :/nwa.
  • Central configuration of individual ABAP and Java Web services and Web service clients:
    SAP NetWeaver Administrator for PI available on a Process Integration system at :/nwapi.


What administration functions are available for changing the system configuration of PI?

When you set up the Integration Engine for XML message processing, you can change the default configuration settings shipped by SAP. For example, by using transaction SXMB_ADM, you can apply global and specific configuration data settings, configure XML messages archiving, configure settings for error analysis, and so on.

More information: Configuring the Integration Engine.

For the Adapter Engine, you can change the configuration of the corresponding JEE services by using the SAP NetWeaver Administrator (available at :/nwa). You can also leverage the automated configuration capabilities offered by the Central Technical Configuration (CTC) templates.

Monitoring

My PI landscape comprises three PI installations: one in North America, one in Europe and in one in Asia, respectively. Can I centrally monitor my PI landscape?

Yes. By using the SAP NetWeaver Administrator for PI, you can centrally monitor several PI instances.
In addition, PI monitoring and administration capabilities can be centrally accessed from within SAP Solution Manager 7.0.

At the same time, you can take advantage SAP of the Computing Center Management System (CCMS) infrastructure, which is also available in SAP NetWeaver Process Integration, to centralize the monitoring of your Process Integration infrastructure. The PI monitoring information from CCMS can also be made available in SAP Solution Manager

What is the relationship between the Runtime Workbench that was used for monitoring in previous PI releases and the SAP NetWeaver Administrator for PI available in PI 7.1?

Monitoring capabilities from the Runtime Workbench have been made available in the SAP NetWeaver Administrator for PI for central, landscape-wide monitoring. Selected monitors in the SAP NetWeaver Administrator for PI have been further enhanced and additionally integrated to facilitate, for example, cross navigation between the individual monitors, and lower the TCO. Additional capabilities have been provided in the SAP NetWeaver Administrator for PI to enable the monitoring of Web service communication, for example, WSRM-compliant traffic.

The SAP NetWeaver Administrator for PI is new functionality developed for SAP NetWeaver Process Integration 7.1. In PI 7.1, both the Runtime Workbench and the SAP NetWeaver Administrator for PI are available. However, the SAP NetWeaver Administrator for PI is planned to gradually replace the Runtime Workbench.

What is the main advantage of the SAP NetWeaver Administrator for PI over the Runtime Workbench?

The SAP NetWeaver Administrator for PI allows you to centrally monitor multiple PI installations while with the Runtime Workbench you can monitor the local PI installation.

Which tool do you recommend that I use for monitoring in PI 7.1 – the Runtime Workbench or the SAP NetWeaver Administrator for PI?

Not all monitors of the Runtime Workbench have been completely integrated into the SAP NetWeaver Administrator for PI, yet. Hence, SAP recommends that customers currently use the Runtime Workbench for PI monitoring in production scenarios.

Which components from my PI infrastructure can I monitor with the SAP NetWeaver Administrator for PI and with the Runtime Workbench? Are there any differences?

You can use both the Runtime Workbench and the SAP NetWeaver for PI to display and monitor the following components, all of which are part of the Integration Server:

  • Integration Engine (central)
  • Business Process Engine
  • Mapping Runtime
  • Adapter Engine (central)
  • ABAP proxy systems (business systems with an Integration Engine)
  • Non-central Adapter Engines
  • Java SE adapter
  • Integration Directory
  • Enterprise Services Repository


In addition, by using the Runtime Workbench you can monitor the component status of the System Landscape Directory as well as of the Runtime Workbench itself.

In the SAP NetWeaver Administrator for PI, can I centrally monitor point-to-point Web service communication that have I configured centrally from the Integration Directory?

The sender or receiver systems which you centrally configured for point-to-point communication through the Integration Directory are visualized in the SAP NetWeaver Administrator for PI. From within the SAP NetWeaver Administrator for PI, you can centrally perform message monitoring on those systems.

Additionally, SAP plans to deliver aggregated message monitoring information for the message traffic processed by all components of the PI infrastructure. This aggregated information will be displayed in the SAP NetWeaver Administrator for PI. For example, on a single page, you will be able to view message monitoring information for the messages processed by the Advanced Adapter Engine, the Integration Engine, and so on. This aggregated message processing information will be also include information for the point-to-point Web service communication centrally configured through the Integration Directory.

What is the role of SAP Solution Manager 7.0 in the administration of SAP NetWeaver Process Integration?

SAP Solution Manager 7.0 enables you to centrally manage your entire SAP solution landscape. It is a platform that:

  • Provides the integrated content, tools, and methodologies you need to implement, support, operate and monitor your enterprise's solutions from SAP
  • Enables companies to minimize risk and increase the reliability of their IT solutions.
  • Helps companies reduce TCO throughout the solution life cycle, manage their core business processes and link business processes to the underlying IT infrastructure.


Release 7.0 (Support Package Stack 15) of SAP Solution Manager is structured along role-based work centers which facilitate the easy navigation of end-users. As part of the SAP Solution Manager platform, administration capabilities for SAP NetWeaver Process Integration 7.0 and 7.1 are centrally available from within SAP Solution Manager's System Administration work center under Administration Tools.

How are the PI monitoring and administration tools integrated into the SAP Solution Manager?

The System Administration work center of the SAP Solution Manager features hyperlinks to the relevant PI tools. The PI tools themselves are executed on the satellite PI system which is managed by the SAP Solution Manager.

Which CCMS monitoring tools should I use to monitor PI?

For PI, the Computing Center Management System (CCMS) provides a special alert monitor template called Process Integration. (Transaction RZ20, SAP CCMS Monitor Templates

You can use this alert monitor to monitor the ABAP and Java components (including the Business Process Engine and the Java-based adapters) of your Process Integration landscape centrally, and to identify different categories of system errors and application errors in the various interfaces and interface namespaces of the components involved.

In addition, the Web-Service-Runtime Monitor is available in the Computing Center Management System (transaction RZ20). The system triggers an alert whenever problems occur during the configuration of the Web service runtime, or whenever there are runtime errors of various categories or performance bottlenecks when certain threshold values are exceeded.

How can I check if a component of my PI infrastructure, for example the Adapter Engine, is available and up and running?

You can monitor the availability and the operational status of the PI components in the Runtime Workbench (Component monitor) or the SAP NetWeaver Administrator for PI (the overview page for a selected PI component). The status of the component is communicated via color-coded traffic lights and summary status information. Data about the status of the component is retrieved from the CCMS (each PI component executes a self-test at regular configurable intervals). In addition, each component is pinged for availability every time you start the Runtime Workbench or the SAP NetWeaver Administrator for PI.

How can I track the performance of message processing in my PI landscape?

By using the Performance monitor, you can obtain detailed and aggregated performance statistics on the processing of messages exchanged between senders and receivers and processed by PI. The Performance monitor helps you identify bottle-necks in message processing when the latter takes an anomalously long time. It also facilitates the ongoing sizing of the PI system and subsequent fine tuning and optimization.

You can slice and dice aggregated performance information and drill down into the performance for the processing of individual messages. Performance data can be retrieved from the Integration Server or SAP's PMI infrastructure.

Is it possible to track the route of message traffic throughout my PI landscape?

The End-to-End monitor allows you to monitor the path of individual messages through individual PI components from start to end, including service interfaces in the sending and receiving business systems. You can also monitor the individual message processing steps executed in individual PI components.

How can I check if messages were processed correctly in my PI landscape and what is their status?

You can use the Message monitor to track the processing status of XML messages. You can view and manage the messages persisted in the database as well as archived messages. The Message monitor also enables you to display messages in an aggregated overview format and drill down to the details of individual messages. In addition, you can find out what errors have occurred and to establish what caused these errors.

Can I view and change the content of a message that has failed within, for example, a step in a process/BPM because of for example, error in the content/data of the message?

Yes, by using the capabilities of the Message monitor in PI 7.1, you can edit the payload of XML messages as well as their message headers, including dynamic header attributes. You can edit asynchronous messages in status error.

The changes you make to the messages are logged. When you edit the message, a new version of it is created and persisted, and the system records the username of the user who made the changes, the actual changes that were made and the time when those changes were made. This history of the message and its versions can be displayed in the Message monitor.

Authorizations for editing the message payload are granted with a special user role which increments the PI Administrator authorizations.

Is there an audit trail capability in the SAP NetWeaver Process Integration that enables me to follow what has been changed or read by whom in the system?

Changes in SAP NetWeaver Process Integration are recorded. Read access is not recorded.

When a message has been changed, for example by editing its payload, a new version of the message is created. The username of the user who made the change and the time of change are recorded. The message versions can be displayed in the Message monitor.

Configuration changes to the Integration Engine are displayed in the transaction SXMB_ADM and changes to the Adapter Engine are logged by the standard SAP Application Server Java infrastructure, The changes can be visualized in the SAP NetWeaver Administrator (available at :/nwa).

I noticed that there are some messages in status error in PI.  What does PI offer for control over failed messages?

SAP NetWeaver Process Integration provides basic restart capability through queuing messages in the Integration Server. If a message is sent in guaranteed delivery mode, the Integration Server stores it in persistent queues. The retry mechanism and messaging protocol ensure an exactly once (in order) delivery of messages to receivers, or messages are assigned to error queues for later error handling by an administrator.

I have configured communication that uses the WSRM (Web Service Reliable Messaging) protocol. How can I monitor this WSRM-compliant communication?

SAP NetWeaver Process Integration offers the Sequence monitor which allows you to monitor the status of WSRM sequence processing, as well as the status of processed messages within queues. You can identify errors in message processing and analyze what caused them. In addition, you can terminate and restart sequences.

What other monitoring capabilities, apart from the ones mentioned so far, does SAP NetWeaver Process Integration offer?

The monitoring capabilities of SAP NetWeaver Process Integration are not limited to the ones highlighted above. A comprehensive set of monitoring capabilities allows you to monitor and administer communication channels, proxy runtimes, cache connectivity, as well as to prioritize message processing, and so on. For more information on the monitoring capabilities in SAP NetWeaver Process Integration, refer to the SAP Library documentation available at http://help.sap.com -> SAP NetWeaver 7.1 ->  SAP NetWeaver Process Integration Library

Does the SAP NetWeaver Administrator for PI offer any capabilities to help me diagnose and troubleshoot problems with the message traffic?

Yes. You can leverage the capabilities of the Message monitor available in the SAP NetWeaver Administrator for PI and the Runtime Workbench. It features an audit log for individual asynchronous messages where you can view the message processing activities as well as identify causes for message processing errors.

For erroneous WSRM-compliant message processing, the Sequence monitor features a dedicated display for error analysis information about WSRM sequences.

Next, from the SAP NetWeaver Administrator for PI you can centrally view log and trace records for Web service communication (both for ABAP and Java Web services and Web service clients).

In addition, by using SAP Solution Manager Diagnostics, integrated and available in SAP Solution Manager 7.0, you can perform end-to-end workload and trace analysis for the PI infrastructure.

More information about analyzing and troubleshooting problems with SAP NetWeaver Process Integration is available in the SAP NetWeaver Process Integration 7.1 Troubleshooting Guide at http://service.sap.com/operationsNWpi71 -> Process Integration -> Troubleshooting Guide - SAP NetWeaver PI 7.1.

Can the logging functionality of SAP NetWeaver Process Integration handle several levels of actions?

SAP NetWeaver Process Integration allows tracing and logging of XML message processing with configurable multiple levels of log and trace severity and the corresponding detail of log and trace records. The Adapter Engine and the Integration Engine store log and trace information for every message.

Adapters produce tracing and logging data and offer appropriate tools for working with logs and traces. For example, the Adapter Engine writes log and trace information which can be visualized and searched by using the standard log and trace tooling of the SAP Application Server Java where you can filter log and trace records by severity. Also, it is possible to log each individual processing step (receipt, routing, mapping, adapter call, and so on) so that it can be monitored on the Integration Server.

SAP NetWeaver Process Integration offers the Message monitor for working with log and trace records of individual messages. In addition, monitoring data such as engine and queue status is also reported to the CCMS for overall monitoring and alerting.

Search-Based Monitoring

I need to be able to search for messages based on the message payload. How does PI enable me to do that?

As of SAP NetWeaver 7.0, SPS06, Message monitoring in the Runtime Workbench supports searching by adapter-specific message attributes as well as by content in the message payload. To enable this, messages have to be indexed using the TREX search and classification engine.

With SAP Enhancement Package 1 for SAP NetWeaver Process Integration 7.1, SAP plans to deliver a new capability, called user-defined message search. It will be available out-of-the-box in the SAP NetWeaver Administrator for PI (in the Message monitor) to enable the easy search of PI-processed messages based on data in the message payload. The user defined-message search allows you to search for asynchronous messages exchanged between specific service interfaces and processed both in the ABAP and Java worlds of the integration Server. You can search for messages by using business-relevant criteria, such as, sales order number, customer ID, and so on.

Does the user-defined message search index the whole of a message’s payload?

You are free to specify which parts of the payload of a message you want to have indexed by the search so that it best suites your needs at search-time. The search then uses the XPATH technology (XML Path Language) to extract from the payload the data you have specified by which you can later search.

In the TREX-based search, there is a certain (configurable) delay between the moment a message gets processed and the moment it gets indexed and I can search for it.  Is this the case with the user-defined message search?

No. The user-defined message search indexes messages at runtime and you can search for messages as soon as they are processed.

When does the user-defined message search index messages, before or after mapping?

Currently, messages processed on the Integration Engine are indexed both before and after mapping, and messages processed on the Advanced Adapter Engine are indexed before the mapping takes place.


Alerting

Can PI proactively alert me when something goes wrong in my PI landscape?

Yes. By using the message-based alerting capabilities of PI, you can receive alerts when problems occur in the message processing flow across your PI landscape. The message-based alerting provides you with great flexibility in determining the conditions on which you receive the alert. For example, PI can raise an alert when a specific type of error, for example a mapping error, occurs on a specific adapter, for example the iDOC adapter, in the communication between service specific interfaces.

Alerts are sent to the alert inbox of PI (available in the Runtime Workbench and the SAP NetWeaver Administrator for PI) to subscribed recipients (individual users or whole user groups).

In addition to the message-based alerting, you can leverage the CCMS alert-based monitoring which can notify you whenever the status of a system is deviant. Alerts are centrally displayed in the CCMS alert monitor (transaction RZ20).

In contrast to message-based alerting, which proactively alerts you of a critical situation, by default, CCMS alert-based monitoring reactively displays the status when a problem occurs. An administrator has to explicitly enter the CCMS alert monitoring to get an overview of the system status. Both message-based alerts and CCMS alerts, however, can be sent to recipients via email.

Is it possible to receive the CCMS alerts displayed in the transaction RZ20 in the PI alert inbox (or vice versa)?

Yes. By using an auto-reaction method (CCMS_Send_Alert_to_ALM), you can have alerts from the CCMS automatically forwarded to the PI alert inbox. Conversely, you can have message-based alerts forwarded to CCMS. You achieve that, you use transaction SM37 to configure a background job (SXMSALERT _PROCESS_DATA_GET) which does the forwarding.

In addition, you can configure PI message-based alerts to be forwarded to the alert inbox of the SAP Solution Manager 7.0.

Is it possible to receive alerts when the processing of a message in PI takes too long?

You can receive alerts in the CCMS alert monitor when the processing time of PI messages nears or reaches a pre-set threshold value. The data for the message processing is collected on the Integration Server. The aim is to detect performance bottlenecks within your Integration Server.

You configure message performance-based alerting in transaction SM30, by maintaining the ALXMBPFALERT table. More information: SAPNote 730193.

Via what channels can I receive alerts?

You can receive message based alerts in the PI alert inbox (available in the Runtime Workbench and the SAP NetWeaver Administrator for PI), or by SMS, email, or fax. Alerts displayed in the CCMS monitoring tree can also be sent via email.

Is a message-based alert informative in any way or it just tells me there is an alert?

PI message-based alerts are content-rich and provide you with information which you can use for initial problem isolation. The body of an alert contains the so called container variables, such as error code, message ID, sender/ receiver interface or party, and so on, which you specify when you configure an alert category. These variables get populated with actual information at runtime to preserve the context and provide you with the specifics of the situation in which the alert was raised.

In addition, after you have received an alert and analyzed its content, you can easily jump form the alert itself to the PI Message monitor via which you can additionally drill down and inspect the problem.

Does PI support the SNMP protocol?

Yes. As part of the CCMS monitoring architecture of SAP NetWeaver, the SNMP protocol is supported. It extends the alerting capabilities of PI by enabling you to send alerts as SNMP traps.

More information: Sending Alerts Using SNMP Traps

Testing

How can I test Enterprise Services?

The Web Services Navigator allows you to test multiple operations of Enterprise Services as well as simple Web services deployed in your landscape. It is a Web Dynpro-based tool running on SAP Application Server Java and is available at the following URL: :/wsnavigator.

More information: Testing Web Services in the Web Services Navigator

Can I test asynchronous operations of Enterprise Services?

Yes, by using the Web Services Navigator you can test asynchronous service operations that comply with the Web Services Reliable Messaging (WSRM) standard. The availability of this functionality is planned for SAP Enhancement Package 1 for SAP NetWeaver 7.1.

In the Web Services Navigator, can I save my test cases so that I can reuse them later?

Yes, you can save the test data which you use to test Enterprise Services in test scenarios. For subsequent tests, you can upload the test data and use it to test different instances of the same service hosted by the same or a different provider system.

How can I test integration scenarios?

You can test an integration scenario from within the Runtime Workbench (Component monitor) or from the SAP NetWeaver Administrator for PI (the overview page for a selected PI component).

You can send a test message, complete with a test payload, to the Integration Server to test the status of the mapping, routing, etc. configuration. You can also send an outbound message to the Advanced Adapter Engine to test the outbound communication channel.

Former Member

No comments