PI – Operations
SAP NetWeaver Process IntegrationDate Training Center Instructors Education Website
Participant Handbook
Course Version: 74Course Duration: 3 Day(s) Material Number: 50089240
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Trademarks
• Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.
• IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. • ORACLE® is a registered trademark of ORACLE Corporation.
• INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.
• UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. • Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,
VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
• HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
• JAVA® is a registered trademark of Sun Microsystems, Inc.
• JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
• SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.
Disclaimer
THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING
WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,
INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.
This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.
Typographic Conventions
American English is the standard used in this handbook. The following typographic conventions are also used.
Type Style Description
Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options.
Also used for cross-references to other documentation both internal (in this documentation) and external (in other locations, such as SAPNet).
Example text Emphasized words or phrases in body text, titles of graphics, and tables
EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.
Example text Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
Icons in Body Text
The following icons are used in this handbook.
Icon Meaning
For more information, tips, or background
Note or further explanation of previous point
Exception or caution
Procedures
Indicates that the item is displayed in the instructor's presentation.
Course Overview ... ... ... ... ... vii
Course Goals . . . .. . . .. . . .. . . .. . . .. . . .vii
Course Objectives . . . .. . . .. . . .. . . .. . . viii
Unit 1: SAP NetWeaver PI 7.1 Landscape and Operation Considerations ... ... ... ... ... 1
The Technical Architecture of SAP NetWeaver Process Integration . . . .. . . .. . . .. . . .. . . .. . . .. 3
Overview - SAP NetWeaver PI Operation Tasks and Tools . . . 28
Administration of SAP NetWeaver PI Components . . . .. . . 50
Distribution Options of SAP NetWeaver PI Components . . . 95
Message Load Considerations . . . .. . . .. . . .. . . .109
Unit 2: SOA Management – Web Services Configuration & Services Registry ... ... ... ... .. 151
Setup Web Service Runtime . . . .. . . .. . . .. . . .152
Configuration of Web Services . . . .. . . .. . . .. . . .157
Services Registry . . . .. . . .. . . .. . . .. . . .169
Mass Configuration . . . .. . . .. . . .. . . .. . . .188
Unit 3: SOA Management – Monitoring ... ... .. 201
SAP NetWeaver PI Monitoring Landscape . . .. . . .. . . .203
System & Component Monitoring. . .. . . .. . . .. . . .228
Monitoring Activities - On Demand or Alerting Based . .. . . .259
Performance Monitoring . .. . . .. . . .. . . .. . . .279
Unit 4: Error Handling and Resolution ... ... .. 289
Error Detection . .. . . .. . . .. . . .. . . .. . . .290
Error Resolution .. . . .. . . .. . . .. . . .. . . .313
Unit 5: Message and BPE Archiving & TREX Integration.... .. 327
Message Archiving & Deletion on Integration Server (ABAP) .328 Message Archiving on Adapter Engine (JAVA) . . . .. . . .342
Integration Process Administration (BPE) . . . .. . . .. . . .348
TREX Integration. . . .. . . .. . . .. . . .. . . .352
Unit 6: Security Aspects ... ... ... .. 359
Security Considerations . . .. . . .. . . .. . . .. . . .360
Adapter-Specific Security .. . . .. . . .. . . .. . . .370
PI User and Tool Security . . . .. . . .. . . .. . . .. . . .374
Unit 7: Software Logistics ... ... ... ... 381
SPS and Patch Procedure . . . . .. . . .. . . .. . . .. . . .382
BIT480 SAP NetWeaver Process Integration 7.1 – Administration and Operation allows the user to operate a SAP NetWeaver PI system in a way that is most beneficial to your enterprise environment.
Through this course, the participants will become familiar with PI landscape planning considerations, monitoring concepts, and ways of handling PI in case of error situations. The course provides an overview of the administration tasks in an SAP NetWeaver PI 7.1 system, which builds a solid foundation for the SAP system administrator taking care of a SAP NetWeaver PI 7.1system in operation. Since Process Integration is the entry point for SOA enablement, the course addresses features of a SAP NetWeaver PI 7.1system to successfully manage services available in the landscape. In order for the administration staff to be able to keep the system in a healthy operating state, PI-specific housekeeping tasks as well as update procedures are laid out. To complete the picture from the operational point of view, security aspects and software logistic aspects are discussed.
Target Audience
This course is intended for the following audiences:
• Consultants and administrators who want to administrate and monitor an SAP NetWeaver Process Integration 7.1 system (SAP NetWeaver PI 7.1) • SAP system administrators responsible for keeping the system in a running
state at customer site
• SAP operation and maintenance consultants
Course Prerequisites
Required Knowledge
• BIT100 SAP NetWeaver Process Integration – Overview • BIT400 SAP NetWeaver Exchange Infrastructure • ADM100 Administration AS ABAP I
• ADM200 Administration AS Java Recommended Knowledge • JA100 SAP J2SE Fundamentals • BIT140 XML in SAP Solutions
Course Goals
This course will prepare you to:
• Perform the administration and monitoring activities specific to an SAP NetWeaver PI 7.1 system
• Diagnose performance issues and error situations and determine ways to resolve these
Course Objectives
After completing this course, you will be able to:
• Explain the architecture and the components of SAP NetWeaver PI 7.1 • Know how which necessary components to need to be set up for a monitoring
environment
• Know how to monitor the operational state of the system and how to monitor the processing of messages and service interfaces
• Know how to pinpoint and resolve error situations within the system and address system performance and message throughput issues
Unit 1
SAP NetWeaver PI 7.1 Landscape and
Operation Considerations
Unit Overview
At the conclusion of this unit, you will be able to understand the architecture of SAP NetWeaver PI components and have a notion of the distribution options for planning a whole SAP NetWeaver PI landscape. You have an understanding of which SAP NetWeaver PI relevant tasks are to be considered, beside of regular SAP Basis administration tasks.
Unit Objectives
After completing this unit, you will be able to:
• Outline the technical architecture of SAP NetWeaver PI 7.1 • Name the components of an SAP NetWeaver PI 7.1 system • Be aware of SAP NetWeaver PI specific administrative tasks
• Name the tools used for SAP NetWeaver PI system configuration and maintenance tasks
• Be able to select the appropriate tool for a certain administration task • Describe which parts of an SAP NetWeaver PI system need to be
administered
• List the administration tasks in the SAP NetWeaver PI system
• Name the components of a SAP NetWeaver PI 7.1 system that can be distributed throughout the landscape
• Tell if the distribution of SAP NetWeaver PI 7.1 components will benefit your setup
• Know about features of SAP NetWeaver PI addressing high-volume scenarios
• Recommend resource optimizing features to your PI scenario implementation team
• Describe the capabilities of the components to leverage certain PI configuration options
Unit Contents
Lesson: The Technical Architecture of SAP NetWeaver Process
Integration. .. . . .. . . .. . . .. . . .. . . .. . . .. . . .3
Exercise 1: Check URL Information and Installed Usage Types .. . . 25
Lesson: Overview - SAP NetWeaver PI Operation Tasks and Tools.. . . 28
Exercise 2: SAP NetWeaver PI Operation Tasks and Tools . . . .. . . 47
Lesson: Administration of SAP NetWeaver PI Components . . . .. . . 50
Lesson: Distribution Options of SAP NetWeaver PI Components . . .. . . 95
Lesson: The Technical Architecture of SAP NetWeaver
Process Integration
Lesson Overview
This lesson describes the technical architecture and components of an SAP NetWeaver PI 7.1 system.
Lesson Objectives
After completing this lesson, you will be able to:
• Outline the technical architecture of SAP NetWeaver PI 7.1 • Name the components of an SAP NetWeaver PI 7.1 system
Business Example
Your company wants to implement SAP NetWeaver PI 7.1. Therefore, a clear understanding of the technical architecture is needed. As an SAP system administrator you are responsible for maintaining the system landscape, so you want to get an overview what the PI system consists of from a technical point of view.
Introduction
To enable application-to-application processes, SAP NetWeaver provides one platform to centrally manage the design, configuration, and execution of business processes.
SAP NetWeaver PI delivers a message- and standard-based integration of processes within a company by seamless connecting both SAP and non-SAP applications.
Using SAP NetWeaver PI, you can centrally design, configure, and execute application-to-application processes (A2A processes) as well as business-to-business processes (B2B processes) both within and beyond your company.
The shared collaboration knowledge is based on open standards. This ensures openness and interoperability for communication with existing integration solutions and connection to non-SAP applications or third-party systems. SAP provides content to allow an out-of-the-box integration of SAP solutions with other SAP or non-SAP applications.
Using one common infrastructure for the integration of business processes between SAP and non-SAP applications, the complexity of a company’s system landscape is reduced. This promotes synergies between IT building blocks and offers the chance to increase the company’s overall performance. In addition,
maintenance costs are reduced by supporting all phases of the solution life cycle. This means support for configuration and execution as well as the phase of change at the end of the life cycle.
Relying on SAP NetWeaver, IT organizations are enabled to use standards-based Web services to form new and innovative business solutions that meet their changing business needs quickly. In particular, SAP NetWeaver provides service-oriented architecture (SOA) middleware that facilitates communication between disparate applications. From a logical point of view, SOA middleware consists of an Enterprise Services Repository and Services Registry, an
enterprise services bus, and SOA management tools. With SOA middleware, IT professionals can rely on an open and standards-based platform to accelerate business integration.
SAP NetWeaver PI is SAP's implementation of SOA Middleware thus SAP NetWeaver PI is at the heart of an SOA System Landscape.
The following figure shows the building blocks of an SOA Landscape.
Figure 1: Enterprise SOA Infrastructure Building Blocks
SAP NetWeaver Process Integration
The architecture of SAP NetWeaver PI 7.1 is based on an established architecture for realizing cross-system business processes, and is a further development of preceding releases (SAP NetWeaver 7.0 usage type Process Integration and SAP XI 3.0 as part of SAP NetWeaver 2004). SAP NetWeaver PI 7.1 plays an important role in supporting an service-oriented architecture (SOA). The focus is
SAP NetWeaver PI is based on general standards to enable 3rd-party systems to be integrated. At the center of SAP NetWeaver PI there is an XML-based communication that uses HTTP (Hyper Text Transfer Protocol). Regardless of the used scenario, the application-specific contents are transferred in user-defined XML (eXtensible Markup Language) messages from the sender to the receiver either directly, or via the Integration Server.
The figure below gives an overview of the key capabilities of SAP NetWeaver PI:
Figure 2: SAP NetWeaver PI – Key Capabilities Overview
SAP NetWeaver PI 7.1 enables the integration of the applications of the following communication parties:
• B2B Party: Any business partner who wishes to integrate their application with other applications outside their own system landscape. Scenarios that require industry standards are supported as well as any scenarios that do not adhere to a particular industry standard.
• SAP: Applications that run on SAP systems. This includes the processing of events by using the BAM infrastructure.
• 3rd-Party Application: Applications from 3rd-party providers within one system landscape, for example database or file system-based.
• 3rd-Party Middleware: Middleware systems from 3rd-party providers that are required for the integration of applications within a company and across company boundaries.
SAP NetWeaver PI also supports internal company scenarios and cross-company scenarios. It enables you to connect systems from different vendors (non-SAP and SAP) in different versions and implemented in different programming languages (Java, ABAP, and so on) to each other. Like the rest of the SAP NetWeaver platform, SAP NetWeaver PI is based on an open architecture, uses open standards (in particular those from the XML and Java environments) and offers services that are essential in a heterogeneous and complex system landscape.
SAP uses a scenario-based approach that addresses the customer's most important business issues in a flexible way by providing them with modular industry-specific solutions, with a fast total return on investment (ROI) and predictable investment levels that support their end-to-end business processes.
SAP NetWeaver PI represents a particular usage type, selected at installation time. It determines the capabilities offered by a collection of the installed and configured (technical) software components specific to the role as a Process Integration system.
Figure 3: IT Scenarios and Software Units
SAP NetWeaver PI and IT Scenarios
IT scenarios supported by SAP NetWeaver PI address the requirements of IT management, developers, consultants, and other members of the technical
IT scenarios help customers, partners, and ISVs to install and operate SAP NetWeaver PI, to run business applications, including both custom-built and packaged applications, or to implement a defined IT concept, such as evolving a company’s system landscape into a service-based architecture.
Figure 4: Evolution towards an SOA-based Business Process Platform IT scenarios focus on major IT challenges, such as the need to combine different integration technologies, to develop composite applications leveraging existing investments, or to build new business processes in a flexible way. Business Process Management is a typical example of an IT scenario in this context. An IT scenario consists of multiple IT processes which are grouped into scenario variants. Implementation guidance is provided by reference models and the visualization of end-to-end-processes.
SAP NetWeaver PI can be used to carry out various IT scenarios: • Enabling Application-to-Application processes
By enabling application-to-application processes, organizations can seamlessly connect SAP and non-SAP applications within the enterprise, orchestrating the process flow between them using message-based and standards-based methods for process integration. Using SAP NetWeaver PI, a single platform can manage the design, configuration, and execution of all business processes within the heterogeneous system landscape of an enterprise.
• Enabling Business-to-Business Processes
Organizations can seamlessly connect their own business processes with those of their partners using message-based and standards-based methods for process integration. SAP NetWeaver PI supports various communication channels as well as process coordination and surveillance.
• Business Process Management
Business process management (BPM) with SAP NetWeaver PI covers business process modeling, configuration, execution, and monitoring, with process models executed by either the business applications or the central integration server. Organizations can use predefined content to configure business processes and can relate application-embedded settings to business process models.
• Enabling Enterprise Services
With SAP NetWeaver PI, organizations have a single infrastructure for uniform service definition, implementation, and usage based on Web services technology and standards. SAP NetWeaver PI supports enterprise services for user interaction as well as application-to-application and business-to-business interactions using synchronous, asynchronous, stateful, and stateless communication models.
Software Units
SAP NetWeaver delivers software units which are to be installed on hosts within an IT landscape. These software units are systems, standalone engines and clients.
SAP systems are the main building blocks of SAP NetWeaver. They are identified by unique SAP system IDs (SAPSIDs) and configured for a certain purpose, as indicated by usage types. SAP NetWeaver PI comprises the usage types Application Server ABAP (AS ABAP), Application Server Java (AS Java), and Process Integration (PI).
• AS ABAP is used to provide the ABAP foundation of SAP NetWeaver PI. Application Server ABAP provides a complete development and runtime environment for ABAP-based applications. It is optimized for the development of highly scalable business applications. The ABAP development and runtime environment makes it possible to develop complex business applications, without having to worry explicitly about technical details, such as process or memory administration, multi-user capability, database connections, or similar issues. These are provided in the basis services or are integrated directly in the ABAP runtime. The application development is similarly independent of the underlying platform. The application server decouples the application coding completely from the operating system and database in use.
• AS Java is used to provide the Java foundation of SAP NetWeaver PI using the Java Engine, a Java EE-compliant application server for running enterprise applications. In addition to the pure Java EE standard technologies, the Java Engine implements complementary technologies, such as Web Dynpro or Web Services that are targeted at supporting large-scale, real-business application development projects.
• PI consists of core components that model, design, automate, and integrate processes in one or more application systems. For the integration of internal and cross-company processes, PI is used to incorporate all the functions of what was formerly known as Exchange Infrastructure (XI). In addition, PI contains core components for Business Process Management for application-embedded and application-unbounded processes. The Advanced Adapter Engine is also part of usage type PI. You use Advanced Adapter Engine to connect to SAP systems (RFC adapter) and external systems. You use the various adapters in Advanced Adapter Engine to convert XML and HTTP-based messages to the specific protocol and format required by these systems, and the other way around. You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced Adapter Engine. Optionally (for performance reasons), you can install a non-central Advanced Adapter Engine separately as a system with AS Java and parts of the usage type PI on a separate host.
Standalone engines of SAP NetWeaver are additional installable software units. They do not work as full-blown systems of SAP NetWeaver, but as standalone engines that provide a specific (server) functionality in combination with one or more SAP NetWeaver systems.
In conjunction with SAP NetWeaver there are several standalone engines available such as Gateway, Search and Classification (TREX), Web Dispatcher, Advanced Adapter Engine, Adapter Engine (Java SE), and the SAP Partner Connectivity Kit. • On a Gateway instance there are no normal work process types (dialog,
background, update, enqueue, or spool). Only the gateway process (gwrd) is started. If there is an SNA connection to an R/2 system, gateway work processes (gwwp) are also started. In this way, it is possible to install an SAP instance of an SAP NetWeaver system based exclusively on a standalone gateway.
• You can use Search and Classification (TREX) to search for indexed messages on an SAP NetWeaver PI system. Message search using an index provides additional methods of searching for specific messages. If the messages are indexed, you can also use adapter-specific message attributes and data from the message payload for the search in addition to search for static header attributes. You can apply the index-based message search to one or all indexed components of an integration landscape domain: Integration Server, Adapter Engines, and ABAP business systems.
• The SAP Web Dispatcher resides beneath the Internet and your SAP system. It is the entry point for HTTP(s) requests aiming at your system, which may consist of one or more SAP NetWeaver application servers. As a "software web switch", the Web dispatcher can reject or accept connections. When it accepts a connection, it balances the load to ensure an even distribution of requests between the servers. You can use the Web dispatcher in ABAP/Java systems and in pure Java systems, as well as in pure ABAP systems.
Set aside security aspects (i.e. entry point in the DMZ, SSL, URL filtering), you can use the Web dispatcher simply as a load balancer between multiple SAP NetWeaver Application Server instances. Since the Web Dispatcher is optional for every SAP system, it is not contained in the system landscapes and the implementation sequences of the IT scenarios.
• The Advanced Adapter Engine is used to connect to SAP systems (RFC adapter) and external systems. You use the various adapters in the Advanced Adapter Engine to convert XML and HTTP-based messages to the specific protocol and format required by these systems. For specific sender/receiver combinations, messages can be processed without invoking the central Integration Engine. In principle, you connect external systems using the adapters that are installed centrally or non- centrally in the Advanced Adapter Engine. You can use the Advanced Adapter Engine that is part of your PI system as a central Advanced Adapter Engine. Optionally (i.e. for performance reasons), you can install a non-central Advanced Adapter Engine separately as a system with AS Java and components of the usage type PI on a separate host.
Engine (Java SE) to connect to external systems. Using the various adapters in Adapter Engine (Java EE), XML and HTTP-based messages can be converted to the specific protocol and format required by such systems. Adapter Engine (Java EE) only provides some of these adapters as a standalone version with restricted functions for operating systems that do not support SAP NetWeaver PI 7.1, but that do have at least a Java Runtime Environment 5.0. Therefore, you should only use the Adapter Engine (Java EE) if the platform prerequisites do not allow you to use the Advanced Adapter Engine.
• The Partner Connectivity Kit (PCK) runs on AS Java with parts of the usage type PI. It enables a system of a smaller company or subsidiary that does not run SAP NetWeaver PI to connect to your SAP NetWeaver systems.
Clients are additional installable programs or tools. They either reside on local front-end PCs accessed by users or on back-end systems where they act as client programs within an SAP NetWeaver system landscape.
SAP NetWeaver PI provides a number of front-end clients and tools including SAP GUI and SAP NetWeaver Developer Studio.
For the APAP part of the SAP NetWeaver PI system, SAP offers three different client applications for accessing ABAP applications: SAP GUI for HTML, SAP GUI for Java, SAP GUI for Windows.
The SAP NetWeaver Developer Studio is SAP’s Integrated Development Environment (IDE) for Java and is based on the open-source tools framework Eclipse 3.3. With the SAP NetWeaver Developer Studio, you can develop Java EE 5 applications from scratch using the built-in support for new technologies, such as EJB 3.0 and JSF 1.2.
Architecture Overview
The SAP NetWeaver PI system architecture includes components that are used at design time, configuration time, and runtime. Information about the systems and software components used in an integration scenario are stored in the System Landscape Directory.
The Enterprise Services Builder and the Integration Builder are the tools for accessing the design and configuration-time components. Developers and configurators use these to access the Enterprise Services Repository and Registry and the Integration Directory.
The Enterprise Services Repository is the central repository where models and enterprise services are modeled and their metadata is stored.
The Integration Directory is used to work with all of the configuration options for an integration scenario in the SAP NetWeaver PI system.
Figure 5: Architecture Overview of an SAP NetWeaver PI System
The Integration Server provides the runtime environment for processing messages received by the SAP NW PI system. It includes the following components: • The Business Process Engine for executing Integration Processes
(cross-component business processes)
• The Integration Engine for processing all messages for all scenarios in a consistent way
• The Central Adapter Engine for connecting to application systems that are not based on the SAP Web Application Server version 6.20 or higher
The PI Monitor (NWAPI) and Runtime Workbench are used for central monitoring and management of the SAP NetWeaver PI and all of its components.
Design Components
Pre-delivered integration content for SAP solutions open for collaboration knowledge of non-SAP systems, using open standards (e.g. WSDL) provision for customers/partners to enhance PI design time objects Java-based graphical tools Overview of the design components in an SAP NetWeaver PI system.
Figure 6: The Enterprise Services Builder with its ESR
Configuration Components
Within SAP NetWeaver PI, the following options and possibilties for the configuration and handling of the components are offered.
Adapt integration content to specific configuration
Derive integration content from Enterprise Services Repository
Open for customer to add collaboration knowledge relevant to non-SAP components
Java-based graphical tools
Central configuration for B2B processes BPM centralized adapter configuration
Figure 7: Overview of the Configuration Components in an SAP NetWeaver PI 7.1 system
The Enterprise Service Builder contains the Enterprise Services Repository (ESR) and Services Registry. The ESR is the central repository in which service interfaces and enterprise services are modeled and their metadata is stored. It is an integral part of SAP NetWeaver.
The repository is open for customers and partners to also enrich this content with additional services that they would need for their own use. So, if you look at the ESR in some more detail you see that there are two parts: the ESR and the Services Registry. The ESR is really the master data repository of service objects for Enterprise SOA. What do we mean by “Design Time Repository”? This refers to the process of designing services.
Additionally, the ESR supports the whole process around contract first or the well known outside in way of developing services. It provides you with a central modeling and design environment which provides you with all the tools and editors that enable you to go through this process of service definition. It provides you with the infrastructure to store, manage, and version service metadata. Besides service definition, the ESR also provides you with a central point for finding and managing service metadata from different sources, including application deployments – this is where the Services Registry comes in. The Services Registry is the UDDI part of the ESR which enables service consumers to find services. Once these two components are in place, visibility is controlled, versions are managed, proposed changes are analyzed and communicated, usage is
Figure 8: Enterprise Services Repository and Services Registry – Overview The ESR evolved from the Integration Repository. It stores objects, such as global data types (GDTs) and service interfaces. It allows re-use of existing data and leverages existing investment. It also stores new and enhanced objects, such as process component models and service interfaces.
Figure 9: Enterprise Services Repository evolved from the Integration Repository
The Enterprise Services Repository and Registry has several usage scenarios: • Process Visibility and Design Governance
• Service Provisioning • Process Integration • Composition
Process Visibility and Design Governance enables for SOA design governance. There are Process Component architecture models in the Enterprise Services Repository which can be used to drill down to standards based service interface design.
Service Provisioning delivers service metadata. This can be used to model message interfaces and service interfaces based on GDTs. Using the ESR, the service metadata is stored in one central repository.
Process Integration is used for enabling A2A and B2B processes. The services defined in ESR can be accessed for consumption in A2A and B2B scenarios. The composition scenario refers to the possibility of developing composite applications. Consumer applications may query the Services Registry for services that were designed in the ESR.
Figure 10: Enterprise Services Repository Usage Scenarios
The Adapter Framework
The Integration Server processes messages that are received in the XI-SOAP format; systems that are capable of producing messages in this format (for example, mySAP components based on SAP Web Application Server v. 6.20 or higher) can communicate natively with PI. All other systems, including older SAP releases, communicate through adapters. The Central Adapter Engine is based on the integrated SAP J2EE engine. It includes functionality for message handling, queuing, and security. There is an included module processor that lets you extend the basic functionality of adapters by calling additional modules for processing messages in the adapter. Individual resource adapters are “plugged in” to the
the Application Server ABAP; for instance, the IDoc adapter is part of the ABAP layer, and all IDocs are processed by the IDoc Adapter. For any IDocs that you wish to process at the ALE layer of the Integration Server, you must maintain an exception table that specifies which IDocs are processed in the normal way. Further adapters residing on the ABAP stack are the XI (Plain) Adapter and the WS (WS-RM) Adapter.
Additional adapters based on the J2EE framework can be installed non-centrally, and can be configured and monitored centrally.
The resource adapters that are available with the Adapter Framework (Application Server JAVA) include:
• RFC Adapter • JDBC Adapter • JMS Adapter
• Marketplace Adapter
• SAP BC (header extension for support of Quality of Service) • RosettaNet (RNIF 2.0) Adapter
• CDIX (RNIF 1.1) Adapter • File/FTP Adapter
• SOAP Adapter • Mail Adapter
PI includes extensive and growing B2B support for communication with business partners using industry standards such as RosettaNet, CIDX, PIDX, and UCCNet. Collaboration agreements in the Integration Directory configure B2B scenarios, including aspects such as certificate handling, partner ID, and so on.
Figure 11: The Architecture of the Adapter Framework
Business Process Engine
Integration Processes are Business Processes that can run across multiple systems and are expressible in the standard web protocol for Business Process execution, BPEL4WS (Business Process Execution Language for Web Services). You will also see Business Processes referred to as Business Process or cross-component Business Processes in the documentation. If you are familiar with SAP Business Workflow, then you can think of these Business Processes as workflows that run across multiple components. The Integration Server includes a built-in Business Process Engine.
It includes:
• A persistence layer (the process/message store) • The runtime for process execution
• The logic for correlation handling
Business Processes allow you to send and receive multiple messages relating to a single document; for instance, line items for a purchase order may be gathered from several sources. Correlations let you relate the incoming documents to a unique key, for instance a PO number so that incoming documents are processed only with the master document to which they belong.
Figure 12: Cross-component Business Process Management with the Business Process Engine
System Landscape Directory
SAP System Landscape Directory (SLD) is a central information provider that contains two sorts of information about landscape topology:
• Landscape description (catalog of physical and logical systems in the data center)
• Component information (description of all software products from SAP and other vendors)
PI components are client applications to SLD; for instance, an integration engine can determine its role by reading it from the System Landscape Directory. SAP’s Solution Manager is another client application to SLD. SLD is populated with data about SAP software by SAP; that is, an administrator uploads a file to the SLD that contains the description of all currently supported SAP products and software components. ABAP and Java systems in the system landscape register themselves automatically by using data suppliers. Customers are then to add entries for non-SAP products and software components. Additionally, other vendors that support the CIM model can provide software descriptions of their products. You can access SLD by pointing a browser to http://<full qualified hostname>:<HTTP port>/sld. You will be prompted for a user name and password.
Figure 13: System Landscape Directory in the PI Landscape
The SAP NetWeaver PI 7.1 system can run against an SLD 7.0 or a SLD 7.1 installed and configured on the together with an SAP NetWeaver PI 7.1 system. This course does not cover SLD specific landscape considerations. If you need more information and help regarding the SLD planning, please refer to the SLD Planning Guide available on the SDN at https://www.sdn.sap.com/irj/sdn/nw-sld. SLD related administration tasks consists of regularly updating the CIM model and SAP Component Repository (SAP CR content). Important information about the necessary administration steps are explained in SAP Note 669669 - Updating the SAP Component Repository in the SLD.
Monitoring Components
Monitoring a system landscape is a complex task of significant importance for every company that operates one or more SAP systems. The complexity increases with every additional system, component, or extension.
With the monitoring architecture of the Computing Center Management System (CCMS), SAP provides a flexible and universally usable infrastructure with which you can monitor your entire IT landscape centrally, and which reports problems quickly and reliably.
Figure 14: CCMS Monitoring Architecture
The PI Monitoring Landscape offers the following monitoring tools. • Central Monitoring System (based on CCMS)
• Solution Manager
• Wily Introscope Workstation • NetWeaver Administrator
• NetWeaver Administrator for PI: NWAPI
The concept of the monitoring architecture is to make all required information available in a Central Monitoring System (CEN), and therefore to make the administrators’ work easier. Problems are displayed as soon as they occur; the log files can also be accessed from one location, which reduces the time required for error identification and correction. In this way, the monitoring architecture allows you to achieve greater efficiency with lower costs.
Figure 15: Solution Manager Plays a Central Role in the Monitoring Landscape
Looking at the big picture, the SAP Solution Manager is the central platform for managing your SAP System Landscape. It provides means for alerting you proactive with real-time monitoring before problems become severe.
Looking solely at Process Integration it also offers several central monitoring tools, which permit the administrator to get a central view of all components and messaging of the PI System. Architectural components include:
• Computing Center Management System (CCMS) • Process Monitoring Infrastructure (PMI)
• Alerting Framework
The Runtime Workbench allows an administrator to access central monitoring information for all components as well as configuration for the monitoring architecture.
Figure 16: Monitoring Components
Exercise 1: Check URL Information and
Installed Usage Types
Exercise Objectives
After completing this exercise, you will be able to: • know how to determine the necessary URL parts
• know how to check for installed usage types on your system
Business Example
Task:
Execute the following steps in the training system.
1. Call transaction SMICM and check HTTP port and full qualified hostname information.
2. Call URL consisting of http:<full qualified hostname>:<HTTP Port> with suffix /utl/UsageTypesInfo.
Solution 1: Check URL Information and
Installed Usage Types
Task:
Execute the following steps in the training system.
1. Call transaction SMICM and check HTTP port and full qualified hostname information.
a) SMICM→Button: Services
2. Call URL consisting of http:<full qualified hostname>:<HTTP Port> with suffix /utl/UsageTypesInfo.
a) When you call the URL on your training system, you should see the following usage types information:
Active Usage Types
Product Name UT Code Short Name Description SAP NetWeaver 2007 PI PI Process Integration SAP NetWeaver 2007 AS AS Java Application Server Java SAP NetWeaver 2007
AAS AS ABAP Application
Lesson Summary
You should now be able to:• Outline the technical architecture of SAP NetWeaver PI 7.1 • Name the components of an SAP NetWeaver PI 7.1 system
Lesson: Overview - SAP NetWeaver PI Operation Tasks
and Tools
Lesson Overview
This lesson introduces the mandatory administrative tasks and tools required for SAP NetWeaver PI Operation.
Lesson Objectives
After completing this lesson, you will be able to:
• Be aware of SAP NetWeaver PI specific administrative tasks
• Name the tools used for SAP NetWeaver PI system configuration and maintenance tasks
• Be able to select the appropriate tool for a certain administration task
Business Example
A SAP NetWeaver PI system has recently been installed in the system landscape of your company. You, as a system administrator, want to know which additional SAP NetWeaver PI relevant tasks are needed.
And you are interested to know which tools are available for system maintenance and operational tasks, and you want to know which tools are necessary for what type of task.
Overview of Administrative Tasks
We assume that your SAP NetWeaver PI 7.1 system is installed and configured based on the necessary Post Installation tasks. Information about operation tasks and descriptions is rovided by SAP in the the Technical Operations Manual (TOM) that can be accessed in the SAP library at http://help.sap.com/saphelp_nwpi71/help-data/en/45/dc863f455f3417e10000000a114084/frameset.htm.
A dedicated section is available for PI specific tasks at http://help.sap.com/saphelp_nwpi71/help-data/en/57/08bb3f23823c17e10000000a114084/frameset.htm • Monitoring Tasks – Component Monitoring – Performance Monitoring • System Management Tasks
– Starting and Stopping of System(s) , Instances, and failing messages – Backup and Restore
– Archiving and Deletion of Messages • Troubleshooting PI Messaging
– Error Detection – Error Resolution • Software Logistic
– Release and Upgrade management – Transport and Change management
For monitoring, archiving and deletion of messages, troubleshooting and software logistics we have dedicated units to come. In this unit we will introduce shortly the available operation relevant tools and provide you with an basic understanding of which tasks should be considered on a daily, weekly or only if necessary activity to be covered by our SAP NetWeaver PI operations organization.
Introduction - SAP NetWeaver PI Tools
The SAP NetWeaver PI tools page provides a central entry point to access the several components of the SAP NetWeaver PI system:
Figure 17: SAP NetWeaver PI Tools Startscreen
• Enterprise Services Builder and the Services Registry (accessed using the Enterprise Services Repository)
• The Integration Builder (accessed using the Integration Directory) • The System Landscape Directory
• The SAP NetWeaver PI Monitor (Link: NetWeaver Administrator) and Runtime Workbench
To access the SAP NetWeaver PI tools, you can use transaction SXMB_IFR from the SAP GUI. Alternatively, you can navigate in a browser window directly to the URL http://hostname:port/dir/start/index.jsp. In this case, hostname is the fully-qualified name of the Integration Server, and port refers to the http port of the address of the Integration Server (ICM).
To access the Java components for NetWeaver SAP NetWeaver PI 7.1, you need an SDK (Java 2 Software Development Kit), version 1.5 or higher, on the front end. The SDK installation includes the installation of Java Web Start (JWS). JWS is a caching application for fat Java clients. The Enterprise Services Builder and the Integration Builder applications are each approximately 20-30 MB in size, therefore they have to be cached in the local machine's memory, to prevent them from being downloaded every time they are called.
The following figure gives an overview of the components accessed through the SAP NetWeaver PI tools.
Figure 18: Components Directly Accessible Through the Start Screen
Enterprise Services Builder
The Enterprise Services Builder is a Java application that is used to design and edit SOA objects, such as models, interface services.
Figure 19: Enterprise Services Builder Gives Access to the Enterprise Service Repository
The Enterprise Services Builder provides the tool for the design time SAP NetWeaver Process Integration. Its capabilities include:
• Navigation and object handling • Drag&Drop editing
• Versioning and history • Selection (F4) help
• Un-docking and docking of editors • Editing documentation
• Importing and exporting objects
Changes are saved locally to user-specific change lists. Upon activation of the change list, an activation check is performed and, if passed, the objects are created in their active version on the Integration Server, and the cache of the Integration Server is updated.
The ES Repository provides a comprehensive metadata repository that can be used for SOA provisioning. Objects in the ES Repository include:
• Integration scenarios • Process component models
• Service interfaces (Enterprise Services)
• Global data types (based on core component technical specification) • Interface mappings
Figure 20: Enterprise Services Repository - Objects
Services Registry
A registry is usually identified as one of the first requirements of SOA adoption, and registries play an important role in governance. In simple terms, a registry is a catalog or index that acts as the “system of record” for the services within an SOA. A registry is not designed to store the services themselves; rather, it indicates their location by reference.
Having a centralized catalog of services is significant from an organizational perspective because it enables the easy discovery, reuse, and management of services.
Figure 21: The Service Registry Start Page
Registry capability adds location information to the Enterprise Services Repository necessary for consumption (UDDI standard). A single source for discovery enables simple mass configuration and runtime governance. The taxonomy puts services in a business context.
There are two communication scenarios: P2P and brokered communication P2P is used if services within backends can communicate directly; if additional integration services are required, then brokered communication through the SAP NetWeaver PI Runtime (Integration Server) is used. For all service related communications the same Service Runtime is used.
The Service Registry can be accessed through the SAP NetWeaver PI Tools start page or directly by calling http://<full qualified hostname>:<HTTP port>/sr.
Integration Builder
The Integration Directory is accessed by means of the Integration Builder, which is used for carrying out configuration time activities. It has the same look and feel as the Enterprise Services Builder.
Figure 22: The Integration Directory in the Component View of SAP NW SAP NetWeaver PI
The Integration Builder is used to access configuration objects in the SAP NetWeaver PI system. Configuration time activities are always carried out within a specific system landscape of the customer environment. This is the reason why the Integration Builder is used solely at customer site.
Central Tools
While the SAP NetWeaver Administrator covers the configuration and monitoring aspects of the overall system, there is a specific area that addresses the special requirements of the process and integration environment.
The SAP NetWeaver Administrator for PI tool (NWAPI) covers the special requirements of the SAP NetWeaver Process Integration, e.g. messages, adapters, etc. It is a central monitoring tool for SAP NetWeaver PI landscapes using the SAP NetWeaver Administrator framework.
This tool is set out to replace the Runtime Workbench (RWB). Since the release of SAP NetWeaver 7.1 SP03 key functionalities of the RWB have been made available in NWAPI.
Note: The Usage of NWAPI is currently not recommend (SAP NetWeaver PI 7.1).
There is a usage limitation on NWAPI -check out SAP Note 100417 for latest changes.
The following are the main functionalities available in SAP NetWeaver Administrator for PI:
• Message monitoring • Performance monitoring • Cache monitoring • Alert inbox/rules • End-to-end monitoring • Adapter monitoring
• Communication channel monitoring (Adapter Engine) • Sequence monitoring
• Web service logging and tracing
It can be reached through the SAP NetWeaver PI tools start page or directly by calling http://<full qualified hostname>:<HTTP port>/nwapi.
Figure 23: SAP NetWeaver Administrator for PI
Note: Here we solely describe the NWAPI, as it is a tool specific for the SAP NetWeaver Process Integration. We describe the SAP NetWeaver Administrator as the more general tool for administration in the following lesson.
Before you can use the SAP NetWeaver Administrator for PI, some configuration settings need to be performed. The SLD must contain the systems and
components, basic CCMS configurations must exist in your system landscape. Further configuration is done with the help of the SAP NetWeaver Administrator Configuration Wizard.
The administrator has to execute the configuration template from: SAP NetWeaver
Administrator→ Configuration Management → Scenarios → Configuration Wizard
The exact configuration steps can be found under SAP NetWeaver Process
Integration Library→ Administrator's Guide → Configuration of SAP NetWeaver
→ Configuration of SAP NetWeaver Systems → AS Java Configuration →
Configuration Wizard→ Wizard-Based Configuration of the NWA → Configuring the Central NWA.
SAP Notes 1122868, 1160261 and 1115280 include more details about the necessary configuration steps to run the SAP NetWeaver Administrator for PI. We recommend to wait until official release of NWA for PI (currently planned with SAP NetWeaver PI 7.1 enhancement package 1 earliest).
Figure 24: Execute Configuration Wizard Templates to Setup the SAP NetWeaver Administrator for PI Monitor
The Runtime Workbench is still available through the start page and currently contains functionality, that is now yet available with NWAPI. It is mentioned here to underline that both the NWAPI and the RWB address an mostly equal set of functionalities, but the focus will be set on NWAPI for administration purposes in upcoming SPs of SAP NetWeaver PI.
Figure 25: The Runtime Workbench (RWB)
Further Tools and Configuration Components
There are various components of the SAP NetWeaver PI that are not or not fully covered by the central tools. Several tools are available to access these components.The System Landscape Directory is a central repository of information about software and systems in the data center called the Common Information Model (CIM).
Figure 26: System Landscape Directory Start Screen
The Exchange Profile is an XML document that is stored in the main database of the SAP NetWeaver Process Integration. The parameters contained in this document define some basic technical settings. Most of them are initialized automatically during the installation phase, but in some cases the administrator may need to maintain them.
The SAP NetWeaver PI provides a maintenance interface for this file. The maintenance screen for the Exchange Profile can be accessed at:
SAP NetWeaver PI Tools page→ Administration → Repository Tab; Properties Administration→ Exchange Profile.
Settings that are maintained in the Exchange Profile include connection parameters such as hostnames, ports, users, and passwords that allow the various components of the SAP NetWeaver PI to communicate.
Figure 27: Exchange Profile maintenance interface
The Integration Server is used primarily to process XI messages. The Integration Engine is the runtime engine for XI messages. The Integration Engine processes messages that are rendered in the special XI-SOAP format.
It is important to distinguish between the terms Integration Engine and Integration Server. The Integration Engine running on the central Process Integration system is configured as the Integration Server. The other Integration Engines running on different Application Systems are acting as clients communicating with the Integration Server with XI messages.
Figure 28: Integration Server Components
Transaction SXMB_ADM is the entry transaction to various configuration and administration possibilities.
Figure 29: SXMB_ADM for Integration Server and Application System
Here, the port above refers to the http port of the Internet Communication Manager (ICM) of the AS. To find out the number of this port, go to transaction SMICM and choose Goto→ Services (or press Shift-F1).
With SAP NetWeaver PI 7.1 the ICM takes over the role of the Java Dispatcher know in 6.40 and 7.0. In SAP NetWeaver PI 7.1 only the ICM HTTP port is used to access both stacks.
The query string at the end of the URL would be different for other pipeline entry points. For instance, if a document was sent from the Integration Server to the pipeline on an Application System, the URL would be http://<full qualified hostname>:<HTTP port>/sap/xi/engine?type=receiver.
Figure 30: Transaction SICF and SMICM
Configuration objects from the Integration Directory are cached at the Web Application Server for fast access at runtime. The cache can be viewed and managed in transaction SXI_CACHE. A cache refresh (either a delta or a full refresh) can be started inside this transaction.
Connection data for configured Adapter Engines are also cached. To see this information, call transaction SXI_CACHE, choose Goto→ Adapter Engine
Cache.
In an productive system a manual intervention of a explicitly started cache refresh should not be necessary. Only in emergency situations a cache refresh might be requested by SAP support.
Figure 31: Transaction SXI_CACHE
Out of the PI configuration tools page (http://<full qualified hostname>:<HTTP port>/dir) the cache status can be checked by selecting Administration and selecting the tab Repository or Directoryand navigating down to Lock and Cache
Administration→ Data Cache Overview.
For general administration purposes, further tools are used. There may be tasks such as adding or deleting of additional server processes. The configuration of thread pool sizes and thresholds are examples of advanced administration tasks.
Figure 32: SAP AS Java: Config Tool and Telnet Console
The main tools for these basis administration and configuration tasks on operating system and database level are the Config Tool and the Telnet Console. The Config Tool is a Java application that has to be started locally on the host of the SAP NetWeaver PI system. The Telnet Console is a connection via the telnet protocol accessing the Java Application Server on port 5XX08 (XX has to be filled in wit the system number). In the figure above, you can see screenshots of these tools. These are mentioned for reasons of completeness. For a detailed explanation of these tools, refer to course ADM200 Administration AS Java.
For system oriented operation the SAP Management Console (SAP MC) provides a common framework for centralized system management. It allows you to monitor and perform basic administration tasks on the SAP system centrally, thus simplifying system administration. Starting with SAP NetWeaver 7.1 the SAP MC is available as a Java applet that can be run from any Web browser supporting Java. Thus, you can administer remote systems without needing a local installation. To be able to start the SAP MC applet make sure that you have fulfilled the following requirements:
• You have Java Runtime Environment (JRE) 1.4.2 or higher installed. • Your Web browser supports Java.
In your Web browser, execute the following URL: http://hostname:5xx13. For example, if the instance number is 60, in this case the port is 56013. This starts the SAP MC Java applet.
Figure 33: SAP Management Console - Java Applet
Exercise 2: SAP NetWeaver PI Operation
Tasks and Tools
Exercise Objectives
After completing this exercise, you will be able to:
• get familiar with the NetWeaver Administrator for PI • start up the SAP Management Console
• check the CIM model version and the CR version on your SLD
• check the existing parameters of category MONITOR - Integration Engine Configuration
Business Example
Get familiar with various tools.Task:
[Enter a high level description of the task the learner will perform in this exercise.] 1. Start the NetWeaver Administrator for PI from the Tools page nad browse
around.
2. Start the NetWeaver Administrator for PI directly in the Internet Browser via suffix /nwapi.
3. Start the SAP Management Console for stack administration of the training system.
4. Open the SLD and navigate to the Administration part to check which CIM model version and CR versionl is installed on the SLD assigned to the training system.
5. Check with transaction SXMB_ADM the Integration Engine Configuration - Category MONITOR.
Solution 2: SAP NetWeaver PI Operation
Tasks and Tools
Task:
[Enter a high level description of the task the learner will perform in this exercise.] 1. Start the NetWeaver Administrator for PI from the Tools page nad browse
around.
a) Logon via SAPGUI to the training system and call transaction SXMB_IFR. Start NetWeaver Administrator under Configuration and
Monitoring.
2. Start the NetWeaver Administrator for PI directly in the Internet Browser via suffix /nwapi.
a) URL: http://<full qualified hostname>:<HTTP port>/nwapi
3. Start the SAP Management Console for stack administration of the training system.
a) URL: http://<full qualified hostname>:5xx13 with xx = Instance Number.
4. Open the SLD and navigate to the Administration part to check which CIM model version and CR versionl is installed on the SLD assigned to the training system.
a) Logon via SAPGUI to the training system and call transaction SXMB_IFR. Start System Landscape Directory under System
Landscape. . Alternative you can call the URL with suffix /sld directly.
Goto Administration.Select Server→ Details.Select tab Data. Here you will find the Model Version (3.1.4) and the CR content version (1.5.32 and SAP_CR 4.3)
5. Check with transaction SXMB_ADM the Integration Engine Configuration - Category MONITOR.
a) Logon via SAPGUI to the training system and call transaction SXMB_ADM. Select Integration Engine Configuration. Choose category MONITOR and press button Configuration.
Check the existing entries and get familiar with the available parameter information by pressing the in front of the parameter. Check the possible values for the parameters.
Lesson Summary
You should now be able to:• Be aware of SAP NetWeaver PI specific administrative tasks
• Name the tools used for SAP NetWeaver PI system configuration and maintenance tasks
• Be able to select the appropriate tool for a certain administration task
Lesson: Administration of SAP NetWeaver PI
Components
Lesson Overview
This lesson gives you the knowledge of the components, tools and the specific tasks which are part of PI administration.
Lesson Objectives
After completing this lesson, you will be able to:
• Describe which parts of an SAP NetWeaver PI system need to be administered
• List the administration tasks in the SAP NetWeaver PI system
Business Example
There are several components of a PI system that require administration. As a system administrator you need to have an understanding of these components and the tasks to be performed.
Administration with the SAP NetWeaver Administrator
SAP NetWeaver Administrator (NWA) is a tool for administration and monitoring. The NWA combines the most important administration and monitoring tools for Java and ABAP systems in a browser-based user interface.You can start the NWA using the following URL: http://<full qualified hostname>:<HTTP port>/nwa
Figure 34: SAP NetWeaver Administrator The NWA categorizes following features: • Administration
Starting and stopping systems, instances, services, and applications User administration
• Technical Configuration • Monitoring
System and Component Monitoring Log information
• System Analysis
Performance analysis
Application trace and performance trace
The NWA is used to administer one particular system and is therefore bound to a certain host.
Note: The current version of the NWA does not allow the administration of ABAP systems.
The monitoring functions can be used for ABAP and Java systems.
The interface allows for the seamless navigation to other SAP NetWeaver administration tools (User Management Engine, also System Landscape Directory and Adaptive Computing).
The management functions included in the SAP NetWeaver Administrator are grouped in work centers according to the type of functionality that they provide. The following work centers (represented as tabs) are available:
• Operation management • Configuration management
• Availability and Performance Management • Problem management
• SOA management
In the Operation Management work center, the following functions are available:
Users and Access (Identity Management)
Systems (instance information display, start and stop functions) Data and Databases (Java Archiving tasks)
Jobs (Access to the Java Scheduler)
The Configuration Management work center includes the following options for configuring your system:
Virtual Host Configuration (create new virtual hosts and configure existing ones for your system)
Managing Login Modules
Managing Authentication Policy for AS Java
JMS Server Configuration (view and manage JMS provider server configurations)
Java System Properties (view the system properties)
Viewing Application Modules’ Configuration (contains details of the deployed applications and modules)
Application Resources Management (create and configure Application resources)
UDDI Server Configuration
Web Services Configuration (information about the configuration of Web services and Web service clients)
Figure 35: NWA Operation Management & Configuration Management
In the Availability and Performance Management area in the NWA, you can monitor different system information relevant for the system operation.
• Java System Reports • Log Viewer
• Locks
The Problem Management section of the NWA includes the following administration options:
• Java Class Loader Viewer • JNDI Browser
• Log Viewer
For systems 7.1, you can use the SAP Host Control Agent. It gives you the ability to:
View ABAP log messages Manage with debugging
Control the amount of displayed log data Filter and view logs and traces
Search log and trace records
Merge list-formatted logs and traces View archives of logs and traces
Create your own custom views to view a certain set of log records Import and export custom views
• Log Configuration
In the SOA Management section the following features can be found: • Destination Template Management
• Mass Configuration
• Services Registry Configuration • Profile Management
• System Global Settings
• Business Administration Mass Configuration • Web Services Administration
• Publication Restrictions
• Web Services Logging & Tracing • PI Adapter Monitoring
• PI Message Monitoring
• PI Background Processing (for the Adapter Engine only) • Sequence Monitoring
Figure 36: NWA Availability and Performance Management, Problem Management & SOA Management
User Administration and Authentication
All components of SAP NetWeaver PI that run on the Application Server use the underlying infrastructure provided by the SAP NetWeaver AS for the following: • User management
• Administration • Authorizations • Authentication
The only exception may be adapters on the J2SE based Adapter Engine. User Store
Users are maintained in the ABAP user store. This can also be integrated with LDAP-based user administration. Each SAP NetWeaver PI component that resides on an SAP NetWeaver AS refers to the user management of the ABAP part of this SAP AS. PI Java applications running on an SAP AS authenticate against the users maintained in the ABAP part. This is the standard case for SAP NetWeaver PI. Certificate Store
XI and RNIF protocols support message level security-based on digital signature. The RNIF protocol also supports encryption. The required certificates to be used need to be entered into the key store of the AS Java engine. In
the Integration Directory these certificates are referred by the name of the key store view and the certificate name. It is recommended to store CA certificates in the TrustedCAs view.
SAP NetWeaver PI makes use of the Application Server Add-In Installation User Concept. Application Server Java uses one client of its AS ABAP as its user master. This means for the user concept of SAP NetWeaver PI: Roles defined in AS ABAP are available as Groups in AS Java. The authorization concept of AS Java components within SAP NetWeaver PI is based on AS ABAP roles.
Figure 37: Application Server Add-In Installation User Concept
Dialog Users Roles
Each dialog user role has authorizations for multiple components of SAP NetWeaver usage type PI. The roles contain task specific authorizations and they all contain at least display authorizations in all PI components.
The following dialog user roles are provided: • SAP_XI_DISPLAY_USER • SAP_XI_SUPPORT • SAP_XI_DEVELOPER • SAP_XI_CONFIGURATOR • SAP_XI_CONTENT_ORGANIZER • SAP_XI_MONITOR • SAP_XI_MONITOR_ENHANCED • SAP_XI_ADMINISTRATOR • SAP_SLD_ADMINISTRATOR • SAP_SLD_CONFIGURATOR
To make changes to authorizations on the ABAP side, proceed as follows for each dialog user role:
1. Call transaction PFCG
2. Copy the single role SAP_XI_ -ROLE- _ABAP into the customer namespace (replace the prefix SAP)
3. Create a new composite role in the customer namespace (for example, *_XI_ -ROLE-)
4. Assign the new single role (suffix _ABAP) to the new composite role 5. Assign the new SAP single role (suffix _J2EE) to the new composite role 6. Make changes to the new single role (suffix _ABAP)
7. Generate an authorization profile for the new single role (suffix _ABAP) Service User for Communication
User and connection for internal communication are read from the Exchange Profile. Therefore, changes to the Service Users also have to be reflected in the Exchange profile if used there. Users for external communication (system user) must have role SAP_XI_APPL_SERV_USER. External communication means
external from a Process Integration point of view. Users for external
communication should not be service or dialog users, because these users could be used to log on to PI in dialog mode.
For each connected application system create a copy of a system user to send messages to the Integration Server. It is recommended to use the PIAPPLUSER as a template for that purpose.
