PIADMINI

Confidential | Copyright © Larsen & Toubro Infotech Ltd.

PI Administration

16 Jul 2012

Confidential | Copyright © Larsen & Toubro Infotech Ltd. 2

Contents

Overview Technical System Landscape Administration Monitoring Runtime Workbench Management Administering the Business Process Engine Performance Optimization Measures Archiving and Deletion Procedure Cache Handling Troubleshooting


Overview

SAP NetWeaver Process Integration (SAP NetWeaver PI) is used as follows:

● The architecture of SAP NetWeaver PI 7.1 is based on an established architecture for realizing cross-system business processes, and is the same as in lower 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 enterprise service-oriented architecture (Enterprise SOA). The focus is on the service-based integration of applications.

SAP NetWeaver PI is based on general standards so as to enable 3rd-party systems to be integrated. At the center of SAP NetWeaver PI is an XML-based communication that uses HTTP (Hyper Text Transfer Protocol). Irrespective of the scenario used, the application-specific contents are transferred in messages in user-defined XML (eXtensible Markup Language) from the sender to the receiver either via the Integration Server, or directly between the systems involved.


Technical System Landscape


Administration

The tasks to be performed for the administration of a PI environment can be grouped as follows:MonitoringThis section provides information about the monitoring of your system landscape.ManagementThis section provides information about additional maintenance tasks to be performed during operation, for example, starting and stopping systems and instances, logging and tracing, backup and restore, and so on.Software logisticsThis section provides information about release and upgrade management, transport and change management, and software maintenance.TroubleshootingThis section provides information about how to handle problems and error situations.

http://help.sap.com/saphelp_nwpi711/helpdata/en/48/aeb1925bb5356be10000000a421937/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/48/aeb19b5bb5356be10000000a421937/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/48/aeb18f5bb5356be10000000a421937/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/48/aeb1805bb5356be10000000a421937/content.htm


Monitoring

Any scenario based on SAP NetWeaver PI can be monitored using the SAP NetWeaver standard monitoring solutions CCMS (Computing Center Management System) and SAP NetWeaver Administrator.SAP NetWeaver Administrator offers an entry point for PI monitoring purposes. The following monitoring functions are supported:

Component monitoring

Message monitoring

Performance monitoring

Adapter Engine status monitoring

Communication channel monitoring

JPR monitoring

Cache monitoring

Alert configuration


Monitoring Requirement

Following parameters must be activated in Exchange ProfileCom.sap.aii.rwb.server.centralmonitoring.r3.aashostCom.sap.aii.rwb.server.centralmonitoring.r3.clientCom.sap.aii.rwb.server.centralmonitoring.r3.sysnrCom.sap.aii.rwb.server.centralmonitoring.r3.httpport

For technical user PIRWBUSER detailsCom.sap.aii.rwb.serviceuser.nameCom.sap.aii.rwb.serviceuser.pwdCom.sap.aii.rwb.serviceuser.language

For END-to-End monitoring and alert monitoring, we need to activate SICF services.Execute report RSXMB_ACTIVATE_SICF_SERVICES


Monitoring Tools

SAP NetWeaver Administrator (local)Entry point for monitoring your local SAP NetWeaver system. Can be

accessed at http://<host>:<port>/nwa.

Runtime Workbench (RWB)Entry point for PI monitoring purposes. Can be accessed from the PI

Tools start page or at http://<host>:<port>/rwb.

Computing Center Management System (CCMS)

Transaction SXMB_MONIAdditional monitoring functions for the Integration Engine to be accessed from your SAP Easy Access menu under Process Integration Monitoring Integration Engine −Monitoring .

Transaction SXMB_MONI_BPEAdditional monitoring functions for the Business Process Engine (BPE) to be accessed from your SAP Easy Access menu under Process Integration Monitoring Process Engine −Monitoring .


Runtime Workbench

Runtime Workbench as a tool for monitoring an individual PI installation. The Runtime Workbench runs on the Integration Server, and allows the monitoring of distributed PI components, such as local Advanced Adapter Engines or proxy runtimes from SAP business systems.You can start the Runtime Workbench from the PI start page of your Integration Server (http://<host>:<port>/dir) under Configuration and Monitoring Runtime Workbench.

You have the following options in PI monitoring: Component Monitoring Message Monitoring End-to-End Monitoring und Configuration Performance Monitoring Index Administration SLD Registration Alert Configuration and Alert Inbox Cache Monitoring


RWB – Component Monitoring

PurposeYou use component monitoring in the following cases:● To get an overview of the status of the individual PI components● To call the configuration data of individual components● To use test messages to check whether the runtime components are functioning correctly● To test whether cache connectivity is functioning correctly● To archive the Message Security Settings or Whole Messages● To check the status of your communication channels or the Java Proxy Runtime configured in them.● To display current technical data for your Adapter Engine● If you want to prioritize message processing on your Adapter Engine.

You use the Runtime Workbench to display and monitor the following components:● Integration Server including the Integration Engine (central), Business Process Engine, Mapping Runtime, Adapter Engine (central)● ABAB proxy systems (business systems with an Integration Engine)● Non-central Adapter Engines● Java SE Adapter● System Landscape Directory● Integration Directory● Enterprise Services Repository● The Runtime Workbench itself


RWB - Communication Channel Monitoring

PurposeYou use the communication channel monitor to call information about communication channels that are set up for the selected Adapter Engine, and to administrate these channels.

If you are running the Adapter Engine on a server cluster, the communication channels comprise multiple instances for the various cluster nodes.

You have started the Runtime Workbench, are in component monitoring, and have selected an Adapter Engine as the component. On the Status tab page, you have chosen Communication Channel Monitoring to call the communication channel monitor.

Important Column DescriptionStatus - Status of the communication channel. The following statuses are possible:

Green (): Channel is started and functioning without errors.Red (): Channel is started but errors have occurred.Yellow (): Channel is started, but inactive.Grey (): Channel is stopped.Not available (remove): Adapter is not registered; no information about

channel.Control - Displays how the communication channel is controlled.

Manual - You control the communication channel by choosing Start or Stop.Automatic - The communication channel is controlled by availability times.External - The communication channel is controlled by an HTTP request.

Processing Errors (not displayed as default)

http://help.sap.com/saphelp_nwpi711/helpdata/en/7a/1268c12feb5146a4430552bf478f30/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/45/06bd029da31122e10000000a11466f/content.htm


RWB - Message Monitoring

PurposeYou use message monitoring in the following cases: To track the status of messages

To find errors that have occurred and establish what caused themThe central message-monitoring tool is the Runtime Workbench. You can also run message monitoring by using Integration Engine monitoring (transaction SXMB_MONI), which you can call from your SAP Easy Access user menu.

Message monitoring enables you to use the following functions:· Display and manage messages· Displaying the Message Overview· Searching for messages using an index.· Filter the displayed messages by specific criteria· Configure the message display· Edit messages.

http://help.sap.com/saphelp_nwpi711/helpdata/en/7a/1268c12feb5146a4430552bf478f30/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/41/b715045ffc11d5b3ea0050da403d6a/frameset.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/88/09dd6970a8f34d9a1747b342af9991/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/45/d48d3d81eb4a88e10000000a155369/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/43/60359ae92f5f87e10000000a1553f6/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/17/f19f3f12e1eb0ce10000000a114084/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/ef/c79e3f60f13c17e10000000a114084/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/44/f5c3de84056c30e10000000a114a6b/content.htm


RWB - Performance Monitoring

PurposeYou use performance monitoring to display statistical data on the performance of message processing. The data comes from the Integration Server (IS) or the Process Monitoring Infrastructure (PMI).

Process FlowUse performance monitoring to display the following data:● Aggregated overview data for message processing● Individual overview data for message processing● Aggregated detailed data for message processing performance● Individual detailed data for message processing performanceUse selection criteria to restrict the data that is displayed. For example, you can restrict the data to:● The data source● A specific component● A message processing mode● A specific time interval

Note - The system only displays messages that are processed successfully within the specified time interval.

http://help.sap.com/saphelp_nwpi711/helpdata/en/c3/2f90980e309d4e9fcaa5bb20ff479a/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/a8/a81b0b6473cb49bc34effad6eab13b/frameset.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/c8/7ecc3fbeb83946e10000000a114084/content.htm

http://help.sap.com/saphelp_nwpi711/helpdata/en/4c/2fb4409dbba461e10000000a155106/content.htm


RWB -Cache Monitoring

PurposeCache monitoring displays objects that are currently in the runtime cache of either of the following receivers (cache instances) of cache data:● Integration Server (ABAP Cache)● Adapter Engine (Central and Local)● Mapping Runtime Cache (Adapter Engines)● Business Systems (with Web Service Communication)

Process FlowIn cache monitoring, different cache objects are monitored depending on the cache instance concerned. Selection criteria are available for each cache object; you can use these selection criteria to search for current objects in the runtime cache.A table of hits is displayed. The content of this table varies depending on the cache object you have selected. For most cache objects, you can display details for individual hits from the hit list. To do this, select the radio button in the first column of the relevant line. Regardless of which cache object you select, you always have the option of calling a Notification Table that displays information about runtime cache updates and any problems that arose.A Status Table lets you display the status of the last cache update for each cache instance.


Process Integration – Management

The management of SAP NetWeaver PI includes various aspects:

User ManagementStarting and StoppingLogging and TracingExchange Profile MaintenanceData ArchivingBackup/Restore and RecoveryPeriodical Tasks


Management - User Management


Management - Starting and Stopping


Management - Logging and Tracing

Components Based on AS ABAPThe Integration Engine uses logging and tracing to log and analyze the processing steps of messages.While a message is being processed by the pipeline of the Integration Engine, the current status of the message is logged as a separate message version (log version).Traces in XML format are attached to the message and the entire message is saved (persisted) in the database. No message data is persisted in the file system.You can view message log versions and traces by using the message monitor of the Integration Engine.

Components Based on AS JavaThe Java-based parts all use the standard logging of AS Java. This can be configured by using the log configuration function of the SAP NetWeaver Administrator under Problem Management Logs and Traces Log Configuration (alias: /nwa/log-config).On the Integration Server host (Enterprise Services Repository and Integration Directory may be installed on another server), <Javadir> stands for the following in the table below (where n specifies the number of cluster nodes):/usr/sap/<SAPSID>/<instance_name>/j2ee/cluster/server<n>


Management - Logging and Tracing – Part 2

Tracing is activated by default. To change the preset trace level, perform the following steps:•Call Log Configuration.•Show the Tracing Locations.•Select a location (say com.sap.aii.*).•Change the Severity to the required value.

Logging is activated by default. To change the preset log level, perform the following steps:•Call the Log Configuration.•Show the Logging Categories.•Choose ROOT CATEGORY -> Applications -> Exchange Infrastructure -> Adapter or Adapter Framework.•Navigate to the required category and choose it.•Change the Severity to the required value.

Old logs are compressed (zipped up) to save disk space. By default, logs are written to a maximum of five files with 10 MB capacity of each file. Thus, when this set of five files is full, the system rotates back to the first file and starts overwriting the old logs. Before overwriting the old logs, the log configuration function backs up the five files into a zip file. So, each zip file contains a set of five log files. The logs within these zip files are called archive logs.You can view traces, log files, and archive logs by using the log viewer function of the SAP NetWeaver Administrator under Problem Management Logs and Traces Log Viewer (alias: /nwa/logs).


Management - Exchange Profile Maintenance

The exchange profile is an XML document with parameters that define certain basic technical settings. Most of them are initialized automatically during the installation phase, but in some cases the administrator may need to maintain them. You can access the maintenance screen at:

http://<host:port>/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp

In this HTTP address, host and port are the host name and connection port of your Integration Server.You are prompted for a user name and a password. A user with the AS Java security role administer is required. By default this role is mapped to role SAP_XI_ADMINISTRATOR_J2EE of AS ABAP.

The HTTP address provides you with a browser-based interface for editing the exchange profile.


Management - Periodical Tasks


Management - Periodical Tasks (2)

Management - Periodical Tasks (3)


Process Integration – Administering the Business Process Engine


The administration of the BPE comprises the following tasks:

● Starting and Stopping the BPEYou can start or stop the BPE, or determine its status by using a transaction SWF_XI_ADM_BPE.

● Setting Up Error Notifications for AdministratorsYou can specify that an administrator is to receive a message when an integration process has an error status. The administrator receives the message in the workflow inbox of SAP Business Workplace. You can specify that the system is to forward the message to an e-mail address for the user.

● Deleting Process Data No Longer RequiredYou can use a report RSWF_XI_INSTANCES_DELETE to delete process data that is no longer required. This enables you to release the occupied memory. Execute this report regularly to reduce the amount of memory required.Execute the RSWF_XI_INSTANCES_SHOW report to determine which data is deletable.

Process Integration – Performance Optimization Measures


RFC Quota on R/3 side

Jco Service Provider

Gateway Parameters

PI – Integration Engine – Tuning CategoryEO_INBOUND_PARALLELEO_INBOUND_PARALLEL_SENDEREO_INBOUND_TO_OUTBOUNDEO_OUTBOUND_PARALLELIS_RETRY_LIMITEO_MSG_SIZE_LIMITEO_MSG_SIZE_LIMIT_PARALLELB_EO_IN_PARALLELB_EO_OUT_PARALLELB_EO_IN_PARALLEL_SENDERBALANCING

Process Integration – Performance Optimization Measures


PI – Integration Engine – Runtime CategoryENGINE_TYPEHTTP_TIMEOUTERROR_ON_NO_RECV_FOUNDACK_YSTEM_FAILURECACHE_DIRTY_READCACHE_REFRESH_PACKAGE_SIZEENTRY_LOCKLOGGINGLOGGING_SYNCTRACE_LEVEL

Parameter Settings on J2EE sideJ2EE application ThreadManagerTuning the JAVA VM

Process Integration – Archiving and Deletion Procedure


Archiving – Transaction SXMB_ADMPERSIST_DURATIONARCHIVE_PARALLELPERSIST_ARCH_MANUAL_CHANGES

Deletion Procedure – Transaction SXMB_ADMPERSIST_DURATIONPERSIST_HISTORYPERSIST_DURATION_ERRORDROP_MAX_TABLE_LOADROWS_PER_LOOP

Process Integration – Cache Handling


CPA Cache:For complete cache refresh – http://<hostname>:<port>/CPACache/refresh?mode=full

For delta cache refresh – http://<hostname>:<port>/CPACache/refresh?mode=delta

Process Integration - Problem Analysis for the Enterprise Services Repository (ESR) and Integration Directory


Starting the Tools (Java Web Start)To start the SAP NetWeaver PI tools, Java Web Start must be installed on the clientPC. Enterprise Services Builder and Integration Builder run on top of Java™ 2Standard Edition 5.0 (J2SE 5.0), which includes Java™ Webstart. Refer SAP note 801868 for more information.

Memory LogIf problems occur in the PI tools, you can use the memory log for further problemanalysis. Use the memory log only if you are able to reproduce the problem, becausethe log in the browser is overwritten after 1000 lines.

To increase the trace level or view the trace, use the following URL:Integration Directory: http://server:port/dir/support/private/index.htmlEnterprise Services Repository: http://server:port/rep/support/private/index.html

Increase trace level - Edit Memory Log Configuration -> Reset to DEBUG -> SaveView Trace - View Memory Log

Note - Reset the log level to DEFAULT after your analysis and save to avoid performance problems.

Process Integration - Problem Analysis for the Enterprise Services Repository (ESR) and Integration Directory


Java LogsAll PI applications that run in the AS Java Engine write their logs to the AS JavaEngine logs.1 - applications.logAll error messages from Java applications are written to theapplications.<number>.log file. The file can be found in the file system under..j2ee\cluster\server<number>\log.To analyze the logs, use the LogViewer plug-in in the SAP NetWeaver Administrator(NWA).http://<server:port>/nwa -> Problem Management -> Logs and Traces -> Log Viewer

2 - Java defaultTrace.trcTo trace applications in the Java Engine, you can increase the trace level for aspecific PI application.To increase the trace level, call the SAP NetWeaver Administrator.http://<server:port>/nwa -> Problem Management -> Logs and Traces -> Log Configuration -> Show: Locations ->Select the location com -> sap -> aii -> ibdir (Integration Directory) or com -> sap -> aii -> ibrep (Enterprise Services Repository) -> Change the severity to DEBUG -> Choose Copy to Subtree -> Save the entry

Process Integration – ABAP Proxy Generation


Problem - You have problems during proxy generation and need more information about how to analyze these issues.

AnalysisIf you have problems during proxy generation, you can use the followingtools/transactions for initial checks and further analysis: Transaction SPROXYThe interfaces are taken from the Enterprise Services Repository of theconnected PI system. To make sure this connection is running correctly, usethe test reports provided in transaction SPROXY -> Connection Test button:

o Report SPROX_CHECK_IFR_ADDRESS checks whether the connection tothe exchange profile is running and whether the parameters are set.

o Report SPROX_CHECK_HTTP_COMMUNICATION checks whether theHTTP communication of the system is running.

o Report SPROX_CHECK_IFR_RESPONSE checks whether the connectionto the ES Builder is running correctly.

o Report SPROX_CHECK_IFR_CONNECTION checks whether the datacoming from the ES Builder can be correctly interpreted.

Administration Links


PIADMINI

Documents

Transcript of PIADMINI