NetWeaver 7.3.1 Process Integration Troubleshooting

NetWeaver 7.3.1 Process Integration Troubleshooting
SAP NetWeaver
Process Integration
Troubleshooting Guide
SAP NetWeaver 7.3
EHP 1
Document Version 2.00 – January 2012
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com
© Copyright 2011 SAP AG. All rights
reserved.
technology invented and implemented by
Netscape.
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.
MaxDB is a trademark of MySQL AB,
Sweden.
Some software products marketed by SAP
AG and its distributors contain proprietary
software components of other software
vendors.
Microsoft, Windows, Outlook, and
PowerPoint are registered trademarks of
Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2,
Parallel Sysplex, MVS/ESA, AIX, S/390,
AS/400, OS/390, OS/400, iSeries, pSeries,
xSeries, zSeries, z/OS, AFP, Intelligent
Miner, WebSphere, Netfinity, Tivoli, and
Informix are trademarks or registered
trademarks of IBM Corporation in the United
States and/or other countries.
Oracle is a registered trademark of Oracle
Corporation.
UNIX, X/Open, OSF/1, and Motif are
registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood,
MetaFrame, WinFrame, VideoFrame, and
MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C 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
SAP, R/3, mySAP, mySAP.com, xApps,
xApp, and other SAP products and services
mentioned herein as well as their respective
logos are trademarks or registered
trademarks of SAP AG in Germany and in
several other countries all over the world. All
other product and service names mentioned
are the trademarks of their respective
companies. Data contained in this document
serves informational purposes only. National
product specifications may vary.
These materials are subject to change
without notice. These materials are provided
by SAP AG and its affiliated companies
("SAP Group") for informational purposes
only, without representation or warranty of
any kind, and SAP Group shall not be liable
for errors or omissions with respect to the
materials. The only warranties for SAP
Group products and services are those that
are set forth in the express warranty
statements accompanying such products
and services, if any. Nothing herein should
be construed as constituting an additional
warranty.
Documentation in the SAP Service
Marketplace
You can find this documentation at the
following address:
http://service.sap.com/instguidesnw
(select release SAP NetWeaver 7.3)
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style
Example text
Description
Words or characters quoted from the screen. These include field
names, screen titles, pushbuttons labels, menu names, menu paths,
and menu options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, graphic titles, and table
titles.
EXAMPLE TEXT
Technical names of system objects. These include report names,
program names, transaction codes, table names, and key concepts of
a programming language when they are surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Output on the screen. This includes file and directory names and their
paths, messages, names of variables and parameters, source text,
and names of installation, upgrade and database tools.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Angle brackets indicate that you replace these
words and characters with appropriate entries to make entries in the
system.
EXAMPLE TEXT
Keys on the keyboard, for example, F2 or ENTER.
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
1 Introduction.................................................................................8
Updates ........................................................................................................... 8
Delta Information ............................................................................................ 8
Additional Information ................................................................................... 8
2 Installation, Patching, Update, and Upgrade ............................9
3 System Copy .............................................................................10
System Copy Information ............................................................................ 10
4 Advanced Adapter Engine Extended [AEX] ............................11
Differences to a full PI installation .............................................................. 11
Additional Information ................................................................................. 12
5 SOA Design and Configuration Tools .....................................13
Problem Analysis for the Enterprise Services Repository (ESR) and
Integration Directory .................................................................................... 13
Enterprise Services Repository .................................................................. 15
Integration Directory .................................................................................... 16
Services Registry ......................................................................................... 17
Web Services Configuration........................................................................ 57
Web Services Navigator (WS Navigator) .................................................... 60
6 Proxy .........................................................................................62
ABAP Proxy .................................................................................................. 62
Java Proxy Runtime (JPR) ........................................................................... 69
7 Adapters ....................................................................................70
Error Tracking in the Adapter Engine (Java SE) ........................................ 70
Error Tracking in the Adapter Engine (Java EE) ........................................ 72
PAS: Message Failed on the Adapter Engine ............................................ 75
FAQs about Adapters................................................................................... 80
IDoc Adapter (Advanced Adapter Engine) ................................................. 82
Attachment Support in Adapters ................................................................ 86
Message and Channel Monitoring in Adapter Framework........................ 87
Local Message Processing on the Advanced Adapter Engine ................ 94
Problems and Solutions .............................................................................. 95
IDoc Adapter ................................................................................................. 95
File Adapter ................................................................................................. 108
RFC Adapter ............................................................................................... 108
Plain HTTP Adapter .................................................................................... 111
Problems using Seeburger Adapters for SAP NetWeaver PI ................. 112
4
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Information About SAP Conversion Agent by Informatica ..................... 119
8 Runtime ................................................................................... 121
Demo Examples .......................................................................................... 121
PI Error Codes Information........................................................................ 121
Message Packaging ................................................................................... 122
XML Validation ............................................................................................ 123
Timeouts in PI ............................................................................................. 127
Code Pages in PI ........................................................................................ 133
Known Restrictions of EOIO ..................................................................... 133
EOIO Message Analysis............................................................................. 134
Acknowledgments Supported in Adapters .............................................. 137
PI Runtime................................................................................................... 141
Web Service Runtime ................................................................................. 147
Adapter Framework Runtime .................................................................... 147
Business Process Engine (BPE) Runtime................................................ 151
9 PI Communication ..................................................................160
Internal Communication ............................................................................ 160
Messaging Communication ....................................................................... 169
10
Caches ................................................................................. 173
Analysis of Cache Problems ..................................................................... 173
JAVA_CACHE ............................................................................................. 173
Problems and Solutions ............................................................................ 174
SXI_CACHE ................................................................................................. 175
11
Mapping ...............................................................................177
Error Analysis of Mapping Problems ....................................................... 177
PAS: Mapping Fails for a Specific Message Type ................................... 177
Error Analysis of Caching Problems for PI Mappings ............................ 202
Error Analysis of Encoding Problems within PI Mappings..................... 203
Error Analysis of Problems with Split and Merge Mappings .................. 206
Problems and Solutions ............................................................................ 212
Mapping as a service ................................................................................. 212
12
Monitoring ...........................................................................213
Central PI monitoring with SAP Solution Manager ................................. 213
Monitoring for Process Integration and Orchestration installation ....... 213
PI Monitors in SAP NetWeaver Administrator ......................................... 213
Monitoring with Runtime Workbench ....................................................... 221
User-defined message search................................................................... 223
Index-based message search using TREX............................................... 224
February 2011
5
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Component-based message alerting ........................................................ 224
Alert configuration using the Alert Framework ....................................... 224
13 SAP Partner Connectivity Kit (PCK)- not delivered with 7.3
EHP1 ............................................................................................. 226
14
Network................................................................................ 227
Timeouts in HTTP Communication ........................................................... 227
Network Aspects with PI ............................................................................ 229
15
Transport .............................................................................232
Software Logistics in PI ............................................................................. 232
Problems with Setting Up CMS ................................................................. 232
16
Archiving .............................................................................237
Troubleshooting Archiving ........................................................................ 237
17
System Landscape Directory (SLD) ...................................245
Troubleshooting the System Landscape Directory ................................. 245
Analysing SLD Self-Registration Problems ............................................. 246
Problems and Solutions ............................................................................ 252
18
AS Java ................................................................................ 256
How to Determine the AS Java Version and SP ...................................... 256
How to Determine the HTTP Port of the AS Java .................................... 256
AS Java Central Notes ............................................................................... 256
PI Services in AS Java ............................................................................... 257
AS Java Engine Clustering ........................................................................ 260
Using Full Thread or Heap Dump to Analyse AS Java Problems .......... 261
19
HA (High Availability) .......................................................... 263
HA (High Availability) Troubleshooting .................................................... 263
20
Security & User Management.............................................264
User Concepts ............................................................................................ 264
Security Aspects ........................................................................................ 267
21
PI Performance....................................................................272
How to Analyse Performance Issues on your PI System ........................ 272
PAS: PI Performance.................................................................................. 274
22
Integration of SAP Applications ........................................281
Information About Integration of SAP Applications ................................ 281
23
Appendix .............................................................................282
Useful Transactions for Troubleshooting ................................................ 282
6
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Logs and Traces ......................................................................................... 282
SAP NetWeaver Support Service .............................................................. 283
Checklist for Opening Customer Messages ............................................ 284
February 2011
7
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
1 Introduction
This guide helps you when analyzing problems associated with Process Integration
(PI). It describes where to find information in error situations and how to trace
problems. It covers troubleshooting information for the following releases of SAP
NetWeaver: SAP NetWeaver 7.3 including Enhancement Package 1 (EHP1)
The guide is also available via SAP Note 1665708 - PI Troubleshooting Guide 7.30
EHP1.
You can access the versions of guide for earlier releases as follows:

SAP NetWeaver 7.3: SAP Note 1452440 – PI Troubleshooting Guide 7.3

SAP NetWeaver PI 7.1 (including enhancement packages): SAP Note
1060264 - PI Troubleshooting Guide 7.1

SAP NetWeaver XI 3.0/7.0: SAP Note 806546 - XI 3.0/7.0: XI
Troubleshooting Guide

SAP NetWeaver XI 2.0: SAP Note 972663 - XI 2.0: XI Troubleshooting Guide
Updates
To find the newest troubleshooting information you can refer to the following section
on SAP Community Network: PI Troubleshooting Guide for 7.3.1
Delta Information
The current version of the PI Troubleshooting guide is based on the version for SAP
NetWeaver 7.3. It includes details specific for NetWeaver 7.3 EHP1 in the following
areas:

Process Integration and Orchestration

Component-based message alerting

IDoc Adapter for Advanced Adapter Engine

Mapping as a service

User-defined message search
Additional Information
The guide provides also the following details:
8

Overview of the information to provide when opening customer messages for
SAP; see the Checklist for Opening Customer Messages section.

Remote and onsite services offered by SAP: see the SAP NetWeaver
Support Service section.

The How-To Guides mentioned in this guide can be found using the following
link: http://service.sap.com/instguidesnw > SAP NetWeaver 7.3 >
Supplementary Information > How-To Guides.
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
2 Installation, Patching, Update, and Upgrade
Troubleshooting information for installation, patching, update, and upgrade would be
published in the following section on SAP Community Network:
PI Troubleshooting Guide for 7.3.1
February 2011
9
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
3 System Copy
System Copy Information
Problem
You need more information about the options available for copying PI systems.
Solution
System copy guides at http://service.sap.com/instguidesnw  SAP NetWeaver 7.3
 Installation  “ 2- Installation SAP NetWeaver Systems”  SAP NetWeaver 7.3 Installation Guides  choose the appropriate system copy guide
You can use the SAP NetWeaver system copy tools to copy your PI system. For
more information, see SAP Notes 1042437 - Hom./Het.System Copy for SAP
NetWeaver Based on Kernel 7.10 and 1259011 - Hom./Het.System Copy for SAP
NetWeaver based on Kernel 7.11.
Problem:
You are working with SAP NetWeaver PI and want to execute the "PI System Copy"
CTC Wizard after a System Copy
Solution:
See SAP Note 1299373 - Configuration Wizard: PI System Copy
10
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
4 Advanced Adapter Engine Extended [AEX]
The Advanced Adapter Engine Extended (AEX) is a new, Java-only installation option of PI
which was introduced with NetWeaver 7.30. It is based on the Advanced Adapter Engine
messaging runtime which is deployed together with an ESR and Integration Directory to form
a self-sufficient PI installation.
Note: Since the AEX is just a new combination of existing components, most of the existing
chapters in this guide also apply to trouble shooting in an AEX installation, but keep in mind
that AEX does not include any ABAP. Any ABAP-based hints or procedures (like transaction
“sxmb_moni” etc.) can be ignored in this case.
Some chapters which are useful for AEX:
6 – SOA Design and Configuration Tools
8 – Adapters (excluding ABAP-based adapters)
Adapter Framework Runtime
(Other chapters also contain information which may be relevant for AEX, but you should keep
in mind the differences between AEX and a full PI)
Differences to a full PI installation
The major difference between AEX and a full PI installation is obviously the missing ABAP
stack. As consequence, AEX is also missing all functionalities which depend on the ABAP
parts of PI:
-
-
No ccBPM
No ABAP-based adapters (like WSRM)
The Advanced Adapter Engine runtime only supports Integrated Configurations
(none of the “classical”, separated configuration objects like Receiver
Determination, Interface Determination or Sender/Receiver Agreements)
No ABAP mappings
4.1.1 Configuration
Configuration of an AEX installation is done via the service “XPI Service: AII Config Service”
instead of the Exchange Profile for a dual-stack PI installation.
You can access the service properties either via
-
PI start page > “Administration” > “Property Configuration”
or directly in the NetWeaver Administrator
-
http://<server>:<port>/nwa > “Configuration” > “Infrastructure” > “Java System
Properties”
Select the service “XPI Service: AII Config Service”
February 2011
11
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
The property “com.sap.aii.ibrep.core.usage_type” must be set to “AEX” for an AEX
installation.
4.1.2 User Management
Since there is no ABAP, the user management of an AEX installation is handled by the Java
UME. To access PI, users have to be assigned to one or more of the following user groups:
SAP_XI_DEVELOPER
SAP_XI_CONFIGURATOR
SAP_XI_CONTENT_ORGANIZER
SAP_XI_ADMINISTRATOR
SAP_XI_MONITOR
SAP_XI_SUPPORT
These user groups correspond to the ABAP roles with the same name in a full PI installation.
Additional Information
4.1.3 Documentation
Additional information about the AEX can be found in the documentation:


Advanced Adapter Engine Extended (explains the AEX in the larger context)
Using the Advanced Adapter Engine Extended:
Using Advanced Adapter Engine Extended Stand-Alone
Connecting Advanced Adapter Engine Extended to an Integration Server



Configuration guide: Basic Configuration for SAP NetWeaver PI Advanced
Adapter Engine Extended
Security guide: SAP NetWeaver PI Security Guide (AEX)
Process Integration and Orchestration Package
4.1.4 Notes
SAP Note 1435392 - describes the correct SLD configuration for an AEX installation
SAP Note 1414465 - Configuration Wizard: PI-AEX initial setup
12
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
5 SOA Design and Configuration Tools
Problem Analysis for the Enterprise Services Repository
(ESR) and Integration Directory
Problem
You need information about how to analyze and solve problems associated with the
PI tools (ESR and Integration Directory).
Analysis
Starting the Tools (Java Web Start)
To start the SAP NetWeaver PI tools, Java Web Start must be installed on the client
PC. Enterprise Services Builder and Integration Builder run on top of Java™ 2
Standard Edition 6.0 (J2SE 6.0), which includes Java™ Web Start.
In the event of problems, see SAP Note 801868 - Java(TM) Web Start in XI 3.0:
FAQ/Troubleshooting for more information.
Memory Log
If problems occur in the PI tools, you can use the memory log for further problem
analysis. Use the memory log only if you are able to reproduce the problem, because
the log in the browser is overwritten after 1000 lines.
To increase the trace level, use the following URL:
Integration Directory: http://server:port/dir/support/private/index.html
Enterprise Services Repository: http://server:port/rep/support/private/index.html
 Edit Memory Log Configuration
 Reset to DEBUG
 Save
To check the log, use the following URL:
Integration Directory: http://server:port/dir/support/private/index.html
Enterprise Services Repository: http://server:port/rep/support/private/index.html
 View Memory Log
 Show this filter
Reset the log level to DEFAULT after your analysis and save to avoid performance
problems.
February 2011
13
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Java Logs
All PI applications that run in the AS Java Engine write their logs to the AS Java
Engine logs.
applications.log
All error messages from Java applications are written to the
applications.<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
Java defaultTrace.trc
To trace applications in the Java Engine, you can increase the trace level for a
specific PI application.
To increase the trace level, call the SAP NetWeaver Administrator.
 http://<server:port>/nwa
 Troubleshooting
 Logs and Traces
 Log Configuration
 Show: Tracing 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
The trace is written to the defaultTrace.<number>.trc file. The file can be found in the
file system under ..j2ee\cluster\server<number>\log.
To analyze the log, use the LogViewer plug-in in the SAP NetWeaver Administrator.
 http://<server:port>/nwa
 Problem Management
14
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
 Logs and Traces
 Log Viewer
Reset the trace level to ERROR after your analysis, copy the setting to the subtree,
and finally save the entry to avoid performance problems.
Enterprise Services Repository
5.1.1 Problems and Solutions
5.1.1.1 Supported XML Schema and WSDL
Problem
You want to know which XML schema and WSDL are supported in PI.
Solution
In SAP NetWeaver 7.3, it is possible to import external definitions to the Enterprise
Services Repository for different purposes:

Make external schemas available centrally in the ESR

Use external schemas for the design and implementation of your
collaborative process in the ESR
Editors in the ESR expect WSDL or XML schema definitions (imported external
definitions are therefore converted).
For technical reasons, not all features of XSD can be supported. You can find
information on how the different editors and the proxy generation behave in the
following document: Supported XML Schema and WSDL
5.1.1.2 Import of IDoc or RFC - No Connection to Source System
Problem
You want to import an IDoc/RFC from a target SAP system to the Repository. The
connection step does not work.
Solution
1. Ensure that the logon group entry is correct. If using SPACE, check that it is
written in capital letters.
2. Check that the host name and client are correct.
3. Implement section 5 of SAP Note 593058 - New RFC Load Balancing
Procedure.
4. The message server must be known in the etc/services file on the Integration
Builder host. Navigate to the target system. In /etc/services or on NT
C:\WINNT\system32\drivers\etc\services, find the entry for the message
server, for example sapmsE14 3614/tcp. Enter this in the services file of the
February 2011
15
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
PI server (or the services file of the Integration Builder if distributed
installation has been used).
5.1.1.3 Import of IDoc Type Fails
Problem
The import of some IDoc types fails in the Integration Directory despite the logon and
selection steps being successful. You get an error message stating that the IDoc
type is not correct or that no message exists; the import hangs.
Solution
The cause of the problem is probably in the system from which you are trying to
import the IDocs.
1. Check the IDoc type in transaction WE60 (try to create a parser). If prompted,
check the segment definition of any erroneous segments in transaction
WE31.
2. Check whether the user has the necessary authorizations; for more
information, see the Importing IDocs and RFCs and SAP Note 677732 Authorization for MDI Within Framework of Adaptive RFC.
3. Check whether the necessary function modules are available. See SAP
Notes 672745 - Missing Function modules for MDI and 212011 - EDI/IDoc:
Access to IDoc Metadata.
4. Check whether the RFC function module DD_DOMA_GET is remoteenabled. See SAP Note 718320 - Problems Using MDI to Access DDIC
Types.
5. Check whether any short dumps or errors are written in the source system.
Integration Directory
5.1.2 Problems and Solutions
5.1.2.1 Adapter Engine Not Visible in SLD, RWB, or Directory
Problem
You cannot see your Adapter Engine in the SLD or in the Runtime Workbench;
furthermore, it is not possible to select it in the Directory channel configuration.
Analysis
See the Adapter Engine Not Visible in SLD, RWB, or Directory section.
16
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Services Registry
5.1.3 How to Check if the Services Registry is Configured
Correctly
Problem
You want to check if the connection to the Services Registry is configured and get
the URL for accessing it.
Analysis
Variant 1 (recommended):
1. Go to SAP NetWeaver Administrator  SOA Technical Communication 
System Connections.
2. Choose Provider Systems tab.
3. Choose New.
4. Choose input help for field System Name.
February 2011
17
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
If connection to Services Registry is configured, published systems in Services
Registry will be listed in Advanced Search view.
If connection to Services Registry is not configured, error message is displayed in
Advanced Search view.
18
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
1) Variant 2: Go to SAP NetWeaver Administrator (NWA) (http://server:port/nwa)
SOA  Application and Scenario Communication  Single Service
Administration.
(or Configuration  Connectivity  Single Service Administration).
2) Choose Consumer Proxies.
3) View details about runtime configurations of ServicesRegistrySi proxy definition.
4) If you get an error message that Web Service End Point URL for the runtime
configuration of ServicesRegistrySi proxy definition is incorrect, then the Services
Registry is not configured.
February 2011
19
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
5) The connection to the Services Registry is configured if URL
http://<host>:<port>/sr is accessible; the value in the Web Service End Point URL
must have the following format:
http://<host>:<port>/ServicesRegistrySiService/ServicesRegistrySiPort.
20
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
The security settings of the default runtime configuration is HTTP Authentication
mechanism with correct credentials (to check security settings, choose Security
tab)
February 2011
21
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
5.1.4 How to Configure the Services Registry
Problem
You get an error message “No SR connection available, set it up and try again.”
Example:
Solution
Variant 1: Configure the connection to the Services Registry with the CTC template:
5.1.4.1 Wizard-Based Configuration of Services Registry
After full installation, and before manual configuration, you can run the functional unit
configuration tool to initially set up Services Registry. This tool saves you time and
manual steps. You can use the tool to perform the following tasks:
22

Configuring a central Services Registry in your system landscape

Setting destinations for the UDDI server and classification service, or register
Services Registry in SLD (optional)
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
5.1.4.1.1
Procedure
5.1.4.1.2
Accessing the Configuration Wizard
1. Access SAP NetWeaver Administrator using the following address:
http://[host]:[port]/nwa
2. Navigate to
Configuration Management
Scenarios
.
3. Choose Configuration Wizard.
5.1.4.1.3
Configuring a Central Services Registry
1. In the SAP NetWeaver system that you want to be able to connect to the
central Services Registry, start the Connection Configuration to Central
Services Registry task.
2. Enter the necessary information as follows:
o
When entering the endpoint URL, it must be in the following format:
http://<host>:<port>/ServicesRegistrySiService/ServicesRegistry
SiPort.
NOTE
You should set as a central Services Registry only systems with the
newest version of Services Registry in your landscape.
o
When entering a user name, the user account must be available on
the AS Java of the central Services Registry and needs to be
assigned to certain Services Registry-specific roles. One of the
following combinations of user management engine roles has to be
assigned to this account:

SERVICES_REGISTRY_READ_WRITE and also one of the
following: UDDI_TierN or UDDI_Admin

Both SERVICES_REGISTRY_READ_ONLY and UDDI_Tier1
For more information, see Services Registry Roles.
5.1.4.1.4
Setting Destinations for the UDDI Server and Classification Service
CAUTION
This is an optional task. You should perform it only if one or more of the following
applies:

You use a non-SAP UDDI server.

You have an AS ABAP release in your system environment with a lower
version than 7.0 SP14 (for SAP NetWeaver 7.0 versions) or 7.1 SP04 (for
SAP NetWeaver PI 7.1 and later versions).
February 2011
23
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Note that setting destinations for the UDDI server and classification service prevents
you from using the role-based access control functionality.
On the SAP NetWeaver system that is intended to serve as a central Services
Registry, start the Services Registry Destinations Creation task and enter the
necessary information. When entering a user name, consider that the user account
needs to be assigned to the UDDI_Admin and
SERVICES_REGISTRY_READ_WRITE roles.
After the functional unit configuration tool finishes successfully, it sets the necessary
logical destinations.
5.1.4.1.5
Registering Services Registry in SLD
On the SAP NetWeaver system that is intended to serve as a central Services
Registry, start the Registering Services Registry instance in SLD task and enter the
necessary information.
5.1.4.1.6
Result
You can access the central Services Registry using the following address:
http://<hostname>:<port>/sr_central. Without configuring a central Services
Registry this address leads you to the Services Registry on your local AS Java.
Variant 2:
If there are some previous configurations of the Services Registry done this variant
should be used.
5.1.4.2 Manual Configuration
5.1.4.2.1
Creating a Connection to the Central Services Registry
1. To start SAP NetWeaver Administrator, enter the following address in a Web
browser:
http://[host]:[port]/nwa
2. Choose SOA Management
Single Service Administration
Application and Scenario Communication
.
3. On the Consumer Proxies tab, enter ServicesRegistrySi in the Find field and
choose Go.
4. Select ServicesRegistrySi.
5. On the Configuration tab, select ServicesRegistrySiPort.
6. On the General tab, change the WS Endpoint URL to the one of your central
Services Registry.
The URL must have the following format:
http://[host]:[port]/ServicesRegistrySiService/ServicesRegistrySiPort
7. On the Security tab, set the authentication method for the Services Registry.
24
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
8. Select either User ID/Password (Basic) or Logon Ticket.
Apply at least basic authentication.
9. Select Details and enter the user ID and password of a user account on the
system that hosts the central Services Registry.
The following roles must be assigned to the technical user account you
specify at this step:
5.1.4.2.2
o
For read access: SERVICES_REGISTRY_READ_ONLY and the
UDDI role UDDI_Tier1.
o
For unlimited access to Services Registry content:
SERVICES_REGISTRY_READ_WRITE and the UDDI role
UDDI_Admin.
Maintaining the Connection to the Central Services Registry
The system that you have configured to use a central Services Registry connects to
it using the credentials of a user account on the system that hosts this Services
Registry. In case this user account expires, your system would not be able to
connect to the central Services Registry and might behave like it is not configured. In
such situation, you can do the following:
1. Navigate to the Security tab as described above, and check if authentication
type is set to User ID/Password (Basic).
2. If this is the case, check whether the user and the password that are entered
are correct.
You can check if the password is not expired by trying to log on with the user
and password to the system that hosts the central Services Registry.
3. If the password is expired the system can ask you to change it. Change the
password, or request an administrator on this system to do this.
After changing the password, make sure the user account has been used for
logging in at least once before you use it to configure a central Services
Registry on another system.
4. On your system, enter the new password into the Security tab as described
above and save the changes.
If this user and password are used for other configurations update them too.
5. Try to access the central Services Registry from your system.
5.1.4.2.3
Result
Access the central Services Registry using the following address:
http://[host]:[port]/sr_central.
February 2011
25
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
5.1.4.2.4
Setting Destinations to UDDI Server and Classification Service
You need to set the destinations to UDDI server and the classification service
manually only if one or more of the following applies:

You use a non-SAP UDDI server.

You have an AS ABAP release in your system environment with a lower
version than 7.0 SP14 (for SAP NetWeaver 7.0 versions) or 7.1 SP04 (for
SAP NetWeaver 7.1 and later versions).
5.1.4.2.4.1 Managing Destination Templates
In SAP NetWeaver Administrator, choose
Destination Template Management .
SOA
Technical Configuration
5.1.4.2.4.2 Creating Destination to the UDDI Server

If you want to use a non-SAP UDDI server, use an older release version of
AS ABAP, or use any version of Visual Composer, you need to create the
following destination:
o
Destination Type: WSDL
o
Destination Name: UDDI_DESTINATION
o
URL: http://[host]:[port]/uddi/wsdl/uddi_v3_service.wsdl
The URL used as an example is valid for the SAP UDDI server. If you
are using a non-SAP UDDI server, the URL would be different.
o
For authentication, select HTTP Authentication, and then choose User
ID/Password (Basic).
o
Enter a user ID and password.
Make sure the user account you provided is assigned to the
UDDI_Admin and SERVICES_REGISTRY_READ_WRITE roles.

26
NOTE

Consider that when using the UDDI_DESTINATION destination you cannot
use the role-based access control feature of Services Registry and cannot
apply usage profiles.

When you want to use role-based access, you need to create the following
destination:
o
Destination Type: WSDL
o
Destination Name: UDDI_DESTINATION_V11
o
URL: http://[host]:[port]/uddi/wsdl/uddi_v3_service.wsdl
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
The URL used as an example is valid for the SAP UDDI server. If you
are using a non-SAP UDDI server, the URL would be different.
o
Authentication: select HTTP Authentication, and then select Logon
Ticket.
NOTE
When both UDDI_DESTINATION and UDDI_DESTINATION_V11
destinations are present, the latter takes precedence for SR

When you want to connect to a non-SAP UDDI server using the AuthToken
authentication mechanism, you need to create the following destination:
o
Destination Type: WSDL
o
Destination Name: UDDI_DESTINATION_AUTH_TOKEN
o
URL:
http://[host]:[port]/uddiat/wsdl/uddi_v3_service_authtoken.wsdl
The URL used as an example is valid for the SAP UDDI server. If you
are using a non-SAP UDDI server, the URL would be different.
o
For authentication, select HTTP Authentication, and then choose User
ID/Password (Basic).
o
Enter a user ID and password.
Make sure the user account you provided is assigned to the
UDDI_Admin and SERVICES_REGISTRY_READ_WRITE roles.


NOTE
The UDDI_DESTINATION_AUTH_TOKEN destination is used only as a
holder of the credentials of the user used in get_AuthToken request. It is
mandatory to perform all of the following additional configurations:
o
UDDI_DESTINATION_AUTH_TOKEN must be used along with one
of the above described destinations, UDDI_DESTINATION or
UDDI_DESTINATION_V11.
o
These destinations should have the same endpoint URL as the
UDDI_DESTINATION_AUTH_TOKEN destination, for example:
http://[host]:[port]/uddiat/wsdl/uddi_v3_service_authtoken.wsdl
o
These destinations should have authentication method set to None.
5.1.4.2.4.3 Creating Destination to the Classification Service
Create a new destination with the following properties:

Destination Type: WSDL
February 2011
27
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide

Destination Name: CLASSIFICATION_DESTINATION

URL: http://[host]:[port]/ClassificationService/CS?wsdl

Authentication: HTTP Authentication

Select User ID/Password (Basic).

Enter a user ID and password.

If this user is not an administrator, assign the roles UDDI_Admin and
SERVICES_REGISTRY_READ_WRITE.
5.1.4.2.5
Result
After changing the destination to the UDDI server and the classification service, you
need to restart the AS Java engine. The destination of the SAP UDDI server and the
classification service must point to the same AS Java.
5.1.5 Problems and Solutions
5.1.5.1 Initial Services Registry UI Opens, but Exception Shown at Top
of Page
Problem
The initial Services Registry UI screen opens, but an exception is shown at the top of
the page. The exception may have one of the following attributes:
a.) SRExceptionerror code: 29100 detail message: An exception occurred while
obtaining UDDI Logical Ports.
This situation indicates that something is wrong with the connection to the
UDDI registry, which is used by the Services Registry as a back end.
b.) TransportBindingException during request to UDDI Invalid Response code
(401). Server <http://...................../uddi/api/inquiry/> returned message
<Unauthorized>
28
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
This situation indicates that the Services Registry cannot establish a
connection to the UDDI registry, which is used as a back end, because
incorrect credentials are being used to connect to the UDDI registry.
Possible Reasons
There is one possible reason for this problem: An incomplete or incorrect
UDDI_DESTINATION is provided, which is used by the Services Registry to connect
to the UDDI registry.
Troubleshooting Steps:
To check whether the provided UDDI_DESTINATION is correct and complete, do the
following:
1.) Log on to SAP NetWeaver Administrator (NWA) (http://server:port/nwa)
2.) Go to SOA  Destination Template Management
February 2011
29
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
3.) The following screen opens: “Destination Template Management: Destination
Templates”
4.) Check whether an entry UDDI_DESTINATION exists.
5.) If the UDDI_DESTINATION entry does not exist, this means that the Services
Registry will use the local UDDI registry (that is, the SAP UDDI
implementation, which is shipped as a standard J2EE application within SAP
NetWeaver). In this case, you must make sure that the SAP UDDI application
is up and running on SAP NetWeaver. To do this, go to SAP NetWeaver
Administrator (NWA) (http://server:port/nwa) Operations  Systems 
Start and Stop.
On the page that opens, select the Java Applications tab, and search for an
application with the name tc~uddi. Make sure that this application is available
and is started.
30
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
6.) If there is an entry UDDI_DESTINATION, click it to view its details:
Make sure that:
a) Destination type is WSDL
b) If a SAP UDDI Registry is used, the URL must have the type:
http://<host>:<port>/uddi/wsdl/uddi_v3_service.wsdl
If a non-SAP UDDI registry is used, you must consult your vendor
documentation and provide the URL on which the WSDL of the UDDI
registry resides.
c) The security settings of the UDDI_DESTINATION are correctly set. If
you are using the SAP UDDI Registry, you should use HTTP
Authentication and check the User ID/ Password (basic)
Authentication checkbox, as shown on the following screen:
February 2011
31
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
If you are using the HTTP Basic Authentication as shown above, make
sure you have provided the correct user name and password by clicking
the Details button just below the Authentication area.
d) If any changes are made of UDDI_Destinations the changes will take
effect only after the restart of application tc~esi~uddi~sr~ear. In order
to do this, go to SAP NetWeaver Administrator (NWA)
(http://server:port/nwa) Operations  Systems  Start and Stop.
On the page that opens, select the Java Applications tab, and search
for an application with the name sr~ear. Make sure that this
application is available
32
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Choose Stop and then Refresh in order to insure that that application is stopped.
Then choose Start and again Refresh. When the tc~esi~uddi~sr~ear application is
restarted the UDDI_DESTINATION will take the affect.
February 2011
33
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
5.1.5.2 Services Registry Link on J2EE Start Page Does Not Work
Problem
The SAP NetWeaver start page opens, but clicking the Services Registry link results
in an error indicating that the page cannot be displayed.
Possible Reasons
The Services Registry proxy is not configured correctly.
Troubleshooting Steps
Configure your Services Registry proxy correctly. The host and port are taken from
this configuration to determine the URL on which to invoke the Services Registry UI.
In other words, the Services Registry proxy configuration determines the URL to
which the calls to the SAP Services Registry UI are redirected.
1) Log on to SAP NetWeaver Administrator (NWA) (http://server:port/nwa)-
SOA - Application and Scenario Communication  Single Service
Administration.
34
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
2) On the window that opens, choose the Consumer Proxies tab. Type
*Service* in the “Find” input field and choose “Go”. In the results table that is
shown, locate the port type with name ServicesRegistrySi.
3) Select the port type with name ServicesRegistrySi and namespace
http://sap.com/esi/uddi/sr/api/ws/ . Select the Configuration tab. In the table
ServicesRegistrySi Logical Ports that opens below, select
ServicesRegistrySiPort. Finally, choose Edit as shown in the screenshot
below and make sure that you enter the correct end point URL (the correct
format of the URL is http://<host>:<port>/
ServicesRegistrySiService/ServicesRegistrySiPort), as well as security
settings.
February 2011
35
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
5.1.5.3 Free Text Search Is Not Working
Problem
On the SAP Services Registry UI start page, select Free Text from the Search By list
box and type a word to search for in the input field. Choose “Go”. A warning
message appears with content “TREX search cannot be performed. TREX is not
available on the system.”
Possible Reasons
The free text search function in Services Registry uses TREX as an indexing engine;
if you do not have it installed in your landscape you will not be able to use this
function. Accordingly, there are two possible reasons for this problem:
(a) The TREX search engine is available but is not configured.
(b) The TREX search engine is not available in the landscape.
Troubleshooting Steps
First of all, make sure that you have the TREX product installed in your landscape.
Usually, the TREX product is separately shipped, so consult your system
administrator. Once you have confirmed that TREX is available and working in your
landscape, do the following:
1.) Check the connection to the TREX search engine from the Services Registry
configuration settings. To do this, log on to SAP NetWeaver Administrator
(NWA)  SOA  Technical Configuration  Services Registry
Management.
36
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
2.) Click the Services Registry Management link. Select the Services Registry
Settings tab.
Choose Test TREX Connection. If you see a message in green font
“Successfully connected to TREX Server”, your connection to TREX is
enabled and working. Consequently, the free text search function in the
Services Registry UI should now be working. If you see an error message in
red font, first try to update your TREX connection by choosing Update TREX,
and then test the communication with TREX once again. If there is another
red error message, you should configure your TREX service.
3.) To configure the TREX service, go to NWA  Configuration  Infrastructure
 Java System Properties.
February 2011
37
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
4.) In the Java System Properties: Overview window, select the Services tab and
search for the TREX service.
5.) There should be one search match: the TREX Service entry. Select it and
navigate to the context table at the bottom of the page. There you must
configure the parameter nameserver.address with an entry of type
tcpip://<hostname>:<port>.
5.1.5.4 Not All Operations Are Available in UI (for Example Delete a
Service, Hide a Service Definition, Publish a Service)
Problem
Services Registry APIs contain around 40 operations. However, from the Services
Registry UI, a user can invoke mainly operations (such as find, get, and so on), and
publish (save) operations.
How can a user invoke any operation in the Services Registry using a UI tool?
Possible Reasons
There is one reason for this problem: The Services Registry UI offers only a subset
of all available Services Registry operations. There is another application, which is
part of SAP NetWeaver, called WS Navigator (Web Service Navigator). This is a
general tool for invoking Web services. The WS Navigator works with any WSDL
containing a description of a callable service – it generates a proxy containing all
operations exposed in the WSDL file and provides a convenient UI for invoking any
of these operations. To use the WS Navigator, follow the steps below.
Troubleshooting Steps
To call the WS Navigator, use the following link:
http://<hostname>:<port>/wsnavigator
38
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
1) In the Select Service step of the application that opens, enter the WSDL of
the Services Registry in the WSDL URL input field and choose Next.
February 2011
39
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
To determine the WSDL of the SAP Services Registry, do the following:
a) Go to NWA  SOA  Application and Scenario Communication 
Single Service Administration.
b) On the Service Definitions tab, search by WSDL PortType Name, typing
Services* in the Find input field.
c) Choose the port type with name ServicesRegistrySi, navigate to the
WSDLs tab in its context menu, and copy the WSDL of the Services
Registry from there:
40
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
d) Copy the link to this WSDL and paste it in the WSDL URL input field in
Step 1 of the WS Navigator application as specified in step (1).
2) Choose Next.
3) As a result, you see all operations described by the Services Registry
WSDL.
4) Choose the operation you would like to execute. If we assume you want to
delete a service definition, you must select the operation
hideServiceDefinition. Choose Next.
Set all parameters that are needed for the operation you chose. In our case,
you must provide either a logical key of the service definition you want to
hide, or you have to provide the UDDI key of the service definition, which can
be taken from the Services Registry user interface. Navigate to
http://<host>:<port>/sr, find and select the needed Service Definition. You
can find the UDDI key in the Details tab.
February 2011
41
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Choose Next and the request will be executed.
42
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
5.1.5.5 Where Do I Find More Documentation Related to the SAP
Services Registry?
Problem
You lack a list of documentation related to the Services Registry.
Solution
Below you can find a list of documentation related to the Services Registry.
SAP Library sections:

Configuring the Services Registry
February 2011
43
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide

Discovering services in the Services Registry

Publishing a Web Service (AS ABAP)

Publishing to the Services Registry (AS Java)
5.1.5.6 Error Message “Container for Bean… Has Already Been
Destroyed”
Problem
If you access the Services Registry using SOAP, the SOAP response is a fault
message, in which the <faultstring> element consists of the following description:
>> nested exception is:
>> com.sap.engine.services.ejb3.runtime.InactiveContainerException:
>> Container for bean
>> sap.com/tc~esi~uddi~sr~ear*annotation|tc~esi~uddi~sr~impl~ejbm.jar*annotation
>> ServicesRegistryFacade has already been destroyed
If you access the Services Registry using the Services Registry UI, you get an
exception that contains the same message as above:
Possible Reasons
This problem might occur in several cases:
(a) After restart of the application sap.com/tc~esi~uddi~sr~ear
(b) After a partial deployment of SDAs/SCAs related to the Services Registry
Solution
If your problem occurs only when the Services Registry is accessed using SOAP,
simply resend your initial SOAP request (several times if necessary). If your problem
occurs in the Services Registry UI, restart the application tc~esi~esp~er~ui (this is
the Services Registry UI application).
5.1.5.7 Error Message “You Don‟t Have Read Permissions for Services
Registry”
Problem
44
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
On the SAP Services Registry UI start page, the error message “You don’t have read
permissions for Services Registry. Contact your system administrator.” appears.
Possible Reasons:
You do not have read permissions for the Services Registry.
Troubleshooting Steps
The user that is used to log on to the initial Services Registry UI screen must have
the necessary permissions. Generally, there are two types of permissions (user
roles) for the Services Registry:
SERVICES_REGISTRY_READ_WRITE – this role gives both read and write
permissions for the Services Registry to the user to whom it is assigned.
SERVICES_REGISTRY_READ_ONLY – this role gives only read permissions for
the Services Registry to the user to whom it is assigned.
Contact your system administrator to assign any of the above roles to a given user,
follow the steps below:
1.) Log on to NWA and choose Configuration  Identity Management.
February 2011
45
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
2.) On the Identity Management page that opens, enter the name of the user in
the Search Criteria input field, and choose Go. Select the user and a table
called Details of User <User name> appears just below. In this table, choose
Modify. Select the Assigned Roles tab, enter Service* in the search input field
and choose Go. Two roles should be found:
SERVICES_REGISTRY_READ_ONLY and
SERVICES_REGISTRY_READ_WRITE. Select one of the roles and choose
Add (at the bottom left of the page). Finally, Save the changes made.
As a result, the user will be assigned the role to view, or view and write to the
Services Registry.
5.1.5.8 Cannot Establish a Connection to the Services Registry Due to
Various Exceptions
Problem
A typical use case would be the start page of Web Service Navigator (WS
Navigator), on which you are trying to search for service interfaces in the Services
Registry by using the Services Registry radio button, as shown below:
46
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
However, instead of connecting to the Services Registry, an exception is shown.
Possible Reasons
a) The Services Registry proxy is not configured at all
b) The Services Registry proxy is not configured correctly
Troubleshooting Steps for Reason (a)
If the Services Registry proxy is not configured at all, check the text in the exception
you receive (in the logs).
February 2011
47
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
In order to display the logs, log on to NWA (http://<server:port>/nwa) and choose
Troubleshooting  Logs and Traces  Log Viewer.
If the exception contains the text “java.net.MalformedURLException: no protocol:
URL to the Central Services Registry e.g.
http://host:port/ServicesRegistrySiService/ServicesRegistrySiPort”, you have to
configure the Services Registry proxy:
1.) Go to NWA and choose SOA  Application and Scenario Communication.
2.) Select the Single Service Administration link.
3.) In the Single Service Administration window, select the Consumer Proxies
tab.
4.) Enter Services* in the Find input field and choose Go.
5.) Select ServicesRegistrySi in the Proxy Definitions table.
6.) In the Details About ServicesRegistrySi Proxy Definition table, select the
Configuration tab.
7.) Select the logical port ServicesRegistrySiPort.
Choose Edit and in the table Details About ServicesRegistrySiPort Logical
Port enter the URL for the Central Services Registry in the Web Service End
Point URL field: The correct format of the URL is http://<host>:<port>/
ServicesRegistrySiService/ServicesRegistrySiPort.
8.) Select the Security tab, and configure the Services Registry security settings.
Select HTTP Authentication with User ID/Password (Basic). In the Details
area below, provide the credentials of a user who has either the
SERVICES_REGISTRY_READ_ONLY or
SERCICES_REGISTRY_READ_WRITE role.
48
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Your Services Registry proxy is now configured.
Troubleshooting Steps for Reason (b)
If your Services Registry proxy is not configured correctly, you may get an exception,
for example “Server… returned message <Unauthorized>… Invalid Response code
(401)”:
If you get an exception like the one above, make sure you have performed all
troubleshooting steps for reason (a). Pay special attention to step (9) and make sure
you configured the SR proxy to use HTTP Authentication with User ID/ Password
(Basic) with a user who is authorized to perform SR read/write operations.
If ServicesRegistrySiPort is properly configured but the problem still exists, check if
UDDI_DESTINATION and CLASSIFICATION_DESTINATION are created. If they
are created, check if they are correct and complete, do the following:
February 2011
49
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
1.) Log on to NWA (http://server:port/nwa) and choose SOA  Destination
Template Management, respectively CLASSIFICATION_DESTINATIONS.
2.) The following screen opens: “Destination Template Management: Destination
Templates”.
3.) Check whether an entry UDDI_DESTINATION exists. If the destinations exist
select UDDI_DESTINATION, click it to view its details:
50
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Make sure that the following conditions are fulfilled:
e) Destination type is WSDL.
f)
If a SAP UDDI Registry is used, the URL must have the type:
http://<host>:<port>/uddi/wsdl/uddi_v3_service.wsdl.
If a non-SAP UDDI registry is used, you must consult your vendor
documentation and provide the URL on which the WSDL of the UDDI
registry resides.
For CLASSIFICATION_DESCTINATION, the URL must have the
type:
http://[host]:[port]/ClassificationService/CS?wsdl.
g) The security settings of the UDDI_DESTINATION are correctly set. If
you are using the SAP UDDI Registry, you should use HTTP
Authentication and check the User ID/Password (Basic)
Authentication checkbox, as shown on the following screen:
h) If you are using HTTP Basic Authentication as shown above, make
sure you have provided the correct user name and password by
choosing Details (below the Authentication area). If any changes are
made for UDDI_Destinations, the changes will take effect only after
the restart of application tc~esi~uddi~sr~ear. In order to do this, go to
NWA (http://server:port/nwa) and choose Operations  Systems 
Start and Stop. On the page that opens, select the Java Applications
tab, and search for an application with the name sr~ear. Make sure
that this application is available.
February 2011
51
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Choose Stop and then Refresh in order to insure that that application is stopped.
Choose Start and then Refresh. When the tc~esi~uddi~sr~ear application is
restarted, the UDDI_DESTINATION will take effect.
5.1.5.9 Cannot Publish a WSDL into the Services Registry Using the
Services Registry UI Due to an Exception
52
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Problem
This use case involves publication of an external WSDL from the Services Registry
UI. “External” means that the WSDL is outside of the network in which the Services
Registry resides. An example could be trying to publish a WSDL from the Internet
into the company intranet. Let us assume we want to publish the WSDL of
Amazon.com into the Services Registry. An error message occurs indicating that
“Cannot connect to http://soap.amazon.com/schemas2/AmazonWebServices.wsdl.Unable to connect to soap.amazon.com:80 - soap.amazon.com”:
This situation indicates that there is a problem connecting to an external WSDL file
(outside of the corporate network).
Possible Reasons
The SAP NetWeaver proxy is not configured.
Troubleshooting Steps
Configure the SAP NetWeaver proxy as follows:
1.) Go to NWA  SOA  Technical Configuration  SOA Middleware Global
Settings.
February 2011
53
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
2.) On the HTTP Proxy tab, enter the details about your proxy server (host, port,
user name, and so on) and choose Save.
3.) Your SAP NetWeaver proxy is now configured.
54
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
5.1.5.10 Services Registry Returns Error Code: 10160, Detail Message:
A Save Request Exceeded the Quantity Limits for a Given
Structure Type.
When one of the roles UDDI_ThierN or UDDI_Thier1 is assigned to a user, this user
is restricted to publish a limited quantity of entities into the Services Registry and
UDDI. When this limit is exceeded, an error message appears when the user tries to
publish.
Solution
1. In NWA (http://<host>:<port>/nwa) choose SOA  Technical Configuration 
Services Registry Management.
2. Choose UDDI Server Configuration and then choose the General tab.
3. Set the Disable Tier Limit Checks checkbox.
4. Choose Save.
5.1.5.11 Publication to Service Registry Fails with a Message Like
“com.sap.esi.uddi.sr.api.exceptions.SRException: An attempt
was made to use the publishing API to change data that is
controlled by another party.”
Reason and Prerequisites
Services Registry has been configured and you were able to publish data into it.
When the ServicesRegistrySiPort configuration is changed and a new user is
assigned with different ID/Password Authentication details, it will not be possible to
republish the previously existing data if the newly assigned user does not have
UDDI_Admin role.
February 2011
55
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Solution
1. Navigate to NWA (http://[host]:[port]/nwa) and choose SOA  Application and
Scenario Communication  Single Service Administration. On the Consumer
Proxies tab select ServicesRegistrySi. On the Configuration tab select
ServicesRegistrySiPort.
3. On the Security tab, choose Details to see the User ID.
4. Log on to NWA and choose Configuration  Identity Management.
5. Select the user from step 3 and navigate to Assigned Roles tab. Choose Modify,
assign the UDDI_Admin role, and save the changes.
5.1.5.12 Services Registry Returns Time out
Symptom
Calling the Services Registry returns the following exception:
java.rmi.RemoteException: TransportBindingException... ..
java.net.SocketTimeoutException: Read timed out.
Reason and Prerequisites
In the Services Registry settings, the value of the Max wait-time for HTTP response
parameter is not big enough.
Solution
1. Increase the value of the Max wait-time for HTTP response parameter for
ServicesRegistrySiPort. In order to do this, access NWA (http://[host]:[port]/nwa) and
navigate to SOA  Application and Scenario Communication  Single Service
Administration. On the Consumer Proxies tab, select ServicesRegistrySi. On the
Configuration tab, select ServicesRegistrySiPort. On the Transport Settings tab,
increase the value of the Max wait-time for HTTP response field and save the
changes.
56
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
2. If there are UDDI_DESTINATION and CLASSIFICATION_DESTINATION
destinations, increase their Max wait-time for HTTP response parameter.
Using NWA, navigate to SOA Management  Technical Configuration 
Destination Template Management. Select UDDI_DESTINATION. In the details,
increase the values of Max wait-time for HTTP response parameter and save the
changes. Repeat the same for CLASSIFICATION_DESTINATION.
Web Services Configuration
The information in this section is relevant for SAP EHP 1 for SAP NetWeaver PI 7.1.
Information about ABAP Web Service Configuration can be found in SAP Note
1319507 - Overview: Analysis of ABAP Web Service Configuration.
5.1.6 Problems and Solutions
5.1.6.1 Web Service or Service Group Is Not Published into the
Services Registry
Problem
You have created a publication rule using the Create Publication Rule wizard,
available at SAP NetWeaver Administrator  SOA  Application and Scenario
Communication  Publication Rules.
February 2011
57
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
However, the Web service (or service group) included in the publication rule is not
published in the Services Registry.
Analysis
1) Go to SAP NetWeaver Administrator  SOA  Application and Scenario
Communication  Publication Rules.
2) Check the State of the publication rule.
The State of publication rule could be Published, To be Published or Failed.
58
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Published:
If you have redirected connections to another Services Registry, state remains
Published even an automatic republication was not triggered. Select publication rule
and press button Republish for republishing.
To be Published:
Publication is done by a background process which takes some time to upload data
to the Services Registry. If the State is To be Published then the background process
might not have finished yet. When State becomes Published or Failed then
publication has completed successfully or with failure respectively. Use refresh
button for getting latest State.
Failed:
A Failed state indicates that the publication process has finished with errors.
5.1.6.2 Consumer Assignment in Configuration Scenario has „Failed‟
State
Problem
You have created a consumer assignment in a configuration scenario using the
Create Configuration Scenario wizard, which is available at SAP NetWeaver
Administrator  SOA  Application and Scenario Communication  Business
Scenario Communication (or Application Communication), but it is in Failed state.
Analysis
1) Go to NetWeaver Administrator  SOA Management  Technical Configuration
 System Connections, tab Provider Systems.
2) Select the row with the failed assignment and select Show Log button. .
3) A new browser with error log will be opened. In most of the cases generation fails
because of technical error like incorrect credentials, missing User Account or
assigning system connection which doesn‟t host services, grouped by service
group. Read the error message and possible solutions.
February 2011
59
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
You may also look up the Troubleshooting guide for ABAP Web Service Runtime
via SAP Note – 1457547: Support Utilities for Web Service processing.
Web Services Navigator (WS Navigator)
5.1.7 Problems and Solutions
5.1.7.1 Exception when Services Registry Search Type is Used
Problem
You get an error message when the Services Registry search type is chosen.
Analysis
Check if the connection to the Services Registry is set up correctly. For information
about how to check and configure the connection to the Services Registry, see 5.1.3
and 5.1.4.
5.1.7.2 Access to the Web Service Host Is Not Allowed
Problem
When you try to open a WSDL URL you get the error message: It is not allowed to
access URL <WSDL URL>.
60
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Solution
The problem can be fixed by an administrator (user with administrator rights) of the
Java AS where you are accessing Web Services Navigator.
The administrator has to add the requested host to the Web Services Navigator
White List. Do the following:
1. Open NWA of the Java AS where you are accessing the WS Navigator.
2. Navigate to SOA Management  Technical Configuration  SOA
Middleware Global Settings.
3. On the WS Navigator tab, add the requested host to the list of Allowed Hosts.
To add more than one host name in the list, use (;) or (|) as a delimiter.
Wild cards (*) and (?) can also be used.
February 2011
61
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
6 Proxy
ABAP Proxy
You have the option of using ABAP proxies to connect an application to SAP
NetWeaver PI. The proxies first need to be generated, then the XI runtime in the
application system is used to transport the messages.
Prerequisites
In SAP NetWeaver PI you can connect business systems based on AS ABAP 6.20
once you have installed the PI add-on in the business systems as described in the
Installation Guide for SAP Exchange Infrastructure Release 2.0 SR1. If you are using
a business system based on AS ABAP 6.40 or higher to connect to an Integration
Server based on SAP NetWeaver 7.3, you do not need to install any add-ons. If you
are using a business system based on AS ABAP 6.20 you need to install the XI 2.0
AddOn. Check SAP note 1397878 - scwb and snote functionality for proxies.
Also check SAP Notes 1029220 - End of Maintenance for SAP XI 2.0 and 439915 Exchange Infrastructure Integration Server 2.00 for more information about 6.20 addon installations and patching.
The configuration of the business system to be connected to an Integration Server is
described in the SAP Library section Configuring Business Systems with Integration
Engine and the subsections:
 Transaction SXMB_ADM  Integration Engine Configuration
For an application system you have to maintain the role of the business
system as an application system. Set the corresponding Integration Server as
an HTTP destination (for example, dest://INTEGRATION_SERVER). Create
the destination in transaction SM59 and set the type to HTTP Connections to
R/3 System. Test the connection by using the Connection Test button; you
should get HTTP 500 – Empty HTTP Request received, because no „real‟
XML document is sent during this test.

If you have problems, check the SAP Notes of the relevant CSN component
BC-XI-IS*.
Transaction SLDCHECK
Since the applications communicate with the SLD to get their own business
system and Integration Server information, the application system needs to
be maintained in the SLD and the connection to the SLD needs to be running
from all business systems. Use the transaction SLDCHECK to check whether
this is the case.
If you have problems, check the SAP Notes of the relevant CSN component
BC-CCM-SLD.
62
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
6.1.1 ABAP Proxy Generation
6.1.1.1 ABAP Proxy Generation Troubleshooting
Problem
You have problems during proxy generation and need more information about how to
analyze these issues.
Analysis
If you have problems during proxy generation, you can use the following
tools/transactions for initial checks and further analysis:
 Transaction SPROXY
The interfaces are taken from the Enterprise Services Repository of the
connected PI system. To make sure this connection is running correctly, use
the test reports provided in transaction SPROXY  Choose the Proxy
Generation Online Documentation Info
button. Choose
The option Connection to ESR and execute each of the below reports listed
by click.
o Report SPROX_CHECK_IFR_ADDRESS checks whether the connection
to the exchange profile is running and whether the parameters are set.
o Report SPROX_CHECK_HTTP_COMMUNICATION checks whether the
HTTP communication of the system is running.
o Report SPROX_CHECK_IFR_RESPONSE checks whether the
connection to the ES Builder is running correctly.
Note: Report SPROX_CHECK_IFR_CONNECTION used to check
whether the data coming from the ES Builder can be correctly interpreted
is now part of Report SPROX_CHECK_IFR_RESPONSE.
For more troubleshooting information concerning ABAP proxy generation, see SAP
Note 1229048 - Proxy Generation Troubleshooting.
Related SAP Notes:
1229048 - Proxy Generation Troubleshooting
886682 - Proxy Inconsistencies
783088 - Generated Proxy Class Cannot Be Deleted
944029 - XML Schema Supported by ABAP Proxy Generation
6.1.1.2 Problems and Solutions
6.1.1.2.1
SPRX 097 - Enterprise Services Builder Data Not Understood
Problem
The error message SPRX 097: Enterprise Services Builder data not understood is
displayed when performing the connection test in transaction SPROXY.
February 2011
63
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Solution
Make sure your business system is set up as follows:
1. Transaction SXMB_ADM
- Role of System: Application System
- Corresponding Integration Server:
dest://<your_sm59_http_destination>
2. Ensure that the RFC destinations LCRSAPRFC and SAPSLDAPI are
maintained and working.
3. Run SLDCHECK to verify that the connection to the System Landscape
Directory works. In the event of errors, also check the SAP Notes for CSN
component BC-CCM-SLD.
4. Check that the Enterprise Services Repository is running and that data is
maintained there.
6.1.1.2.2
HTTP Error ICM_HTTP_CONNECTION_FAILED
Problem
You get the above error while running report SPROX_CHECK_IFR_RESPONSE in
transaction SPROXY.
Solution
The report SPROX_CHECK_IFR_RESPONSE executes an HTTP call to itself to test
if the HTTP communication is working. If there are problems, check the following:
 Is the ICM running and the HTTP port active in transaction SMICM? For more
information, see SAP Note 634006 - ICM Messages Explanatory Note.
 Check the dev_icm trace file and see whether there are any errors. For
information about where to find the trace and how to increase the trace level, see
SAP Note 634006 - ICM Messages Explanatory Note.
 Check SAP Note 773830 - FQHN Determination in ICM and make sure the host
name is set correctly.
 If you find errors in the dev_icm trace file, check the SAP Notes for CSN
component BC-CST-IC.
6.1.1.2.3
Wrong URL in SPROXY
Problem
While running SPROXY, the wrong URL is generated to the Repository.
Solution
Check the following:
 Can the exchange profile be accessed and is it maintained correctly?
o Check transaction SLDCHECK. If there are errors, also check the
SAP Notes for CSN component BC-CCM-SLD, which is the
corresponding component for SLDCHECK.
o Check the values set in the exchange profile.
 If the system is a business system based on AS ABAP 6.20, make sure the
add-on is installed.
64
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
6.1.1.2.4
Pop-Up Authentication Window in SPROXY
Problem
After calling transaction SPROXY, a dialog box appears prompting you to enter the
user and password.
Solution
There is an inconsistency in the passwords for user XIAPPLUSER/PIAPPLUSER.
Ensure that the password for the user is maintained correctly in transaction SU01 in
the Integration Server and the exchange profile. Pay special attention to upper/lower
case.
6.1.1.2.5
Exchange Profile Configuration Using Central SLD
Problem
You are using a landscape with a central SLD and are using transaction SPROXY.
You are not sure which exchange profile will be used when pulling the data for a
connection test.
Solution
A central SLD scenario involves a central SLD, but not a central exchange profile.
The exchange profile used is always the one on the Integration Server the
application system connects to the exchange profile using the SM59 destination
LCRSAPRFC.
6.1.1.2.6
ICM_HTTP_TIMEOUT in SPROXY
Problem
While running the test reports in SPROXY and also while testing the connection
between both systems, you get the error ICM_HTTP_TIMEOUT.
Solution
Have a look at the Timeouts in XI section and check the information in SAP Note
824554 - ICM and SAP Web Dispatcher Timeout Parameter. The CSN component
for ICM timeouts and configuration is BC-CST-IC.
6.1.1.2.7
SPRX081 - No Connection to Enterprise Services Builder (Only Generic Data
Visible)
Problem
You get the above error message after calling transaction SPROXY.
Solution
Check all the prerequisites listed at the beginning of the ABAP Proxy and ABAP
Proxy Generation section. Follow the instructions from the configuration guide to
connect the business system to PI.
February 2011
65
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Make sure that, if you are using an AS <6.40 system as a business system to
connect to PI, you have the add-on installed on your system.
6.1.1.2.8
SPRX000 - Message Interface „&1‟ References External Message „&2‟
Problem
You get the above error message while trying to generate an ABAP proxy from
transaction SPROXY. You are generating the proxy in a system based on AS ABAP
6.20.
Solution
Unfortunately, the feature for creating an ABAP proxy from an external definition is
only available in SAP NetWeaver XI 3.0 and higher.
6.1.1.2.9
SPRX118 - Package &1 Does Not Belong to Component &2
Problem
You get this error when attempting to create a proxy in transaction SPROXY. You
are using the sap.com namespace and trying to generate the proxy in your own
package.
Solution
Generating proxies from the sap.com namespace into non-SAP packages is not
allowed. SAP shipped content should not be modified in any way. The guidelines are
not to edit or add any namespaces to the imported software component versions
supplied by SAP. Instead you should make the objects shipped by SAP available in
your own software component version. Once these objects are in your namespace
you should be able to generate proxies from them. However, as stated, you should
not modify any SAP shipped objects, regardless of whether this is within or outside
your own namespace.
For more information about proxy generation, see SAP Library section Proxy
Generation.
6.1.1.2.10 SPRX109 - Objects from Other Namespaces Missing. Unable to Save.
Problem
You get the above error when attempting to create a proxy in transaction SPROXY
for a service interface.
Solution
Objects that are used by an interface and are in other namespaces have to be
generated first. They cannot be generated together. Therefore, proxies have to be
generated first for the underlying objects.
66
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
6.1.1.2.11 You use the Proxy Generation Design Time, but get the Following Error
During Proxy Generation “Could not establish connection to ES Repository
by using 'SAP_PROXY_ESR ': Connection Failed:404”
Solution
As part of a security enhancement, the remote access to the Exchange Profile is
restricted. This depends on the setting of the Exchange Profile property (section
IntegrationBuilder): com.sap.aii.ib.remote.exprof.enabled
If the value of this property is false (default in SAP NetWeaver 7.3), the RFC
destination SAP_PROXY_ESR has to be used (default connection to the ESR from
the ABAP backend transaction SPROXY).
For more information, see SAP Note 1493325 (Using RFC ESR Destination for
Transaction SPROXY) and SAP Note 1486380 (Missing Authentication in Access to
Configuration).
6.1.2 Runtime
Sending and receiving of proxy messages is done using the local Integration Engine
(PI runtime) in the application system.
6.1.2.1 ABAP Proxy Runtime Troubleshooting
Problem
You have problems using the ABAP proxy runtime and you need more information
about how to trace, debug, and analyze these issues.
Analysis
If you have problems during runtime you first should check the prerequisites listed in
the ABAP Proxy section (SXMB_ADM  Integration Engine Configuration,
SLDCHECK)
Proxy Debugging and Tracing
If you have problems in the proxy runtime, you can use the debugging and trace
tools described in the How-To Guide How to Debug XI Applications (this guide is not
yet available for SAP NetWeaver 7.3 but can be used for this release).
6.1.2.2 Problems and Solutions
6.1.2.2.1
Messages Are Not Processed
Problem
Messages are not processed in the PI runtime in the application system. In
transaction SXMB_MONI the messages have status „Scheduled for Outbound
Processing‟ or „Message Recorded (Commit follows)‟ and the status does not
change.
February 2011
67
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Solution
In transaction SXMB_MONI check the entry in the Queue Status column:

If the status is „Waiting in queue‟ the RFC queue is probably not registered at
the QIN scheduler. Check if the respective queue (see the Queue ID column
in SXMB_MONI) is available in transaction SMQR and has the type R for
registered. If the queue in SXMB_MONI is XBTS0002, for example, check for
an entry XBTS* in SMQR.
If the queue does not have type R, select the queue and choose Registration.
If you cannot find the queue in transaction SMQR at all, use the queue
registration functionality in transaction SXMB_ADM  Manage Queues.

If the status is „Queue stopped‟, click the entry in the Queue ID column, and
double-click the queue until you see the entries within the respective queue.
The first one will be in an error state. Double-click the entry and you will see
the message in error. Check the error, correct it, and restart the message.
If the error cannot be corrected, cancel the message in transaction
SXMB_MONI so that the other messages in the queue can be processed.

If the message has the status „Released for Processing (WS)‟, you have to
check the bgRFC queue and the WS sequences.
In the ID column click on the bgRFC queue to get to the bgRFC queue
monitor. This displays more information about the problem/error.
To get to the Sequence Monitor, click the sequence ID in the
Queue/Sequence column. The WS sequence and the WS runtime error is
displayed.
6.1.2.2.2
HTTP_COMMUNICATION_FAILURE
Problem
You see error messages in the message monitor from transaction SXMB_MONI with
the above error message for ABAP proxy communication scenarios.
Solution
If the error is shown in the ABAP proxy sender system:
Check the SM59 HTTP connection set in SXMB_ADM  Integration Engine
Configuration. This connection is used to send the message to the PI Integration
Server. Check server, port, user, and password and choose Test Connection to test
the communication.
If the error is shown in the Integration Server:
Check the configuration parameters set in the Integration Directory receiver channel.
If a SM59 destination is used, check it as described above.
68
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Java Proxy Runtime (JPR)
6.1.3 JPR (Java Proxy Runtime) Troubleshooting
In SAP NetWeaver PI, you can use Java proxies to connect an application to a PI
system.
Problem
You have problems using the Java proxy runtime and need more information about
the configuration and use of the JPR.
Analysis
For information about how to configure the connection of the Java proxy runtime to a
PI system, see SAP Library section Integration Using the Java Proxy Runtime.
February 2011
69
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
7 Adapters
Error Tracking in the Adapter Engine (Java SE)
(Problem) Introduction
This section provides an overview of the stand-alone Adapter Engine with regard to
tracing, logging, configuration, and other support-relevant information. It does not
cover specific errors, but describes the means of analysis within the Adapter Engine
(Java SE). The following information helps you to localize errors and/or provide
support with all relevant information.
The Adapter Engine (Java SE) differs from the Adapter Engine (Java EE). It
is a stand-alone tool that runs on its own Java Virtual Machine. It can be
installed on any business system and is delivered with XI 2.0 (as the only
Adapter Engine), as well as with XI 3.0/PI 7.0/PI 7.1 [including its
enhancement packages]/SAP NetWeaver 7.3 (in addition to the Adapter
Engine (Java EE) and the PCK). Apart from a few exceptions, the handling
and the functionality in XI 3.0/PI 7.0/PI 7.1[including its enhancement
packages]/ SAP NetWeaver 7.3 is the same.
Folder Structure
The following file structure is created during the installation of the Adapter Engine:
Tech_adapter (contains run_adapter and logging.properties)
 Administration
 Base configuration
 Configuration (contains configuration files)
 Data
 LogFiles (contains logs and traces)
 PersistLayer
These folders contain all relevant information for supporting the Adapter Engine and
are referred to in the following sections. Parts of the files can be displayed using the
browser interface of the Adapter Engine; this is explained in the relevant file
description.
Logs and Traces
In general, the Adapter Engine writes two types of log: one contains general
information about processes in the Adapter Engine, the other contains adapterspecific information.
The Adapter Engine log is written in the Adapter_<number>.log. These files are
located in the file system in the LogFiles folder and can be viewed either by opening
the respective file at the operating system level or by starting the browser interface of
the Adapter Engine (http://<host>:8200) and navigating to Traces. You configure
their quantity and size by using the file tech_adapter -> logging.properties. The
70
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
default values are five files (Adapter_0.log to Adapter_4.log) with a size of 2 MB
each. Once five files of 2MB each exist, the files are overwritten. If an error occurs,
we recommend saving the log files immediately.
The adapter-specific log is written to the <Name_of_adapter>.log. These files can
be found in the Log Files folder. Unlike the Adapter_<number>.logs, this type of log
is not meant to be read at operating system level, but by using the browser interface
of the Adapter Engine and clicking the name of the specific adapter. There is only
one file for each adapter, which is overwritten as soon as the respective adapter is
restarted. If an error occurs, save the log file immediately; do not restart the adapter
until you have done so. You can restrict the size of the file by using parameters,
which are described in the documentation of the Adapter Engine (minimum version
XI 2.0 SP5, the parameters are called maxViewSize, maxFileSize, archviveFiles).
Special information for the RFC adapter: In addition to the adapter-specific
information that is contained in the rfc_adpater.log file, the RFC adapter writes a
trace file called Adapter_rfc.log. This is the default name and must not be changed. It
is set using the RFCAdapter.traceFile parameter and contains valuable information
about errors in the RFC adapter.
Trace Level
To track errors, it may be necessary to increase the trace level of the respective logs
and to reproduce the error to receive further and more detailed information about the
error. This is achieved as follows:
For the Adapter Engine logs, use the logging.properties file to set the respective
location to a sufficient trace level. For example: The following error is reported in an
Adapter_<number>.log:
“Sep 22, 2004 11:36:43... ...i.messaging.adapter.File2XMBProcessor [fileprocessor]
Error: Unexpected exception running file2xmbprocessor
Java.lang.NullPointerException”.
To increase the trace level, edit the logging.properties by adding the following line:
“com.sap.aii.messaging.adapter.File2XMBProcessor.severity=DEBUG”.
Restart the Adapter Engine to apply the new settings.
The scope of information in the adapter-specific logs cannot be changed.
To increase the trace level for the RFC adapter, set the RFCAdapter.trace
parameter in the RFC adapter configuration. The levels are as follows:
0 = none, 1 = error, 2 = standard, 3 = request, 4 = payload, 5 = binary payload
outbound.
Note that at trace level 5, the JCo trace is activated as well. The output of this
JCo trace can be found in the tech_adapter folder and has the name
JCO<number>.trc.
February 2011
71
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Configuration Files
You set the parameters for each adapter by using the Configuration button on the
Web interface of the Adapter Engine. This information is saved at operating system
level in the Configuration folder. The name of the configuration file corresponds to
<adapter_name>.properties. In the event of an error, copy this information to the
message for your support organization or SAP.
Additional Information
The following additional information may be useful when analyzing a problem in the
Adapter Engine and you must therefore make it available to support organizations.
 Version of the Adapter Engine. To determine the version, open the Web
interface and navigate to About Adapter Engine. Choose General Information
to display the version as the parameter name Adapter Engine (for example,
2.0.1412).
 Version of the JDK. Navigate as above to the Java.runtime.version parameter
in the General System Information.
 Class path and VM parameters used by the Adapter Engine. This information
can be found in the run_adapter.<OS_specific_type> file, for example
run_adapter.bat for Windows.
SDN: Web Logs
For frequently asked questions (FAQs) about adapters in the Adapter Engine (Java
SE), see the SAP Developer Network (SDN).
Error Tracking in the Adapter Engine (Java EE)
Problem
You need information about how to increase the trace level and find the error
messages and more information about the errors in the Java EE-based adapters
(File, JDBC, JMS, RFC, BC, SOAP, Mail, Marketplace, RNIF, CIDX, HTTP_AAE,
and IDoc_AAE).
Analysis
Version of Adapter Engine
For a description of how to find your Adapter Engine version, see SAP Note 784471 Determining Installed Adapter Framework Version.
Adapter Monitoring
For an initial check of your configured channels and to check whether they can be
started without errors, use adapter monitoring:

72
Logon to the SAP NetWeaver Administrator (http://server:host/nwa) and
choose SOA  Monitoring  PI Communication Channel Monitoring. The
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide




channel information is available in the monitor after the communication
component and the channel have been successfully activated. However, in
the case of the SOAP adapter, the adapter status is not available until the
first request is sent to the adapter. For more information, see SAP Note
1000528 (FAQ: XI 3.0 / PI 7.0 Adapter and Channel Monitoring You could
also perform the above checks using the Runtime Workbench
In the Runtime Workbench http://server:port/rwb, choose Component
Monitoring and select Components with Status All.
Choose Display.
Select the appropriate Adapter Engine.
Choose Communication Channel Monitoring.
Audit Log (Message Details)
If you have problems during message processing in the messaging system, first
check the audit log (message details) of the respective message. You can find this
detail in NWA and also in Runtime Workbench [RWB] monitoring:
NWA:
Logon to the NWA (http://server:host/nwa) and choose SOA  Monitoring 
Message Monitoring on tab Message Status Overview.

Design your search on the Time range.

Choose GO.

Select your message using the correct selection parameter based.

Status Value tab is generated for your Selection.

Based on your selection click on the message count under the column
Number which opens the corresponding Message Details section.
February 2011
73
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
RWB:
http://server:port/rwb





Choose Message Monitoring.
Select the appropriate Adapter Engine.
Choose Display.
Select your message using the correct selection parameter.
Choose Details.
For more information about the audit log, see SAP Note 751915 - Differences
between trace, log and audit log.
Log File
For more information about errors, check the following log file:
/usr/sap/[SID]/[Instanz]/j2ee/cluster/server[N]/log/applications.[n].log
Use the NWA Log Viewer to analyze this file.
For more information about the log file, see SAP Note 751915 - Differences between
trace, log and audit log.
Increasing the Trace Level
If you need more information about the error or problem, you can increase the trace
level of your adapter and check the relevant trace file. This is described in SAP Note
761921 - Creating an XI adapter framework trace file.
For more information about the trace file in general, see SAP Note 751915 Differences between trace, log, and audit log.
JCO Trace in RFC Adapter
For a description of how to get a JCO trace for the RFC adapter, see SAP Note
793434 - Enabling JCO trace while using XI 3.0 RFC adapter.
74
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
SDN: Web Logs
For frequently asked questions (FAQs) about adapters and the Adapter Framework
runtime, see the SAP Developer Network (SDN).
PAS: Message Failed on the Adapter Engine
Problem Description
An XML message is successfully sent from the Integration Server (IS) to an Adapter
Engine (AE). The delivery semantic is exactly once (EO). The payload of the
message can be an IDoc or any other payload. The problem occurs on the AE, which
means that the message was successfully delivered from the IS point of view. The
XML message monitor shows the processed successfully flag, as shown below.
When the XML message has successfully arrived at the Adapter Framework, the AE
processes the message and passes it to the file adapter. The file adapter writes the
XML message to the file system, as shown below.
Integration
Integration Server
Server
Integration Engine (ABAP)
IDOC
Adapter
Adapter
Pipeline Services
Adapter
Adapter
Adapter Engine
Engine Java EE
Adapter Engine (J2EE)
File Adapter
File
File
System
System
Basics
February 2011
75
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
If the XML message was successfully delivered to the Adapter Engine, it can be
monitored with the message monitor in SAP NetWeaver Administrator or in the
Runtime Workbench (RWB).
http://<Host>:<PORT>/nwa
SOA  Monitoring  Message Monitoring
or
http://<Host>:<PORT>/rwb
Message Monitoring
The AE receives the message, processes it, and forwards it to the receiver (that is,
the file adapter). While the AE processes the message, it passes several statuses:

TO_BE_DELIVERED:
The status of the message when it is initially handed over to the AE.

DELIVERING:
The status of the message when it has left the AE queuing system and is in the
process of being transmitted across the wire or delivered to an application.

DELIVERED:
The status of the message when it has successfully reached its intended
receiver.

HOLDING:
The status of an EOIO message that cannot be delivered until its predecessors
have been delivered.

SYSTEM ERROR:
The status assigned to a message when all attempts (retries) to deliver the
message to its receiver have failed.

CANCELED WITH ERROR :
The status assigned to a message when an administrator decides to abort the
sending of the message, or when a message could not be delivered due to a
fatal exception that cannot be repaired.

WAITING:
The status of a message where at least one attempt to send it has failed, and it
is currently waiting for another attempt.

ALL CONTAINING ERRORS
The status of “System Error” and “Canceled with Error” messages.

Unknown
Not used at the moment.
76
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
In this scenario you should see only the statuses WAITING, DELIVERING,
NON_DELIVERED, or DELIVERED. Statuses such as HOLDING or FAILED usually
happen only for delivery semantics EOIO (exactly once in order) or BE (best effort).
TO_BE_DELIVERED occurs when the message is put into the AE receive queue.
This is done using the AE receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCO
L>
The AE returns HTTP 200 to the Integration Server only if this was executed
successfully. In this example scenario, the status TO_BE_DELIVERED should not
appear since we assume that the IS has successfully called the servlet.
The status is updated from TO_BE_DELIVERED to DELIVERING when
the message has left the receive queue and the event handler lookup
was successful. Therefore, there is a small gap where
TO_BE_DELIVERED may remain in the message monitor even though it was
has been from the IS successfully. However, this is outside the scope of
this document.
The other four statuses appear in the following order:

Message status DELIVERING
When the message has left the AE queuing system and the lookup of the event
handler was successful, the message gets the status DELIVERING. This
status is kept while the message is transmitted across the wire or delivered to
an application. Usually the message only has this status for a short time period
and you would not see it. However, this status could be visible in cases where
an HTTP response takes a long time, for example.

Message status WAITING
When the first attempt to deliver the message has failed (a recoverable
exception arose), the message is usually rescheduled and the status is
updated to WAITING. As long as the message is in this status, the AE tries to
deliver the message according to the configured retry settings (default 3
retries).

Message status NON_DELIVERED
If all retries were unsuccessful, the message gets this status. It is possible to
restart message processing from this status.

Message status DELIVERED
This is the final status if the message has been delivered successfully.
Analysis
The message monitoring is the central tool for monitoring XML messages on the
Adapter Engine.
Go to SAP NetWeaver Administrator  SOA  Monitoring  Message Monitoring,
choose Database tab.
February 2011
77
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
It shows all messages that have been processed in the Adapter Engine. With the
standard filter criteria, you can look for messages that have been processed in a
given time interval and that have a given status. By using the advanced filter criteria,
you can refine your search, for instance by specifying asynchronous inbound
messages from a specific partner.
In error situations, perform the following steps:

Inspect the message details, in particular the message log. The message log
contains information about the executed processing steps in the Adapter Engine.
Often, it shows details about the error. You can also access the XML message
down to its message bytes and check if all partners and other factors are set as
expected. The figure below shows an example.

If you do not find information about the error in the XML message audit log,
check the logs and traces of the underlying AS Java. You access this log file
through SAP NetWeaver Administrator:
http://<Host>:<PORT>/nwa
Troubleshooting  Logs and Traces  Log Viewer
From the Show View drop down open view System Logs and Traces. If
appropriate, specify filter criteria, such as severity or expected text fragments in
the message, to narrow down the relevant log/trace entries. Select the log entry
78
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
and then expand the node of the log to see details. If you may need further
details you may choose the options under Related Logs.

If this does not explain the problem sufficiently, increase the trace level and
reproduce the problem. Navigate to http://<Host>:<PORT>/nwa
Troubleshooting  Logs and Traces  Log Configuration, and increase the
severity of the Tracing Location com.sap.engine.messaging to DEBUG.
Propagate the severity to the subtree and save your settings. Also increase the
severity for other locations according to your scenario, for example
com.sap.aii.adapter.file if the file adapter is involved. If you are not sure which
components are involved, increase the severity of the PI parent location
com.sap.aii.
February 2011
79
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Then, restart message processing by using the message monitor in SAP
NetWeaver Administrator. Select the message and choose Resend.
Detailed error and debug messages are then displayed. Access the log/trace viewer
and search for traces with severity ERROR, WARNING, or stack traces.
Do not forget to reset the severity to ERROR again after your analysis.
Use the parent location com.sap.aii and com.sap.engine.messaging
again and copy the ERROR severity to the subtree. Save the setting. A
DEBUG trace level can slow the system down.
FAQs about Adapters
PI has an Adapter Engine that runs on the AS Java Engine of the SAP NetWeaver
Application Server. It contains several adapters:
JMS, File, JDBC, RFC, SOAP, Marketplace, Mail, BC, RNIF, CIDX, XI
These adapters run as services in the AS Java Engine, and are configured in the
Integration Directory by using sender and receiver channels.
Problem
80
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
You want to know more about the Adapter Engine (Java EE) and the adapters it
contains.
Solution
You can find more information about the messaging system and the different
adapters in the Adapter Engine in the following SAP Notes:
821268 XI 3.0 Adapter Framework: Overview of available FAQ notes
816022 FAQ XI 3.0 J2EE Adapter Engine/Messaging System
813993 FAQ: Message status in the adapter framework
774854 FAQ XI BC Adapter
730870 FAQ XI 3.0/ PI 7.0/ PI 7.1 RFC Adapter
821267 FAQ: XI 3.0 / PI 7.0/ PI 7.1 File Adapter
831162 FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter
856346 FAQ: J2EE JMS Adapter
1099720 XI JMS Adapter and TIBCO EMS: FAQ
1086303 XI JMS Adapter and IBM Websphere MQ: FAQ
1086306 XI JMS Adapter and JBoss AS: FAQ
1090516 XI JMS Adapter and BEA Weblogic JMS: FAQ
856597 FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter
856599 FAQ: XI 3.0 / PI 7.0 / PI 7.1 Mail Adapter
870270 FAQ note for initiating support related to Ispeak (CIDX, RNIF)
1039369 FAQ XI 3.0/7.0 Axis Adapter
1000528 FAQ: XI 3.0 / PI 7.0 Adapter and Channel Monitoring
854536 XI 3.0 / PI 7.0 AF: Information Required by SAP Support
The configuration of the mail adapter is described in the guide How to Use the Mail
Adapter. (This guide is not yet available for PI 7.1 but can be used for this release.)
The configuration of the SOAP adapter is described in the guide How to use the XI
3.0 SOAP Adapter. (This guide is not yet available for PI 7.1 but can be used for this
release.)
How to monitor RNIF and CIDX scenarios is described in the guide How To Monitor
Industry-Speak Scenarios.
Important PI adapter service properties (service XPI Adapter: XI) are described in
SAP Note 791379 - XI Adapter Service Properties Documentation.
February 2011
81
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
The properties of the messaging system service XPI Service: Messaging System are
described in SAP Note 791655 - Documentation of the XI Messaging System Service
Properties.
The properties of most of the PI services are described in SAP Library section Java
Service Properties for the Adapter Framework and the linked sections.
FAQs about the deployment of the adapter framework are described in SAP Note
830039 - FAQ: Deployment of the XI Adapter Framework.
IDoc Adapter (Advanced Adapter Engine)
SAP NetWeaver Process Integration supports the integration of components based
on intermediate documents (IDocs) by providing the IDoc adapter.
In releases prior to SAP NetWeaver 7.3, the IDoc adapter runs only on the
Integration Engine (based on AS ABAP).
From SAP NetWeaver 7.3, also the Advanced Adapter Engine provides an IDoc
adapter (based on AS Java). This adapter type is called IDoc adapter (AAE)
(technical adapter type in Integration Directory IDOC_AAE).
For more troubleshooting information, see http://wiki.sdn.sap.com/wiki/x/sQGADw.
Problem
Receiver channel throws exception while processing IDocs with exception String
”The Configuration for Sender/Receiver Partner Number/Port is incorrect. Enter
proper values in Sender/Receiver Component”
Solution
1. Set the adapter-specific attributes for XI Service and XI Party. To do this, in the
business component menu choose Adapter-Specific Identifiers.
82
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
2. Pass control record in the idocxml.
If no control record is present, the adapter-specific attributes are used to set control
of the IDoc document.
Problem
IDoc Communication channel status is GREEN [running successfully]; however, it
has different status per node in a cluster environment.
Solution
1. It is sufficient for IDoc to be started in only one of the nodes. It would ensure
load-balancing and fail safety internally via the SAPJRA layer.
2. Stop and Start IDoc channel.
February 2011
83
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
3. Check any channel lock (NWA Troubleshooting  Locks  SAP/PI/IDOC
(Lock context). If a lock is not released for long time with same lock id, the
reason for the problems might be in the channel configuration. Delete lock and
stop channel manually. (The lock id is same as channel id.)
Problem
Channels are in error state with message “Default destination not started.”
Solution
Create Default destination XI_IDOC_DEFAULT_DESTINATION in NWA 
Configuration  Infrastructure  Destination.
Perform the following steps:
1. Choose Create.
2. Enter Destination name (XI_IDOC_DEFAULT_DESTINATION)
3. As Destination Type, enter RFC.
4. Choose Next.
5. Enter connection and transport security setting as shown in the screenshot
below (details of PI systems being used) and choose Next.
6. Enter Logon Information as below and choose Finish.
84
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Problem
Channels start with warning XI IDOC_DEFAULT_DESTINATION_<SID> destination
not started.
Solution
Create destination XI_IDOC_DEFAULT_DESTINATION_<SID> if you do not want to
use XI_IDOC_DEFAULT_DESTINATION for metadata.
Problem
IDoc has been sent from sender and messages are flowing via sender
communication channels but neither IDoc is received on receiver nor are messages
sent via receiver communication channel.
Solution
This might happen in case on sender side EOIO is enabled with queue name. Check
in message monitoring for messages by using the relevant queue name. There might
be some old messages which are in holding state and hence further processing is
not happening. Either cancel or resend all the messages and then message for
current scenario will be resent.
Problem
Error while channel start with exception as:
com.sap.conn.idoc.IDocRuntimeException:
com.sap.aii.af.idoc.exception.IDOCAdapterException:
com.sap.aii.af.idoc.exception.IDOCAdapterException: com.sap.aii.af.idoc.exception.
IDOCAdapterException: No ServiceIdentifier available for channel, with party = <>
and service = <>
Solution
In the communication component, check that Adapter-Specific Identifier are
maintained. If not, maintain them (See screenshot for first problem to know how to do
this) and perform a Stop- Start cycle for the channel.
February 2011
85
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Attachment Support in Adapters
Problem
You are having difficulty implementing integration scenarios using attachments.
Beside of the message payload you want to use additional attachments and you are
not familiar with the handling of attachments in SAP PI.
The given documentation is unclear or you detect missing functions.
Introduction
A list of adapters that support attachment handling can be found in see SAP Library
section Adapter Configuration.
Solution
File Adapter
For the sender file adapter the Additional File(s) indicator can be used as described
in SAP Library section Specifying Additional Files in the Sender File Adapter.
For more information about the Adapter Engine (Java SE) sender file adapter, see
SAP Library section Configuring the Sender File/FTP Adapter.
SOAP Adapter
For the sender/receiver SOAP adapter the conversion parameter "Keep Attachments"
must be set to allow attachments to be included.
For the Adapter Engine (Java SE) you have to set “XMBWS.KeepAttachments” to true.
Mail Adapter
For the sender/receiver mail adapter you must have selected XIPAYLOAD as the
message protocol and use the conversion parameter "Keep Attachments".
For more information about using the mail adapter with attachments, see the HowTo-Guide How to Use the Mail Adapter, unit 3.2.4 Sending a Mail with Attachment.
(This guide is not yet available for PI 7.3 but can be used for this release.)
Additional questions related to mail adapter attachments (for example: Can I choose
the name of an attachment in the mail? How can I set the file name of a mail
attachment?) are listed and answered in SAP Note 856599 - FAQ: XI 3.0 / PI 7.0 / PI
7.1 Mail Adapter.
General
The adapter module PayloadSwapBean is useful when you want to replace the
application payload of the XI message that contains the business data with another
payload that is appended to the XI message as an attachment. For more information,
see SAP Library section Adding PayloadSwapBean in the Module Processor.
86
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Additional information regarding this adapter module is also available in SAP Note
794943 - XI 3.0 Adapter Framework Payload Swapping Module.
If you want the attachment name to be passed and evaluated in PI, the following
SAP notes explain in more detail the relationship between the payload name and the
content description and what you can do to manipulate the attachment accordingly:
SAP Note 779981 - Changing Content Type in Mapping
SAP Note 960502 - XI payloadName and Content Description Relationship
SAP Note 1020191 - Change Content Type of an XI Message in Mapping
Analysis Support Tool
For detailed troubleshooting of your scenario, for example the data transfer of the
external communication, you can use the data analyzer tool TCPGateway. The tool
and more information can be found in SAP Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI
7.1 SOAP Adapter, question „How can I trace the whole message?‟.
Alternatively, you can use any other TCP/IP sniffer tool available in your
organization.
Message and Channel Monitoring in Adapter Framework
The message exchange in the adapter framework has to be monitored in the
NetWeaver Administrator based SOA monitoring.
http://<hostname>:<port>/nwa SOA  <list of monitors>
There are several different monitors with special views of the message exchange.
Problem
You want to know more about the monitoring possibilities for channels and message
exchange in the Adapter Engine (Java EE) and the adapters it contains.
Solution
Communication Channel Monitor
To monitor the adapter channels, you can use the Communication Channel Monitor,
which can monitor configuration errors as well as connection issues. For more
information, see SAP Library section Monitoring Communication Channels. More
information can be found in SAP Note 1000528 - FAQ: XI 3.0 / PI 7.0 Adapter and
Channel Monitoring.
NWA-based Channel Monitoring
February 2011
87
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
RWB-based Channel Monitoring
Message Monitoring
You monitor message exchange in the Message Monitoring. Here, all messages
processed in the Adapter Engine can be found, and restartable messages can be
edited, restarted, or cancelled.
88
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
NWA -based Message Monitoring
RWB-based Message Monitoring
PI Message monitoring also provides an overview monitor, which shows the number
of messages in different statuses for selected interfaces
February 2011
89
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
NWA-based Message Overview
RWB-based Message
Overview
90
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Message Statuses Available
The message status set in the adapter framework can be TBDL (to be delivered),
DLNG (delivering), DLVD (delivered), WAIT (wait), HOLD (hold for EOIO), FAIL
(failed), and NDLV (not delivered). They are described in detail in SAP Note 813993
- FAQ: Message Status in the Adapter Framework.
DLVD and FAIL are final statuses that cannot be changed. DLNG is a temporary
status during message processing; it cannot be changed. TBDL is also a temporary
status but can be restarted to bring the message to the front of the processing queue
when a large (backlog) queue exists. WAIT and NDLV are set for messages in error;
these messages can be restarted or canceled.
The HOLD status is set for an EOIO message whose predecessor has not yet been
successfully processed. These messages are restarted automatically when the
predecessor is restarted. If the predecessor message is canceled, the HOLD
messages can be restarted or canceled. Note that canceling EOIO messages goes
against the "Exactly Once In Order" delivery semantics. Only use this option in
emergency situations that cannot be solved in any other way and make sure
beforehand that the applications involved can handle this behavior.
Backlog Monitor
To check the messaging backlog, a cluster-wide channel backlog monitor is
integrated into the NWA-based monitoring and Runtime Workbench; you access this
monitor by choosing “PI Adapter Engine Status” with NWA or „Engine Status‟ in the
component monitoring for the specific adapter engine in RWB.
NWA-based Backlog Monitor:
RWB-based Backlog Monitor:
February 2011
91
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
The „Backlog‟ tab shows how many messages are in the queue for a specific sender
or receiver service. They are divided into the following groups:

EOIO Backlog
This group counts the number of messages that are currently in status HOLD.

Processing Backlog (with errors)
This group counts the number of messages that are currently in status WAIT.

Processing Backlog (without errors)
This group counts the number of messages that are currently in status TBDL
and DLNG.

Error Backlog
This group counts the number of messages that are currently in status NDLV.
If you choose „Monitor‟, it is possible to propagate the backlog to CCMS and to
define threshold values there to get alerts in case of a high backlog in Adapter
Engine message processing. For more information, see SAP Library section
Displaying Technical Data for the Adapter Engine.
Availability Time Planning
92
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
You can plan availability times for communication channels to enable them to be
started and stopped automatically. It is possible to activate and deactivate channels
for certain time periods.
The monitor is accessible in the NWA based monitoring via the PI Communication
Channel Monitoring  Availability Planning tab.
For more information, see Planning Channel Availability.
The monitor is in the Runtime Workbench Component Monitoring for the Adapter
Engines. Choose „Communication Channel Monitoring‟ and follow the link
„Availability Time Planning‟.
February 2011
93
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Local Message Processing on the Advanced Adapter
Engine
Using integrated configuration you can define local message processing on the
Advanced Adapter Engine. The Advanced Adapter Engine provides mapping and
routing for this locally. Message processing is executed on the Advanced Adapter
Engine from one adapter to another without the involvement of the Integration
Engine. This can result in significant improvements in performance.
For local message processing, the central as well as the non-central Adapter
Engines can be used.
You can implement all adapters on the Adapter Engine for local message processing
on the Advanced Adapter Engine.
If you do not use the integrated configuration, message processing will continue to
be performed using the Integration Engine
Problem
You need information about how to increase the trace level and find the error
messages and more information about the message transfer in the Advanced
Adapter Engine.
Analysis
For more information about the Advanced Adapter Engine, see the guide How-To
Configure Integrated Configurations in the Advanced Adapter Engine and SAP
Library section Advanced Adapter Engine.
To get started with the Advanced Adapter Engine Configuration, execute the Simple
Use Case (7.3) - Variants 8 to 13 for the Advanced Adapter Engine and/or Simple
Use Case (7.3) for de-central Advance Adapter Engine
Error Tracking in the Adapter Engine (JavaEE)
Since the Advanced Adapter Engine is technically the same as the „old‟ J2EE
Adapter Engine, for more information about error tracking in the Advanced Adapter
Engine, see Error Tracking in the J2EE Adapter Engine.
The routing and mapping information can be found in the Runtime Workbench
(RWB)  Message Monitoring for the configured Adapter Engine. Select the
message and check the Details  Audit Protocol.
FAQs About Adapters
Since the adapters used in the Advanced Adapter Engine are identical to the ones in
the central Adapter Engine, for more information see FAQs about Adapters.
94
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Adapter Monitoring
Since processing in the Advanced Adapter Engine is done using the Adapter Engine,
monitoring is done using the RWB. For more information, see Message and Channel
Monitoring in Adapter Framework.
Problems and Solutions
7.1.1.1 Using SAP .NET Connector Programs Together with PI Not
Allowed
Problem
Using PI in combination with the .NET Connector is not allowed. The .NET
Connector is not released for communication with external RFC client/server
programs. It is only released to communicate directly with SAP back ends. For more
information, see SAP Note 756754 - External Communication with RFC.
You are looking for alternative ways to connect your .NET programs to PI.
Solution
The connection to the Microsoft Studio is officially only possible by integrating PI
interfaces as Web services using the SOAP or plain HTTP adapter (SAP NetWeaver
PI 7.1) or the communication channel with adapter type WS (EHP 1 for SAP
NetWeaver PI 7.1 and later).
You can implement an alternative connection between .NET and PI as explained in
the article “Looking for replacing SAP.NET connectors with SAP XI?”:
http://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131
“Reliable Messaging between SAP XI 3.0 and Microsoft BizTalk Server 2004
using SOAP-compliant Communication”:
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7521a237-07010010-499b-b3285b789c0d
IDoc Adapter
7.1.2 FAQs About the IDoc Adapter
The IDoc adapter converts IDocs to XI messages and XI messages to IDocs to
enable communication between PI and systems that can only send and receive IDoc
messages.
The IDoc adapter runs in the ABAP part of the PI system and is called by using the
RFC protocol. The outbound IDoc sends the IDoc to the receiving system using the
tRFC protocol.
February 2011
95
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Problem
You want to know more about the IDoc adapter, how it must be configured, and how
to analyze errors.
Analysis
The configuration of IDoc exchange in the business and PI system is described in
SAP Library section Integration Using the IDoc Adapter (Integration Engine).
The guide How to Configure the IDoc Adapter (not available yet for PI 7.3, but you
can still use the guide for XI3.0) provides a step-by-step description of the
configuration of the IDoc adapter.
The guide How to Sample IDoc-XI Scenarios (not available yet for PI 7.3, but you
can still use the guide for XI3.0/7.0) gives some examples of how to configure
different IDoc-XI-IDoc scenarios using alternative identifiers and header mappings.
For a description of how to work with acknowledgments in IDoc scenarios, see the
guide How to Handle Acknowledgments for IDoc (not available yet for PI 7.3, but
you can still use the guide for XI3.0/7.0). SAP Note 777175 - IDoc Adapter:
Requesting Acknowledgments describes how to determine whether the IDoc adapter
requests an acknowledgment or not.
The procedure for converting IDoc partners to PI partners is described in SAP Note
792333 - IDoc Adapter: Converting Partners.
SAP Note 728792 - IDoc Adapter: Fields of the IDoc Control Record describes how
PI handles the IDoc control record.
7.1.3 PAS: Sending an IDoc Through PI Failed
Problem Description
An application sent an IDoc through PI. The respective message did not arrive at the
receiver system.
Example Scenario
96
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Backend
Backend System
System
XI Integration Server
Integration Engine (ABAP)
SAP
SAP
System
System ALE
IDoc
Adapter
Pipeline Services
XIAdapter
AdapterEngine
Engine
Adapter Engine (Java)
File Adapter
Backend
Backend System
System
(Non
(Non SAP)
SAP)
File
File
System
System
An application sent a message through PI. The message was sent as an IDoc and
the IDoc number is known. The message should have been transformed on the
Integration Server into an XI message, sent to the file adapter, and stored in the file
system, from where it is retrieved by a non-SAP application.
Possible Error Causes

Incorrect configuration in the Integration Directory, for example incorrect
routing

Incorrect technical configuration of PI, for example the IDoc adapter is not
properly configured

Problems in underlying technologies, for example the file system is full.
Main Tools: SAP NetWeaver Administrator
Transactions: IDX1, IDX5, SXMB_MONI, SM58, SM21
Analysis
For an overview of analysis steps see the flow chart.
February 2011
97
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
...
1. Gather Information About the Failed IDoc/Message
In this step you need to get the relevant information to track the document through
PI, that is, to find out the path the failed document took from sender to receiver.
Let us assume that the initial information includes the sender system SID, the time
the IDoc was sent, and the sender message type.
2. Find the Location of the Failure
Try to find out in which PI component the error occurred. Candidate components
depend on the scenario used. The standard scenario involves a sender system, the
Integration Server (IS), and a receiver system. Basically, there are two ways to find
out in which system the error occurred: Use end-to-end monitoring, or search
through the systems step-by-step beginning with the sender, then the IS and finally
the receiver system by using the individual monitoring tools.
98
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Here we describe the individual monitoring (step-by-step approach), in other words,
we inspect the component-based monitoring tools in succession, from the sender
through the Integration Server and Adapter Engines to the receiver. The analysis
starts with the sender system and proceeds towards the receiver. In the scenario
described here, this process begins with checking the IDoc status in the sender.
3. Check the IDoc Status on the Sender
Call transaction WE05 in the sender system. Either set an appropriate time frame or
enter the IDoc number to see if the IDoc was sent.
Once you have made a selection, you see a screen with the IDoc and its statuses.
You can see if the IDoc has been successfully passed to TRFC handling.
If transaction WE05 says that the IDoc handling was successfully passed to TRFC
(IDoc status 03), look in transaction SM58 in the sender system for errors in function
module IDOC_INBOUND_ASYNCHRONOUS. For instance, you may find the
following entries:
Function Module:
IDOC_INBOUND_ASYNCHRONOUS
Target System:
<destination>
Date:
03.01.2007
Time:
14:02:22
Status Text:
Transaction IDX1: Port <port>, Client
<client>, RFC destination contains errors
The following are possible error causes at the receiver:

Port/client not assigned to an RFC destination
Call transaction IDX1 and check that an RFC destination is maintained for
the port <port> and the client <client>.
For IDocs that are sent from SAP systems, the port is assembled from the
prefix SAP and the SID of the SAP system.
Check whether the RFC destination has been entered correctly.
February 2011
99
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide

The RFC destination contains errors (for example, the user does not have
required authorizations)
Use transaction SM59 to check the RFC destination.
Errors Caused by Incorrect IDOC Configuration on IS
If the IDoc adapter is not properly configured on the Integration Server, these errors
become visible at the sender system. Check transaction SM58 for failed IDoc function
modules. In the case of authentication or authorization errors, you can also find
information in the system log (transaction SM21).
Possible errors:

Destination for reading metadata not defined in transaction IDX1


4
Reading of IDoc metadata by the IS failed due to authentication,
authorization, or other technical problems. You can check if loading the
metadata works in transaction IDX2.
Check XI Message on Integration Server
If the IDoc arrived at the IS, it is transformed into an XI message. Hence, failures are
always visible in the message monitor. The message monitor can be accessed using
transaction SXMB_MONI or the Web browser (Runtime Workbench).
If you know already that the Integration Server is the location where the message
failed (having used end-to-end monitoring to locate the error-causing system) you
can skip section 4.1.
4.1 Determine Whether Error Occurred on the IS
Check IDoc in IDX5
Log on to the PI system and check the inbound queue to see if the IDoc was
received. To do this, use transaction IDX5. You must enter the time frame in which
the IDoc was sent. In the figure below you can see the output of transaction IDX5.
MessageID is the GUID of the PI system for this particular IDoc. The IDoc number is
the IDoc number as stored by the Integration Server. Transaction ID is the
transaction ID which is used in the sending process of the IDoc.
100
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Check Associated Message in SXMB_MONI
When you double-click the entry in IDX5, the system navigates to transaction
SXMB_MONI, where you see details of the faulty message. See the following section
for how to proceed further.
4.2 Find Error Cause
Open the detail view of the error message. There are different ways to display the
detailed message view:

Navigate directly from end-to-end monitoring

Navigate through the message list, and then select the error message. In
the detail view, inspect the error header of the message.
In the example above, you can see the error code
OUTBOUND_BINDING_NOT_FOUND, with an explanatory text:
No receiver agreement found for sender INLD50033057,PIP0C2_R0102_Responder and
receiver
U6X,PIP0C2_R0102_Initiator,http://sap.com/xi/RosettaNet/PIP0C2_R0102,Asynchronou
sTestConfirmationAction
When errors occur in the Integration Engine, this information can help you to find
problems. Typical error categories are described in the subsequent sections.
4.2.1
Possible Configuration Errors
Error in Inbound Processing
No business systems are defined in the SLD for the sender system ID and client.
Therefore, the communication component in the Directory does not contain the
correct SID and client. As a consequence, the transformation of the IDoc to the XI
message fails.
Routing Error
If the receiver of a message cannot be determined, this may have two causes:
The definitions in the Integration Directory are inconsistent or incomplete.
February 2011
101
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Example:
For a given set of message header information, no receiver
determination has been defined; this message cannot then be delivered.
This is also the case if the physical address information is undefined or
incorrect (wrong URL, wrong user).
The technical base configuration is wrong.
Example:
The target business system used in a receiver determination is not
defined in the SLD, or the user for logging on to the target system does
not have the required authorizations.
You find the receiver determined by the Integration Server in the element
<SAP:RECEIVER> of the main header. The addressing information is
computed in the pipeline step Technical Routing and entered in the
OutboundBinding header.
The following are typical routing error situations:
No outbound binding found
Correction: Define an outbound binding for this message in the
Integration Directory. Restart the message.
No receiver agreement found
Correction: Define receiver agreement in the Integration Directory.
Restart the message.
Wrong physical address
After successful execution of the pipeline step Technical Routing, the
OutboundBinding message header specifies the technical address in the
ChannelAttributes element. The physical address can be specified by
means of an SM59 destination, or by defining the target URL directly in
the header. In the former case, call transaction SM59 and check the
destination specified. In the latter case, check whether the attributes in
the header define a valid target address.
Mapping Error
The analysis of mapping problems is described in more detail in section Error
Analysis of Mapping Problems and the problem analysis scenario Mapping fails for a
certain Message Type.
102
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Problem with Cache Update
The analysis of caching problems is described in more detail in section Analysis of
Cache Problems and the problem analysis scenario Mapping fails for a certain
Message Type.
Outbound Adapter
Here, the relevant pipeline step in the message monitor is Call Adapter. A number of
HTTP communication errors may occur. For further analysis of the problem cause,
see the HTTP documentation on error codes.
Depending on the error code, you may have to check the address that has been
determined in the pipeline step Technical Routing and that can be found in the
outbound binding. Check whether the address points to the intended receiver (in our
scenario, the intended receiver is the Adapter Engine) and that the authentication
data is valid. If the outbound binding refers to an SM59 destination, you can test the
connection by calling transaction SM59.
In the case of authentication or authorization errors (HTTP error codes 401, 403),
make sure that the user and password are defined on the receiver (in the Adapter
Engine), and that the user has the appropriate role (the user needs to have the role
SAP_XI_IS_SERV_USER_MAIN).
Low-Level Technical Problem
Possible error causes are an incorrect message format or an unavailable code page.
In this case you have to analyze the problem further together with technical experts.
February 2011
103
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
4.2.2
Check Integration Server Queues to See Whether Message Is Stalled
If the message that has not yet been delivered is not in an error state, this is
probably because the message is blocked in the qRFC queues of the Integration
Engine.
Check Queue Status
Call the Integration Server and call transaction SMQR in the sender and receiver
Integration Engine in the corresponding system client.
Check the status of the scheduler and the status of the XBQ* and XBT* queues:

Inbound qQueues
XBTI* (ExactlyOnce)
XBQI* (ExactlyOnceInOrder)

Outbound queues
XBTO* (ExactlyOnce)
XBQO* (ExactlyOnceInOrder)

Acknowledgment queues
XBTB* (ExactlyOnce)
XBQB* (ExactlyOnceInOrder)

Large message queue
XBTL* (ExactlyOnce)
If the scheduler has the status Waiting, it is waiting for free work processes. This is
why delays occur when messages are processed.
If not all necessary queues are registered, you can search for queues with the name
prefix above by using transaction SMQ2. Use transaction SXMB_ADM to register the
queues in this case.
Check Queue Configuration
For a complete analysis, make sure that the queues of the Integration Server are
registered. To do this, call the transaction for Integration Engine administration
(SXMB_ADM) and select the function Manage Queues.
5
Check Message on Adapter Engine
See problem analysis scenario Message Failed on the Adapter Engine.
104
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
7.1.4 Problems and Solutions
7.1.4.1 IDoc Control Record Overwritten
Problem
The IDoc adapter does not pass the fields of the IDoc control record filled in the
payload of the XML message to the target system. The fields are overwritten by the
contents taken from IDoc adapter configuration.
Solution
You can control the function by selecting the Apply control record values from
payload flag in the corresponding communication channel in the Integration
Directory. See also SAP Notes 789895 - Behavior Default for IDoc Control Record
and 728792 - IDoc Adapter: Fields of the IDoc Control Record.
7.1.4.2 Changes Not Reflected
Problem
You have changed the structure of an IDoc in the source or target system. However,
the IDoc adapter still uses the old structure for IDoc <-> XML conversion.
Solution
Delete the metadata for the IDoc in transaction IDX2 and reload it.
7.1.4.3 IDOC_ADAPTER.METADATA/ATTRIBUTE_IDOC_METADATA
Problem
Error message IDOC_ADAPTER.METADATA – Segment &, segmentnumber & not
correct in structure & or IDOC_ADAPTER. ATTRIBUTE_IDOC_METADATA can be
found in the XML message when trying to send the message to the
outbound/receiver IDoc adapter.
Solution
The structure of the message does not correspond to the IDoc structure. Compare
the payload of the XI message with the IDoc structure shown in transaction WE60 in
the target SAP system.
You can use the IDX_CHECK_METADATA report to compare the IDoc metadata in
the cache of the PI system with the IDoc structure available in the receiver system.
See SAP Note 907957 - IDoc-Adapter: Metadata inconsistent after update for
information about the availability of the report.
February 2011
105
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
7.1.4.4 IDOC_ADAPTER.ATTRIBUTE_INV_SND_SERV
Problem
Error message IDOC_ADAPTER. ATTRIBUTE_INV_SND_SERV: Unable to convert
sender service to an ALE logical system occurs in the XML message when it is sent
to the IDoc adapter.
Solution
The sender system must have a logical system name assigned as an adapterspecific identifier in the business system, business communication component, or
business process in the PI runtime cache.
Assign the logical system name to the business system in the SLD. Then, update the
adapter-specific data in the business system in the Integration Directory. Open the
respective business system in the Integration Directory and choose Change. Use the
menu path Communication Component  Adapter-Specific Identifiers and update
the logical system name from the SLD by choosing Compare with System
Landscape Directory.
For business communication components and business processes, assign the
logical system name directly in the Integration Directory by choosing Communication
Component  Adapter-Specific Identifiers.
Now save the communication component and activate the change list. The logical
system name will be updated in the PI runtime cache. You can check this in
transaction SXI_CACHE. Search for the communication component and check if
there is an entry for the communication component schema LogicalSystem for the
same communication component ID.
7.1.4.5 Change Logical System for IDoc Adapter
Problem
You add or change a logical system name for a business system in the SLD but it is
not used during runtime.
Solution
The logical system name also needs to be updated in the runtime caches.
After changing the logical system name in the SLD, you have to update the adapterspecific data in the business system. Open the respective business system in the
Integration Directory and choose Change. Use the menu path Communication
Component  Adapter-Specific Identifiers and update the logical system name from
the SLD by choosing Compare with System Landscape Directory. Now save the
business system and activate the change list. The logical system name will be
updated in transaction SXI_CACHE.
106
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
7.1.4.6 Inconsistent Adapter Metadata
Problem
You send IDocs to the Integration Server but the data in the XML structure created
from the IDoc is not correct. This may cause problems during mapping or when
updating data in the receiver system.
You send XI messages from the Integration Server to another system by using the
IDoc adapter. The data received is not correct or the XI message gets an error
during the adapter call because the metadata is not correct.
Solution
If the IDoc structure is changed in the sender or receiver system, the metadata
cache in the PI system must be updated as well because this data is used to convert
the IDoc to an XML structure or the XML to an IDoc structure. To update the
metadata in the PI system, you must delete the old metadata in transaction IDX2.
During processing of the next XI message using this data, the cache will be filled
automatically.
You can use report IDX_CHECK_METADATA to compare the IDoc metadata in the
cache of the PI system and the IDoc structure available in the receiver system. See
SAP Note 907957 - IDoc-Adapter: Metadata Inconsistent After Update for
information about the availability of the report.
7.1.4.7 Error While Processing Acknowledgments for IDocs
Problem
You send an IDoc from system A to the Integration Server and request an
acknowledgment. PI sends the message to system B which sends back an
acknowledgment. Now PI has to correlate the acknowledgment to the original IDoc
from system A.
The acknowledgment message cannot be correctly correlated to the original IDoc
and the processing stops with the error ATTRIBUTE_NO_REQUEST in the PI
system.
Solution
If the acknowledgment message stops with the error ATTRIBUTE_NO_REQUEST,
the request XI message based on IDoc A no longer exists and so the original sender
cannot be determined. To avoid problems with acknowledgments for already
archived or deleted messages, you can add the hop list information to the request
message. In this case the sender can be determined from the hop list, therefore no
request message is necessary. You can do this in the communication channel. Be
aware that this is only possible if you are sending the message to the XI adapter
(proxy).
February 2011
107
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
File Adapter
7.1.5 Problems and Solutions
7.1.5.1 (6798) - ERROR Finished Sending to Integration Engine with
Error &
Problem
The inbound/sender file adapter cannot send a file to the Integration Engine. You get
the following error message (4076): „ERROR\: Finished sending to Integration
Engine with error "{0}"‟ in the log of the adapter.
Solution
Depending on the error that is passed in the parameter {0}, do the following:
 HTTP 404 File not found
Check the sender/inbound file-adapter configuration. In particular, the
XMB.TargetURL parameter often references the Java port (usually 50000)
instead of the SAP NetWeaver AS port. You have to use the port that can be
found in transaction SMICM by choosing Goto  Services.

Java.net.ConnectException: Connection refused‟
Check if the HTTP service is active (use transaction SMICM) and if the
correct client/user/password is used. Try to log on to the system using this
user.
7.1.5.2 FTPS Protocol
Problem
Are there any adapters that support the FTPS protocol?
Solution
FTPS can be used in the file/FTP adapter in the Adapter Engine (Java EE) for PI 7.1.
RFC Adapter
7.1.6 FAQs About the RFC Adapter
The RFC adapter converts remote function calls (RFCs) to XI messages and XI
messages to RFCs to enable communication between PI and systems that can only
send and receive using remote function modules.
The RFC adapter runs in the Adapter Engine, that is, as a service in the Java
Engine.
108
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Problem
You want to know more about the RFC adapter, how it must be configured, and
where to find more information about tracing.
Analysis
Configuration
For a description of how to configure RFC exchange in the business and PI system,
see SAP Library section Integration Using the Advanced Adapter Engine.
An example of the RFC adapter configuration can be found in the shipped demo
examples. For more information, see the Demo Examples section.
For a description of how to connect external systems using the RFC adapter, see
Configuring the Sender RFC Adapter
For PI 7.1 you can find very useful information about the RFC adapter in SAP Note
730870 - FAQ XI 3.0/ PI 7.0/ PI 7.1 RFC Adapter.
Runtime
For information about troubleshooting problems in the Adapter Engine, see the
section Error Tracking in the Adapter Engine.
Increasing the Trace Level
If you need more information about the error or problem, you can increase the trace
level of your adapter and check the relevant trace file. This is described in SAP Note
761921 - Creating an XI adapter framework trace file.
JCO Trace in RFC Adapter
For a description of how to get a JCO trace for the RFC adapter, see SAP Note
628962 - How to switch on the SAP JCo trace.
7.1.7 Problems and Solutions
7.1.7.1 Maximum Connections Set in RFC Communication Channel
Problem
You do not know what value to set in the Maximum Connections field in the RFC
communication channel.
February 2011
109
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Solution
This value is used to set the number of gateway connections used for message
exchange.
To improve the performance of your message exchange you may have to increase
the value of maximum connections. The value has to be set according to the number
of messages to be processed in parallel. The value is internally limited to 50.
Note that if the RFC sender channel is configured to use more than one connection
to the SAP Gateway, there will be one registration at the SAP Gateway for each
connection. If the RFC adapter runs on a Java cluster with more than one server
node, the number of registrations at the SAP Gateway is the number of connections
configured in the RFC sender channel multiplied by the number of cluster nodes the
RFC adapter is running on.
7.1.7.2 Unicode Setting in RFC Communication Channel
Problem
You do not know when to set the Unicode flag in the RFC sender communication
channel.
Solution
The connection information set in the sender channel is used to establish a
connection to the sender system. This connection is used to get the metadata and
for the RFC message exchange. The Unicode flag has to be set in the sender
channel when the sender system is a Unicode system.
- Sender system is a Unicode system:
If the sender system is a Unicode system, you have to set the flag for Unicode in the
communication channel and select the 2 Bytes radio button for Unicode on the
Special Options tab in the RFC destination (TCP/IP) used for data exchange in the
sender system. To check the correct setting, choose Unicode Test in the RFC
destination in transaction SM59 after you have activated the channel.
- Sender system is non-Unicode system:
If the sender system is a non-Unicode system, you do not have to set the flag for
Unicode in the communication channel. There is no way to set to Unicode in the RFC
destination (TCP/IP) used for data exchange in the sender system. To check the
destination, use the Test Connection button in the RFC destination in transaction
SM59 after you have activated the channel.
7.1.7.3 Changes in Function Structure Not Applied
Problem
You applied changes to the structure of a function module in the SAP system, but the
RFC adapter still uses the old definition.
Solution
See SAP Note 730870 - FAQ XI 3.0/ PI 7.0/ PI 7.1 RFC Adapter (section 5).
110
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
7.1.7.4 RFC Adapter with Non-SAP Systems
Problem
Can the RFC adapter be used to communicate with external non-SAP systems?
Solution
For more information about how to connect external systems using the RFC adapter,
see Configuring the RFC Adapter.
7.1.7.5 WAIT during call to BAPI_TRANSACTION_COMMIT
Problem
BAPI_TRANSACTION_COMMIT issued from the RFC adapter performs COMMIT
WORK asynchronously. This is due to the fact that it is not possible to issue a WAIT
parameter to BAPI_TRANSACTION_COMMIT from the RFC adapter and therefore
the WAIT parameter is always taken as false. As a result, when the control returned
back to the RFC adapter from BAPI_TRANSACTION_COMMIT, it could not be
ascertained whether commit completed.
Solution
Refer to SAP Note 1342143 (RFC Adapter: WAIT during call to
BAPI_TRANSACTION_COMMIT)
Plain HTTP Adapter
7.1.8 FAQs About the Plain HTTP Adapter
PI provides an HTTP adapter to convert plain HTTP requests to XI messages and XI
messages to plain HTTP requests to enable communication between PI and systems
that can only send and receive HTTP calls.
The HTTP adapter runs in the ABAP part of the PI system and communicates with
the sender and receiver systems using the HTTP protocol by using the Internet
Communication Manager (ICM).
Problem
You want to know more about the plain HTTP adapter, how it has to be configured,
and how to analyze errors.
Analysis
Configuration
For a description of how to configure HTTP exchange in the business and PI system,
see SAP Library section Configuring the Plain HTTP Adapter.
February 2011
111
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
For more information about the HTTP adapter, see SAP Note 839803 - Plain HTTP
Adapter: Calling the HTTP service.
Runtime
If you have problems sending requests to or receiving calls from the HTTP adapter,
you can use the ICM trace to get more information about the problem. See SAP Note
634006 - ICM messages explanatory note question 9.
Problems using Seeburger Adapters for SAP NetWeaver
PI
Over the past 17 years, SEEBURGER has developed a large number of EDI
adapters (including thousands of mappings and dozens of EDI communication
protocols) for different scenarios in various industries. Seeburger offers the following
industry-specific packages to meet the needs of customers.
Each package contains basic EDI process functions, mappings of SAP XML to an
EDI flavor for certain common business documents, and supported communication
protocols based on experience in that particular industry.
All adapters run on the Adapter Framework of SAP NetWeaver PI, based on the
J2EE connector architecture (JCA). The underlying adapter technology ensures that
best-effort delivery, guaranteed-exactly-once delivery, guaranteed-in-order delivery,
an automatic retry mechanism, and automatic switching to alternative communication
channels are available for all kinds of communication.
All adapters support the inbound direction (sender adapter) and outbound direction
(receiver adapter). A broad range of international code pages and character sets are
supported. These include Unicode, ASCII, and EBCDIC.
The adapter configuration is carried out in the Integration Builder (Integration
Directory) of SAP NetWeaver PI.
7.1.9 Installation and Update
7.1.9.1 Compatibility: SEEBURGER Release SAP SP Versions
Problem
Where can SEEBURGER solution users obtain information about available releases,
supported SAP versions, and Service Packs?
Analysis
SEEBURGER solution releases have different versioning than SAP releases.
Customers require information about supported combinations of SAP releases and
SEEBURGER releases.
112
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Solution
Check SEEBURGER Knowledge Base entry Release Overview.
Also refer to Release Matrix attached to the SAP Note 890721 - SEEBURGER SAPXI Adapter:SP Correlation.
7.1.9.2 How Should the Already Installed Components Be Updated?
Problem:
You already have an installed SEEBURGER solution and would like to update to the
latest version.
Solution:
Follow the instructions in the SEEBURGER Master Installation Guide for both
installation and update scenarios. In particular see section “Uninstall Outdated
Versions”.
7.1.10
Runtime
7.1.10.1 SeeFunctions Error: VariableBeanServlet/CounterBeanServlet:
Could Not Call …
Problem
When using the SEEBURGER SeeFunctions the error message
“VariableBeanServlet: could not call getVariable() method of the Servlet” or
“CounterBeanServlet: could not call nextCounter() of the Servlet” occurs.
Analysis
The SEEBURGER SeeFunctions component provides persistent variables or
counters for use in BIC mappings or message mappings. The persistence layer is
accessed by HTTP servlet communication. The default settings host “localhost” and
port “50000” are assumed; in cases where the J2EE Engine port is not the default
port (50000), the base URL must be configured using the SEEBURGER Property
Store.
Solution
Use the SEEBURGER Property Store to configure the base URL of the J2EE
Engine. Create an entry in the property store with the following values:
Namespace: http://seeburger.com/xi/SeeFunctions
Name/Key: provider.servlet.server
Value: http://hostname:port/
Note that hostname can be either the real host name or “localhost”, and the port
must be replaced by the (HTTP) J2EE Engine port.
February 2011
113
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
7.1.10.2 ConnectException: Connection Refused
Problem
The adapter logs and/or traces contain Java exception stack traces of the
SEEBURGER Java package com.seeburger.simplecomm.CommClient.send() with a
stack trace similar to this:
Mar 25, 2008 2:42:35 PM com.seeburger.simplecomm.CommClient.send()
[SAPEngine_System_Thread[impl:5]_49] # Error # Cannot connect to host,
java.net.ConnectException: Connection refused Caused by:
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:464)
at java.net.Socket.connect(Socket.java:414)
at java.net.Socket.<init>(Socket.java:310)
at java.net.Socket.<init>(Socket.java:125)
at com.seeburger.simplecomm.CommClient.send(CommClient.java:177)
at com.seeburger.simplecomm.CommClient.send(CommClient.java:147)
at
com.seeburger.frame.monitor.recover.spi.AdapterCallback.registerAdapter(AdapterC
allback.java:72)…
Analysis
The technical adapter (for example, AS2, Host FTP, OFTP_TCP) comes with a
monitor to view message/report correlations, the SEEBURGER MessageIDMonitor,
and SEEBURGER Recovery Monitor. The monitor communicates with the technical
adapter by TCP/IP-based message exchange using a broker to find the receiver for
each message. This broker is called CommunicationService or
seeburger.com/com.seeburger.xi.webapp.commservice and is required for
communication between the monitor and technical adapter. For this reason, the
CommunicationService must be deployed and running and must be allowed to bind
port 6201.
Solution
Make sure that the application CommunicationService is deployed and running in
your J2EE Engine. This application must be deployed and started on all cluster
nodes/Adapter Engine/J2EE instances where a technical adapter by SEEBURGER
is in use.
7.1.10.3 SEEBURGER Message Monitor – Message Status Description
Problem
The SEEBURGER Message Monitor displays messages that have been
sent/received by SEEBURGER technical adapters and their status (along with further
details, depending on the adapter used). It is not obvious in all cases what the status
in question means.
114
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Analysis
A description of possible status values is required.
Solution
See the table below for a description of all allowed status values.
Status
Currently in progress
Error on send, will be retried
Error on send, will not be
retried
Sent, no report expected
Waiting for delivery, receipt,
or both reports
All requested reports are OK
Not all requested reports
were OK
Error on receipt, task might
be retried
Error on receipt, task will not
be retried
Received, no report
requested
Initiation to backend pending
Timeout has been reached
Description
Message is being processed
Message has not been sent but will be
retried
Message has not been sent and will not be
retried
Message has been sent, no reports expected
Message has been sent, waiting for 1 or
more reports
All requested reports were OK
Not all requested reports were OK
Error while receiving, might be sent again
Error while receiving, will not be sent again
Message received, no report requested
Message/Report received and currently
being processed
Not all reports were received before timeout
expired
7.1.10.4 Technical Adapter Cannot Be Used in Service Without Party
Scenario
Problem
Some adapters do not support the use of communication channels for services
without a party. The reason for this is that these adapters require party information
(for example, AS2 ID, OFTP Odette code) for sending or receiving messages.
Analysis
The restriction that is imposed by some technical adapters needs a workaround.
Solution
Receiver communication channels of adapters that do need party information can be
used in “service without party” configurations where a header mapping is used in the
receiver agreement. The header mapping needs to map the sender/receiver party to
the party objects that contain the required party information.
February 2011
115
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
7.1.10.5 Some SEEBURGER Tables Cause Heavy CPU Load
Problem
Heavy load has been identified as being caused by SEEBURGER tables with names
similar to SEE_MSGIDSTORExxxx.
Analysis
The SEEBURGER technical adapters make use of a MessageIDStore, which is used
for correlating messages and reports/MDNs/EERPs. The MessageIdStore table
deployment does not contain indexes for these tables, which can lead to heavy load
in environments where the message throughput is high.
Solution
See SAP Note 965084 - Important Information About SEEBURGER Components,
which contains detailed information about creating indexes for these tables.
7.1.10.6 Adapter Cannot “Find“ Configured Private Keys/Certificates
Problem
Errors in communication channels of SEEBURGER technical adapters occur with
errors that may describe problems finding/accessing keystore entries.
Analysis
The communication channel and/or sender/receiver agreements contain “aliases”
that specify paths to keystore entries (for example: TRUSTED/as2/partner-cert).
Even though the aliases used are correct, the adapter is not able to find/access
these entries. Problems like this are usually caused by either the use of incorrect
aliases or insufficient privileges for the user specified in the managed connection
factory properties (connector container service) of the adapter.
Solution
Perform the following checks:
116
-
Is the specified alias correct?
-
Does the user (adapterUser) specified in the connector container service
(SAP NetWeaver Administrator) exist?
-
Is the password (adapterUserPassword) correct for the user?
-
Make sure you use a user type that does not require a password change.
-
Assign the role view-creator of the keystore view you are using to the
adapterUser.
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
7.1.10.7 Error: Unsupported Key Size or Algorithm Parameter
Problem
The technical adapter produces error messages, such as “Unsupported key size or
algorithm parameters” in one or more of the following:
1) Traces/lLogs
2) Adapter Status Monitor
3) Communication Channel Monitor
Analysis
When working with certificates and private keys, for most key lengths it is necessary
to have the unlimited strength policy files installed in the VM in use.
Solution
Install the JVM unlimited strength policy files (after making sure that laws, rules, and
restrictions allow this) in every VM running adapters/modules/components working
with private keys and/or certificates.
7.1.10.8 Error: Cannot Create Reservation(s)
Problem
The technical adapter produces error messages such as “Cannot create
reservation(s)” in one or more of the following:
1) Traces/Logs
2) Adapter Status Monitor
3) Communication Channel Monitor
Analysis
Communication channels may require resources to manage concurrent access to
certain resources, like VAN mailboxes or hardware resources. These resources are
bound to hosts, which means they are accessible from certain hosts. All hosts that
are allowed to access a certain resource (that is: create a reservation for this
resource) require an assignment in the resource configuration (SEEBURGER
workbench). An assignment connects a resource to a host name, which can be fully
qualified or a short version of the host name (for example, myhost or
myhost.mycompany.com).
Solution
Check the Adapter Status Monitor or Communication Channel Monitor to find entries
for the adapter start that state the host name that the adapter is aware of. The status
February 2011
117
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
message that contains the host name usually looks like this: Adapter has been
started (RC-XI-007Q3-20080325165149-1.7.3) as node: hostname.company.com
Use the exact value (in this case: hostname.company.com) to create the assignment
and make sure that sufficient channels (total) have been specified in the resource
definition. For outbound processing, the number of channels (total) must be higher
than the number of channels (incoming).
7.1.10.9 How to Identify XI Messages in the SEEBURGER Message
Monitor
Problem
In cases where detailed status information is required (for example, has the MDN for
AS2 message x been received?), it might be necessary to identify messages in the
SEEBURGER Message Monitor by an XI message ID.
Analysis
The technical adapters store message status information in the MessageId Store,
which can be monitored using the SEEBURGER Message Monitor. Since in most
cases XI message IDs cannot be reused for the wire protocol (AS2, OFTP, FTP, and
so on), the MessageID Store correlates externally-used message IDs with internal XI
message IDs.
Solution
The SEEBURGER Message Monitor contains facilities to search for message IDs,
which can be either external or internal (and primary or secondary depending on the
use case). Use the text search with the field “ID” to search for XI message IDs in any
of the MessageId Store fields.
7.1.10.10 How to Avoid Passwords Being Displayed in Plain Text on
Seeburger User Interfaces
Problem
In some Seeburger monitoring user interfaces, passwords are displayed as plain
text. This is also applicable for passwords configured in the channel configuration of
non-Seeburger adapters.
Analysis
The Seeburger monitoring user interfaces are not able to decide which fields are
password fields, based on the information they receive from the CPACache. As a
result, all fields are displayed as plain text. The passwords are also displayed as
plain text instead of asterisks.
118
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Solution
To set any field as a password field, (this is also applicable for fields belonging to
non-Seeburger adapters), an administrator should navigate to the Property Store on
the Seeburger Workbench. There, all fields that may be passwords and should be
displayed as asterisks should be identified by adding the field names as: *password*,
*pwd*, ...
Important Notes for reference:
0001486798 ExtendedTools Upgrade 2.0.x to 2.1.1 and later
0001290210 SeeCPAChannelStoppedException
0001442196 Authentication certificate alias is empty
0001315091 Wrong status information in MessageMonitor, AS2, Asynch. MDN
0001320466 SEEBURGER AS2 adapter stops processing messages
0001322292 TxRollbackException: Messages in Sender Channels are skipped
0001312458 Deployment of SEEBURGER adapter fails
0000890722 SEEBURGER Adapter Release Notes
0001000964 SEEBURGER support information
0001375621 Local Processing not possible with SEEBURGER adapters 2.1Q1x
0001404959 OutOfMemory: Memory usage even beyond MaxHeapSize
0001400412 MessageSplitter fails due to too long message-ID-map
0001265132 Performance issues when using the SEEBURGER adapters
Information About SAP Conversion Agent by Informatica
In PI the SAP Conversion Agent by Informatica can be used to convert any data
format to XML format.
Problem
You want to know more about the SAP Conversion Agent by Informatica, for
example, how it can be used and how it must be configured.
Solution
For more information about the SAP Conversion Agent by Informatica, see SAP
Library section Conversion Agent.
In SAP Note 894815 - FAQ: NetWeaver Conversion Agent you can find general
information about the Conversion Agent (CA), as well as licensing and links to
available documentation.
February 2011
119
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
120
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
8 Runtime
Demo Examples
Problem
You want to test your PI system based on SAP NetWeaver 7.3 after installation or
you want to know more about the configuration of scenarios in PI.
Solution
In SAP NetWeaver 7.3 some test scenarios are created to test the PI functions and
to learn more about PI and how to configure scenarios within your PI system. All
objects necessary for the configuration are delivered by SAP.
To get started you should use the scenarios described in the guide:
Using NW 7.30 Process Integration Dual Stack:
Simple Use cases for NW 7.30 PI Dual Stack
Simple Use cases for NW 7.30 Decentral Adapter Engine
For more advanced scenarios, see the guide SAP NetWeaver 7.30 Process
Integration: Demo Example Configuration
The exercises Demo Example Exercise Cancel Flight Booking/ Demo Example
Exercise Cancel Flight Booking (with ccBPM) are available as development scenario
examples.
Using NW 7.30 Advanced Adapter Engine Extended:
Simple use cases
PI Error Codes Information
Problem
You would like to know which error statuses are possible in the PI Integration Server
during processing of messages to enable better error handling by your support
organizations. In addition, you would like to know if the specific message status
allows automatic or manual retries, or none at all.
Solution
Executing the ABAP report SXMS_ENUMERATE_SYSERR_CODES on the
Integration Server generates a list of all possible error codes for the message states
in the Integration Server.
Values are displayed with their corresponding explanation for the restart mode:
A : Correctable By Automatic Retry
February 2011
121
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
M :
Correctable By Manual Retry
N :
Not Correctable
The possible messages states for the Adapter Engine/Messaging System are
explained in SAP Note 813993 - FAQ: Message Status in the Adapter Framework.
Message Packaging
Starting PI 7.1 you can improve the performance of message processing by grouping
asynchronous messages in packages and then processing each message package
in one LUW.
Each package contains individual, unrelated messages. They are saved to the
database individually; no special package archiving function is available.
Messages can end up in various different packages while they are being processed
because a new package is created for each processing step.
You configure how packages are created in the sender system and in the central
Integration Engine. Packages can be received and saved in the receiver system.
They are then processed as individual messages.
Problem
You would like to know more about this feature, how to configure it, and where to find
more information in the event of errors.
Solution
Sender adapters handle message packages in different ways:

The Advanced Adapter Engine can receive packages but cannot create them.

The Business Process Engine (BPE) can process packages. For more
information, see SAP Library section Message Packaging for Integration
Processes.

The IDoc adapter sends all messages that have the same interface to the
Integration Server in one RFC call. It can send IDoc message packages to an
IDoc receiver.
When sending IDoc message packages, we recommend using message
packaging rather than the function for activating IDoc message packages
(transaction IDXPW), because you do not need to make any additional
configuration settings and because there is no delay in message
processing.
122

The plain HTTP adapter cannot process packages.

The Web service runtime can receive packages but processes the messages
individually.
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide

The messages are transferred to the mapping as a package; however, they
are actually processed individually. It is not possible to configure mappingbased message packaging.
Message packaging is activated in transaction SXMB_ADMIN  Configuration 
Configure Integration Engine by using the PACKAGING parameter in the Category
RUNTIME. To activate packaging, set the value to 1. Starting PI 7.1 packaging is
activated by default.
You can configure message packaging to suit your requirements. To do so, you
define configuration types (transaction SXMS_BCM). You then assign these to the
different locations (for example, inbound processing in IS) where message
packaging can be used in transaction SXMS_BCONF. To make a global package
configuration such as this more specific, you can assign a configuration type not just
to a specific message packaging location, but also to a specific sender or receiver ID
(defined in transaction SXMSIF). This configuration type is then applied instead of the
global configuration for those messages that correspond to this sender or receiver
ID. This method also enables you to deactivate message packaging for specific
receivers. For more information, see SAP Library section Configure Message
Packaging.
To monitor package statistics, you first have to activate the statistics using
transaction XMSPKSTATCNF, then you can monitor them in transaction
XMSPKSTATMON.
You can log errors that occur when packages are being processed. To do so, you
have to set the parameter LOGGING_AMF_ERR in category RUNTIME to 1 in
transaction SXMB_ADM  Configuration  Configure Integration Engine. When the
parameter is active and the processing of a message in a package fails, an error
message is created with the package ID as the message ID.
You must only use this parameter in a development system or for the purpose
of analyzing an error situation because it is possible that any errors that occur
will be reported more than once.
For more information about monitoring message packages, see SAP Library section
Monitoring Message Packaging.
For more information about message bulking in general, see SAP Notes 1037176 XI Runtime: Message Packaging and 1058623 - BPE: Message Packaging, and SAP
Library section Message Packaging.
XML Validation
It is possible to switch on XML validation in order to check the XML payload of the
service interface against the XML schema (message type, data type, external
definition) defined in the Enterprise Services Repository.
February 2011
123
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Problem
You would like to know more about this feature, how to configure it, and where to find
more information in the event of errors.
Solution
You define if and where the validation of the message payload takes place in the
respective collaboration agreement. For scenarios using Advanced Adapter Engine,
validation of the message payload can be specified in the integrated configuration.
For classical scenarios (using the Integration Server) you can define XML validation
in the following way:

In a sender agreement, choose between validation in the sender adapter and
validation in the Integration Engine. If validation takes place in the adapter, a
synchronous response is sent to the sender when an error occurs. If
validation takes place in the Integration Server, the message is set to error
status and it can be processed by the administrator in the Runtime
Workbench.
In the receiver agreement, you can configure the validation in the Integration Engine.
For scenarios using Advanced Adapter Engine you define XML validation in the
following way:

124
In Inbound Processing tab (of an integrated configuration), you can choose
Validation by Adapter to enable XML validation on the sender side. If
validation takes place in the adapter, a synchronous response is sent to the
sender when an error occurs.
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
In Outbound Processing tab, choose Validation by Adapter to enable XML
validation on the receiver side.
Validation in the Sender Adapter
If the sender adapter has created the message, you can perform the validation of the
message payload. If the structure of the payload differs from the definition of the data
type provided for comparison, message processing is stopped. The adapter sends a
synchronous response to the sender of the message, informing the sender about the
structure error. The industry-specific adapters inform the sender asynchronously, as
required by the RNIF and CIDX protocols.
All sender adapters (including non-SAP adapters) can perform this kind of validation.
Validation in the Integration Engine
In inbound and outbound processing, validation of the message payload is
performed as pipeline step in the Integration Engine. If the structure of the message
payload does not match the saved definition of the data type, an error description is
generated. The error description contains status information and a list of all structure
errors. Message processing is stopped. The message is set to error status and an
error report is saved.
Messages that have an error status after validation has been executed can be
processed further by an administrator in the Runtime Workbench. The administrator
can resend messages and skip the validation step.
Fault messages, receipt acknowledgments, and exceptions are not validated.
For more information about XML validation in PI, see XML Validation and the How to
Perform XML Validations in SAP NetWeaver Process Integration 7.1 guide.
February 2011
125
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Problem
You get a Schema not Found Error while validating the message on the
sender/receiver side.
Solution
You can check the Cache monitor if the xsd of the message is available in the cache.
This can be checked by following steps below:
o
o
o
Navigate to NWA and choose SOA Management  Monitoring  PI Cache
Monitoring.
Go to Mapping Runtime Tab  XML Schema tab.
Search for the message using Interface Name, Namespace, Software
Component Version as search criteria and check for the respective schema in
the details part below as shown in the image.
If the schema is not available in the cache monitor, try to activate the corresponding
collaboration agreement or integrated configuration object.
If XML Validation does not find schema in cache, then the file system is checked for
the corresponding schema. In this way, the fall-back option to previous releases is
also supported.
Problem
You need to update the Schema available in the Cache monitor with the updated
schema available in Enterprise Services Repository.
Solution
You can use the Synchronize from ESR utility available in Cache monitor. For this to
use follow the steps same as in section 2.
126
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Choose Synchronize from ESR and your data will be updated with the data available
in ES Repository. On successful update you will receive a message Data
Synchronized from ESR as shown in figure below.
Problem
You get an error during the message validation step while the message is validated
using PI on the sender/receiver side.
Solution
This generally happens when the message does not adhere to the message
structure defined by the xsd.
You can see the detailed error available in the audit logs under message monitoring.
You can then update your message with the structure that adheres to the structure
defined by the schema.
Problem
You want to persist the message even if it fails with XML Validation error on the
sender direction.
Solution
This is possible with the message versioning function (available as of SAP
NetWeaver 7.3). You can configure Store on Error mode for XML Validation sender
direction in the XI Adapter service. More information on this setting can be found in
Message Versioning Guide.
Timeouts in PI
Problem
In PI, timeouts can occur in various different places: while calling the Integration
Builder, during cache refresh, at runtime, while (re)starting the Java Engine, while
February 2011
127
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
calling the Adapter Framework, and so on. This section gives an overview of several
known timeout issues and the parameters for adapting timeout settings.
Solution
Timeout during Cache Refresh
 RFC destination INTEGRATION_DIRECTORY_HMI
 Tab page Special options  timeout
 After the PI post-installation steps, default set to 30000 ms
Timeout Calling the Mapping During Runtime
 Timeout for establishing RFC connection (only if all mapping threads are
busy)
Occurs rarely
gw/reg_timeout = 60
Default: 60 s

Number of mapping threads in Java engine
Number of processes for RFC destination AI_RUNTIME_<SID> in the Java
service JCo RFC Destinations in the SAP NetWeaver Administrator
Default after PI post-installation steps: 10
Timeout Processing XI Messages

Work process processing timeout
rdisp/max_wprun_time = 900
Default: 600 s
Timeout Calling the Adapter Framework or Calling an External Partner Using
the HTTP Protocol
 ICM 402 timeout for http client calls (IS -> AF): ICM_HTTP_TIMEOUT
Value for all ports: icm/keep_alive_timeout (Default: 60 seconds)
Value for specific ports: icm/server_port_0 =
PROT=HTTP,PORT=<icmhttpport>, TIMEOUT=30, PROCTIMEOUT=900
PROCTIMEOUT not set  TIMEOUT is used  TIMEOUT not set 
icm/keep_alive_timeout is used
Default: TIMEOUT and PROCTIMEOUT not set –>icm/keep_alive_timeout is
used
In the event of errors, increase the PROCTIMEOUT value for the
HTTP/HTTPS ports used. Do not increase icm/keep_alive_timeout or the
TIMEOUT value as this would lead to higher resource consumption.
For more information, see SAP Note 824554 - ICM Timeout Parameters and
section Timeouts in HTTP Communications.
128
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide

PI parameter in transaction SXMB_ADM  Integration Engine Configuration:
Category RUNTIME, Parameter HTTP_TIMEOUT
This timeout overwrites the ICM timeout setting in icm/keep_alive_timeout
and icm/server_port_0 for outgoing HTTP calls.
Default: 0 - not set

Timeout setting up the connection to the external partner: HTTP 404
icm/conn_timeout=5000
Default: 5000 ms
HTTP 401 Calling the Adapter Framework
 Calling the AF may result in HTTP 401 during high load; this is caused by too
few connections to the ABAP user management or a timeout waiting for a
new connection.
The connection pool for user verification calls to the ABAP side is controlled
with Java destination UMEBackendConnection. The settings „Max.
Connections‟ and „Max. Wait Time‟ can be used to control the timeout.
The „Max. Connections‟ setting controls the maximum number of connections
that can be used in parallel. If all connections are in use and a new one is
needed, the „Max Wait Time‟ setting specifies the time to wait for a free
connection (in milliseconds). After this time the attempt is treated as an error.
Default for Max. Connections: 20
Default for Max. Wait Time: 10.000 ms
Increase parameters until problem disappears: for example, Max.
Connections=50, Max. Wait Time=60000
For more information, see SAP Note 816022 - FAQ: XI 3.0 J2EE Adapter
Engine / Messaging System.
Timeout Calling the Integration Server from the Adapter Framework
 ICM timeout for incoming HTTP calls (AF -> IS): ICM_HTTP_TIMEOUT
Value for all ports: icm/keep_alive_timeout (default: 60 seconds)
Value for specific ports: icm/server_port_0 =
PROT=HTTP,PORT=<icmhttpport>, TIMEOUT=30, PROCTIMEOUT=900
PROCTIMEOUT not set –> TIMEOUT is used  if TIMEOUT is also not set
 icm/keep_alive_timeout is used
Default: PROCTIMEOUT and TIMEOUTnot set –>icm/keep_alive_timeout is
used.
For more information, see SAP Note 824554 - ICM Timeout Parameters and
section Timeouts in HTTP Communications.
February 2011
129
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide

Timeout because of insufficient available dialog work processes in Integration
Server.
rdisp/wp_no_dia
Default: 2
Timeouts in the Adapter Framework
 Cluster communication timeout in Adapter Framework Core
Property of Service "XPI Service: AF Core" within SAP NetWeaver
Administrator
clusterCommunicationTimeoutMsec.
This specifies the timeout value for the cluster communication in the AS Java
Engine. Even though the default value of 15 seconds should be sufficient for
the adapter monitoring functionality, you can increase this value in cases
where you are experiencing cluster timeout exceptions of the cluster
communication mechanism of the Java Engine.
Default: 15000 [ms]
See SAP Library section Java Service Properties for the Adapter Framework.

Cluster timeout in Adapter Framework messaging system
Property of Service " XPI Service: Messaging System" within SAP
NetWeaver Administrator
messaging.cluster.timeout
The "messaging.cluster.timeout" property specifies the timeout value for the
internal cluster communication of the AS Java Engine. The default value of
60 seconds is very generous. If cluster timeout errors still occur, you must
increase this value.
Default: 60000 [ms]
For more information, see SAP Note 791655 - Documentation of the XI
Messaging System Service Properties.

Sync message processing XI adapter
This timeout property is only relevant for synchronous messages. The value
specifies how long the messaging system waits for a response during
synchronous communication. If this time elapses, a "MessageExpired"
exception is triggered.
Property of Service "XPI Adapter: XI" within SAP NetWeaver Administrator
xiadapter.inbound.timeout.default
Default: 180000 [ms]
For more information, see SAP Note 791379 - XI Adapter Service Properties
Documentation.
130
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Timeouts in Different AS Java-Based Adapters
 FTP adapter setting within the channel
ftp.timeout=timeoutSecs
For more information, see SAP Note 849089 - XI 3.0 File Adapter: FTP
Timeout Handling.

Synchronous message delivery timeout in the SAP Business Connector
adapter (BC adapter)
Property of Service " XPI Adapter: BC" within SAP NetWeaver Administrator
syncMessageDeliveryTimeoutMsec
This property controls the timeout while sending synchronous messages from
the SAP Business Connector adapter to the Adapter Framework and the
other way round. It is also used to set the valid until field of a synchronous
response message sent from the adapter to the SAP Business Connector.
Default: 300000 [ms]
See SAP Library section Java Service Properties for the Adapter Framework.

Synchronous message delivery timeout in the RFC adapter
Property of Service " XPI Adapter: RFC" within SAP NetWeaver Administrator
syncMessageDeliveryTimeoutMsec
When an RFC server sends a sRFC call as a synchronous XI message to the
Adapter Framework, it uses the module processor. The last module in the
chain must be the RFC adapter module (localejbs/RfcAFBean). Within this
module, the XI message is sent to Adapter Framework messaging. This
property sets the timeout, which is used to send the message and wait for a
response. If the given time has elapsed, an exception is thrown by the
Adapter Framework and sent back to the sender.
Default: 300000 [ms]
See SAP Library section Java Service Properties for the Adapter Framework.

Synchronous message delivery timeout in the SOAP adapter
XI.Timeout in SOAP sender channel
This is the timeout for synchronous message delivery to the Adapter
Framework. You can change this value by setting the XI.Timeout parameter
in the module configuration table. The value must be set in milliseconds (for
example, 300000 for 5 minutes).
Default: 5 minutes
For more information, see SAP Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1
SOAP Adapter.
Timeout Calling the Integration Builder Tools

HTTP client read timeout
February 2011
131
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
ServletInputStreamTimeout (default: 10000ms)
ServletsLongDataTranferTimeout
For more information, see SAP Note 807000 - HTTP Requests Are Not Fully
Read After Timeout.
Timeout Starting Java Services (HTTP 503)
 Load timeout for Java services
SAP NetWeaver Administrator → Service Manager → LoadTimeout
parameter
Default after setting from PI installation:
IBM iSeries: 20
Other platforms: 7

Connect timeout to listener bean of Adapter Framework
Property of Service “XPI Service: AF Core” in the SAP NetWeaver
Administrator
messaging.connectionDefinition (name=AFW, .., pollInterval=60000 [ms],
pollAttempts=60, ..)
The "pollIntervall" and "pollAttempts" properties define how often and at what
interval the messaging system tries to access the listener beans.
During startup (using JNDI Lookup): In the default system, this is a maximum
of 10 attempts every 60 seconds. This is necessary because the messaging
system (MS) is implemented as a Java service, whereas EJBs are part of a
Java application. During server startup, applications are always in a second
phase after the services; therefore they are unavailable during the MS
initialization. If your system starts very slowly (if it takes more than 10
minutes), you may need to increase "pollIntervall" and "pollAttempts".
Default: pollInterval=60000 [ms], pollAttempts=60
For more information, see SAP Note 791655 - Documentation of the XI
Messaging System Service Properties.
Timeouts in the Java Engine
 Cluster manager in SAP NetWeaver Administrator
=>emergency shutdown cluster node during GarbageCollection
ms.keepalive, default: 20000 [ms]
ms.notification.timeout, default: 180000 [ms]
ms.reconnect.timeout, default: 180000 [ms]

132
SCS instance
Timeout for cluster
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
ms/keepalive, default: 300 [s]

HTTP session timeout
In the event of too many open HTTP sessions
NetWeaver Administrator:
Configuration Management  Application Modules
sap.com/com.sap.xi.repository  rep
Tab Context
sap.com/com.sap.xi.directory  dir
Tab Context
sap.com/com.sap.xi.services  run
Tab Context
Parameter: Session Timeout
Default: Session Timeout = 15
Code Pages in PI
Problem
You want to connect systems which have different code pages and want to know
more about how to work with code pages in the PI adapters.
Solution
More information can be found in the guide How to Work with Character Encodings
in Process Integration (not available yet for PI 7.3, but you can still use the guide for
7.0).
Known Restrictions of EOIO
Problem
You are having problems with EOIO (Exactly Once In Order) handling and you are
unsure about the current EOIO support for the different adapter types, ccBPM, and
so on.
Solution
The following sections contain known restrictions of message handling with the
quality of service Exactly Once in Order (EOIO).
RFC Adapter
The RFC adapter supports EOIO. For more information, see SAP Note 730870 FAQ XI 3.0/ PI 7.0/ PI 7.1 RFC Adapter - Question Which flavors of RFC are
supported?
February 2011
133
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
IDoc Adapter
The EOIO function of the IDoc adapter functions for a back-end system of SAP
NetWeaver AS Release 6.40 and higher. For older SAP releases, the standard ALE
transfer function of tRFC (Exactly Once) is used.
For more information, see Maintaining an IDoc Communication Channel.
JMS Adapter
When using EOIO in the sender channel, you have to specify the queue ID.
You can enter a cluster ID. This specification prevents queue jumping in the JMS
queue and guarantees that only one server node is used to process messages with
EOIO.
If you do not enter the cluster ID, the EOIO channel is activated automatically on a
different working node. This configuration ensures node failover by the adapter in a
clustered environment.
For more information, see SAP Library section Configuring the Sender JMS Adapter
(XI Settings - Parameters: Quality of Service).
SAP Business Connector Adapter (BC Adapter)
The BC adapter does not support EOIO.
For more information, see SAP Note 774854 - FAQ XI BC Adapter – Question “Q:
Which quality of service (QoS) is supported?”.
ccBPM:
The Business Process Engine does not automatically support EOIO from inbound to
outbound.
For more information, see SAP Note 833740 - BPE-TS: EOIO Messages Using BPE
Become EO Messages.
Interface Split:
Prior to XI 3.0 SP11 the interface split was set up in the Integration Directory (several
interfaces are assigned to one receiver) and the processing quality of service
automatically changed to EOIO. This leads to problems in scenarios where you
access outbound/receiver adapters that do not support in-order processing and
therefore react with a system error.
For more information, see SAP Note 781356 - XI3.0 SP10: Processing Sequence of
Interfaces.
EOIO Message Analysis
Problem
You experience issues with EOIO interfaces and would like to know how to analyze
the situation in more detail. You would like to find predecessor messages for a
134
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
dedicated EOIO message.
Introduction
EOIO processing is using the conversation ID in the AFW and the queue ID in the
Integration Server.
Analysis
How to Find Messages With Specific Conversation ID/Queue ID?
The EOIO interface in this example is using the queue ID DEMOQID.
Integration Server
Use transaction SXMB_MONI → Monitor for Processed XML Messages. Specify
data/time on the Standard Selection Criteria tab. Switch to the Advanced Selection
Criteria tab and specify the queue ID by using the input help. The required value for
this field for PI inbound queues comprises the prefix (for example, XBQI) followed by
the EOIO specific queue ID (for example, DEMOQID). The value for PI outbound
queues comprises the receiver information (for example, XBQOE) followed by the
EOIO specific queue ID (for example, DEMOQID).
The input help offers you only the current and existing queue names of messages in
the system during the specified time interval. Usually only the value for the PI
outbound queue is still visible due to longer processing time spent in PI outbound
queues.
Input help display:
Adapter Framework
Use RWB → Message Monitoring for component Adapter Engine <SID> to display
messages in the AFW. Choose “Show Additional Criteria” and enter the value of the
sequence ID (for example, DEMOQID) that you are interested in.
February 2011
135
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
In the result list you can add additional columns to the display by clicking the Button
to expand tray icon in the Configure Table Columns line.
Select the additional table columns Sequence ID, Serialization Context, and
Sequential Number to display the values for more detailed analysis.
Another monitor available for EOIO is the EOIO Sequences Monitor. The monitor
can be found in Runtime Workbench  Component Monitoring  select the Adapter
136
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Engine  Button 'Engine-status'  Tab 'Additional data‟  Messaging Details 
Messages in EOIO Sequences. Here you can find all EOIO messages still to be
processed sorted by serialization context and sequential number:
Acknowledgments Supported in Adapters
Problem
You want to use acknowledgments in your PI scenario and want to know which
adapters support which acknowledgments.
Introduction
An acknowledgment is an XI message created as a response to a request XI
message. It contains the „ack‟ header. It does not normally contain a payload
(exception: the IDoc adapter always creates acks with payloads). An
acknowledgment always references the request XI message by using the MsgID in
the field of the main header RefToMessageID. Acknowledgments use the „back
pipeline‟ (for example, CENTRAL_BACK). We differentiate between system
(transfer) and application acknowledgments.
The acknowledgment has to be requested by the sender system/adapter. This
information is transferred to the receiver. If the receiver adapter does not support the
acknowledgment type requested, it must send back a „NotSupported‟ message, that
is, SystemErrorAckNotSupported.
February 2011
137
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Possible Acknowledgment Requests
Sending
async.
message
transient
SystemError
arrived at
receiver
transient
AppError
permanent
AppError
permanent
SystemError
Possible
acknowledgment
SystemError
requests:
SystemOK
AppError
AppOk
AppOK
 SAP AG 2003, Title of Presentation, Speaker Name / 6
Characteristics of an Acknowledgment Message
Ack Header:
-Category - Permanent, Transient
- Status – OK, Error
RefToMessageID: XML property in the main header filled with request message ID
Pipelines:
- CENTRAL_BACK
- SENDER_BACK
RECEIVER_BACK
Payload:
Acknowledgment has no payload.
Exception is an acknowledgment coming from the IDoc adapter
The following table shows what types of acknowledgments are requested by the
sender adapter and sent back by the receiver adapter.
138
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Adapter
Plain HTTP Adapter
IDoc Adapter
ABAP SOAP Adapter
Proxy (ABAP/java)
PE Adapter (Process Engine)
FTP/File Adapter (J2EE)
JDBC Adapter (J2EE)
JMS Adapter (J2EE)
SOAP Adapter (J2EE)
Marketplace Adapter (J2EE)
Mail Adapter
BC Adapter
RFC Adapter
CIDX Adapter
RNIF Adapter
FTP/File Adapter (J2SE)
JDBC Adapter (J2SE)
JMS Adapter (J2SE)
SOAP Adapter (J2SE)
System
Direction Ack
Sender
Receiver x
Sender
Receiver x
Sender
Sender
x
Receiver x
Sender
x
Receiver x
Sender
Receiver x
Sender
Receiver x
Sender
Receiver x
Sender
Receiver x
Sender
Receiver x
Sender
Receiver x
Sender
Receiver x
Sender
Receiver x
Sender
x
Receiver x
Sender
x
Receiver x
System
ErrorAck
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Application
Ack
x
x
x
x
x
x
-
Application
ErrorAck
x
x
x
x
x
x
x
x
x
x
Sender
Receiver
Sender
Receiver
Sender
Receiver
Sender
Receiver
x
x
x
x
-
-
x
x
x
x
Some adapters provide special settings or parameters that influence the requesting
or sending of acknowledgments:
IDoc Adapter:
- Acknowledgments are requested by default. Use report IDX_NOALE to
change this.
- SystemAcks and SystemErrorAcks are created by the IDoc adapter, the other
acknowledgment types are created using ALEAUDIT IDocs. When using
ALEAUDIT IDocs, the ALE must be configured in the sender and receiver
system.
February 2011
139
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
-
To get SystemAcks and SystemErrorAcks you have to schedule the report
SXMS_REFRESH_ADAPTER_STATUS to update the adapter status and
trigger the acknowledgment. For more information about scheduling the job,
see SAP Note 920155 - SXMS_REFRESH_ADAPTER_STATUS with Time
Interval.
JMS Adapter (Java EE):
- In the JMS receiver channel in the Integration Directory, you can configure
whether SystemAck or SystemAckNotSupported are sent. Such a
configuration is necessary if the message delivery by the JMS adapter in your
scenario is not sufficient to trigger a SystemAck.
- In PI 7.1 the JMS adapter sends SystemErrorAcks if requested (for example,
if the receiver cannot be reached). There can be several SystemErrorAcks,
with one acknowledgment message for each retry. These can also be
followed by a SystemAck if there is a successful retry.
RFC, BC, File, JDBC, SOAP, and Mail Adapter (Java EE):
- In PI 7.1 these adapters send SystemErrorAcks if requested (for example, if
the receiver cannot be reached). There can be several SystemErrorAcks,
with one acknowledgment message for each retry. These can also be
followed by a SystemAck if there is a successful retry.
JMS, RFC, BC, File, JDBC, SOAP, and Mail Adapter (Java EE):
- A permanent SystemErrorAck is sent if the message is set to a permanent
error state by the administrator.
Java SE Adapter:
- A SystemErrorAck is sent from the Integration Server if the receiver adapter
reports an error back to the Integration Server.
- If requested the Java SE adapters send SystemAcks. This can be configured
with the XI.AckFinal parameter. For more information, see SAP Note 953783
- XI J2SE Adapter XI 3.0 SysAck Support.
PE Adapter (Process Engine - ccBPM):
- For more information about acknowledgment handling in ccBPM, see SAP
Note 837285 - BPE TS: Acknowledgments in the BPE.
Runtime:
- The RUNTIME/ACK_SYSTEM_FAILURE parameter defines whether
restartable system errors are reported (value 1) or not (value 0) for
asynchronous messages that expect an acknowledgment. The parameter is
set in transaction SXMB_ADMIN  Integration Engine Configuration; the
default setting is 0.
- In the event of non-restartable system errors, the Integration Server always
sends a SystemErrorAck if requested.
140
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
General:
In the PI receiver channel you can select whether the hop list is transferred to the
receiver as well. If the receiver sends back an acknowledgment, the original sender
can be taken from the transferred hop list. If the hop list is not transferred together
with the message, the original sender has to be taken from the request message and
it must not be archived until all acknowledgments are processed.
PI Runtime
8.1.1 Runtime Troubleshooting
The PI messages are sent from sender systems to the PI pipeline in the Integration
Server. In PI there are several steps to be executed that can cause problems
(receiver determination, mapping, technical routing, and so on).
Problem
You have a problem during PI message processing in the PI runtime and want to get
more information about the error and how to analyze and solve it.
Analysis
Trace in the XI Message
To get more information about an error in the PI message, increase the trace level
from 1 (default) to 3. The trace in the PI message in transaction SXMB_MONI is then
written with trace level 3.





To set the trace level in the system, call transaction SXMB_ADM.
Choose Integration Engine Configuration.
Choose Specific Configuration.
Set the TRACE_LEVEL parameter of category RUNTIME to value 3 (if the
parameter does not exist, create it using the New Entries button).
Save the setting.
If you want to analyze one particular message that has caused an error, you can
increase the trace level during restart of the message.
 Select the message in transaction SXMB_MONI.
 Choose Restart.
A popup will ask you if you want to increase the trace level.
 Choose Increase.
The trace will be written with level 3 for the steps after restart.
This only works for messages that can be restarted from transaction SXMB_MONI. It
does not work for synchronous messages or for messages that are already
processed successfully.
February 2011
141
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Logging of Different Pipeline Steps
To get more information about the different pipeline steps in PI message processing,
you have to increase the logging setting from 0 (default) to 1. All pipeline steps which
the messages then run through are logged in the PI message and you can view them
using transaction SXMB_MONI. This can be very helpful if you want to view the
message payload before and after the mapping step.






To set logging in the system, call transaction SXMB_ADM.
Choose Integration Engine Configuration.
Choose Specific Configuration.
Set the LOGGING parameter of category RUNTIME to value 1 (if the
parameter does not exist, create it using the New Entries button.)
Save the setting.
For the logging of synchronous messages, set the LOGGING_SYNC
parameter of category RUNTIME to 1.
Error Analysis Settings
To analyze special messages or special connections you can use the error analysis
settings in the system.
 Call transaction SXMB_ADM.
 Choose Error Analysis Settings.
 Create new entry.
You can create an entry for the sending user (user ID), the queue ID, the quality of
service, or a message ID. On the Action tab page, select TRACELEVEL if you want
to increase the trace level or select LOGGING if you want to activate the logging.
After saving, the settings are active and you can send a new message.
ICM Trace
If you want to trace the complete data transfer by using HTTP, you can use the ICM
trace described in SAP Note 634006 - ICM Messages Explanatory Note. This can be
used for all incoming and outgoing requests that use the HTTP protocol. It does not
work for IDoc and RFC calls. These adapters use the RFC protocol.
SDN: Web Logs
Frequently asked questions (FAQs) about the Integration Engine can be found on
SAP Developer Network (SDN).
142
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
8.1.2 How to Troubleshoot and Solve Queuing Problems on
the Integration Server
Problem
The Integration Server uses pipelines to carry out the required tasks. Each pipeline is
a set of pipeline services that are ABAP object classes, which perform a step on a
message.
These steps are: Receiver Identification, Interface Determination, Message Branch
According to Receiver List, Request Message Mapping, Technical Routing, Call
Adapter.
Technically, these steps are carried out using qRFC. The standard queues for
messages with the QoS (quality of service) Exactly Once (EO) are called XBTI*
(inbound queues) and XBTO* (outbound queues). In addition, there are queues for
QoS EOIO (Exactly Once In Order), for messages with low/high priority, for large
messages, and for acknowledgment messages. In this section, XBTI* and XBTO*
queues are used to explain the principles. Troubleshooting, however, is the same for
all queues.
Depending on the value of the EO_INBOUND_TO_OUTBOUND parameter
(category TUNING of the specific configuration of the Integration Server), the
pipeline services are carried out in the inbound queues (value 0) or in the inbound
and the outbound queues (value 1). The underlying qRFC technique results in a
subsequent handling of the incoming messages: Only the message that occupies the
first slot in the qRFC queue will be handled. Once this message has been
successfully processed, the next message in the queue is handled. If the first
message produces a system error, for example, the receiver system cannot receive
the message, then the status of the queue will change to error and it will not process
any further messages. This situation is often referred to as “the queue is blocked”.
In the daily operation of a PI system, blocked queues are found in different ways,
though the first way is the most common:
1) CCMS (transaction RZ20) issues an alert that a queue is blocked.
2) The end user in the receiver system complains about missing messages.
3) The performance of the system (messages per hour) drops.
Analysis
SAP basic functionality provides a qRFC monitor for inbound and outbound queues.
Although the queues in PI are called inbound and outbound queues, they are
technically both inbound queues. Consequently, only the monitor for inbound queues
can be used to monitor the queues used by PI. The qRFC monitor for inbound
queues is accessed from transaction SMQ2 and shows an overview of all active
queues. To check if a queue is blocked, either set Waiting Queues only to X on the
selection screen or refresh the overview page several times and note the number of
entries.
February 2011
143
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Instead of accessing transaction SMQ2 directly, you can navigate there either from a
given alert in CCMS (transaction RZ20) or from a message in transaction
SXMB_MONI by clicking the queue name in the Queue ID column. Messages in
transaction SXMB_MONI with a green flag (which stands for “Message scheduled”)
are a good starting point for looking for possibly blocked queues.
In transaction SMQ2, navigate forward until you receive the list of queue entries (or
LUW, Logical Unit of Work). From there, navigate forward to the respective blocking
message by double-clicking the entry in the TID column in the first line. Analyze
which problem occurred with this message, for example in the SOAP Header ->
Error.
Solution
First of all, try to solve the problem that led to the blocking of the queue in the first
place. It could, for example, be a receiver that could not be reached. Once the
problem is solved, restart the message in transaction SXMB_MONI. Generally, it is
possible to restart messages from transaction SMQ2 as well, but it is not
recommended and requires a parameter in the Integration Engine configuration to be
changed (category MONITOR and QRFC_RESTART_ALLOWED parameter). After
the message has been successfully processed, the queue is no longer blocked and
starts processing the next messages.
It can, of course, happen that the problem cannot be solved or cannot be solved in a
reasonable amount of time. In this case, you have two options:
1) You can cancel the message manually in transaction SXMB_MONI and it is
subsequently archived and deleted. Once canceled, the queue should start
processing the next message.
Note that canceling a message that is part of an EO or an EOIO (Exactly
Once in Order) queue could have a severe impact on the application logic of
the receiver, because this message will not be sent again by PI.
2) The queue entry (LUW) can be temporarily saved and restarted at a later
point in time in transaction SMQ2. To save the LUW, mark the entry and
choose Edit -> Save LUW. To restart it later, call transaction SMQ3, mark the
entry, and choose Edit -> Restore LUW.
You should never delete LUWs because this leads to inconsistencies
(missing queue entry).
Note that temporarily saving a LUW from an EOIO queue could have a
severe impact on the application logic of the receiver. Make sure that not
sending this particular message is justifiable!
There are also known bugs in previous support packages that can lead to queuing
problems. See the Relevant Notes and Information section.
144
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
How to Avoid Blocked Queues/Improve Performance of Queues
The blocking of queues must be avoided because it can prevent important messages
behind the blocking message from being sent to the receiver system. Leave the
EO_INBOUND_TO_OUTBOUND parameter at its default value of 1 so that a
message is processed by XBTI* and XBTO* queues. At runtime this means that the
message changes queue after the branch/before the message mapping step. Since
blocked queues almost always occur in one of the steps that are handled by the
outbound queues, this will keep the inbound queues (XBTI*) running smoothly. There
is also another even more important reason to use XBTI* and XBTO* queues: These
enable you to use the EO_OUTBOUND_PARALLEL parameter of category TUNING.
This parameter allows you to create separate outbound (XBTO*) queues for each
receiver, with different numbers of parallel queues if the receiver is specified as the
subparameter. Consequently, even if a queue is blocked for a specific receiver,
maybe for a good reason, a message for other receivers will still be processed.
Relevant SAP Notes and Information
The report RSXMB_CHECK_MSG_QUEUE is available for checking inconsistencies
between PI messages and queue entries.
Information about configuration parameters can be found in your system. Call
transaction SXMB_ADM. Choose Integration Engine Configuration -> Specific
Configuration. Choose a category and choose Information.
8.1.3 How to Debug Applications in PI
Problem
Your self-developed integration scenarios or ABAP proxies are causing problems.
You would like to evaluate what is going on with your message forwarded to the
Integration Engine because you are encountering unknown and irresolvable error
situations.
You want to debug the pipeline services of your Integration Engine for incoming
messages from the HTTP service.
Solution
A detailed description about the possible debugging and tracing functions is available
in the How-To Guide How to Debug XI Applications (the guide is not yet available for
PI 7.3 however you can use this 3.0 guide).
February 2011
145
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
8.1.4 Problems and Solutions
8.1.4.1 770 - Message Scheduled (Commit Follows)
Problem
XML message stopped in status 001: Message scheduled (commit follows) and does
not reach the receiver.
Solution
1. Synchronous messages
For synchronous messages this status means that message processing is
not yet complete (neither successful nor with an error). This probably means
that an error occurred on the receiver side but the status was not reported
back to PI (for example, short dump in function being called by RFC adapter).
To find the cause of the problem, have a look in the system log (transaction
SM21) and short dumps (transaction ST22). Otherwise, analyze the problem
in the target system.
2. Asynchronous messages
Check the status of the corresponding RFC queue. If it has the status
RUNNING, you can restart the queue by resetting the status of the first LUW:
Place the cursor on SXMS_ASYNC_EXEC and press Shift+F5.
If you want to delete these messages, you have to use report
RSXMB_CANCEL_NO_COMMIT_MSG. For more information, see SAP Note
712628 - Deleting Messages with Status 001 (Commit is Missing).
8.1.4.2 700 - Scheduled for Outbound Processing
Problem
An XML message stopped in status 012: Scheduled for Outbound Processing and
does not reach the receiver.
Solution
The message is probably waiting in the qRFC queue. Call transaction SMQ2 or
navigate to the queue from the XML message monitor (transaction SXMB_MONI).
Usually, you find the first LUW in the queue that led to an error during processing.
More details of the error are documented in the XML message corresponding to the
LUW. To find this message, double-click the TID of the LUW. Then, you will either
see a screen from which you can get the message ID or (depending on the release)
you are forwarded to the XML message directly.
8.1.4.3 775 Service Unavailable Application Stopped
Problem
The error message “775 Service unavailable Application stopped!” is displayed.
146
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Solution
The problem is that not all Java services can be started by AS Java. Start the SAP
NetWeaver Administrator http://server:port/nwa  Operations  Systems  Start &
Stop  Java Applications. Choose „Retrieve Status‟ to get the information about the
status of the applications. Check if they are running; otherwise choose Start in the
lower part of the window.
Usually the Java Engine starts all services automatically.
Web Service Runtime
8.1.5 Web Service Runtime Troubleshooting
You can use the Web service runtime to exchange messages.
Problem
You are using the Web service runtime to exchange messages and encounter
problems during runtime.
Analysis
Check SAP Note 1292171 - Troubleshooting Guide: ABAP Web Services Runtime to
get more information about troubleshooting the Web service runtime.
Adapter Framework Runtime
8.1.6 Error Tracking in the Adapter Engine
Problem
You need information about how to increase the trace level, find the error messages,
and more information about errors in the AS Java-based adapters (File, JDBC, JMS,
RFC, BC, SOAP, Mail, Marketplace, RNIF, CIDX, HTTP_AAE, IDoc_AAE).
Analysis
For more information about the Adapter Framework runtime, see section „Error
Tracking in the J2EE Adapter Engine‟.
February 2011
147
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
8.1.7 Communication Error when Sending PI Messages from
Messaging System to Integration Engine or from
Integration Engine to Messaging System
Problem
1. The messaging system of the Advanced Adapter Engine tries to send a
message to the Integration Engine but fails with a communication error, for
example:
For asynchronous call:
Transmitting the message to endpoint
http://pwdf6278:50036/sap/xi/engine?type=entry using connection
Axis_http://sap.com/xi/XI/System failed, due to
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error transmitting the message over HTTP. Reason:
java.net.ConnectException: Connection refused: connect.
For synchronous call:
Transmitting the message using connection Axis_http://sap.com/xi/XI/System
failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error transmitting the message over HTTP. Reason:
java.net.ConnectException: Connection refused: connect.
Note the connection prefix is sender adapter type specific (File, JDBC, etc).
The error message is different if the port cannot be reached at all.
when the message is successfully transmitted, the following entry is written:
The message was successfully transmitted to endpoint
http://pwdf6278:50036/sap/xi/engine?type=entry using
connection Axis_http://sap.com/xi/XI/System.
2. Integration Engine tries to send a message to messaging system of the
Advanced Adapter Engine but fails with a communication error, for example:
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
The error message is different if the port is blocked or returns an error.
Analysis
1. Check the following:
 Check the audit log of the message in the messaging system
according to the Error Tracking in the J2EE Adapter Engine section.
 Check the URL that is used to send the message to PI, for example
https://server:ICM-port/sap/xi/engine?type=entry.
 Try to execute the URL in the browser using the user
XIAFUSER/PIAFUSER (name as set during installation).
 Check the error you get:
148
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
o
o
o
o
Page cannot be displayed, cannot find server  server:port
not accessible
HTTP 401  unauthorized
HTTP 403  forbidden
HTTP 404  not found
2. Check the following:
 Check the outbound binding of the message in transaction
SXMB_MONI
 Find the party/communication component/channel the message is
sent to in the tags SAP:PartyName, SAP:ServiceName,
SAP:ChannelName
 Find this channel in the Integration Directory and check which Adapter
Engine is used  central Adapter Engine or af.<sid>.<host>
 Call transaction SXI_CACHE and choose Goto  Adapter Engine
Cache
 Check the URL for the Adapter Engine (CA stands for the Integration
Server – central Adapter Engine), for example
https://server:J2EE-port/MessagingSystem/receive/AFW/XI
 Try to execute the URL in the browser using the user
XIISUSER/PIISUSER (name as set during installation).
  Check the error you get:
o Page cannot be displayed, cannot find server  server:port
not accessible
o HTTP 401  unauthorized
o HTTP 403  forbidden
o HTTP 500  internal server error
o HTTP 503  service not active
Solution
1. There are different solutions:
a. Page cannot be displayed, cannot find server
If HTTPS is used but you want to use HTTP, SSL is probably
activated by mistake.
To deactivate SSL for PI messaging, do the following:
o Open the exchange profile:
http://server:port/dir  Administration  Exchange-Profile
o Delete the messaging value in the
com.sap.aii.connect.secure_connections parameter in the
Connections section.
o Save it.
o Restart the Java server to activate the change.
o Restart the message.
b. Page cannot be displayed, cannot find server
If HTTPS is used but you want to use HTTPS:
February 2011
149
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
o
Check and correct the SSL configuration for the ABAP and
Java sides of the system.
For more information about security in PI, see the SAP NetWeaver
Process Integration Security Guide.
c. HTTP 401
o User XIAFUSER/PIAFUSER has used the wrong password.
o Check the exchange profile and transaction SU01; try to
reset the password.
o Restart the Java Engine to activate changes in the exchange
profile.
d. HTTP 403
o Path sap/xi/engine not active.
o Activate the service engine in transaction SICF as described
in the PI Installation Guide.
e. HTTP 404
o The specified path cannot be found using the server:port
o Check that the port really is the ICM HTTP port (transaction
SMICM) and not the Java port.
o If the port is wrong, change the pipeline URL in the SLD in
the business system of the Integration Server.
o Restart the Java Engine to reset the SLD buffer of the
Adapter Engine.
2. There may be different solutions:
a. Page cannot be displayed, cannot find server
If HTTPS is used but you want to use HTTP, SSL is probably
activated by mistake.
To deactivate SSL for XI messaging, do the following:
o Open the exchange profile:
http://server:port/dir  Administration  Exchange-Profile
o Delete the messaging value in the
com.sap.aii.connect.secure_connections parameter in the
Connections section.
o Save it.
o Restart the Java server to activate the change.
o Delete the Adapter Engine cache in transaction SXI_CACHE
Goto  Cache.
o Restart the message.
b. Page cannot be displayed, cannot find server
If HTTPS is used but you want to use HTTPS:
o Check and correct the SSL configuration for the ABAP and
the Java side of the system.
c. HTTP 401
150
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
o
o
o
o
o
User XIISUSER/PIISUSER has used the wrong password.
Check the exchange profile and transaction SU01; reset the
password.
Restart the Java Engine to activate changes in the exchange
profile.
Delete the Adapter Engine cache in transaction SXI_CACHE
Goto  Cache.
Restart the message.
d. HTTP 403
o User XIISUSER/PIISUSER has no authorization to send
messages to the messaging system.
o This is caused by a deployment error of the Java Engine.
o Undeploy the component com.sap.aii.af.ms.app and
redeploy SAPXIAF*.sca.
o Restart the message.
e. HTTP 500
o Internal error in Java.
o Check the default trace file of the Java Engine using the
SAP NetWeaver Administrator.
f.
HTTP 503
J2EE application com.sap.aii.af.ms.app not active
o Try to (re)start the application using the SAP NetWeaver
Administrator. Choose Systems  Start & Stop  Java EE
Applications or restart the Java engine.
Business Process Engine (BPE) Runtime
8.1.8 Getting Started
Problem
You want to define a business process and need information about how to start.
Solution
Use the SAP Library tutorial Defining an Integration Process to define your first
business process and to get started with BPE.
8.1.9 First Checks
Problem
You have problems in the runtime of your BPE scenario. You want to check whether
your system is correctly configured or whether the system self-diagnosis finds any
related issues. You want to know how to monitor integration processes.
February 2011
151
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Analysis
Before starting to analyze your processes in detail, you should check the global
settings for the BPE in your system. For more information, see SAP Note 807640 BPE-TS: Troubleshooting Guide and the SAP Notes it refers to.
Check the CCMS monitor templates by calling transaction RZ20 and choosing SAP
CCMS Monitor Templates, Process Integration, or by calling transaction
S_B6A_52000011. Check the monitors from the Business Process Engine area for
errors or warnings. Execute the analysis method of the monitors with open alerts.
This will display troubleshooting information related to the error. Follow the advice
given by the analysis method.
Check the messages and process instances related to the problems using the
workflow log. For more information about how to monitor integration processes, see
the SAP Library section Monitoring Integration Processes.
8.1.10
Making Correct Use of Integration Processes
Problem
You cannot decide whether the BPE is the right tool to fulfill the requirements of your
business.
Analysis
You can check all prerequisites for the usage of BPM in the checklist documents in
SAP Library section Defining and Managing Integration Processes.
8.1.11
Message Is Not Received by Business Process
Problem
A message routed to an integration process has not been received by any process
instance. You have checked the related CCMS monitor templates Process
Scheduling, Eventing, and Message dispatching from the Runtime area and “XML
messages” from the Process data area, but they do not help you in finding the cause
of the problem.
Analysis
First, check for configuration errors in the Integration Directory, for example, missing
interface determinations to map the interface of the message to the corresponding
abstract interface of the process. Make sure that the quality of service matches the
one expected by the process, that is, sending synchronous messages (quality of
service BestEffort) to a process with only asynchronous service operations in the
process signature will not work. Check whether the payload matches the definition in
the Enterprise Services Repository with respect to the operation of the service
interface, that is, whether the payload has the expected root tag and namespace.
152
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Check whether the queue used for the message has been stopped by an error. In
message monitoring (SXI_MONITOR) use the “PE” or “SA_COMM” hotspot in the
outbound adapter column to navigate to the queue monitor. Double-click the top
entry in the queue in its User, Queue Name, StatusText or TID column. This will
bring up a support tool screen with information about the message and the BPE
inbound configuration and several support services. Use the information and the
services to check for common problems:

Check whether the error message shown helps to resolve the problem.
Search for SAP Notes using the error message text or the message identifier
which is typically from the SWF_XI_INBOUND message class.

Check whether simulating the message delivery shows the expected result. If
the simulation result shows a specific process instance, use the log button to
navigate to its workflow log and check whether the process instance is in
error status. Note that messages cannot be delivered to process instances in
error status or, if buffering is turned off, to processes without active receive
steps, so follow the advice in the corresponding section to continue the
process instance. If it is not possible to continue the instance, logically delete
it using the procedure described in SAP Note 807906 - BPE-TS: Deleting
Process with Correlations, deactivating the correlation instance that routed
the message to the process instance.

Check whether the correlations in your process definition are correctly
scoped. Check troubleshooting SAP Notes 1040614 - BPE-TS: Process
Instance Contains No Active Receive Steps and 1040354 - BPE-TS:
Unprocessed Messages, which describe the most common errors.

If your process definition uses send, transformation, or receiver determination
steps that do not create a new transaction and that directly follow the receive
step, the cause of the stopped queue could be a process failing in its first
transaction, for example, because of a synchronous call returning an
exception from the receiver application. For background information, see the
How-To Guide How to Configure ccBPM Runtime Part III: Transactional
Behavior of an Integration Process (not available yet for PI 7.3, but the XI 7.0
guide can still be used). For troubleshooting purposes, you might want to
temporarily activate the step property “Create New Transaction” in the
process definition, unlock the stopped queue, and check the workflow log of
the process instance that is now being created, because the process instance
will now fail in a transaction following process instantiation.

If you cannot solve the problem with the guidance given, display the trace
using the corresponding service of the support tool. Check the trace data by
double-clicking the data column of the trace lines. Attach a screenshot of the
Exceptions item tree completely expanded or the data downloaded using the
Save Locally as XML file button to a customer message on the subject.
February 2011
153
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
8.1.12
Process Instance in Status ERROR
Problem
An integration process has been triggered but it has the status ERROR.
Analysis
Check the step history of the technical workflow log for error messages. If the error
messages report communication failures, check whether the Java mapping runtime
is up and running, and whether the receiver system can be reached. After resolving
these communication problems, process instances can usually be continued. Call
transaction SWF_XI_SWPR to restart these process instances with errors.
If restarting the process instances does not succeed, check whether the error
message in the step history helps you to find the cause. If the step with errors is a
transformation step, check the mapping trace (see the corresponding section). If you
cannot resolve the problem with the trace, forward the customer message to
component BC-XI-IBD-MAP.
If the step with errors is a send step, check whether it is failing due to a negative
acknowledgment being received. In this case, you might have to take appropriate
measures to handle this in your process definition, for example, define an exception
branch to handle the problem. If the send step is of mode Synchronous, check the
error message from the receiver system or the messaging layer and take appropriate
actions. If you cannot resolve the issue based on this error message (for example, by
creating an exception branch for the fault message or the system error) and the help
given in the corresponding sections of this document, forward the customer message
to BC-XI-IS-IEN for a detailed analysis.
8.1.13
Process Instance Does Not Continue
Problem
A process instance is not continuing as expected and remains in status STARTED
(in process).
Analysis
Check the system log (transaction SM21) and the ABAP runtime errors (transaction
ST22) for entries corresponding to the time when the process stopped. Resolve the
problems described in the log entries. Then use transaction SWF_XI_SWPC to
continue these process instances.
8.1.14
Display Mapping Trace
Problem
A transformation step raised a system error unexpectedly. You want to check the
mapping trace to check why it failed.
154
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Analysis
Navigate to the workflow log and display the view with technical details. Select the
transformation step in question and open the container tab page. Select the TRACE
container element. If the step does not create a new transaction, the trace is shown
in the text area in the lower part of the dialog. Otherwise, use the context menu entry
“Default method” in the TRACE container element to display the mapping trace.
8.1.15
Problems Related to Service Interfaces
Problem
You are sending a message to an integration process component. The message is
set to error status with the error code BPE_ADAPTER UNKNOWN_MESSAGE.
A transformation step or synchronous send step fails with the error message "No
definition exists for <Interface Namespace> <Interface Name>" (SWF_XMP 021).”
Analysis
Service interfaces that support multiple operations are introduced in SAP NetWeaver
PI 7.1. The message interfaces known from prior releases are still supported by
creating service interfaces of category "XI 3.0 compatible", which restricts them to
only provide a single operation, the so-called default operation.
Operations are distinguishable by the underlying message type, which in turn has to
be defined by a unique root tag and its namespace. Integration processes accessing
service interfaces having multiple operations enforce use of the correct operation by
checking the name and namespace of the payload‟s root element (root tag). When
new messages enter the Business Process Engine (BPE), that is, if a message is
received (using a receive step or synchronous send step) or created (using a
transformation step), its root tag has to match the operation‟s message type,
otherwise the respective step fails.
If messages are not accepted by the BPE with the aforementioned error messages,
check whether the actual payload matches the definition of the message type of the
operation. With respect to the namespace, the subtle differences between the default
namespace (<root xmlns="urn:example:com">), an explicit namespace (<ns1:root
xmlns:ns1="urn:example:com">), an empty namespace (<ns1:root xmlns:ns1="">),
or a tag without an associated namespace (<root>) are a typical source of error.
The requirement that the root tag matches the definition in the Enterprise Service
Repository is not enforced for category "XI 3.0 compatible" service interfaces. This
includes scenarios upgraded from SAP NetWeaver '04 or SAP NetWeaver 7.0. On
the other hand, in scenarios using service interfaces with multiple operations, the
root tag of the payload must adhere to the definition in the ES Repository.
February 2011
155
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
8.1.16
Generic User Decisions
8.1.16.1 Work Item Title
Problem
In the work item list in the Business Workplace, some, or all, of the user decision
work items have "generic decision task" as the title instead of the title configured in
the process definition.
The title of a user decision work item is displayed in a language different from the
user's logon language.
Analysis
The user's logon language differs from the language with which the work item was
created or the title has not been translated into the user's logon language. Due to
performance reasons, the work item titles are not translated into the user's logon
language by default when viewing the list of work items. Instead, the title is displayed
in the language the work item was created with or, if it has not been translated to this
language, the default title for user decisions is displayed.
Make sure that all necessary translations of the title were provided in the process
definition and have been activated. In the Business Workplace, use the menu path
Settings  Workflow Settings  Personal Settings and select the setting Display
Work Item Texts in Logon Language. To change the default for all users, use the
SAP reference IMG in transaction SPRO, path Application Server  Business
Management  SAP Business Workflow  Basic Settings (Workflow System) 
Change Defaults for Personal Workflow Settings.
8.1.16.2 Options of the User Decision
Problem
In the user decision work item in the inbox, the options are all labeled with the same
text so that users do not know which one to choose.
Analysis
The user decision texts have not been translated into the language the user is
logged on in. Translate the texts of the relevant integration process in the Enterprise
Services Builder and activate the changes.
156
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
8.1.17
Message Packaging
8.1.17.1 Reconfiguration
Problem
The reconfiguration of one of the integration processes has been started using
transaction SWF_INB_CONF. However, the reconfiguration does not finish although
no hanging queues are to be found in transaction SMQ2. ccBPM message
packaging is in use in the system.
Analysis
There are still messages to be delivered with the previous configuration. Use
transaction SWF_INB_ADM to check for messages in error, suspended messages,
or messages with scheduled status. If these messages are no longer deliverable, for
example, due to the errors not being recoverable, or because no more delivery
attempts are to be made, logically delete them using the relevant administration
function. As soon as all pending messages for the previous configuration have
reached a final status (either delivered or cancelled), the reconfiguration is
processed.
8.1.18
Principal Propagation
8.1.18.1 Enabling Principal Propagation for a Process
Problem
You want to enable principal propagation for one of the integration processes.
However, in transaction SWF_INB_CONF, the checkbox is missing for this
integration process but it is shown for others.
Analysis
Integration processes can only propagate the principal of the message starting the
process instance. To avoid ambiguity at runtime, principal propagation can only be
enabled for processes that do not use correlations (that is, there are no inbound
messages besides the starting message). If your process needs to use correlations,
principal propagation cannot be enabled for this process.
If your process has only a single inbound message, but you are still not able to
activate principal propagation, check that no correlations are defined or used in the
process definition. Remove any correlation definition, usage, or activation and
activate the changes made to the process definition. You should now be able to
configure principal propagation for this process in transaction SWF_INB_CONF.
February 2011
157
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
8.1.19
Usage of Alert Categories
8.1.19.1 Language Issue: Wrong Language
Problem
Alerts based on ESR alert categories are delivered as e-mails in a language that is
different from the receiving user‟s language.
Analysis
E-mail alerts are not translated into the receiving user‟s language. They are always
delivered in the logon language of the user that processed the control step raising
the alert. Typically, this is the technical user WF-BATCH or one of the other SAP
NetWeaver PI service users.
If you want to ensure a certain language for the e-mails, change the logon language
of the relevant technical user using transaction SU01. If the language of the alert text
is to adapt to the user‟s preferences, the alert inbox has to be used.
8.1.19.2 Language Issue: Generic Text Instead of Alert Short Text
Problem
Alerts based on ESR alert categories are delivered as e-mails with the generic text
“The triggering application determined you as a recipient” instead of the alert short
text.
Analysis
As already stated, e-mail alerts are delivered in the logon language of the user that
processed the control step raising the alert. If no translation of the alert texts is
available for the logon language of the processing user, the fallback text “The
triggering application determined you as a recipient” is used based on message 005
from message class SALERT.
Translate the alert category texts into the logon language of the processing user
using the relevant menu function of the alert category object in the ES Repository.
8.1.20
Prerequisites for Troubleshooting
Remote Connection
SAP R/3 connection to the Integration Server
Front-end connection to Integration Builder
For more information, see SAP Note 769478 - Remote Connection with XI Systems.
158
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Technical Information
According to SAP Note 792971 - BPE: Preparation for an OSS Message, SAP
Support requires the following information:
In the Enterprise Services Repository
 Software component (SWC)
 Software component version (SWCV)
 Namespace
 Integration process
o Step
(if applicable)
o Correlation(if applicable)
 Service interface(s)
At Runtime
 Message GUID
 Process ID
 Queue name
February 2011
159
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
9 PI Communication
Internal Communication
Several PI components are included in a PI landscape. Different technical
connections are used to connect all of them. The PI components themselves are
connected using HTTP and RFC.
Repository
ABAP
Proxy
Runtime
SAP>=6.20
Directory
RWB
SLD
ABAP
Integration Server
XI
Design
Configuration
Monitoring
XI
Integration Engine
IDoc
XI3.0/7.0
Integration
Servers
http
non XI
Back-End
Application
Systems
SAP <=6.10
Central AE
XI
RNIF
PCKs
JMS
...
Non-SAP
systems,
external
partners
XI
RFC
J2EE
Non-Central AE
XI
RFC
RNIF
JMS
...
Java EE
Technical/Internal
Communication
Problem
You want to know more about the existing technical communication within PI and
want to know how to analyze and solve problems in these connections.
Setting Up the Connection
The connection data used to set up the technical communication is stored in different
places, mainly the exchange profile and the SLD. Specific configuration is available
for special connections, for example SM59 destination for cache refresh.
The standard way for one PI component to connect to another is as follows: the
component that wants to establish a connection (the source component) gets its own
specific user name and password from the exchange profile and the host and port for
the target to connect to either from the exchange profile or the SLD. If, for example,
the Integration Server tries to set up a connection to the Adapter Engine, it gets the
Integration Server service user and password from the exchange profile (EP) and the
160
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
host and port of the Adapter Engine from the SLD. The following table shows where
which information is stored:
authentication data:
source username, password
connection data:
target host, port
SLD
-
EP
Repository
EP (e.g. user XIREPUSER)
EP
Directory
EP (e.g. user XIDIRUSER)
EP
Integration Server
EP (e.g. user XIISUSER)
EP
Integration Engine
-
SLD
Adapter Engines
EP (e.g. user XIAFUSER)
SLD
RWB
EP (e.g. user XIRWBUSER)
EP
The connection is set up using this data:
Exchange Profile data:
Component A
Connection (EP/SLD):
com.sap.aii.connect.<component B>.*
Authentication (EP):
com.sap.aii.<component_A>.serviceuser.*
Component B
As you can see in the table, there are two types of connections:

Using EP only: Read connection data of source and target from EP

Using SLD:
- Read authentication data of source from EP
- Read connection data of target:

Read connection data of SLD from EP

Read connection data of target from SLD
So, if the target data needs to be read from SLD, the component first reads the
connection data for the SLD from the exchange profile and uses this data to connect
to the SLD to get the target connection information (host/port).
For more information about the users used for internal communication and which
authorizations are needed, see section User Concepts.
Access to Exchange Profile:
All components need to access the exchange profile to get connection and user data
and other data relevant for message processing and PI configuration. The
connection is set up differently for ABAP and Java components:
Java Components:
The Java components connect to the exchange profile using the RFC connection set
up under the Connection link in the exchange profile UI. The technical user used is
XILDUSER/PILDUSER.
Checks and traces:
February 2011
161
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide

Check availability of exchange profile page (http://server:port/dir 
Administration  Exchange-Profile) and errors there.

Check default.trc of the Java Engine for errors (SAP NetWeaver
Administrator).
You set the trace level of the source location (for example, com  sap  aii
 ibdir for Directory) in the Log Configuration Service in SAP NetWeaver
Administrator. For information about how to increase the trace level, see SAP
Note 761921 - Creating an XI adapter framework trace file.

Logs of the source components accessing the exchange profile and SLD (see
below).
ABAP (IS and Integration Engines):
The ABAP components connect to the exchange profile using the SM59 destination
LCRSAPRFC.
Checks and traces:

Type-T destination LCRSAPRFC on IS - connection test in transaction SM59

Execute transaction SLDCHECK
Access to SLD
The PI components need to connect to the SLD to get connection and landscape
data and for the SLD self-registration. The connection is set up differently for ABAP
and Java components:
Java Components:
The Java components get the connection data for the SLD from the exchange profile
and establish an HTTP connection to the SLD to get connection or to execute the
self-registration at the SLD.
Checks and traces:

Check availability of the SLD page and errors under Administration  Log

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level of the source location (for example, com  sap  aii
 ibdir for Directory) in the Log Configuration Service in SAP NetWeaver
Administrator. For information about how to increase the trace level, see SAP
Note 761921 - Creating an XI adapter framework trace file.

Logs of the source components accessing the exchange profile and SLD (see
below)
ABAP Components (IS and Integration Engines):
The ABAP components connect to the SLD using the SM59 destination SAPSLDAPI
and the data in transaction SLDAPICUST to get connection and own landscape
data.
162
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Checks and traces:

Type-T destination LCRSAPRFC on IS - connection test in transaction SM59

Execute transaction SLDCHECK
Logs and Traces of the Source Components Accessing Exchange Profile and
SLD
To get information about errors, you should check not only the logs and traces of the
exchange profile and SLD themselves, but also the logs of the source application
trying to establish a connection.
Repository (for example, for sending cache notification for adapter metadata
changes)
Checks and traces:

Check Repository memory log for errors
http://server:port/rep/support/private/index.html  View Memory Log  Show
this filter

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level for location com  sap  aii  ibrep in the Log
Configuration Service in SAP NetWeaver Administrator. For information
about how to increase the trace level, see SAP Note 761921 - Creating an XI
adapter framework trace file.
Directory (for example, for getting the Adapter Engines from SLD)
Checks and traces:

Check Directory memory log for errors
http://server:port/dir/support/private/index.html  View Memory Log  Show
this filter

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level for location com  sap  aii  ibdir in the Log
Configuration Service in SAP NetWeaver Administrator. For information
about how to increase the trace level, see SAP Note 761921 - Creating an XI
adapter framework trace file.
Adapter Engine (for getting connection data for Integration Server from SLD to send
messages)
Checks and traces:

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level for location com  sap  aii  af* in the Log
Configuration Service in SAP NetWeaver Administrator. For information
about how to increase the trace level, see SAP Note 761921 - Creating an XI
adapter framework trace file.
February 2011
163
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
RWB
Checks and traces:

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level for location com  sap  aii  rwb in the Log
Configuration Service in SAP NetWeaver Administrator. For information
about how to increase the trace level, see SAP Note 761921 - Creating an XI
adapter framework trace file.
Connections Between PI Components
After getting the connection data from EP and SLD, the connection is set up and the
components communicate directly with each other. The connections between the
Repository, Directory, Integration Server, and Adapter Engines are mainly HTTP
connections for cache refreshes and to get data for the F4 Help. For information
about errors you should check the logs and traces of the two communicating
components.
Repository/Directory
Checks and traces:

Check Repository/Directory memory log for errors
http://server:port/rep/support/private/index.html
http://server:port/dir/support/private/index.html  View Memory Log  Show
this filter

Check cache notification table in the event of caching problems
Repository/Directory  Environment  Cache Notifications

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level for location com  sap  aii  ibdir/ibrep in the Log
Configuration Service in SAP NetWeaver Administrator. For information
about how to increase the trace level, see SAP Note 761921 - Creating an XI
adapter framework trace file.
Integration Server
Checks and traces:
164

Destination INTEGRATION_DIRECTORY_HMI from IS to Directory for cache
refresh – connection test in transaction SM59

Check transaction SXI_CACHE  XI Runtime cache  Display refresh error
for errors

Check dev_icm trace for HTTP communication (SAP Note 634006 - ICM
messages explanatory note)
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Adapter Engine
Checks and traces:

Check CPACache history page in the event of caching problems
http://server:port/CPACache  View cache update history  View
confirmation XML

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level for location com  sap  aii  af* in the Log
Configuration Service in SAP NetWeaver Administrator. For information
about how to increase the trace level, see SAP Note 761921 - Creating an XI
adapter framework trace file.
Monitoring Communication in RWB
There are several components involved in the RWB monitoring communication, for
example Alert Framework, PMI, SLD, CCMS, and TREX.
get component data
RWB
SLD
get CEN data
TREX monitoring
CEN
(Central Monitoring Server)
CCMS
Alerting
PMI
TREX
message monitoring/
self test
indexing
heartbeat
send alerts
PI
components
get PMI data
RWB communication itself:
1. Reading landscape from SLD:
The connection used is an HTTP connection with the SLD parameters read from the
exchange profile.
Checks and traces:

Check availability of SLD page and errors under Administration  Log

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level for location com  sap  aii  rwb in the Log
Configuration Service in SAP NetWeaver Administrator. For information
February 2011
165
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
about how to increase the trace level, see SAP Note 761921 - Creating an XI
Adapter Framework Trace File.
2. Message search in TREX
The connection used is a TCP/IP connection using the TREX Service property
nameserver.address.
Checks and traces:

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level for location com  sap  aii  rwb in the Log
Configuration Service in SAP NetWeaver Administrator. For information
about how to increase the trace level, see SAP Note 761921 - Creating an XI
Adapter Framework Trace File.
CEN (Central Monitoring Server) communication:
The following connections are involved:

CCMS: heartbeat
Connections used are HTTP destinations; for more information, see SAP
Note 634771 - GRMG Customizing File for XI CCMS Heartbeat Monitoring.

PMI: data collection
For the CEN data collection, the RFC destination PMI<business-system>
from CEN to IS/IE is used.
The data of Java components is sent to the Integration Server using Java
Service destinations service  HTTP destination: pmistore.

Components alerting to CEN
Integration Server and Integration Engine use the RFC destination
CentralMonitoringServer-XIAlerts containing exchange profile connection
data (parameters com.sap.aii.rwb.server.centralmonitoring.* and
com.sap.aii.rwb.serviceuser.*).
The Adapter Engines use an RFC JCo connection using exchange profile
connection data (parameters com.sap.aii.rwb.server.centralmonitoring.* and
com.sap.aii.rwb.serviceuser.*).
Checks and traces:

R/3: Test connection of the involved SM59 destinations

Check dev_rfc traces for RFC communication

Check dev_icm trace for HTTP communication (SAP Note 634006 - ICM
Messages Explanatory Note)

Java: Check default.trc of Java Engine for errors (SAP NetWeaver
Administrator)
You set the trace level for location com  sap  aii  rwb in the Log Configuration
Service in SAP NetWeaver Administrator. For information about how to increase the
trace level, see SAP Note 761921 - Creating an XI Adapter Framework Trace
File.TREX Message Indexing:
166
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
ABAP components connect to TREX using the RFC destination as specified in IS
configuration parameter TREX_RFC_DESTINATION of category MONITOR.
Checks and traces:

Test connection of the SM59 destination

Check dev_rfc traces for RFC communication
Java components connect to TREX using a TCP/IP connection set up using the
property nameserver.address of the Java Service TREX Service.
Checks and traces:

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level for location com  sap  aii  rwb in the Log
Configuration Service in SAP NetWeaver Administrator. For information
about how to increase the trace level, see SAP Note 761921 - Creating an XI
adapter framework trace file.
Caching Communication
.
Business system
Integration Builder
•Activate Changelist
•Import
•Request Cache update again
SLD Cache “Own Business system”
Integration Server
Cache
Update
Cache
•
Business
Processes
• Mappings
• Business
Process
Configuration
• Routing Rules
• Collaboration
Agreements
• Collaboration
Profiles
TA: SXI_CACHE
•Delta
•Full (only
on request)
Cache
J2EE: CPACache
•Delta
•Full using URL
Runtime
Access
Integration
Engine
Central Adapter
Engine
SLD Cache “Own Business system”
SLD Cache
Software
components
Components
Business
Process
Engine
SLD Cache
Business
systems
Systems
Cache Update
Repository
Cache
Enterprise
Services
Integration
Repository
Repository
February 2011
Adapter Meta
data
Integration
Directory
Decentral Adapter Engine
Cache
J2EE: CPACache
•Delta
•Full using URL
Adapter
Framework
167
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
All PI components use several caches to cache data from the SLD, exchange profile,
or data from other components. The caches and connections used are described in
the section Analysis of Cache Problems and the guide How to Handle Caches in
SAP XI 3.0 (not available yet for PI 7.1, but the XI 3.0/7.0 guide can still be used).
Integration Builder Tool Access (Repository/Directory)
For the Enterprise Services Repository and Integration Directory, Java Web Start on
the client side is used. The Integration Builder client is downloaded to the client PC,
then an Integration Builder client-server connection is used.
Checks and traces:

Switch on the console output and activate the tracing on the Java Web Start
Control Panel
Open Java Web Start (Javaws.exe) and choose the menu entry Settings.

Check Repository/Directory memory log for errors
http://server:port/rep/support/private/index.html
http://server:port/dir/support/private/index.html  View Memory Log  Show
this filter

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level for location com  sap  aii  ibdir/ibrep in the Log
Configuration Service in SAP NetWeaver Administrator. For information
about how to increase the trace level, see SAP Note 761921 - Creating an XI
Adapter Framework Trace File.
168
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Messaging Communication
The communication from and to external systems to exchange messages is done
using the PI protocol or the protocol the specific adapters support (RFC, HTTP, FTP,
and so on)
Repository
Directory
RWB
SLD
ABAP
Integration Server
ABAP
Proxy
Runtime
SAP>=6.20
XI
Design
Configuration
Monitoring
XI
Integration Engine
Idoc
XI 2.0, 3.0
Integration
Servers
http
non XI
Central AE
Backend
Application
Systems
SAP <=6.10
XI
RFC
XI
PCKs
RNIF
JMS
...
Non-SAP
systems,
external
partners
J2EE
Decentral AE
XI
RFC
RNIF
JMS
...
J2EE
messaging
Problem
You want to know more about the messaging communication in PI and how to
analyze and solve problems in these connections.
Analysis
(s1)
XI, U=c(s1)
ABAP
Proxy
IS
Integration
Server
(r1)
XI, U=d(IS)
ABAP
Proxy
IDoc, U=d(IS)
SAP
legacy
(s2)
(r2)
IDoc, U=c(s2)
SAP
legacy
(s3)
(r3)
plain http, U=c(s3)
http
sender
(s4)
Java
Proxy
Runtime
Java
Proxy
Runtime
XI
U=d(IS)
(s5)
non-PI
System
non-XI, U=c(s3)
plain http, U=d(IS)
Adapter
Engine
XI
U=XIAFUSER
XI
U=XIISUSER
(r4)
(r5)
Adapter
Engine
non-XI, U=d(IS)
non-PI
System
(r6)
(s6)
IS/PCK
http
receiver
XI, U=d(s6)
XI, U=d(IS)
IS/PCK
The figure shows the possible connections for PI messaging.
February 2011
169
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide

The connection data from the sender side to the PI system is maintained in
the sender systems locally: [c(s)]

The connection data from PI to the receiver system is maintained in the
Integration Directory channels in the PI system: [d(IS)]

The connection data between IS and Adapter Engines is maintained in the PI
itself in the exchange profile and/or SLD: [XI]
For more information about the users used for messaging communication and the
required authorizations, see section User Concepts.
Checks and traces:

Check error tag in message in transaction SXMB_MONI or RWB monitoring

Check logs and traces of the involved (adapter-) specific communication (see
below)
Another connection involved during messaging is the mapping connection to the
Java mapping runtime:

The internal SM59 destination AI_RUNTIME_JCOSERVER from IS to the
Java Engine is used for mapping
Checks and traces:

Test destination AI_RUNTIME_JCOSERVER in transaction SM59

Check dev_rfc traces

Check error trace tag in PI message in transaction SXMB_MONI

Check runtime memory log for errors during mapping
http://server:port/run/support/private/index.html  View Memory Log  Show
this filter

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
You set the trace level for location com  sap  aii  ibrun in the Log
Configuration Service in SAP NetWeaver Administrator. For information
about how to increase the trace level, see SAP Note 761921 - Creating an XI
Adapter Framework Trace File.
Supported Messaging Protocols
PI protocol (ABAP and Java proxies, IS, PCK):
The connection used is HTTP based.
Checks and traces:
170

Check dev_icm trace for HTTP communication (SAP Note 634006 - ICM
Messages Explanatory Note)

Check error trace tag in XI message in transaction SXMB_MONI

Check default.trc of Java Engine for errors (SAP NetWeaver Administrator)
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
You set the trace level for location com  sap  aii* in the Log Configuration
Service in SAP NetWeaver Administrator. For information about how to
increase the trace level, see SAP Note 761921 - Creating an XI Adapter
Framework Trace File.
IDoc:
The IDoc adapter communication is based on RFC protocol.
Checks and traces:

Check RFC queue (SM58) in sender and/or Integration Server

Check involved SM59 RFC destinations (for IDX1 and message transfer) –
Test connection

Check dev_rfc traces for RFC communication
RFC Adapter:
The RFC adapter communication is based on the RFC protocol.
Checks and traces:

Check in RWB channel monitoring

Check RFC queue in sender

Check involved SM59 RFC destinations – Test connection

Check dev_rfc traces for RFC communication

Check default.trc of Java Engine for errors in RFC adapter (SAP NetWeaver
Administrator)
Location for tracing: com.sap.aii.adapter.rfc*
Plain HTTP and SOAP:
The HTTP and SOAP adapters use HTTP protocol for communication.
Checks and traces:

Check in RWB channel monitoring

Check SM59 HTTP connection (is used)

Check dev_icm trace for HTTP communication (SAP Note 634006 - ICM
Messages Explanatory Note)
RNIF and CIDX:
RNIF and CIDX communicate using the HTTP protocol.
Checks and traces:

Check in RWB channel monitoring
February 2011
171
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide

Check default.trc of Java Engine for errors in adapters (SAP NetWeaver
Administrator)
Locations for tracing:
com.sap.aii.adapter.rnif.ms & com.sap.aii.adapter.rnif11.ms (RNIF)
com.sap.aii.adapter.cidx.ms (CIDX)
SOAP, Business Connector, and MarketSet:
These adapters communicate using the HTTP protocol.
Checks and traces:

Check in RWB channel monitoring

Check default.trc of Java Engine for errors in adapters (SAP NetWeaver
Administrator)
Location for tracing:
com.sap.aii.adapter.soap* (SOAP)
com.sap.aii.adapter.bc* (BC)
com.sap.aii.adapter.marketplace* (Marketplace)
Other technical adapters: File, FTP, Mail, JMS, JDBC (AE (Java EE))
These adapters communicate using their own specific protocols.
Checks and traces:

Check in RWB channel monitoring

Check default.trc of Java Engine for errors in adapters (SAP NetWeaver
Administrator)
Location for tracing:
com.sap.aii.adapter.file* (File/FTP)
com.sap.aii.adapter.mail* (Mail)
com.sap.aii.adapter.jms* (JMS)
com.sap.aii.adapter.jdbc* (JDBC)
Technical adapters: File, FTP, JMS, JDBC & SOAP (Java SE AE)
Checks and traces:

172
Check logs adapter_<number>.log and <Name_of_adapter>.log in the
Adapter Engine (JavaSE)
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
10 Caches
Analysis of Cache Problems
In PI there are several caches established to make the communication between PI
components as fast as possible. The most important caches are the PI runtime
cache (transaction SXI_CACHE) for the ABAP runtime and the CPACache for the
Adapter Engine runtime.
Problem
You need information about how to analyze and solve problems associated with the
PI caches.
Analysis
For an overview of cache refresh errors in the Enterprise Services Repository or
Integration Directory, see SAP Note 780747 - Cache Overview Displays Errors.
For troubleshooting information about problems in the CPACache refresh, see SAP
Note 741214 - Troublesh. During Cache Update of the J2EE CPACache Service.
For information about the PI caching infrastructure and about where to find
information about possible errors and how to solve them, see the guide How to
Handle Caches in SAP XI 3.0 (not available yet for PI 7.1, but the guide for XI 3.0/7.0
can still be used).
JAVA_CACHE
10.1.1
Problems and Solutions
10.1.1.1 CPA Cache Cluster Contents Inconsistent
Context
The essence of the cache update mechanism to keep the central configuration data
in sync with the several configuration cache implementations in AS Java and AS
ABAP. It is HTTP- based and after any configuration change, the Integration
Directory (ID) sends an invalidation event to the CPACache of any known (de)central Advanced Adapter Engine (AAE).
The AAE then tries to retrieve the changed configuration from the ID, authenticating
itself by its SLD instance name. The cache update transports the configuration in
XML format. In PCK mode, the CPACache service does not accept any cache
invalidation HTTP requests.
February 2011
173
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Problem
If errors occur in the asynchronous cluster communication, CPA Cache contents of
some cluster nodes can become inconsistent.
Probability for such an error is very low, however it cannot be ignored. This issue has
also been reported for customer systems. Presently in such case customer needs to
restart CPA Cache Service on all cluster nodes, as there is no way to find out the
node on which the CPA Cache contents are inconsistent.
Solution
The solution currently available is either to restart the CPA Cache service or to do a
full cache refresh. Both solutions are time-consuming for a production system. The
new solution is to do the local synchronization. Here the nodes will update their inmemory cache with the CPA objects present in the database.
To trigger a local synchronization, perform the following steps:
1. Open NWA (http://<host>:<port>/nwa) and choose SOA  Monitoring  PI
Cache Monitoring. Choose Synchronize. This action will trigger the local
synchronization of all the nodes. To check the status of synchronization,
choose Synchronization Status.
2. Perform a dummy delta refresh using the following link. http://<host>:<port>/
CPACache/refresh?mode=dummy_delta.
Problems and Solutions
10.1.1.2 Unable to Find an Associated SLD Element
Problem
The cache refresh does not work. The error Unable to find an associated SLD
element is in the cache notifications/problems tab page in the Directory, in
transaction SXI_CACHE, or in the CPACache monitor.
Solution
This error is caused by missing elements or inconsistencies in the SLD; sometimes
there is more than one domain registered and the elements are not in the same
domain. For more information and the solution, see SAP Note 764176 - Error in XI
due to inconsistent SLD contents and the section Analyzing SLD self-registration
problems.
174
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
SXI_CACHE
10.1.2
Problems and Solutions
10.1.2.1 AUTHORITY_NOT_AVAILABLE
Problem
The error message cl_http_client RFC_READ_HTTP_DESTINATION
AUTHORITY_NOT_AVAILABLE is displayed in transaction SXI_CACHE.
Solution
1. Check whether the user XIISUSER/PIISUSER (name as set during
installation) with password is maintained in transaction SM59 for the
destination INTEGRATION_DIRECTORY_HMI and that this user is not
locked (transaction SU01).
2. Check whether the user XIDIRUSER/PIDIRUSER (name as set during
installation) has a profile for the role SAP_XI_ID_SERV_USER. If not,
generate the profile and execute the user comparison.
10.1.2.2 NO_INTEGRATION_SERVER
Problem
The error message NO INTEGRATION SERVER is displayed in transaction
SXI_CACHE.
Solution
This error means that this system is not defined as an Integration Server, so the
cache will not be updated.
Check the following:
-
Call transaction SXMB_ADM  Integration Engine Configuration and
check if the role of the business system is Integration Server. Choose
Check (F7) to check if the configuration is consistent with the SLD.
-
Does the transaction SLDCHECK run without errors? Check if the
function call LCR_GET_OWN_BUSINESS_SYSTEM in transaction
SLDCHECK returns role = HUB. If the call returns role = LOC, the
system is defined as an application system in the SLD; no cache
refresh is carried out for application systems.
-
Is the correct SLD maintained in transaction SLDAPICUST?
February 2011
175
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
10.1.2.3 NO_BUSINESS_SYSTEM
Problem
The error message LCR_GET_OWN_BUSINESS_SYSTEM –
NO_BUSINESS_SYSTEM is displayed in transaction SXI_CACHE.
Solution
The system cannot find its business system in the SLD, so the cache is not updated.
Check the following:
176
-
Is the correct SLD maintained in transaction SLDAPICUST?
-
Does the transaction SLDCHECK run without errors? There is
probably no business system defined in the SLD for your system ID
and the current client.
-
Check that the com.sap.aii.connect.integrationserver.r3.client
parameter in the exchange profile corresponds to the Integration
Server client.
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
11 Mapping
Error Analysis of Mapping Problems
In PI you can create and assign mappings to execute them during message
processing in the PI runtime, as well as in the Advanced Adapter Engine Runtime. If
problems occur during mapping there are different options for analysis.
Problem
You are having problems with your mappings and want to analyze them.
Analysis
For more information about the mapping problem and how to increase the trace
level, see SAP Note 1061657 - PI 7.1: Analyzing mapping problems.
Value Mapping
The troubleshooting for value mappings is described in SAP Note 1061811 - PI 7.1:
Analysis of value mapping problems.
PAS: Mapping Fails for a Specific Message Type
Problem Description
The receiver application does not work properly due to incorrect data. Mapping is
used during the message flow.
Analysis
The following figure gives you an overview of the analysis process:
February 2011
177
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
1. Check Receiver Data
...
1. Log on to the receiver system and call monitoring transaction SXMB_MONI.
2. Choose Monitor for Processed XML messages.
3. Define the selection criteria as appropriate to reduce the list of messages.
4. Double-click the first column of the problematic message to display the details.
5. Check the received application data. Is the content as expected?
178
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
2. Is an Operation Mapping Executed on the Integration Server (IS)?
1. Log on to the Integration Server system and call monitoring transaction
SXMB_MONI.
2. Choose Monitor for Processed XML messages.
3. Define the selection criteria as appropriate to reduce the list of messages.
4. Double-click the first column of the problematic message to display the details.
5. Check whether an operation mapping has been executed:
There are two ways to do this:
a) Compare the payload before and after the mapping step (use the buttons
Window 1 and Window 2).
February 2011
179
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
b) Check the trace of the mapping step.
Three different outputs might occur. You can find the entry by searching
(CTRL-F in the window) for the text CL_MAPPING_XMS_PLSRV3ENTER_PLSRV. The relevant entry is contained in the next Trace tag.
a. No operation mapping is necessary. In this case, the trace contains
the message: No mapping required.
180
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
b. An operation mapping is executed. In this case the trace contains the
key information (name and namespace) of the executed operation
mapping.
c. An operation mapping is necessary but is not available in the cache.
In this case, the trace contains the following entry: Interface Mapping
XY is not present in the runtime cache.
3. Should an Operation Mapping Have Been Executed According to the
Configuration?
If you have analyzed the trace as described in section 2 with the result that an
operation mapping is necessary but not executed, the answer is clear – yes.
Otherwise, you have to perform the following steps to get the information:
You can access the information about the sender and receiver from the details of the
message.
February 2011
181
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
...
1. Log on to the Integration Directory.
2. Use the navigation tree on the Objects tab or the query to get the interface
determination used for the message.
182
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
3. Open the interface determination (with a double-click) and check whether an
operation mapping is defined.
4. Check the Operation Mapping Version Used
1. Open the interface determination in the Integration Directory (see above).
2. Start the Enterprise Services Repository and open the operation mapping
referenced by the interface determination (name, namespace, and software
component version are given).
3. Use the navigation tree starting with the software component (version), selecting
the namespace.
If the namespace is not visible, open the Basis Objects node. Look at the
namespaces listed there. This Basis Objects node contains the namespaces of
the software component versions the software component version is based on.
4. From the correct namespace, navigate to Operation Mappings. The mapping
should be present there.
5. To check the version, open the software component object from the navigation
tree and choose the SLD Info tab page. Look at the entry GUID.
February 2011
183
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
6. Compare the information about the name, namespace, and GUID of the software
component version with that used by the Integration Server.
a) Call transaction SXI_CACHE.
b) From the navigation tree, select the interface determination and double-click
it.
c) Compare the version ID field with the software component version of the
Repository and Mapping Name/Mapping Namespace field with the
information stored in the Directory. Any difference indicates that the cache is
not up-to-date and, therefore, that there is an incorrect version of the
operation mapping.
184
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
5. Check Mapping Program Version Used
1. Open the operation mapping in the Repository (see section 4).
Make sure that the object is in status Active (see status information at the top of
the editor). If it is in status Being processed, you are dealing with a version that is
part of your change list but not active, that is, not relevant for the cache (the
same is true for the mapping itself).
2. Navigate to the mapping program(s) (by double-clicking them). Different types of
mappings are possible.
February 2011
185
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
3. In the editor, choose the Info/Properties button to display the date of the last
change (Changed On).
4. To check the version of the mapping used on the Integration Server, start the
Runtime Workbench and choose Cache Monitoring. Select Mapping Runtime as
the cache instance, and as the cache object mapping program, enter the search
criteria for the software component version and the mapping program name (we
recommend that you use the input help as the mapping program name has to
have a special syntax).
5. Compare the two Changed On dates, in other words, check whether the cache
was updated after the last time the mapping changed. If this is not the case, the
cache is not the correct version.
186
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
6. Check Cache Notification Status
The starting point is that the cache on the Integration Server is not up-to-date. An
interface determination, operation mapping, or mapping program is missing or not
present in the correct version.
For the upcoming analysis, useful information is available about the user who
submitted the relevant objects and when this was done. You can find some hints by
opening the relevant objects in the Directory/Repository and clicking on the
Info/Properties button. This displays information about the last changes. The object
ID is also of interest.
1. Start the Runtime Workbench.
2. Choose Cache Monitoring  Show Notification Table.
3. Select Repository Cache Notification Table as the type.
4. Look at the entries for the relevant user and date.
If the notification failed (indicated by the icon), there is a problem with the
Repository -> Directory communication.
5. If all seems to be OK in the Repository Cache Notification Table, choose Type
Directory Notification Table.
6. Look at the entries for the relevant cache instance, user, and date.
February 2011
187
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
7. Check the notification status: green is OK, red indicates an error situation. In this
case, the communication between the Directory and the Integration Server does
not work properly.
7. Check Cache Update Status
1. Perform the steps as described in section 6.
2. In this case, check the Cache Update column. Green is OK, red indicates an
error situation. In the case of an error, you have to switch to the Problems tab.
a) No entries
If there are no entries in the list, the communication between the Integration
Server and the Directory may have failed.
Call transaction SXI_CACHE on the Integration Server and look at the status
there.
188
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Double-click the status to display more details.
b) Entries present
February 2011
189
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
The list displays all objects that could not be updated. Search for the interface
determination, operation mapping, or mapping program that caused the
problem on the Integration Server (wrong version/not present) by its object ID
(this can be found in the trace on the Integration Server or by using the
Info/Properties pushbutton in the Repository/Directory). Double-clicking the
entry displays the error message that has to be analyzed (which should also
be present in the logs).
In both cases, the update may have failed due to connection problems
between the Integration Server and the Directory or the Directory and the
Repository.
If there is no information in the Directory or on the Integration Server, you
have to investigate the PI logs.
8. Check Directory  Integration Server and Repository  Directory
communication
Check Directory  Integration Server Communication:
The notification of the cache on the Integration Server may have failed due to
connection problems because the HTTP service is not running on the Integration
Server.
1. Call transaction SICF.
2. Choose default_host  sap  bc  ping (connection test) and choose Test
service in the context menu of the entry.
Log on to the browser that then opens (you may have to close all browsers). If
this does not happen, this could be caused by a problem with the HTTP service
and has to be analyzed. Check the ICM and its trace for more information; see
SAP Note 634006 - ICM messages explanatory note.
190
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
3. For the logon, use the Directory service user (see section Check Service User
Name and Password at the end of this PAS). If the user and password are
correct, an HTML page is returned containing the following message: Server
reached successfully. If you get an authorization error, you have to check the
user and password entered for the test. Check the user name and password for
the Directory service user by retyping the values as described in section Check
Service User Name and Password at the end of this PAS.
4. Repeat the connection test in transaction SICF and check if it works now.
Check Repository  Directory Communication:
For mapping objects edited in the Enterprise Services Repository, the initial
notification is started from the Enterprise Services Repository. Therefore the
Repository -> Directory communication must be checked.
1. Start a Web browser and enter the following URL:
http://<hostname>:<port>/dir/hmidiag/ext?method=info
(The host name and port could, for example, be extracted from the Process
Integration Tools start page.)
2. A logon request should appear. If this is not the case, the Repository (or possibly
the whole AS Java) is not running and has to be started. Perform the steps as
described in section Check HTTP Service and Status of Applications at the end
of this PAS.
If the logon pop-up appears, use the Repository Service user to log on (see
section Check Service User Name and Password at the end of this PAS).
If the user and password are correct, a HTML page is returned containing
information about the HMI service.
If you get an authorization error, you have to check the user and password used
for the test.
February 2011
191
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
3. You check the user name and password for the Repository service user by
retyping the values as described in section Check Service User Name and
Password at the end of this PAS.
9. Check Integration Server  Directory and Directory  Repository
Communication
The update of the cache on the Integration Server may have failed due to connection
problems when trying to reach the Directory and/or the Repository and/or the Java
stack of the Integration Server (mapping runtime). First check whether the
Directory/Repository/mapping runtime is running (as well as the HTTP service).
Start a Web browser and enter the following URL:

Directory:
http://<hostname>:<port>/dir/hmidiag/ext?method=info

Repository:
http://<hostname>:<port>/rep/hmidiag/ext?method=info

Mapping runtime:
http://<hostname>:<port>/run/hmidiag/ext?method=info
(The host name and port could be extracted from the Process Integration Tools
start page, for example).
A logon request should appear. If this is not the case, the
Directory/Repository/mapping runtime (or possibly the whole AS Java) is not running
and has to be started. Perform the steps as described in section Check HTTP
Service and Status of Applications at the end of this PAS.
If the logon pop-up appears:

For the Directory URL, use the Integration Server service user

For the Repository URL, use the Directory Service user

For the mapping runtime URL, use the Directory Service user
to log on (see section Check Service User Name and Password at the end of this
PAS).
If the user and password are correct in all cases, a HTML page is returned
containing information about the HMI service.
192
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
If you get an authorization error, you have to check the user and password used for
the test.
Check the user name and password for the service users by reentering the values as
described in section Check Service User Name and Password at the end of this
PAS.
Repeat the connection test with the URLs.
10. Retry the Cache Update and Resend the Message
1. To start a new cache update you have to open the problematic interface
determination, operation mapping, and/or mapping program in the
Directory/Repository.
2. Switch to edit mode and save the same version, that is, with no changes to the
content (to activate the save pushbutton, just add and remove a blank in the
short description).
3. Activate the object and resend your message after the cache update is complete.
If you think that more than one object is affected by the cache notification/update
problems, try a full cache refresh.
Since this will take a while and no message processing can take place
during this time, only do a full cache refresh if really necessary.
1. Call transaction SXI_CACHE.
2. From the context menu Runtime Cache, choose Start Complete Cache
Refresh.
3. Call transaction SM58 to check the status of the refresh process.
The cache update is finished if there is no longer an entry for function module
SAI_CACHE3_REFRESH_BACKROUND.
February 2011
193
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
11. Analyze PI Logs
1. Start the Log Viewer in SAP NetWeaver Administrator.
2. Select Default trace (Java) and search for Application sap.com/com.sap.xi*.
Additional Information:
Check Service User Name and Password
Various connections are important for the cache refresh. The applications involved
are the Directory, Repository, and Integration Server. For each of them there is a
service user with a special user role:
Applications and User Roles
Application
User Role
Directory
SAP_XI_ID_SERV_USER
Integration Server
SAP_XI_IS_SERV_USER
Repository
SAP_XI_IR_SERV_USER
The following figure gives a short overview of the communication for
notification/update:
194
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
The information about the user and password is read from the exchange profile in
the case of the Directory and Repository. The Integration Server uses the SM59
destination INTEGRATION_DIRECTORY_HMI.
1. First you have to get the name of the user who has the required role.
For the Directory/Repository, you have to call transaction SUIM in the SAP
system that is used for user management (the default should be the client of the
Integration Server).
If you are not sure, you can check it in SAP NetWeaver Administrator. Choose
Configuration Management  Infrastructure  Destinations and look at the
destination UMEBackendConnection.
February 2011
195
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
2. In transaction SUIM, choose User Information System  User  User by
Complex Selection Criteria  By Role.
3. Enter the service user role:
SAP_XI_ID_SERV_USER/SAP_XI_IS_SERV_USER/ SAP_XI_IR_SERV_USER
A list of user names is displayed (the name is probably
PIDIRUSER/PIISUSER/PIREPUSER).
4. Call transaction SU01 to check whether the user is locked. The Logon Data tab
displays information about the lock status:
196
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
5. You can unlock the user on the initial screen by choosing Lock/Unlock. You also
have to check whether the service user has the correct user type: System or
Service (not Dialog).
6. Check whether the profiles for the user have been generated. Choose the
Profiles tab:
7. If the profile for the role is not generated, you have to call transaction PFCG.
Select the corresponding role SAP_XI_ID_SERV_USER/
SAP_XI_IS_SERV_USER/ SAP_XI_IR_SERV_USER and display the definition.
Choose the Authorizations tab and check the status of the profile generation:
February 2011
197
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
8. If generation is incomplete, switch to edit mode and delete it first. To generate
the profile, choose Display Authorization Data on the same tab page. Then
choose the red/white ball icon and start the generation:
9. As a final step after successful generation, choose the User tab page (on the
previous screen) and perform a User comparison.
At this point, the user name for the service users should be clear and the users
should not be locked. In addition, the role profiles should have been generated
successfully. Now you have to check the caller side entries: Exchange Profile
and SM59 destination.
Exchange Profile:
1. Go to the start page of the Process Integration Tools and click the Administration
link in the navigation area.
2. You have to log on with a PI administrator user.
Choose Administration of Properties  Exchange Profile.
198
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
3. Navigate to IntegrationBuilder  IntegrationBuilder.Directory 
com.sap.aii.directory.serviceuser.name and .pwd or IntegrationBuilder 
IntegrationBuilder.Repository  com.sap.aii.repository.serviceuser.name and
.pwd
4. Check the name of the service user and retype the password that is stored in
SAP user management (if you are not sure about the password, also enter it in
transaction SU01). Then, choose Save. Make sure you set the password as
described in SAP Note 999962 - PI 7.10: Change passwords of PI service users.
5. Return to the administration page and choose Administration of Properties  AII
Properties and choose the Refresh button in the content area (this reads the
properties from the exchange profile).
SM59 Destination:
1. Call transaction SM59.
February 2011
199
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
2. Choose RFC Destinations  HTTP connections to ABAP system 
INTEGRATION_DIRECTORY_HMI.
3. Choose Change.
4. On the Technical Settings tab page you can check the target host and port (they
have to correspond to the ones for the Directory; check this, for example, on the
start page URL of the Process Integration Tools).
5. Switch to the Logon/Security tab page. Here you can see the name of the user
and the password. Check the name of the Integration Server service user and
retype the password that is stored in SAP user management (if you are not sure
about the password, also enter it in transaction SU01). Make sure you always set
the password as described in SAP Note 999962 - PI 7.10: Change passwords of
PI service users.
6. Then, choose Test Connection.
A HTTP return code 500 (Internal Server Error) is OK.
Configuring the Trace Level for Transaction SXMB_MONI
...
1. Call transaction SXMB_ADMIN.
2. Choose Configuration  Integration Engine Configuration.
3. Choose RUNTIME for the category and then choose Change Configuration.
4. Set parameter LOGGING to value 1 and parameter TRACE_LEVEL to value 3.
200
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Check HTTP Service and Status of Applications
To check if the HTTP service of the Java Engine and the applications are running,
perform the following steps:
1. Got to SAP NetWeaver Administrator http://<hostname>:<port>/nwa 
Operations  Systems  Start & Stop  Java Services and check whether the
service HTTP Provider is running. If not, start it by using the Start button.
2. Choose Java Applications and check the status of com.sap.xi.directory,
com.sap.xi.repository, and com.sap.xi.services. If the application is not running,
highlight it and start it by using the Start button.
February 2011
201
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Error Analysis of Caching Problems for PI Mappings
Problem
You are having problems with PI mappings because the mapping cache is not
refreshed. As different caches are involved in the execution of PI mappings, there
are several possible error situations.
Background Information
The following steps take place during runtime when executing a PI mapping:
Java Cache
Programs from
Message Mappings
and Mapping Archives
3
Mapping
Runtime Service
Java Stack
JCO
ABAP Cache
Interface
Determination
Service
1
Interface Determinations
Interface Mappings
Sender
Interface
Mapping
Runtime Service
2
ABAP Stack
Receiver
Interface
1. The interface determination looks up the receiver interface in the ABAP
cache. It also determines:

The ID of the operation mapping

The software component version of the operation mapping
2. The ABAP mapping runtime looks up the mapping steps of this operation
mapping in the ABAP cache:
mapping type (XSLT / Java / ...)
program name
3. The Java mapping runtime loads the program from the Java cache and
executes it.
202
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Analysis
The following errors can occur:
1. RESOURCE NOT FOUND: This error occurs if the mapping program is
missing in the Java cache.
2. NO MAPPING PROGRAM FOUND: This error occurs if the operation
mapping is missing in the ABAP cache.
You can find the error code in the error tag of the XI message in transaction
SXMB_MONI.
3. No mapping configured: This message (no error) is found in the trace tag of
the message in transaction SXMB_MONI if there is no interface determination
in the cache for a message; the message is processed without changing the
interface name and without mapping. The problem may be that there is no
interface determination configured or that the interface determination is
missing in the cache. Compare the entries in the Integration Directory and in
transaction SXI_CACHE.
Solution
If there are several objects missing in the cache or if there is an error in transaction
SXI_CACHE, you should execute a delta or full cache refresh. You do this using the
menu XI Runtime Cache  Start Delta Cache Refresh or Start Complete Cache
Refresh in transaction SXI_CACHE. You should always try the delta cache refresh
first as the complete cache refresh requires more time and resources.
If there is only a problem with some objects, it is possible to refresh only these
objects in the cache. To do so, call the Integration Builder Directory and/or
Repository, make a dummy change in the mapping object, and save and activate.
Then, check the Cache Notification Table (menu entry Environment  Cache
Notifications) and the object in transaction SXI_CACHE or in the cache monitoring in
the Runtime Workbench.
Error Analysis of Encoding Problems within PI Mappings
Problem
In some messages, special characters in the payload are not correct (for example
“España” instead of “España”) or a ParserException is thrown during the mapping.
Background Information About Encoding
The typical reason for encoding issues is that the encoding declaration
<?xml version=„1.0“ encoding=„utf-8“ ?>
does not match the byte representation of the rest of the document:
Correct Messages:
February 2011
203
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Byte Representation:
T e
l
e
f ó
n
i
c
a
d e
E s
p a ñ
a
54 65 6C 65 66 C3 B3 6E 69 63 61 20 64 65 20 45 73 70 61 C3 B1 61
Byte Representation for this iso-8859-1 message:
T e
l
e
f
ó n
i c a
d
e
E s p a ñ a
54 65 6C 65 66 F3 6E 69 63 61 20 64 65 20 45 73 70 61 F1 61
If the declaration is wrong, the following will happen:
Setting iso-8859-1 for a UTF-8 Message
<?xml version=“1.0” encoding=“iso-8859-1” ?>
T e
l
e f
ó
n i
c a
d e
E s p a ñ
a
54 65 6C 65 66 C3 B3 6E 69 63 61 20 64 65 20 45 73 70 61 C3 B1 61
T
e l
e f
à ³
n
i
c a
d e
E s p a à ±
a
Setting iso-8859-1 for a UTF-8 message leads to an incorrect interpretation of the
message. The iso-8859-1 encoding is used to interpret the bytes, so the C3 B3 for ó
in UTF-8 will be interpreted as à ³ as this is the representation in iso-8859-1:
204
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Setting utf-8 for an iso-8859-1 Message
If you set UTF-8 for an iso-8859-1 message you may get an invalid message:
<?xml version=“1.0” encoding=“utf-8” ?>
T
e
l e
f
ó
n
i c a
d e
E s p a ñ
54 65 6C 65 66 F3 6E 69 63 61 20 64 65 20 45 73 70 61 F1
a
61
F1 and F3 are not allowed in a UTF-8 document. If they occur, a ParserException
results:
Solution
In many cases the payload is already incorrect before the message comes into the
mapping. So, before starting an in-depth analysis of the mapping itself, check the
message payload before the mapping step in transaction SXMB_MONI. If the payload
is already incorrect there, the problem comes from the source system or adapter.
Check the encoding declaration and the source message there.
There are also cases where the encoding error happens in a Java mapping. Such
cases usually involve a self-developed Java mapping.
Typically, conversions between characters and bytes are performed in the selfwritten mapping. Often, the encoding is not specified:
byte[] b  String s: s = new String(b,"utf-8");
String s  byte[] b: b = s.getBytes("utf-8");
If no encoding is specified, the default encoding is taken and this might not be the
correct encoding.
Examples of byte conversions in the mapping:
byte[ ] resultBytes = resultString.getBytes( );
better:
byte[ ] resultBytes = resultString.getBytes("utf-8");
InputStreamReader r = new InputStreamReader(inputStream);
February 2011
205
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
better:
InputStreamReader r = new InputStreamReader(inputStream,"utf-8");
Similar: new String(bytes,"utf-8");
Error Analysis of Problems with Split and Merge Mappings
Problem
You have configured a split or merge mapping in the BPE or a split mapping in the
interface determination and want to know more about analyzing problems within this
mapping.
Analysis
There are two places for configuring this kind of mapping: the interface determination
and the BPE.
Interface Determination:
With PI it is possible to use a mapping within the interface determination to
determine the receivers:
During interface determination at runtime, the receiver interface is set to the
“InterfaceCollection” constant and the mapping is determined. After mapping, the
message is split into several result messages. These result messages are bundled
into a bulk message. Therefore, all of these messages must be sent to the same
Adapter Engine, and there are restrictions regarding the adapter type. For more
information, see SAP Library section Defining Message Splits and Mapping-Based
Message Packaging.
The bulk message has its own message header and the interface name
InterfaceCollection.
If there is only one result message, an ordinary message is created, not a bulk
message with one child message.
206
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
To monitor mapping problems during this step you have to use transaction
SXMB_MONI. Here you can check the error and the trace tag of the message.
Note that the child messages of a bulk message are not visible in transaction
SXMB_MONI as independent messages. Only the bulk message is visible. It is,
however, possible to jump to the monitor for bulk messages by using the entry in the
Bulk Message column in transaction SXMB_MONI. Also, you can use report
SXMS_MMF_MONITOR to display the bulk message and the corresponding
individual messages. You can either display all bulk messages for a particular time
period, or enter a specific message ID and display the corresponding parent and
child messages. You can navigate from the list of displayed messages to the monitor
for processed messages
BPE:
In the BPE, you can use split and merge mappings. To check the trace for the
mapping in the BPE, use the following procedure:
In transaction SXMB_MONI, select the message with the problem and follow the link
to PE (process engine).
This will open the workflow log. Choose „List with Technical Details‟ to get the
workflow log with technical details:
February 2011
207
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Choose the icon for „Show Container‟ in the mapping step to get detailed information
about the mapping:
208
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Double-clicking the TRACE entry opens the mapping trace:
February 2011
209
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Internal processing of split and merge mappings:
Internally, a multi XML message will be generated before the mapping is executed.
The mapping is executed for the multi XML message and after the mapping the multi
XML message is split into result messages with normal XML format.
IS Pipeline / BPE
XI message with normal payload
Mapping Runtime
Split
Multi XML
Create
Multi XML
Multi XML
multi
multi
Mapping
Application Mapping
The messages will look like this internally:
Split
Multi XML
Create
Multi XML
Mapping
These internally converted messages cannot be checked within PI monitoring; they
are also not saved in a trace for security reasons.
210
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
There are two important error situations that can occur:
1. Payload of an XML message is already in multi XML format before the mapping
step:
IS Pipeline / BPE
multi
Mapping Runtime
XI message with normal payload
expected, but the source XML is
already in multi XML format.
Split
Multi XML
Create
Multi XML
multi
multi
Mapping
Application Mapping
In this case the mapping will trigger an error or will create an incorrect result XML
(this depends on how tolerant the mapping program is). A message mapping will
most probably throw a cannot-produce-element error message.
Check the message before the mapping step in transaction SXMB_MONI to find out
if the message format is correct.
2. Mapping produces ordinary XML format
BPE
Mapping Runtime
Split
Multi XML
Create
Multi XML
multi
Mapping
Multi XML expected, but the mapping produced
ordinary XML. Afterwards, the split failed.
Application Mapping
In this case the split after the mapping will fail because it expects multi XML. The
mapping service throws an exception, because the split of the multi XML fails.
Check the mapping implementation.
February 2011
211
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Problems and Solutions
11.1.1.1 CANNOT_PRODUCE_ELEMENT in PI mapping
Problem
You get the error CANNOT_PRODUCE_ELEMENT in the mapping step in the
runtime or during the test of a mapping in the Enterprise Services Repository.
Analysis
Check SAP Note 799657 - Error message CANNOT_PRODUCE_ELEMENT in
message mapping for possible root causes and how to analyze the error.
Mapping as a service
The mapping as a service (MaaS) feature involves NetWeaver Business Process
Management (BPM), Enterprise Services Repository (ES Repository), and Process
Integration (PI) runtime for its entirety.
For troubleshooting information about the mapping as a service feature, see
http://wiki.sdn.sap.com/wiki/x/vwGADw.
212
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
12 Monitoring
Central PI monitoring with SAP Solution Manager
Starting with NetWeaver 7.3 (also down ported to 7.11 SP6), SAP offers central
monitoring of all PI components in a PI domain using SAP Solution Manager.
For troubleshooting information, see http://wiki.sdn.sap.com/wiki/x/fgZeDw.
Monitoring for Process Integration and Orchestration
installation
The Process Integration and Orchestration Package combines the integration
capabilities of SAP NetWeaver Process Integration Advanced Adapter Engine
Extended (AEX) with the process modelling, operation, and monitoring capabilities of
SAP NetWeaver Business Process Management (BPM). For more information about
how to use it, see Process Integration and Orchestration Package.
For troubleshooting information about monitoring tasks specific for Process
Integration and Orchestration installation, see http://wiki.sdn.sap.com/wiki/x/rAF8Dw.
PI Monitors in SAP NetWeaver Administrator
With SAP NetWeaver 7.3, SAP delivers a new set of PI monitoring tools as part of
SAP NetWeaver Administrator. These monitoring tools can be used to monitor all
local PI Java components. For more information about how to use them, see
Monitoring the Advanced Adapter Engine.
12.1.1
PI Communication Channel Monitor
Problem
When launching the monitor, no data is displayed and the following message is
displayed instead.
“Communication channel Data Provider not registered for the currently selected
Adapter Engine”.
Solution
Start the application „com.sap.xi.itsam.mdt‟.
February 2011
213
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Follow the steps below to check whether „com.sap.xi.itsam.mdt‟ is started
Steps
1. Navigate to the Operations tab in NWA and then navigate to the sub tab
Systems under the Operations tab.
2. Choose Start&Stop and navigate to the Java Applications tab.
3. Select the application „com.sap.xi.itsam.mdt‟ from the table and start it.
Solution
Start the application „tc~lm~itsam~co~ui~xi~channel~wd‟.
12.1.2
PI Message Prioritization
Problem
When launching the monitor, no data is displayed and the following message is
displayed instead: “Could not retrieve the data, please check the trace for details“.
The trace contains the following „Exception while getting
messagePrioritizationManager reference in Reload Rule -> Object not found in the
lookup of AAM_MessagePrioritizationMangaer‟
Solution
Restart the XPI:AF Service.
Steps
1. Navigate to Operations tab in NWA and then to the sub tab Systems under
the Operations tab.
214
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
2. Choose Start&Stop’ and navigate to the Java Services tab.
3. Select the service „XPI:AF Core‟ from the table and restart it.
Problem
When launching the monitor, no data is displayed and the following message is
displayed instead „Communication failure occurred while connecting to the current PI
component. Check the trace available in SAP NetWeaver Administrator for additional
information.‟
Solution
Start the application „com.sap.xi.itsam.mdt‟.
Start the application „tc~xi~itsam~co~ui~priority~wd‟.
12.1.3
PI Java Proxy Runtime Monitoring
Problem
When launching the monitor, no data is displayed and the following message is
displayed instead „Communication failure occurred while connecting to the current PI
component. Please check the trace available in NetWeaver Administrator for
additional information.‟
Solution:
Start the application „com.sap.xi.itsam.mdt‟.
Start the application „tc~xi~itsam~co~ui~jpr~wd‟.
Problem
The monitor gets launched without any error message but no data is displayed.
Solution
Start the service „XPI Service: Java Proxy Runtime‟.
12.1.4
PI Adapter Engine Status
Problem
When launching the monitor, no data is displayed and the following message is
displayed instead „Communication failure occurred while connecting to the current PI
component. Check the trace available in SAP NetWeaver Administrator for additional
information.‟
Solution
Start the application „com.sap.xi.itsam.mdt‟.
Start the application „tc~xi~itsam~co~ui~engstats~wd‟. .
February 2011
215
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
12.1.5
PI Performance Monitor
Problem
When launching the monitor, no data is displayed and the following message is
displayed instead “Performance data provider not registered for the selected PI
component‟‟
Solution
Start the application „com.sap.xi.itsam.mdt‟.
Problem:
When launching the monitor, no data is displayed and the following message is
displayed “Property profile.performance.runtime of the service com.sap.aii.af.svc is
not active; activate it in ConfigTool‟‟
Solution
Set the profile performance property value to true by following the below steps:
1. Open configtool and under Cluster-Data - Instance –XXX  Services,
select Com.sap.aii.af.svc.
2. Set the value of the parameter „profile.performance.runtime‟ to true on the
Right hand pane of the configtool.
3. Restart the SAP J2EE Engine for the changes to get activated.
12.1.6
PI Cache Monitor
Problem
When launching the monitor, no data is displayed and the following message is
displayed „Communication failure occurred while connecting to the current PI
component. Check the trace available in SAP NetWeaver Administrator for additional
information.‟
Solution
Start the application „com.sap.xi.itsam.mdt‟.
Start the application „tc~lm~itsam~co~ui~xi~cache~wd‟.
12.1.7
PI IDoc Adapter Monitor
Problem
216
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
When launching the monitor, no data is displayed and the following message is
displayed „Communication failure occurred while connecting to the current PI
component. Please check the trace available in NetWeaver Administrator for
additional information.‟
Solution
Start the application „com.sap.xi.itsam.mdt‟.
Start the application „tc~lm~itsam~co~ui~xi~idoc~wd‟.
Start the applications „com.sap.aii.adapter.idoc.ra‟ and
„com.sap.aii.adapter.idoc.app‟.
12.1.8
PI Message Monitor
Problem
When the application is launched, the user gets an error message „Could not
connect to message processing system- java.lang.IllegalStateException: application
[sap.com/com.sap.xi.itsam.mdt], CSN component [BC-XI-IS-WKB] should not use an
unregistered loader for operation [loadClass of
com.sap.aii.mdt.itsam.mbeans.compositedata.SAP_ITSAMXIMsgOvFilter] „.
Solution
Ensure that the application „com.sap.xi.itsam.mdt‟ is started:
1. Navigate to Operations tab in the NWA and then to the sub tab Systems
under the Operations tab.
2. Choose Start&Stop and navigate to the Java Applications tab.
3. Select the application „com.sap.xi.itsam.mdt‟ from the table and start it.
Solution
Ensure the application „tc~lm~itsam~co~ui~xi~msg~wd‟ is started.
1. Navigate to Operations tab in the NWA and then to the sub tab Systems
under the Operations tab.
2. Choose Start&Stop and navigate to the Java Applications tab.
3. Select the application „tc~lm~itsam~co~ui~xi~msg~wd‟ from the table and
start it.
Problem
You choose the Database tab in PI Message Monitor and get an error message „You
do not have permissions to view the message content‟.
February 2011
217
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Solution
You need modify permissions. Check the following document and ask the
administrator to provide you an appropriate role: Monitoring Roles
12.1.9
PI Background Processes Monitor
Problem
When the application is launched, the user gets an error message „Could not
execute current processing step; check trace files for additional information and
contact support for further assistance‟.
Solution
Ensure that the application „com.sap.xi.itsam.mdt‟ is started.
1. Navigate to Operations tab in the NWA and then to the sub tab Systems
under the Operations tab.
2. Choose Start&Stop and navigate to the Java Applications tab.
3. Select the application „com.sap.xi.itsam.mdt‟ from the table and start it.
Solution
Ensure the application „tc~lm~itsam~co~ui~xi~msgarch~wd‟ is started.
1. Navigate to Operations tab in the NWA and then to the sub tab Systems
under the Operations tab.
2. Choose Start&Stop and navigate to the Java Applications tab.
3. Select the application „tc~lm~itsam~co~ui~xi~msgarch~wd‟ from the table
and start it.
Problem
When the application is launched, the user gets an error message „You have readonly permission for this application‟. Check the document and ask the administrator
to provide you an appropriate role: Monitoring Roles
12.1.10 PI Sequence Monitor
Problem
When the application is launched, the user gets an error message „Sequence
Overview: No sequence data retrieved based on selection criteria‟.
Solution
218
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Ensure that the application „com.sap.xi.itsam.mdt‟ is started.
1. Navigate to Operations tab in the NWA and then to the sub tab Systems
under the Operations tab.
2. Choose Start&Stop and navigate to the Java Applications tab.
3. Select the application „com.sap.xi.itsam.mdt‟ from the table and start it.
Solution
Ensure the application „tc~esi~esp~wsrm~itsam~jmx‟ is started.
1. Navigate to Operations tab in the NWA and then to the sub tab Systems
under the Operations tab.
2. Choose Start&Stop and navigate to the Java Applications tab.
3. Select the application „tc~esi~esp~wsrm~itsam~jmx‟ from the table and start
it.
Problem
When the user press the button Start Selection in PI Sequence Monitor and gets an
error message „You have read-only permission for this application‟. Check the
following document and ask the administrator to provide you an appropriate role:
Monitoring Roles
If you have problems, open a CSN message (component BC-NWA-XPI).
12.1.11 Problems and Solutions
12.1.11.1 Exception: AMX_REGISTRY_EXC
Problem
In the connectivity test you see the exception:
<:exceptionID>AMX_REGISTRY_EXC</n0:exceptionID>
<n0:errorText>The object name does not exist in the directory.></n0:errorText>
<n0:errorDescription>Program: CL_SAMX_REGISTRY_EASY=========CP
Include:
CL_SAMX_REGISTRY_EASY=========CM001
Line: 15></n0:errorDescription>
<n0:exceptionClass>CX_SAMX_REGISTRY_EXCEPTION></n0:exceptionClass>
Analysis
Check that the installation numbers are identical in the SLD and the system itself:
http://server:port/sld --> Technical Systems --> Select your system with the type AS
ABAP and check the installation number on the General tab:
February 2011
219
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
In the ABAP system, check the installation number in the menu System  Status:
If they do not match, check and execute the SLD registration in transaction RZ70.
12.1.11.2 Wrong HTTP Port Used in LEPURL
Problem
The LEP (Logical Endpoint) URL used to connect to the ABAP components is
generated with the wrong HTTP port.
220
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Analysis
Check the HTTP port in the URLs to the ABAP components in the routing tables:
http://<integration_server_host>:<port>/tc.lm.itsam.cdp.centralagent_war/test/table/le
purl
ABAPSYS_<SID>_<host>_<client>
http://p178744:50000/sap/bc/srt/pm/sap/mbeanaccessinbound/001/default_profile/1/
binding_mbeanaccessinbound_default_profile
The port from the URL should be active in transaction SMICM  Goto  Services.
If the port is not available in SMICM, you can create it. Set the instance parameter
icm/server_port_<x> to activate a new HTTP port:
icm/server_port_<x> = PROT=HTTP, PORT=<port number>, TIMEOUT=600
Check SAP Note 1230730 - Wrong HTTP port calculation for web service URL for
information about incorrect port generation if the instance number is not 00.
Monitoring with Runtime Workbench
SAP offers the Runtime Workbench (RWB) tools for monitoring the Integration
Engine and the Advanced Adapter Engine.
Starting with NetWeaver 7.3, SAP recommends using the new monitoring tools in
SAP NetWeaver Administrator (described in the PI Monitors in SAP NetWeaver
Administrator section above) for monitoring the Advanced Adapter Engine. While
RWB tools can also be used for this purpose, SAP recommends using them only for
monitoring the Integration Engine.
For more information about how to use the RWB tools, see Monitoring the Integration
Engine.
Problem
You would like to know about the features of the Runtime Workbench (RWB). In
addition, you want to know how to troubleshoot problems that occur while working in
the RWB.
Solution
For a general overview and further description of the available features, see the
information about monitoring in Administrative Tasks.
For information about troubleshooting the Runtime Workbench, see SAP Note
768456 - Troubleshooting Runtime Workbench XI 3.0.
For troubleshooting information about end-to-end monitoring, see SAP Note 885405
- Troubleshooting End-to-End Monitoring in XI 3.0.
February 2011
221
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
RWB and CCMS Monitoring Infrastructure (Transaction RZ20)
The SAP Library section CCMS Alert Monitor provides a general description of
monitoring PI using CCMS.
To display alerts from the RWB in the CCMS, see SAP Note 824039 - XI30 Runtime
Workbench: Display of XI alerts in CCMS.
SAP Note 634771 - GRMG Customizing File for XI CCMS Heartbeat Monitoring
describes how to use the GRMG customizing file for XI to display heartbeat
monitoring in the CCMS.
If you want to implement Single Sign-On for the Runtime Workbench, see SAP Note
757373 - Single Sign-On for Runtime Workbench.
12.1.12 Problems and Solutions
12.1.12.1 Adapter Engine Not Visible in SLD, RWB, or Integration
Directory
Problem
You do not see your Adapter Engine in the SLD or in the Runtime Workbench;
furthermore, it is not possible to select it in the Integration Directory channel
configuration.
Analysis
The Adapter Engine registers itself during startup of the Java application
sap.com/com.sap.aii.af.cpa.app. There are various configuration and inconsistency
problems that can lead to a missing registration.
For more information, see the section Analyzing SLD self-registration problems.
Check the following settings in the SAP NetWeaver Administrator:
222

Is the correct SLD set in the Java service SLD data supplier configuration?

Is the connection data correct in the Java destination SLD_DataSupplier?
Use the Ping Destination button to check the connection.

Is the connection data correct in the Java destination SLD_Client? Use the
Ping Destination button to check the connection.

Is the service SLD data supplier running?

Check if the Java applications for PI are running. To do so, open the SAP
NetWeaver Administrator  Systems  Start & Stop and select „Java EE
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Applications‟. Choose Retrieve Status. Check that all applications containing
com.sap.aii*, com.sap.xi*, or com.sap.lcr* are running.
Check the following settings in the ABAP system:

Does the user maintained in transaction SLDAPICUST contain the role
SAP_XI_APPL_SERV_USER?
Check the following settings in the SLD:

Is the SLD data supplier bridge running? You can check this in SLD ->
Administration  Data Suppliers.

Check that the business system assigned to the Integration Server in the SLD
is correct and is configured as an Integration Server, not as an Application
System. To check this, open the SLD  Technical Landscape, select
Technical System Type Process Integration, and check the assignment to the
application system (the system in which the Integration Server is running
should appear in the Application System column for the Integration Server).
Select the link to display the technical details of the system, then follow the
link to the business system (Business System tab). Check that the business
system role displayed on the Integration tab is Integration Server.

Do the entries in the SLD contain inconsistencies? For more information and
the solution, see SAP Note 1117249 - Incomplete Registration of PI
Components in SLD.
If you change anything in the SLD, do not forget to clear the SLD cache in the
Integration Directory to get the new data from the SLD. To do this, use the
Environment ->Clear SLD Data Cache menu in the Integration Directory.
12.1.12.2 No Adapters are Displayed in Adapter Monitoring
Problem
No adapters are displayed in adapter monitoring. The adapter monitor displays no
result.
Solution
Check in http://<server>:<port>/sap/monitoring/ComponentInfo whether a PCK is
deployed on the PI as well. If so, you have to uninstall it, as it is not technically
possible and not supported by SAP to run PI and PCK on one Java engine.
To uninstall the PCK, follow the procedure described in section Uninstalling a PCK.
User-defined message search
By using the user-defined message search it is possible to search for PI messages
that contain specific payload content without using the TREX as a separate tool.
For troubleshooting information, see http://wiki.sdn.sap.com/wiki/x/nQF8Dw.
February 2011
223
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Index-based message search using TREX
In PI it is possible to search for PI messages by using the payload information in the
PI message using TREX.
Problem
You want to know where you can find more information about the prerequisites for
this function and how to configure the index-based message search.
Solution
You require a TREX installation with the most current support package stack on a
separate server. For information about how to configure the communication between
the ABAP and Java components of PI with the TREX server, see SAP Library
section Configuring Components for Index-Based Message Searching.
You have to set up the index configuration for the PI components in the Runtime
Workbench  Index Administration. This is the central configuration tool for the
index-based message search. You can manage the indexing jobs, check logs, and
specify filters. For more information, see SAP Library section Index Administration.
For installation options and instructions, see SAP Library section Configuring
Components for Index-Based Message Searching.
Component-based message alerting
In releases up to SAP NetWeaver 7.3, SAP provided the Alert Framework
mechanism. With enhancement package 1 for SAP NetWeaver 7.3 and newer
releases, SAP provides additionally a new component-based message alerting
mechanism. For more information about how to configure and use this new alerting
mechanism, see Component-Based Message Alerting.
For troubleshooting information about component-based message alerting, see
http://wiki.sdn.sap.com/wiki/x/mgGADw.
Alert configuration using the Alert Framework
Problem
You need information about how to configure alerts and how to solve problems
during alert configuration.
Solution
The alert configuration procedure is described in SAP Library section Alert
Configuration.
For general information, see SAP Library section Alert Monitor.
For background information about alerts and troubleshooting hints, see SAP Note
913858 - XI3.0 Alerting: Troubleshooting, and the guide attached to SAP Note
932085 - XI 'Message-based Alerting' - additional information.
224
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
12.1.13 Problems and Solutions
12.1.13.1 It Is Not Possible to Select the MTEClass Parameter Called
"SXI_RWBAlerts"
Problem
When you create a Rule Node in transaction RZ20, you cannot select the MTEClass
parameter called SXI_RWBAlerts.
Solution
Configure the PI monitoring tree as described in SAP Library section Configuring the
CCMS Alert Monitor, and add a node for the RWB alerts. See SAP Note 824039 XI30 Runtime Workbench: Display of XI alerts in CCMS.
12.1.13.2 How to Copy the Alert Categories and Alert Rules from DEV to
PRD
Problem
You have a very high number of alert rules defined in your development system. You
would like to move these alert rules into your acceptance/production environment
without having to reenter them all manually.
Solution
Prerequisites:
 To copy the alert configuration data, the user needs the authorization
contained in role SAP_XI_ADMINISTRATOR.
 You have already defined the alert categories in the customizing client, since
only here is it possible to generate the transport request (transaction
ALRTCATDEF).
The alert configuration consists of two parts: alert categories and alert rules.
To copy the alert categories, call transaction ALRTCATDEF in your customizing
client and choose the appropriate action from the Transport menu. This creates a
transport request for the selected alert categories.
Copying the alert rules works in a similar way: Run the report
SXMSALERT_CONFIGTRANS, which creates a transport request for the alert rules.
February 2011
225
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
13 SAP Partner Connectivity Kit (PCK)- not
delivered with 7.3 EHP1
Note: Functions of the Partner Connectivity Kit (PCK), such as connecting smaller business
partners to SAP NetWeaver Process Integration or testing developed adapters or modules,
are now available with the Advanced Adapter Engine Extended (AEX).
The PCK is therefore no longer delivered with NetWeaver 7.3 EHP1.
If you anyway want to access troubleshooting information related to PCK you can download
the Troubleshooting Guide for 7.30 – SAP Note 1452440 – PI Troubleshooting Guide 7.3
226
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
14 Network
Timeouts in HTTP Communication
HTTP is a simple and stateless request response protocol. The HTTP protocol itself
does not provide an HTTP session concept to handle consecutive requests coming
from the same client. Therefore in HTTP version 1.1 the “keep alive” option was
introduced. This means to keep clients connected and stand by for further requests.
But what if no further request is sent or a response never comes back? This will
cause more and more TCP/IP connections to accumulate and block resources. To
get rid of these obsolete connections, the following timeouts have been introduced.
1. Processing Timeout:
The processing timeout is the maximum time for the requestor (client) to wait
for the server‟s response. The requestor may be a client browser or the SAP
Web Dispatcher waiting for the ICM to send back the response. It could also
be the ICM waiting for the ABAP or Java server to send back the response.
This timeout is used to get rid of open HTTP requests with extraordinary or
infinite runtime.
2. Keep Alive Timeout:
The HTTP protocol utilizes TCP/IP connections to transfer HTTP request and
response data. To optimize the TCP/IP connection handling in HTTP, an
opened TCP/IP connection will be held open, to immediately transfer further
HTTP requests of the same client. After some idle time (keep alive timeout),
with no further HTTP request, the TCP/IP connection will be closed.
Prematurely closing the TCP/IP connection only affects performance.
Functionality is not affected as a new TCP/IP connection is opened but with
some small time delay.
Problems with HTTP Timeouts
HTTP requests are often routed to the destination server using multiple components
like proxies, firewalls, load balancers, or web servers. Each component applies its
own timeout settings for HTTP or other connections. The default timeout settings
may be sufficient for simple browsing with short response times. But for business
applications like SAP ECC, the response times may vary greatly, depending on the
selection criteria or server load, for example. As a result, the client will get a timeout
error and the server's response will never reach the client. As the user is normally
not aware of the technical landscape it is impossible for him to locate the real cause
of the problem. On the server side it is also more or less impossible to identify the
problem, as the response may be lost somewhere on its way to the client.
SAP NetWeaver PI, acting as the integration middleware for message exchange
between other systems, is affected by HTTP timeouts in the same way.
SAP Components Affected by HTTP Timeouts
The SAP Internet Communication Manager ICM serves HTTP requests in SAP
NetWeaver. It receives HTTP requests and passes them to the processing
February 2011
227
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
application either in the Web AS ABAP or Web AS Java. After the processing has
finished ICM passes the response back to the client.
The SAP Web Dispatcher acts as a load balancer and reverse proxy for HTTP
requests to be sent to SAP NetWeaver. It also holds open HTTP requests and waits
for the response to be sent back to the client.
Configuring SAP ICM and SAP Web Dispatcher
We recommend setting short time intervals for the ”keep alive” timeout. This is to
reduce the total number of TCP/IP connections to be established in parallel. If the
idle time is greater than 30 to 60 seconds it is more efficient to close the connection
and open a new one for the next incoming request. We also recommend setting the
keep alive timeout in such a way that the smallest value is on the client side and
increases on the server side.
Recommendation for the keep alive timeout:
SAP ICM: 30 sec
SAP Web Dispatcher: 40 sec
The above values are recommendations only and may be adjusted as required.
Special care should be taken with other active network components like load
balancers, firewalls, Web switches, application gateways, proxies, or reverse proxies
that are located in the chain between the client and server; these must be adjusted
accordingly.
The processing timeout is governed by the maximum runtime of HTTP requests on
the server side. Depending on the application used, it may be 30 minutes to one hour
or even more. Whether or not a processing time of 30 minutes or more is feasible
depends on the use case and must be decided individually. Application-to-application
scenarios using PI may cause high load on the back end during mass data transfer.
As a consequence the response times will increase, causing processing timeouts if
not configured appropriately. To avoid processing timeouts in high load situations,
you must observe response times and determine the timeout value accordingly.
SAP Profile Parameters
You configure HTTP or HTTPS ports by using the server_port parameter. We
recommend setting the processing timeout and keep alive timeout for each
server_port individually.
Example:
icm/server_port_0 =
PROT=HTTP,PORT=8080,TIMEOUT=30,PROCTIMEOUT=1800
Other parameters affecting timeouts:

228
icm/keep_alive_timeout
This parameter defines the keep alive timeout for all server ports. The default
value is 30 seconds.
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide

icm/conn_timeout
This parameter limits the time for establishing the TCP/IP connection. Once the
connection is established, this parameter has no further effect. The default value
is 5 seconds.
These parameters are the same for SAP ICM and SAP Web Dispatcher.
Web AS ABAP limits the maximum runtime of an ABAP service in SICF. The
respective profile parameter is:
rdisp/plugin_auto_logout (default value 30 minutes)
Network Aspects with PI
PI features a message-based engine that combines heterogeneous systems into
cross-functional, end-to-end business processes. As an Integration Broker, PI holds
a central position in your system network from a communication perspective.
Problem
1.) You encounter problems with your PI system landscape that may be networkrelated. These problems could be:
- Reproducible communication errors
- Sporadic communication problems or errors
- Performance issues that may be caused or influenced by the network
2.) You are running a PI system and need more information regarding networkrelated issues, configuration, and additional background.
Solution
1.) If you think that you have network-related problems, follow the steps described
below. This is to narrow down the possible cause and to isolate the component
causing the problems.
2.) See the Additional Sources of Information section below.
First of all, you must find out the communication path that is encountering the
problems.
In the case of HTTP communication:
 Check the HTTP ports (using transaction SMICM – choose Services).
Also check HTTPS ports for SSL communication, if applicable.
 Distinguish between HTTP ports of ICM and the SAP AS Java Engine.
 Check whether the SAP Web Dispatcher or another „reverse proxy‟ or „Web
switch‟ is involved in HTTP(S) communication.
If yes, this device will use its own HTTP(S) port.
 Check appropriate trace files for errors
o ICM trace: dev_icm
o SAP AS Java Engine trace
o Web Dispatcher trace: dev_webdisp (usually running on a different
host)
February 2011
229
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide

You may activate HTTP logging in ICM or in the SAP AS Java Dispatcher.
Be aware that this will produce very large log files.
In the case of RFC communication:
 Keep in mind that all RFC communication is handled by the SAP Gateway.
 Each SAP Application Server comes with its own SAP Gateway. Therefore,
two gateways are usually involved (in the sender and receiver systems).
 An RFC destination may define an additional SAP Gateway.
 The relevant services and ports of the SAP Gateway are
sapgwxx and 33xx (xx represents the instance number).
 RFC communication may be routed using the SAProuter.
 Check appropriate trace files for errors:
o Gateway trace: dev_rd (on each application server involved)
o SAP router trace: dev_rout (if it is involved)
Important Note when Checking Trace Files:
Traces of communication components usually contain certain errors. These errors
may be caused by downtimes of other application systems or by incorrect
configurations.
The most difficult task is to identify warnings or errors that are related to your
communication and that are causing problems. This may be achieved in the following
way:
 Carefully check time stamps
(be aware that network timeouts may last for several minutes).
 Check for identifiers of your communication, which may be:
o RFC destination names
o Host names or IP addresses of involved hosts
o User names
Known Problems
Typical problems encountered in PI environments are:
 Connections to PI might fail if you are using different network domains
between client and server applications. For more information, see SAP Note
864268 - XI Login problems when working in multiple network domains.
 The Java stack components of PI are using an SAP proprietary protocol
called P4. Necessary ports for P4 communications are not open in customer
firewalls. For the list of ports used by SAP applications, see the
documentation TCP/IP Ports used by SAP Software mentioned below.
Further Information
When working in a complex and integrated system landscape, you might want to
control the access from the „outside‟ world to your Intranet. The SAP Web Dispatcher
is designed as a general access point for this purpose. For more detailed
information, see SAP Web Dispatcher. See also SAP Note 538405 - Composite SAP
Note on the SAP Web Dispatcher. For troubleshooting the SAP Web Dispatcher, see
SAP Note 634262 - Note on the preclarification of SAP Web dispatcher messages.
230
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Besides using the SAP Web Dispatcher for load balancing, you can also use the
HTTP port of the message server instead of the direct ABAP or Java port in the
configuration. For more information, see SAP Note 751873 - Problem analysis during
the HTTP load distribution.
Using SSL and HTTPS for Communication:
When configuring HTTPS for your message exchange, you must handle the ABAP
and Java parts differently. For more information, see HTTP and SSL.
Additional Sources of Information
You will find further information about the TCP/IP ports used by SAP NetWeaver and
other SAP software in the document TCP/IP Ports used by SAP Software.
For information about security, see SAP Service Marketplace at
service.sap.com/security.
Important SAP Notes:
21151 - Multiple Network Adapters in SAP Servers
962955 – Use of Virtual TCP/IP Host Names
611361 - Host Names of SAP servers: Selection of host names of SAP servers
30289 - SAProuter Documentation: Documentation about SAProuter
538405 - Composite SAP Note on the SAP Web Dispatcher: Information about the
SAP Web Dispatcher
634262 - Note on the Preclarification of SAP Web Dispatcher Messages: Information
about troubleshooting the SAP Web Dispatcher
634006 - ICM messages explanatory note: Information about troubleshooting the
ICM
824554 – ICM and SAP Web Dispatcher Timeout Parameter
737625 – Parameter Recommendations for the ICM
500235 - Network Diagnosis with NIPING: Network diagnosis with SAP tool niping
Basic architecture aspects:
 General architecture, see the Technical Infrastructure Guide on SAP Service
Marketplace.
 System Landscape Directory (SLD), see SAP Service Marketplace at
service.sap.com/installnwpi71 , Planning Guide - System Landscape
Directory.
February 2011
231
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
15 Transport
Software Logistics in PI
Problem
You are looking for strategies for setting up the software logistics for your PI
environment. You do not know how to transport objects in PI.
Solution
The transport of Enterprise Services Repository objects should be done in a threesystem landscape, from development to quality assurance, followed by testing in
quality assurance. After successful testing, the same transport request should be
used for transportation to the productive system.
The transport of Integration Directory objects requires a transport from development
to quality assurance, followed by a new export from quality assurance, and the
transport of this newly generated export to the productive system.
For known restrictions about cross-release transports, see SAP Note 834507 Cross-Release Transports.
For troubleshooting the Enterprise Services Repository and Integration Directory,
see the Problem Analysis for the Integration Builder - Directory & Repository section.
PI objects can be transported using file transfer, CMS (Change Management
Service), or CTS (Change and Transport System).
CTS can be used in SAP NetWeaver PI 7.1 with SP6 and higher. For more
information about transport using CTS, see the documentation section Transporting
Objects of Usage Type Process Integration Using CTS and the how-to guide How To
Configure Enhanced CTS for SAP NetWeaver Process Integration 7.1 SP06.
CTS can be used to transport ABAP and Java objects together, so provides one
central transport environment for your PI landscapes, where you can manage all PIrelevant transport objects from a single entry point.
For information about software logistics of PI objects, see SAP Library section
Transporting ESR Content and Objects of Integration Directory.
Problems with Setting Up CMS
General
232
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
The Change Management Service (CMS) is a tool which can be used in PI as an
alternative to the file system transport for Enterprise Services Repository and
Integration Directory objects. Both Directory and Repository objects can be exported,
approved, and imported in a two or three system landscape from one single
interface, without accessing the file system level.
Problem
During the design, installation, and configuration of CMS with PI, there might be
some issues which need PI- or CMS-specific knowledge.
Analysis
During setup, the CMS reports errors, or the initial tests of PI transports are not
working correctly.
Errors should be displayed either during the export (or in the message windows) in
the Integration Builder or on the CMS interface. If there is no or only generic
information available, have a look in the following places:
 Memory log (Directory or Repository) of a sender PI system
 You find the memory log at the following location(s) under View Memory
Log:
ESR: http://<server>:<port>/rep/support/private/index.html
Integration Directory: http://<server>:<port>/dir/support/private/index.html




Memory log (Directory or Repository) of a receiver PI system (see above)
Engine log of the CMS system
 Open the NetWeaver Administrator and go to Problem Management
 Logs and Traces  Log Viewer and open defaultTrace.trc
Engine logs of sender and receiver PI systems. Open the defaultTrace.trc as
described above.
Engine log of the SLD system (if a separate SLD is used)
If you are opening an OSS message, use the BC-XI component for errors in the logs
of PI systems and the BC-CTS-CMS component for errors in the logs in the CMS
system.
You can find some solutions for errors in the following SAP Note: 780297 Troubleshooting using CMS for PI
Solution
February 2011
233
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Use the How To Transport XI Content Using CMS guide (not available yet for NW
7.3, but the guide for XI 3.0 can still be used) to get started with CMS and to get
more information about the installation, configuration, and use of CMS.
These guides can be found in the SAP Developer Network:
http://www.sdn.sap.com/irj/sdn/howtoguides
For installation options and instructions, see SAP Library section Configuring the
Change Management Service.
Some issues and error messages are explained in SAP Note 780297 Troubleshooting Using CMS for PI.
Notes for CTS issues:
Some issues related to AS ABAP during CTS imports are explained in SAP Note
1139406 – CTS+ Import Issues.
Assertion Error that occurs during CTS+ export is explained in SAP Note 1351604 –
CTS+ export Assertion Error.
Problem:
CMS import of change lists may fail with the error message "caused by
....com.sap.aii.ib.server.propagation.XIPropagationException: [200]: Duplicate key
(input position 6)" when stack trace from CMS is provided or when the issue reported
with "Duplicate key error during import“?
Solution:
If system copy process as part of the ES Repository setup is not done properly, there
are some duplicated entries between the source system and the system where the
copy was done.
Hence, transports between these systems might fail with the error as mentioned
above.
For more information, see SAP Note 1244596 – Duplicate Key Exception.
Problem:
CMS export fails and is notified via system message with the exception
"com.sap.cms.util.exception.conf.CMSFinderException:Workspace name does not
exist:..." ?
Solution:
If software component versions are registered as part of multiple tracks in the CMS,
the track definitions are not updated properly in the XI system and the old track
234
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
definition remains. Therefore, when the export from ES Repository is performed for
these software component versions, an exception is thrown as above. To resolve this
issue, check together with the landscape administrator if the software component
versions are registered as part of multiple tracks and ask him or her to setup a single
track for one software component version.
Problem:
CMS export of change lists fails and a system message is sent with the exception
"com.sap.cms.pcs.request.changerequest.Bundling already done of some of the
activities: Standard Change List -perhaps the activities are already released ......., tcs
returncode was 12".
Solution:
Collect all the default trace on the server and also the application logs and raise a
message in BC-XI-IBF component with the log files attached.
Problem:
Performing a CTS+ export from XI results in an error with message "Parameter
Ticket value has the invalid value null".
Solution:
When the source PI/ES Repository system for CTS+ exports is configured to connect
to the CTS+ domain controller system via an RFC connection and if the user that is
authenticated to contact CTS+ is defined as Configured User, then SSO can be
enabled. SSO helps to use the ticket issued by server to communicate with CTS. If
SSO is configured and if the ticket is not issued by the server properly then the
above exception is thrown and the export fails.
Problem:
Ticket-based authentication for the CTS+ does not work or the CTS+ export fails with
an exception like the following: “JCO.Client.connect failed with
com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing' or
'Destination details cannot be retrieved'.
Solution:
For more information, see SAP Note 1003674 – CTS+ Configuration issues.
Problem:
Importing a transport request via CTS fails with error
class com.sap.aii.util.misc.api.BaseRuntimeException: Parsing generic data
instance: begin of unexpected element 'script'!.
Solution:
February 2011
235
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
The service user which has been configured in the target system of the import has
not reset its password from the initial password. The user needs to rest the password
once the initial password is provided.
236
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
16 Archiving
Troubleshooting Archiving
General
SAP has implemented specific data management functions to stop the PI database
from growing too fast. These functions can be used in the following components:
 Adapter Framework
 Integration Server
 Business Process Engine
 Connected Proxy systems
Data management requires different procedures in each of the components.
Problem
You are not sure if the customer is archiving or following the correct procedure. We
shall address the basic steps for setting up deletion and archiving and where to
check the procedures.
Analysis
For general troubleshooting of archiving and deletion, see SAP Note 872388 Troubleshooting Archiving and Deletion in XI 3.0.
In general, only messages with a final status can be deleted or archived. Messages
that are in error status will not be deleted until they are manually cancelled.
Adapter Framework
The Adapter Framework automatically deletes correctly processed XML messages.
Asynchronous messages are persisted in the database and are automatically
deleted after their storage time has expired.
For monitoring purposes, synchronous messages are persisted in the message store
(MS) for a specified time. Since these messages are held in the memory, you should
not set this value too high because a high volume of synchronous messages can
result in OutOfMemoryError errors. For details, see SAP Note 787221 OutOfMemoryError in the Adapter Framework.
The default periods for this are:
 Correctly processed synchronous messages are deleted after 5 minutes by
default.
 Correctly processed asynchronous messages are deleted after 30 days by
default.
February 2011
237
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
These time values are defined in milliseconds [ms], where 300000 [ms] equals 5
[min], and 2592000000 [ms] equals 30 days. The relevant SAP Note is 791379 - XI
Adapter Service Properties Documentation.
How to set the storage period:
For processed asynchronous messages, specify this period (in ms) in SAP
NetWeaver Administrator  Configuration Management  Infrastructure  Java
System Properties  Services  XPI Adapter: XI
Properties: xiadapter.inbound.persistDuration.default and
xiadapter.outbound.persistDuration.default.
For synchronous messages, specify this period (in minutes) in SAP NetWeaver
Administrator  Configuration Management  Infrastructure  Java System
Properties  Services  XPI Service: Messaging System
messaging.syncMessageRemover.checkInterval.
The asynchronous message cleanup is controlled explicitly by a delete job
configuration in parallel to the archiving job configuration. A default delete job is
automatically created, which runs at midnight. You can view and edit the jobs in the
RWB; choose Component Monitoring -> Select Adapter Engine -> Background
Processing.
The archiving procedures for the Adapter Framework are configured in the Runtime
Workbench:
 Open the Runtime Workbench, select Component Monitoring, and choose an
Adapter Engine.
 In the lower window, choose Background Processing and Security Archiving.
There are two kinds of messages that you can archive in the Adapter Framework:
normal and signed messages.
Signed messages contain additional information (the signatures from the parties);
otherwise signed and unsigned messages are the same. Signed messages may
need to be archived for legal reasons. Both types of messages are stored locally on
a database for the Adapter Framework and therefore need a separate archiving
process. Signed and unsigned messages are also archived in different ways.
If you would like to archive messages, you need to specify them; all other messages
are automatically deleted.
To check if archiving is performed:
 Go to the Runtime Workbench and select Component Monitoring.
 Choose All and click the Adapter Engine.
238
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
At this point you can either choose Security Archiving or Background Processing.
Both will then display an interface to implement and monitor your archiving process.
In both cases you need to choose the timeframe and the interval of the archiving
(Java) process. It is also possible to check the status of archiving. Note that prior to
archiving, the DAS (Data Archiving Service) has to be set up, in which, for example,
the location of the archived messages has to be defined (see the documentation in
SAP Library).
If you want to look at the archive, go to Message Monitoring in the Runtime
Workbench.
In the two dropdown lists, choose the specific Adapter Engine you want to view
archives from. Choose Archives if you want to see messages that are in the archive.
Make sure that you also enter selection values; otherwise no archived messages will
be displayed.
You can now display archived messages.
Integration Server
The Integration Server has a different procedure; you either define an archiving
procedure or an archiving and deletion procedure.
Note: The archiving procedure must be scheduled since manually canceled or
manually edited messages will only be deleted after archiving. The normal
deletion procedure will not touch these messages.
You have to specify for how long XML messages are to be retained in the database
before they are deleted or archived, and how long historical entries for deleted XML
messages are retained in the database.
The thresholds for the archiving and delete times are defined in transaction
SXMB_ADM:

Choose Configuration  Define Interfaces for Archiving and Retention
Periods.
 Choose Retention Period.
The database size and the need to keep it manageable are important because a
high-volume PI system will have much shorter retention times. Another aspect to be
considered when setting retention times is that you might have specific reasons to
retain information.
The history of a XML message is a separate object and needs an additional
procedure for archiving /deletion.
Note that you have to configure archiving and deletion prior to processing of
messages. During message processing a flag will be set in the persistence layer
February 2011
239
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
indicating if a message will be deleted or archived. Changing this flag at a later
point in time is not possible! Therefore, archiving and deletion has to be
configured prior to interfaces going live.
If a message faces an error during processing and was manually cancelled or
manually edited, it cannot be deleted directly but has to be archived. The delete job
will not pick up these messages. Therefore, it is always necessary to configure
archiving on the Integration Engine.
Archiving Processed XML Messages
In the case of processed messages, you can either archive and then delete them, or
delete them immediately.
We recommend that you configure the archiving (and delete) jobs by using
transaction SXMB_ADM, choose Administration  Schedule Archiving Job and
define what kind of interface to archive using transaction SXMB_ADM  Define
Interfaces for Archiving and Retention Periods.
Note that you cannot select acknowledgment service interfaces from F4 help.
Instead you have to enter the interface name and namespace, using the
values that are displayed in transaction SXMB_MONI for the
acknowledgment messages.
The recurrence depends on the volume of messages you wish to archive in the
system. The background job created is called SAP_BC_XMB_ARCHIVE<client>; it in
turn calls the program RSXMB_ARCHIVE_PLAN and the object BC_XMB is
archived. In the system, RSXMB_ARCHIVE_PLAN starts the program
RSXMB_ARCHIVE_MESSAGES automatically. RSXMB_DELETE_MESSAGES is
started afterwards.
This is responsible for archiving and then deleting the messages.
There are currently two points to keep in mind:
 Archiving and delete jobs are client-dependent.
 All of these jobs are scheduled as priority C batch jobs. Consequently, it is
quite possible that the jobs are not started when expected. This can lead to
unexpected issues with database growth.
You can check if the jobs for deletion and archiving are running correctly (in their
respective clients) by calling transaction SXMB_MONI and choosing Job Overview. It
is also possible to display the archives in transaction SXMB_MONI by choosing
Archived XML Messages.
The location for the archived messages depends on the settings in transaction
SARA. Read the documentation to change these settings. The default location for
archived messages is \usr\sap\<SID>\sys\global and the files are named as follows:
BC_BC_XMB_<yyyymmdd>_<number>.ARCHIVE
240
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
If you want to look at the archive, you can also use Message Monitoring in the
Runtime Workbench as explained above.
In the two dropdown lists, choose the Integration Engine you want to view archives
from. Choose Archives if you want to see messages that are in the archive. Here you
can search based on time periods. Alternatively, you can use transaction
SXMB_MONI  Archived XML Messages. This gives you the option of either
searching using the archives directly or the message ID.
Deletion of Processed XML Messages
Messages can be deleted in two ways: „simple deletion‟ and the „switch‟ method. The
configuration is performed in transaction SXMB_ADM  Configure Delete
Procedure.
 The simple method is a straightforward deletion of the messages that have
exceeded the configured retention period
 The switch method sets a „to be deleted‟ flag for the message that is to be
deleted (the delete flags are set if the defined retention time for the message
has been exceeded). The size of the SXMSPMAST table is monitored and
when it reaches a specified fill level, the entries in the table are copied to a
new master table called SXMSPMAST2. The flagged entries are not copied
to the new table. Once everything has been copied to the new table, the „old‟
table is dropped and recreated.
The switch procedure should only be used if, with each execution of the switch, more
entries are dropped than copied. If more than 50% of the messages have to be
copied every time, the simple delete procedure is probably faster and more
appropriate. Therefore, the switch procedure has to be carefully configured based on
the number of messages being processed, the retention period defined, and the fill
level of the tables that trigger the switch.
The prerequisite for using the switch procedure is that your database supports
truncate functionalities to avoid performance problems. For details, see SAP Note
1032733 - Performance Problems After Using Switch to Delete.
You use the DROP_MAX_TABLE_LOAD parameter to control the fill level at which
the switch is triggered. Set the parameter in transaction SXMB_ADM.
 Choose Configuration  Integration Engine Configuration.
 Select Category DELETION and choose Specific Configuration.
The default setting is 90% of the table size. The table size differs between different
installations. To identify the size of your table, use SXMB_MONI  Persistence
Layer Analysis. The Maximum Number of Table Entries defines the size of your table
and is the basis for the DROP_MAX_TABLE_LOAD parameter. This parameter can
be set to more than 100%. No default recommendation can be given for this
parameter since it is based on the number of processed messages and the retention
period defined.
It is important here to note that problems with disk space can arise for the
database because the switch table procedure creates a copy of the tables,
and therefore additional table space is needed until the drop is executed.
February 2011
241
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Experience has shown that values as low as 10% have been used by
customers (due to experimentation on their part).
The table switch also has a performance issue. Since you cannot really
control the exact date on which the switch is triggered, most customers tend
to configure a low percentage to avoid a large table being copied.
To help you calculate the DROP_MAX_TABLE_LOAD and the retention period for a
switch procedure, let us look at the following example:
o
Table size: 1 million entries
o
DROP_MAX_TABLE_LOAD = 90% meaning 900,000 messages are stored
in the system until the switch and deletion is triggered.
o
Retention period = 30 days
o
Throughput = 10,000 messages/day
In this example a table switch will be triggered after 90 days when the fill level is
reached. Any message aged 30 days or older will be marked for deletion. Messages
aged 0 – 29 days are kept, which means 61 days worth of messages will be deleted.
From that point on, there is a “delta” growth of 61 days until the next deletion occurs.
If we assume that each message is 1 MB in size, this results in the following peak
space usage:
900.000 MB (90 days *10.000 messages/day * 1 MB/message in table SXMSPMAST)
+ 290.000 MB (29 days *10.000 messages/day * 1 MB/message in table SXMSPMAST)
= 1.19 TB for copy and dropping procedure
The graphic below illustrates the example above, indicating the number of messages
persisted in the system. Always keep in mind that the switch procedure should only
be used if more messages are to be deleted than copied. If the table switch is
happening every day, this indicates that the above parameters are configured
incorrectly.
242
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Deletion of Processed XML Message History
The history entries for a message also need to be deleted to avoid database
performance issues.
 Call transaction SXMB_ADM.
 Choose Configuration  Define Interfaces for Archiving and Retention
Periods and choose Retention Period. Specify the value for the Retention
Period for History Entries in the Database.
The default setting is 30 days retention, but it can be reduced to a smaller
value, if needed.
Connected ABAP Proxy Systems
For connected ABAP proxy systems, the same rules apply as for the central
Integration Engine. Every Web AS ABAP >= 6.20 has an integrated XI pipeline to
send messages to XI. Furthermore, the proxy systems persist messages in the same
table as the central Integration Engine. Therefore, the necessary deletion/archiving
jobs have to be scheduled there as well.
Business Process Engine
If you use cross-component Business Process Management (ccBPM), you also need
to implement a deletion or archiving procedure. This follows the standard
recommendations for workflow items.
The work item tables can grow quickly (tables included are SWWWIHEAD, SWW*).
A work item is created for each workflow execution and each step in a workflow;
once a work item is completed, it is usually not needed anymore.
February 2011
243
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
To delete all work items from the BPE, you can use the reports RSWWWIDE and
RSWWHIDE. RSWWWIDE deletes the work item (including its attachments and all
dependent work items), RSWWHIDE deletes the work item history. RSWWWIDE can
also delete work items that are not in final status or that are part of a higher-level
workflow. Once you have executed the reports, there is no way to reconstruct the
deleted work items. For more information, see SAP Notes 49545 - Deleting
Unnecessary Work Items and 836092 - Archiving/Deleting Work Items in XI.
You can also implement archiving for ccBPM. Since the Business Process Engine
(BPE) operates with work items, you must use transaction SARA to archive work
items. The SARA archiving object is the WORKITEM. For more information, see SAP
Library section Data Archiving in SAP NetWeaver AS.
You also have the option of „manually‟ archiving items. You can do this by using
report RSWWWIDE_TOPLEVEL and selecting work item type F with status
COMPLETED and the workflow task you wish to archive. If you are not sure which
task you require, you can look it up in transaction SXI_CACHE. Archive integration
processes that start with WS.
In the Integration Server, the location of the archived messages depends on the
settings in transaction SARA. For information about how to change this value, see
the documentation. The archived work items can be displayed using transaction
SARA, entering WORKITEM as the object, and choosing Read. On the selection
screen, choose Object Category XML Object, then the Object Type, and a key (you
can use *).
244
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
17 System Landscape Directory (SLD)
Troubleshooting the System Landscape Directory
This section provides basic information about how to check if the connection to the
SLD is working correctly and how to troubleshoot if there is a problem. The
connection to the SLD is a vital part of PI during development as well as during
runtime. Among other things, a working connection to the SLD is needed to:
 Import software component versions to the Enterprise Services Repository
 Assign business systems in the Integration Directory
 Provide input help for interfaces in the Integration Directory
 Send messages from the Adapter Framework to the Integration Server
 Perform a cache refresh either from the Integration Directory or the ABAP
runtime cache (transaction SXI_CACHE)
Analysis
The ABAP runtime provides the transaction SLDCHECK as a very useful tool for the
analysis of SLD access problems. Log on to the client of the Integration Server and
start this transaction.
The transaction consists of three parts:
1) Logging on to the SLD using a browser.
2) Testing the SLD access itself (the result is displayed in the SAP GUI).
3) Testing the exchange profile (the result is displayed in the SAP GUI). A
successful check will mark all tests green in the SAP GUI. To display screen
shots, see SAP Note 817920 - XI Readiness Check.
Solution
A detailed Problem Analysis Scenario (PAS) is provided in SAP Library. To locate
the relevant website, see SAP Note 768452 - Troubleshooting SLDCHECK.
The following related SAP Notes help to solve problems beyond mere accessibility:
720717 - Reduce the Number of System Landscape Directories
1117249 - Incomplete Registration of PI Components in SLD
764393 - Configuration of the SAP System Landscape Directory
935245 - Importance of "Object Server" SLD Parameter
935474 - Grouping SLD Instances
936318 - Splitting an SLD Instance
954820 - Compatibility of SLD in the System Landscape
996415 - Error During Self-Registration of Repository/Directory in SLD
988168 - Adapting SLD to Multiple Host Names for Integration
1009527 - Exchange Infrastructure Profile Troubleshooting
February 2011
245
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
1018839 - Registering Information in the System Landscape Directory
Make sure that you have read the SLD Planning Guide. Information provided in the
Planning Guide – System Landscape Directory is of utmost importance to ensure
that your SLD is running and installed according to its purpose. The document can
be found on SAP Service Marketplace at http://service.sap.com/instguides  SAP
NetWeaver  SAP NetWeaver 7.3  Installation  …
SDN: Web Logs
Frequently asked questions (FAQs) about the SLD can be found in the SAP
Developer Network SDN blog, part „Software Landscape Directory – SLD‟.
Analysing SLD Self-Registration Problems
The Integration Server needs information about integrated and connected
components to establish internal connections. This information is held at two different
places, the SLD and the exchange profile. The exchange profile contains basic
connection information about PI components (host names, user/passwords, and so
on). Further component information is written during SLD self-registration by the
different components to the SLD. For more information about what information is
stored where, see section Internal Communication.
If the self-registration does not work properly, the whole PI system will not work as
expected. See, for example, the error solution section Adapter Engine Not Visible in
SLD, RWB, and Directory.
Prerequisites:
You configure the self-registration using the following steps:

Activate the self-registration on the SLD Administration page
http://<server>:<port>/sld  Administration  Data Supplier Bridge

Set connection parameters for the ABAP components in transaction RZ70

Set connection parameters for the Java components in the Java service SLD
Data Supplier
For more information, see SAP Library section Configuring, Working with, and
Administering System Landscape Directory.
On the PI side the following settings are required:
246

Connection to SLD is described in the exchange profile

Technical PI users are defined on the SLD server and have authorization to
write to SLD
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Technical Background:
The NetWeaver ABAP system registers its system data, clients, components, and so
on using the settings in transaction RZ70. The NetWeaver Java stack registers its
system data, services, applications, and products using the settings in the Java
service SLD Data Supplier.
Specific PI registrations are performed from the PI Java components:

The Enterprise Services Repository and Integration Directory start
registration when the next tool (Repository/Directory) logon takes place after
restart of the application.

The Runtime Workbench registers automatically upon server restart (7.10
SP5 or later). If necessary, it can be explicitly registered by restarting the
RWB application com.sap.xi.rwb (7.10 SP3 or later) or through the URL
http://<host>:<port>/rwb/rtc?op=init.

The Adapter Engine registers automatically upon server restart (7.10 SP5 or
later). If necessary, it can be explicitly registered by restarting the application
sap.com/com.sap.aii.af.cpa.app.
PI components are grouped together in ”XI domains“, where one XI domain includes
everything around one Integration Server. One SLD may contain several XI domains.
Self-Registration Procedure:
First, the NetWeaver ABAP and Java stacks register in the SLD, then the PI-specific
part takes place.
Two different scenarios have to be taken into account:

Definition of the business system of the Integration Server (manual task or
during running of the template installer)

Self-registration of PI components (automatic)
The procedure is different depending on what happens first. If one of the PI
components Repository, Directory, Adapter Engine, or Runtime Workbench registers
before the business system of the Integration Server is created in SLD, the XI
domain is created during this registration as well. If the business system for the
Integration Server is created first, the XI domain is created by the SLD business
system wizard:
If the automatic self-registration of the PI components happens first, the
following steps are executed:
February 2011
247
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Business
Business
System
System
BCClient
BCClient
XIIntegrationServer
XIIntegrationServer
Is.isNo.isHost
Is.isNo.isHost
Technical System
Description
XIDomain
XIDomain
domain.isNo.isHost
domain.isNo.isHost
XIAdapterFramework
XIAdapterFramework
Adapter Services
Remote Admin Services
1. Check whether XIDomain is already defined:

Read properties from the exchange profile:
integrationserver.name = isHost
integrationserver.r3.sysnr = isNo

Check whether domain entity exists in SLD: domain.isNo.isHost

If not: Create XI subsystem (for example XIAdapterFramework) with
necessary services
plus domain
plus Integration Server

Find associated Integration Server by naming scheme: is.isNo.isHost
o
If not found:Create Integration Server and connect to domain
o
If found:
Connect domain and Integration Server
2. Define business system (procedure is executed as part of the SLD wizard for
BS creation)

Create business system

Check whether XIIntegrationServer is already defined: is.isNo.isHost
isNo and isHost are read from central App Server in SLD

248
If yes, connect
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
If the manual creation of the business system in the SLD happens first, the
following steps are executed:
Business
Business
System
System
BCClient
BCClient
XIIntegrationServer
XIIntegrationServer
Is.isNo.isHost
Is.isNo.isHost
Technical System
Description
XIDomain
XIDomain
domain.isNo.isHost
domain.isNo.isHost
XIAdapterFramework
XIAdapterFramework
Adapter Services
Remote Admin Services
1. Algorithm by SLD business system wizard:

Create business system

Check whether XIIntegrationServer is already defined: is.isNo.isHost
isNo and isHost are read from central App Server in SLD

If not found, create
2. Algorithm by self-registration

Create XI subsystem (for example XIAdapterFramework) with
necessary services

Check whether XIDomain is already defined
Read properties from exchange profile:
integrationserver.name = isHost
integrationserver.r3.sysnr = isNo
Check whether domain entity exists in SLD: domain.isNo.isHost

February 2011
o
If not found:
Create domain
o
If found:
Connect
Find associated Integration Server by naming scheme: is.isNo.isHost
249
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
o
If not found:
domain
Create integration server and connect to
o
If found:
Connect domain and integration server
Self-Registration for HA
For an HA installation, you must follow the instructions in SAP Note 1052984 Process Integration 7.1 - High Availability. With this setup, different exchange profile
parameters are used for the self-registration.
The main difference compared to the standard case is that the central application
server is looked up in SLD and used for name composition.
Whether the HA case or standard case applies for self-registration is determined by
the exchange profile property com.sap.aii.connect.integrationserver.r3.mshost.
com.sap.aii.connect.integrationserver.r3.mshost is empty  standard case
com.sap.aii.connect.integrationserver.r3.mshost is not empty  HA case
Note: The different naming logic applies whenever the property above is not empty,
even if it is not pure “HA” but simple load balancing.
Components After Successful Self-Registration
After successful self-registration, all PI components should be in the SLD and
grouped together in one XI domain. To check this, go to http://<server>:<port>/sld 
Technical Systems, select Technical System Type „Process Integration‟.
The components Integration Directory, Enterprise Services Repository, Integration
Server, RWB, several Adapter Engines and the XI domain itself are displayed, the
domain names have to match exactly (not one short and one long with extension).
Error Analysis:
If the components did not register successfully or they did register but under different
domains, the SLD contains inconsistent entries. This can occur for the following
reasons:

250
Incorrect configuration of the SLD self-registration
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
o
User/password wrong
o
User does not exist in the SLD (if SLD is set up on another system)
o
User does not have correct authorization
o
Incorrect SLD server/port settings

Timeouts during self-registration

Connection problems during self-registration
To find the cause of the problem, check the following logs and traces for errors:

Java default trace

SLD log under http://<server>:<port>/sld Administration  Log

Logs of the registering application:
o
RWB: Java default trace
o
Directory: Java default trace
Memory log: http://<server>:<port>/dir/support/private 
View Memory Log
o
Repository:
Java default trace
Memory log: http://<server>:<port>/rep/support/private
 View Memory Log
o
Adapter Engine: Java default trace
Check the following:

Check the SLD settings in the exchange profile.

Is the business system for the Integration Server defined in the SLD?

Are the technical PI users defined and authorized in the SLD system?
Tip: Try to log on with technical users in SLD UI.


Initiate the self-registration again and check results in SLD afterwards:
o
RWB: Execute http://<host>:<port>/rwb/rtc?op=init
o
Repository: Restart application in SAP NetWeaver Administrator and
log on to the Repository in a new session
o
Directory: Restart application in SAP NetWeaver Administrator and
log on to the Directory in a new session
o
Adapter Engine: Restart application sap.com/com.sap.aii.af.cpa.app
Delete XI domain in SLD, initiate complete self-registration
o
Delete in SLD UI  Technical Systems  Process Integration
o
Reregister by restarting AS Java Engine
February 2011
251
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Deleting SLD Caches After Changing the SLD Content:
SLD content is cached by the PI runtime components. If any changes are made in
the SLD, the components have to be refreshed:

RWB: http://<host>:<port>/rwb/rtc?op=init

Directory: Environment  Clear SLD Data Cache in the Directory UI

Repository: Environment  Clear SLD Data Cache in the Repository UI

Integration Server:
o
Execute transaction SLDCHECK
o
Delete the URLs of the Adapter Engines if they contain incorrect data:
transaction SXI_CACHE  Goto  Adapter Engine Cache
Relevant SAP Notes:
768148 - Using a Separate SLD for XI
1117249 - Incomplete Registration of PI Components in SLD
988168 - Adapting SLD to Multiple Host Names for Integration Server
Problems and Solutions
17.1.1.1 Changes in SLD Are Not Passed to Runtime
Problem
You have changed the ALE name for the business system in the SLD, but these
changes are not reflected at runtime.
Solution
In the Integration Directory, reload the data into the communication component, save
and activate it.
17.1.1.2 Using a Separate SLD for PI
Problem
You want to run your PI system with an SLD on a separate server and want to know
more about the configuration process.
Solution
If you want to use an SLD on a server without a PI installation for your PI system,
you need to proceed as follows:
252
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
-
Create the PI communication users in the SLD system as described in
SAP Note 768148 - Using a Separate SLD for XI.
-
Connect the SLD to the PI system as described in SAP Note 939592
- PI Usage Configuration Versus Central SLD.
If you want to change the SLD used, proceed as described in SAP Note 720717 Reduce the Number of System Landscape Directories (SLD).
17.1.1.3 Adapter Engine Not Visible in SLD, RWB, or Directory
Problem
You do not see your Adapter Engine in the SLD or in the Runtime Workbench;
furthermore, it is not possible to select it in the Directory channel configuration.
Analysis
See the Adapter Engine Not Visible in SLD, RWB, or Directory section.
17.1.1.4 Calling Function LCR_LIST_BUSINESS_SYSTEMS Returned
Exception Code 4
Problem
SLDCHECK shows the following error:
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code
4
=> Check whether the SLD is running
Solution
Check that the user maintained in transaction SLDAPICUST is not locked in the SLD
system and have a look at the information about SLD troubleshooting in SAP Library.
See also the following SAP Notes:
608322 - SLDAPICUST: Discrepancies with the Host Name, FQDN
939592 - PI Usage Configuration Versus Central SLD
999962 - PI 7.10: Change Passwords of PI Service Users
988168 - Adapting SLD to Multiple Host Names for Integration
February 2011
253
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
17.1.1.5 Calling Function LCR_GET_BS_DETAILS Returned Exception
Code 5
Problem
SLDCHECK shows the following error:
Calling function LCR_GET_BS_DETAILS
Retrieving data from the SLD server...
Function call returned exception code 5
=> Check whether the SLD is running!
Solution
In addition to the standard SLD troubleshooting guidelines, see the following SAP
Note:
608322 - SLDAPICUST: Discrepancies with the Host Name, FQDN
17.1.1.6 Calling Function EXCHANGE_PROFILE_GET_PARAMETER
Returned Exception Codes 2 or 3
Problem
SLDCHECK shows the following error:
Calling function EXCHANGE_PROFILE_GET_PARAMETER
Retrieving data from the XI Profile...
Function call returned exception code 2
Access to the XI Profile is currently disrupted.
=> Check whether you can access the XI Profile using a web browser!
Calling function EXCHANGE_PROFILE_GET_PARAMETER
Retrieving data
from the XI Profile...
Function call returned exception code 3
Access to the XI Profile is currently disrupted.
=> Check whether you can access
the XI Profile using a web browser!
Solution
Read SAP Notes 768452 - Troubleshooting SLDCHECK then recheck how you
configured the system.
You might have installed a central SLD and the settings described in SAP Note
720717 - Reduce the number of System Landscape Directories have not been
properly changed.
The exchange profile RFC connection LCRSAPRFC is probably pointing to the
wrong hostname, eventually the central SLD hostname. Please take into
consideration that LCRSAPRFC must always point to the hostname of the system on
which the PI system is running, regardless of SLD being central or local. There is no
such thing as a central Exchange Profile.
254
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
17.1.1.7 Assignment of Roles in SLD
Problem
The assignment of the necessary roles for PI users is unclear, especially as regards
which roles are necessary for a user‟s connection to the SLD server. PI users are
lacking role assignments and authorizations.
Solution
Check the users and the necessary roles in SAP Note 768148 - Using a Separate
SLD for PI.
February 2011
255
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
18 AS Java
How to Determine the AS Java Version and SP
Problem
How do you determine the Java version and SP?
Solution
You can find the version and SP in the std_server<x>.out file in the work directory of
the instance, or check the system information on the page http://<j2ee-host>:<j2eeport>/monitoring/SystemInfo
How to Determine the HTTP Port of the AS Java
Problem
How do you determine the HTTP port of the AS Java?
Solution
Start transaction SMICM on the central instance and choose Goto -> Services. Here
two HTTP ports can be seen, the ABAP HTTP port and the HTTP port of the AS
Java Engine. You could also use the SAP MMC console  AccessPoints perspective.
The default AS Java Engine port is 5<instance number>00, for example, 50100.
AS Java Central Notes
Some PI applications run in the AS Java Engine. It is often necessary to tune or
adapt the parameter settings of the AS Java Engine to improve performance or to
avoid OutOfMemory or „Unable to create new native thread error‟ errors.
Problem
You need more information about parameters and settings for the AS Java Engine.
Analysis
The necessary settings for using Process Integration (PI) 7.30 are outlined in
http://service.sap.com/instguides  SAP NetWeaver  SAP NetWeaver 7.3  Installation
…
For information about where to find logs and traces in the AS Java Engine, see the
section Problem Analysis for the Enterprise Services Repository (ESR) and
Integration Directory.
256
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
For the Java Server, there is a Wiki page with troubleshooting information for specific
error situations within the 7.3 Java Server. See the TroubleShooting Guide for SAP
NetWeaver Application Server Java
For information about troubleshooting AS Java in 7.10, see the following SAP Notes:
SAP Note 1121897 - Central Note for SAP NetWeaver AS Java 7.1
SAP Note 1095476 - Information for troubleshooting of the AS Java
SAP Note 1095475 - How to enable HTTP tracing in the AS Java
More information:
Java Memory Analysis (provides full thread and heap dumps)
PI Services in AS Java
PI applications are separated by either running as a service in the AS Java Engine or
in the ABAP stack of the Integration Engine.
Problem
You need more information about the following:
 Which PI applications are running as a service in the AS Java Engine?
 How can I find out which services are currently running/active?
 Which PI applications are maintained using AS Java deployment?
 How can I see the deployed version?
 What is the content of the deployed SCAs?
Analysis
Which PI applications are running as a service in the AS Java Engine?
PI uses the ABAP stack as well as the Java stack for its applications.
The following PI applications run in the Java stack:
- Central Adapter Engine
o Adapter Framework
o Adapters
 RFC adapter
 JDBC adapter
 File/FTP adapter
 JMS adapter
 SOAP adapter
 Marketplace adapter
 Mail adapter
 SAP BC
 RosettaNet (RNIF 2.0, RNIF 1.1) adapter
 CDIX adapter
February 2011
257
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
-
-
 IDoc_AAE
 HTTP_AAE
o Messaging system
o CPACache
Integration Builder
o Enterprise Services Repository
o Integration Directory
Runtime Workbench
Mapping runtime
System Landscape Directory
As a prerequisite for analysis, check whether the SAP AS Java Engine is running:
In the ABAP stack, call transaction SMICM, choose GOTO -> HTTP-Pluginr –>
Display data. The setting must be: AS Java Server state = active
In the Java stack, open Internet explorer – http://<AS Java-host>:<AS Java-port>.
This should open the administration page of the AS Java Engine.
How can I find out which services are currently running/active?
To check the PI Services, use the SAP NetWeaver Administrator
http://<AS Java-server>:<AS Java -port>/nwa  Operations  Systems  Start &
Stop  Java Services.
The PI services are:
- XPI Adapter: <type> – lists all the available adapters as a PI service:
-
258
XPI Service … – lists the services for PI:
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
How can I see the deployed version?
To get the current version of the PI services, use the SAP NetWeaver Administrator
http://<AS Java-server>:<AS Java-port>/nwa  Configuration  Infrastructure 
System Information  Components Info.
Here you can find the SP release for each of the software components, for example:
Which PI applications are maintained using AS Java deployment?
All PI applications running as a Java service are maintained using Java deployment
(SCA packages).
The following PI services are deployed with the corresponding SCA:
Package
Technical Name (for Current Patch)
XI ADAPTER FRAMEWORK 7.30
SAPXIAF<SP>_<Patch>
SOA MONITORS 7.30
SOAMON<SP>_<Patch>
SOA MONITORS BASIC 7.30
SOAMONBASIC<SP>_<Patch>
February 2011
259
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
MESSAGING SYSTEM SERVICE 7.30
MESSAGING<SP>_<Patch>
ESR 7.30
SAPXIESR<SP>_<Patch>
XI TOOLS 7.30
SAPXITOOL<SP>_<Patch>
PI GUI 7.30
SAPXIGUILIB<SP>_<Patch>
XI 3RD PARTY 7.30
SAPXI3RDPARTY<SP>_<Patch>
XI PCK 7.30
SAPXIPCK<SP>_<Patch>
XI CONNECTIVITY SE 7.30
SAPXICONS<SP>_<PL>.SCA
The PI content is not deployed but imported in the Repository (see SAP Library
section Importing ESR Content.
XI CONTENT PI_BASIS 730
PIBASIS730<SP>_<Patch>
What is the content of the deployed SCAs?
To find out the detailed content of each package, double-click the SCA file. This
opens a WinZip window showing Java SDA archives together with the manifest files
related to the package. To get further details, you can open these archives again
with WinZip to show the single files. Further Information:
SAP Note 784471 - Determining installed Adapter Framework Version.
AS Java Engine Clustering
Problem
You have an instable PI environment due to AS Java Engine instability.
You want to increase the performance of AS Java Engine-related PI components
such as Java mapping and the Adapter Framework (AFW).
Solution
If you notice that the AS Java server node crashes with an out-of-memory error, or
you are experiencing message delays in mapping processing, or message delays in
the AFW in high-load intervals, we recommend installing the AS Java Engine with
multiple server nodes.
If your hardware for the central instance is not capable of running multiple server
nodes, you have the option of installing additional AS Add-In dialog instances in your
PI system.
Running PI in an AS Java Engine cluster environment requires specific preparation
and effort by the system administrator and interface developers.
260
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
See the detailed information in SAP Note 1079478 - Using a J2EE Cluster in the PI
7.10 Environment and the guide How-To Scale Up EHP 1 for SAP NetWeaver
Process Integration 7.1 (PI 7.11) (not available yet for SAP NetWeaver 7.3,).
Using Full Thread or Heap Dump to Analyse AS Java
Problems
Problem
The AS Java Engine started, but stopped after a certain amount of time with high
CPU consumption, or the application stopped but the AS Java Engine is still running,
sometimes with an out-of-memory error.
Analysis
First, read SAP Note 1095476 - Information for Troubleshooting of the AS Java.
It is very useful to have a full thread dump if the AS Java Engine is running with high
CPU consumption. See SAP Note 1095473 - How to Get a Full Thread Dump in AS
Java. We recommend that you create the thread dump once the AS Java Engine is
running properly and once when an error occurs. To analyze not only the current
thread status as a snapshot but the important changes over time, it is essential to
always take a series of thread dumps (for example, 3 dumps with a 20 second time
interval).
After creating the full thread dump, you will find the string full thread dump as the
header in the STD_SERVERx.out file.
You can use ThreadDumpScan to analyze the result of a full thread dump.
ThreadDumpScan is a simple Java SE application that scans the Java VM console
output and generates summary tables for verbose:gc output and full thread dumps
found in the console log.
To analyze Out of Memory errors, a heap dump is necessary. For information about
how to create the heap dump, see SAP Notes 1095476 - Information for
Troubleshooting of the AS Java The SDN article Analyzing Java out of Memory
Problems with IBM Heapdump Facility describes how to analyze and find a possible
cause of Java OutOfMemory errors while running SAP NetWeaver Java components
on top of an IBM JVM.
For more information on full thread and heap dumps, see
https://wiki.sdn.sap.com/wiki/display/Java/Java%20Memory%20Analysis.
Solution
What to look for?
February 2011
261
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
1. Learn more about Out of Memory [OOM] using the following page:
http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Kernel)OOM+Wizard.
2. Try to find the explicit deadlocks in the dump file. Java will detect the simple
deadlocks automatically.
3. Check how many threads have the status “waiting for monitor entry”. These
threads are blocked and are therefore critical if their status does not change
over time. Therefore, you have to compare several dumps for the analysis.
4. If you analyze threads to find the root cause for high CPU usage, you have to
look at the threads with status “runnable”. How many threads are in this
state? What is their stack trace? Which package prefixes can be determined?
Can these threads and their status be explained by the load currently on the
system or do they show unusual behavior? Again, to analyze running threads
you have to compare several dumps to see if these threads finish their work.
To analyze which of the running threads is causing the high CPU usage..
5. Often a problem is also indicated by multiple worker threads having the same
stack trace. This may indicate a starvation or deadlock situation. Therefore,
you have to scan the threads in the single dumps and look for the number of
threads with the same stack trace. Here as well it is important to compare the
different thread dumps taken.
6. If the errors are similar to “OutofMemoryError: unable to create new native
thread…”, or after analyzing the dump file you found that almost all the
threads are in use, go to the ConfigTool, choose cluster data -> server -> cfg
-> kernel -> propertysheet -> Application Thread Manager, double-click the
property sheet, and change the value of MaxThreadCount to 150 - 300.
When increasing the number of threads it is also necessary to increase the
number of maximum database connections (DB pool size) and the number of
processes on DB level.
7. If you are using HP-UX together with PI, and if the AS Java server cannot
start or hangs after being started, try to change the Kernel Unix parameter
NKTHREAD to 3000 or 6000, MAX_THREAD_PROC to 10000 or 20000. For
more information, see SAP Note 534867 - J2EE Server on HP-UX.
8. For any other problem, analyze the dump file and try to find where the error
occurs.
262
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
19 HA (High Availability)
HA (High Availability) Troubleshooting
Problem
You have problems setting up PI in an HA environment and need more information
concerning this issue.
Analysis
The supported installation variants for Process Integration in SAP NetWeaver 7.3 for
High Availability are described in SAP Note 1052984 - Process Integration 7.1 - High
Availability.
In addition you might be interested in general PI system distribution options such as
installing PI on multiple dialog instances, how to set up the load distribution between
dialog instances and Adapter Engines, installation of PI with or without separated
database systems, installation of additional non-central Adapter Engines, and so on.
For information about PI distribution configuration, see the How-To Guide How-To
Scale Up SAP Exchange Infrastructure 711 (this guide is not available yet for SAP
NetWeaver 7.3, but you can still use the guide for PI 7.11, because the concepts are
still valid).
February 2011
263
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
20 Security & User Management
User Concepts
Different users are created during installation for PI internal and external
communication. Each PI component has its own user to log on to other components,
for example the Integration Directory uses the PIDIRUSER (or equivalent if another
name is used during installation) to log on to the other components.
Problem
You have authentication or authorization issues in your PI system and want to know
more about the users and authorizations used for PI internal and external
communication and how to analyze this kind of error.
Technical Background:
Authentication means that the user and password are checked during logon to
verify that the principals (users, systems) are who they claim to be, based on a set of
credentials provided. The authentication can be done using:

User name/password

X.509 certificate (e.g. SSL)

SSO certificates (SAP assertion ticket, SAML assertions)
Authorization means that the user needs the right permissions to access specific
resources to ensure only authorized users can execute specific actions.
SAP delivers predefined roles for technical users (internal communication),
messaging users, and dialog users. PI-specific users are created during installation
together with their roles.
For message exchange, only the user PIAPPLUSER is created during installation.
This user is assigned role SAP_XI_APPL_SERV_USER. PIAPPLUSER should be
used as the master copy for other messaging users. Using different application users
for different interfaces will provide better monitoring and error analysis capabilities
during production. The following table shows which components need a messaging
user with role SAP_XI_APPL_SERV_USER. For ABAP and Java proxy receiver
systems, the user needs not only the role SAP_XI_APPL_SERV_USER but also
application-specific authorization according to the application executed by the proxy
call:
For PI administration, configuration, and monitoring, SAP delivers several PI-specific
roles for dialog users. These roles have to be assigned to the dialog users
responsible for specific tasks in the PI system, for example role
SAP_XI_ADMINISTRATOR should be assigned to the PI system administrator.
264
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
For more information about the technical users for internal communication with their
roles created during installation per Usage Type, see User Management and
Authorization Concepts (Dual-Stack) and User Management and Authorization
Concepts (AEX).
Synchronization of ABAP and Java Roles
Depending on the chosen installation option, you use both ABAP-based and Javabased user management in different ways. In the following section we provide an
overview of the different possible setups of user management for the different
installation options:
Standard (Dual-Stack) PI Installation
This installation option is based on both AS ABAP and AS Java. Therefore, each PI role
consists of two sub roles (ABAP and Java).
The synchronization between ABAP and Java is done by mapping ABAP profiles to
Java groups. This mapping is configured in the User Management Engine (UME) of
the Java Engine. For PI systems you configure this mapping against the source
ABAP user store so that the ABAP profiles are mapped to the Java groups.
If ABAP roles need to be copied, you should never copy Java roles (for example,
SAP_XI_ADMINITRATOR_J2EE) as this prevents easy support package
adjustment. You can copy the ABAP role and use it together with the Java role
delivered by SAP in one new composite role.
SAP
Composite Roles
Single Roles
SAP
Java
New
SAP
ABAP
SAP
Java
New
ABAP
As an option (for example, in case you install the non-central Advanced Adapter
Engine), you can use a “local” Java-based UME for the Java-based parts of your
landscape (Advanced Adapter Engine). In that case, roles and users are not
synchronized between AS ABAP and AS Java and both kinds of user management
operate independent.
Advanced Adapter Engine Extended
In case you have chosen this installation option, you use only Java-based user
management. Therefore, only Java groups and roles exist.
Analysis
The user name and password of the technical users for internal PI communication
are maintained in the exchange profile. For information about how the internal
February 2011
265
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
communication is established and where to find logs and traces in the event of
errors, see the section Internal Communication.
For internal communication, SSO or SSL with client authentication is not supported.
The user name and password for the messaging users for messaging
communication are maintained in:

Sending system (for example, in an SM59 destination in an ABAP sender
system)

Exchange profile (for PI internal messaging – Integration Server/Adapter
Engine communication)

Integration Directory (for outgoing messages)
For information about how the messaging communication works and where to find
logs and traces in the event of errors, see section Messaging Communication.
For HTTP-based adapters, SSL with client authentication is supported; for more
information, see HTTP and SSL in SAP NetWeaver Process Integration Security
Guide.
For principal propagation, an SAP assertion ticket is used; for more information, see
SAP Note 974873 - Principal Propagation and SAP Library section Configuring
Principal Propagation.
For dialog user access, ordinary AS user management (user name/password, SSO)
is used.
SSO is supported for Integration Builder and RWB within the same browser session.
Checks and Traces:
In the event of errors, perform the following checks:

266
Check user in transaction SU01
o
Are the passwords set consistently according to SAP Note 999962 PI 7.10: Change Passwords of PI Service Users?
o
Does the user exist (for example in SLD system)? For more
information about the necessary users in the SLD system, see SAP
Note 768148 - Using a Separate SLD for XI.
o
Is the user locked?
o
Are the correct roles assigned?
o
Are the profiles for the roles generated?

Log on with the user and password to the component directly using the UI.

Execute checks and check logs and traces of the involved components as
described in sections Internal Communication and Messaging
Communication.
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Reference User Management and Authorization Concepts (Dual-Stack) and User
Management and Authorization Concepts (AEX) in the SAP NetWeaver Process
Integration Security Guide to see the technical users for internal communication
with their roles created during installation per Usage Type
Security Aspects
As the central infrastructure for exchanging business documents, PI has to make
sure that the involved processes can be executed in a secure manner. Particular
security requirements have to be considered if business partners communicate over
the Internet.
XML messages may contain confidential business data. In order to protect them
against eavesdropping and unauthorized access, the communication lines as well as
the storage locations of XML messages need to be made secure.
In addition to the business data exchanged using PI, the various components of PI
need to communicate with each other on a technical level in order to keep the
infrastructure running. Security requirements apply to these technical
communications as well, because confidential information such as user names and
passwords may have to be sent or stored, or both.
Problem
You are not sure if the customer is enabling PI security features in the correct way.
Check the corresponding guide for the different components.
Analysis
PI General Security Features:
The PI security features are described in the SAP NetWeaver Process Integration
Security Guide. It explains the options for data protection for each PI component and
contains a description of how to set up secure communication for the different PI
components. It also contains information about all PI service users used for
communication between the PI components.
Single Sign-On Activation Issue:
See SAP Library section Single Sign-On Configuration.
Data-Dependent Authorization Issue:
The data-dependent authorization steps are described in SAP Library section
Creating Users with Data-Dependent Authorizations.
ACL Concept:
The ACL (access control list) concept was introduced to allow the execution of
special messages only to a list of users. This list is also known as an access control
list. For more information, see SAP Library section Service Users for Message
Exchange.
February 2011
267
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Folder-based and object based permissions in Integration Builder:
Note that the Enterprise Services Builder and the Integration Builder offer the
following alternative authorization models:

Role-based permissions

Permissions based on access control lists (ACLs)
Which model is used depends on the configuration. Check out the PI documentation
for more information in case you encounter troubles.
Message-Specific Configuration of HTTP Security:
With PI it is possible to define a security level for certain HTTP-based PI inbound
messages using sender-specific configuration (sender channels or sender
agreements) in the Directory. For more information, see SAP Library section Defining
Sender Agreements and the linked sections. Usually the adapter that is used
supports a transport-level encrypted protocol such as HTTPs, FTPs, and SNC.
Transport-level Security for PI-Internal Communication
“PI-internal” communication refers to technical communication between different PI
components such as Integration Engine, Advanced Adapter Engine, Integration
Builder, and SLD, for example.
PI-internal communication can be switched to HTTPs and SNC (for RFC).
Enabling SSL on the AS ABAP Stack:
See SAP Library documentation Configuring the AS ABAP for Supporting SSL.
Enabling SSL on the SAP AS Java Stack:
See the SAP Library documentation Configuring the Use of SSL on the AS Java.
Enabling SNC on the AS:
See the SAP Library documentation Configuring SNC for Using the SAPCRYPTOLIB
on the SAP Web AS.
Note that in addition to the enabling of SSL, HTTPs and SNC on the underlying
application servers, additional configuration steps are necessary. For more
information, see the related PI documentation.
Web Service Security Questions:
For more information, see the SAP Library documentation WS Security XML
Signature/Encryption.
Network Security Issue on PI:
268
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
To allow authorized communication in a firewall, you need to know which ports are
used by PI for communication.
The ports used by PI are listed below:
Table of Ports Used by PI:
Connection
Explanation
Direction of
Information
1)
Flow
Example:
<sn> = 01
ABAP
Dispatcher
Used by SAPGUI
→(outside –
in)
3201
ABAP Message
Server
Used for load balancing
→(outside –
in)
3600
RFC connection
External RFC client connects to Gateway
and external RFC registers on GW as
server program
→(outside - in)
3301
←(inside - out)
4801 for
SNC
SAPlpd
For printer
→(outside - in)
515
HTTP Adapter
Connection
The incoming request to sender HTTP
adapter
→(outside - in)
8001
SOAP Adapter
Connection
The incoming request to sender SOAP
adapter
→(outside - in)
50100
Telnet
connection
This connection is used for telnet
→(outside - in)
4701 for
SNC
2)
50101 for
SSL
50108
Note: Telnet should not be used for administrative functions, as it does not provide
the needed security capabilities.
Message-Level Security Issues:
For a description of how to configure signing/encryption of messages, also known as
message-level security for PI message exchange, see SAP Library section
Message-Level Security.
PI provides message-level security only for specific communication paths, but not
end-to-end. For example, the communication from the Advanced Adapter Engine to
the Integration Engine can be secured by message-level encryption. However the
communication within the Integration Engine can‟t be secured by this mechanism.
1)
Outside - in: indicates a communication path from the client network to the server network.
Inside - out: indicates a communication path from the server network to the client network.
2)
Defined in /etc/services.
February 2011
269
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Problem:
You use certificates as authentication method but you get errors.
Solution:
Check if certificates are expired. The underlying application server may offer a
notification for certificates set to expire.
Solution
Check if user is locked. This may be the case if the password of a messaging user or
system user was changed, but the password was not updated.
Problem
You use the security archiving functionality but get errors.
In detail, you make use of the security archiving in Runtime Workbench (RWB). This
function archives messages with content type S/MIME (for example in case the CIDX
adapter is used). Security archiving can be con configured in RWB (choose  Status
tab  Security Archiving). The data is stored in table XI_SEC_MS.
Solution
The messages are stored in database tables that may have exceeded their limits. To
be checked: Configure the automatic cleaning of these tables, or apply backups.
Problem:
You want to customize the permissions of Java-based user interfaces such as RWB.
Solution
Check the related UME actions and modify the user roles in UME. UME actions are
documented in related SAP Notes and the PI Security Guide.
SAP Note: Note 1370334 - Securing Payloads in Message-Monitoring
Problem
You use certificates as authentication method but you get errors.
Solution
Check if certificates are expired. The underlying application server may offer a
notification for certificates set to expire (to be checked).
User Management Issues:
270
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
For a description of how to change passwords for the PI service users in a PI 7.1
environment, see SAP Note 999962 - PI 7.10: Change Passwords of PI Service
Users.
February 2011
271
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
21 PI Performance
How to Analyse Performance Issues on your PI System
Problem
You are having performance problems in your PI system. Message processing in
your PI system is taking a long time and does not fulfill your requested message
throughout.
Analysis
Check if the PI system performance is generally poor, or if it is just the processing of
specific messages that is taking a long time.
Message-Specific Performance Problems:
A comprehensive guide that helps you isolate bottlenecks and provides possible
tuning options can be downloaded from SAP Note 894509 - XI Performance Check.
The guide PI Best Practices: Sizing and Performance Tuning provides guidelines in
terms of sizing and performance of a PI system. [The guide for PI 7.30 is not yet
available however you can use the PI 7.11 version]
A short list of possible starting points is listed below:
Analyze the performance header of the messages in transaction SXMB_MONI;
identify the pipeline service causing long processing times by evaluating the time
difference between the begin and end time stamps. Depending on which pipeline
service is responsible for the long processing time, further investigation is required:
 DB_ENTRY_QUEUING / DB_SPLITTER_QUEUING:
Check that all PI queues are registered in transaction SMQR. Check that
enough dialog work processes are available on the Application Server for
tRFC processing. Transaction SARFC shows you the current status of
available dialog resources.
 PLSRV_MAPPING_REQUEST:
Check and analyze the used mapping in more detail.
 PLSRV_CALL_ADAPTER:
Check the performance of the Adapter Engine/Adapter Framework.
General PI System Performance Problems:
1) Check the ABAP stack including OS/DB of the PI system by using the transactions
listed in SAP Note 15374 - Checklist: Performance Analysis.
To interpret the results displayed in the transactions, you need to be familiar with the
SAP System Performance Analysis. The following gives you an idea of where to look
272
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
for more details:




Detection of high CPU times:
Check which processes are causing high CPU usage.
Detection of high DB request times:
Check for CPU/memory bottleneck on database server.
Check for network problems.
Check for expensive SQL statements.
Check for database locks.
Check for missing indexes.
Check for missing optimizer statistics.
Check for small database buffers.
Detection of higher processing times than CPU time:
Check for CPU bottleneck.
Check for network problems/communication problems.
Detection of high load times:
Check for program/CUA/screen buffer.
2) Check the Java stack of the PI system by using the Java System Reports
provided in SAP NetWeaver Administrator http://<server>:<port>/nwa  Availability
and Performance Management  Java System Reports.
3) Are you using ccBPM scenarios that cause heavy system loads? See the solution
for Error! Reference source not found. below.
4) Are you using IDoc scenarios that cause heavy system loads? See the solution for
IDoc below.
Solution
ccBPM
If you encounter performance issues with scenarios running ccBPM processes,
check for design advice for ccBPM use cases in SAP Library section Checklists for
Integration Processes.
IDoc
If you are encountering performance issues with IDoc scenarios, check whether SAP
Note 814393 - Multiple IDoc Instances in an XI Message could help you redesign a
much faster solution for your scenario.
Java Clustering
For information about using Java Engine clustering to improve the performance of
your PI system, see the AS Java Cluster Architecture section.
Others
February 2011
273
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
If you are still experiencing performance issues and you cannot solve them using the
guidelines and information provided in this paragraph, you might want to involve SAP
specialists by opening an SAP message under component SV-BO-XI.
SAP also offers GoingLive services for your PI systems. These services evaluate the
overall system settings and configuration. For a general description of GoingLive
service, see SAP Service Marketplace and SAP Note 617604 - SAP Remote
Services for SAP Exchange Infrastructure for the detailed setup of your PI system for
the remote service.
PAS: PI Performance
This section describes three typical performance problem analysis scenarios (PAS).
The cases are selected to cover as many analysis tools and functions as possible, as
XImany
3.0 different
Example
Landscape
well as
PI software
components. The focus is set on the analysis of
problems regarding the Java coding and runtime, since this still poses a challenge.
Server
Server 22
Server
Server 11
CPUs
NW04: XI Integration Server
ABAP Runtime
SAP
SAP
System
System
Pipeline Services
Server
Server 33
CPUs
J2EE Runtime
Adapter
J2EE Runtime
Mapping Execution
Server
Server 44
Ext.
Ext.
System
System
 SAP AG 2004, Title of Presentation / Speaker Name / 1
1. Expensive application mapping: A specific performance problem caused
by a complicated message mapping.
a. Involved software components: Integration Server, PI mapping
runtime
b. Involved tools: Runtime Workbench, message monitoring:
performance header, SAP NetWeaver Administrator (NWA)
274
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
2. Bottleneck in ABAP->Java mapping communication: A general
performance problem on the Integration Server during parallel mappings
caused by non-optimal configuration.
a. Involved software components: Integration Server, PI mapping
runtime
b. Involved tools: Runtime Workbench, message monitoring:
performance header
3. CPU overload due to Java garbage collection: A general performance
problem on the Adapter Engine server caused by high load from VM garbage
collection.
a. Involved software components: Integration Server, Adapter Engine
b. Involved tools: Runtime Workbench, message monitoring:
performance header, SAP NetWeaver Administrator
21.1.1
Expensive Application Mapping
Problem Description
It takes a long time to process an XI message in a specific pipeline step.
Example Scenario
Server
Server 22
Server
Server 11
CPUs
Integration Server
ABAP Runtime
SAP
SAP
System
System
Pipeline Services
Server
Server 33
CPUs
Java Runtime
Adapter
Java Runtime
Mapping Execution
Server
Server 44
Ext.
Ext.
System
System
During a GoingLive Optimization Session for an SRM scenario, an invoice is sent
from an SUS system to an MM backend using PI as a pre-production test. A
standard SAP scenario SUS2MM is used for the interface. The total response time of
the business process is more than 2.3 sec, which is not acceptable for the customer,
since the business process is time-critical and has a high volume.
Verification of Symptoms
Call SXMB_MONI, select the PI message in question and go to the performance
header. Pipeline step PLSRV_MAPPING_REQUEST is the longest pipeline service.
February 2011
275
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Possible Error Causes
Bad mapping algorithms
Analysis Overview
Analysis Details
In a pre-production system, you can test a single message of a specific type by
sending it separately and looking at the response time within PI.
Message Monitoring (SXMB_MONI)
Log on to the Integration Server and call transaction SXMB_MONI: Monitor for
processed XML messages.
Select messages with status „Processed Successfully‟ from the last hour.
276
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
In the list of messages displayed, you can identify your message by the sender,
receiver, or time stamp, for example. Double-click it to select it and you can take a
look at the message content.
Performance Header
Choose the latest performance header from the tree on the left side and look at the
SOAP header in the upper window on the right side.
February 2011
277
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
By comparing the time stamps given in the format <YYYYMMDDHHMMSS.msec>
for all pipeline steps, you can find the step with the longest time.
In this example the mapping step takes the longest time to complete.
You have to know the overall PI architecture to find the next analysis step. The
mapping request is the only step that is processed within AS Java. Therefore, any
further analysis has to be done with SAP NetWeaver Administrator.
21.1.2
Bottleneck in ABAP->Java Mapping Communication
Description
A customer has a difficult problem with his mapping on the Integration Server. All
was well until the start of a new scenario yesterday. It consists of small IDocs sent
from an SAP system to the Integration Engine (including mapping), which directs
them to a file adapter on a different server at a maximum rate of approximately 3-4
per second from 8am to 9am. Although the CPU load of the Integration Server drops
to only 40%, the qRFC queues are getting longer and longer.
Analysis
As expected, the performance monitoring of the Runtime Workbench shows
increasing queuing times for the respective messages. A selection from the PMI
(Process Monitoring Infrastructure) source shows no problems of note on the Java
side for the file adapter.
The customer looks at the statistical records, selected for the specific RFC
destination for this Java Engine and sees that the connection times increase
considerably over time. The customer suspects a problem on the Java Engine side
concerning the RFC connections. The customer starts SAP NetWeaver Administrator
and looks for the number of RFC connections under Configuration Management 
Infrastructure  JCo RFC Provider -> Select the Program ID AI_RUNTIME* 
Server Count and increases the value from 5 to 20.
278
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
Five connections were obviously insufficient to handle the massive requests for
mapping at peak times. Too few registered mapping threads meant that the
outbound queues become blocked every time a message was waiting for a free
mapping request.
21.1.3 CPU Overload Due to Java Garbage Collection:
Performance Analysis Under Load Conditions
Description
A customer experiences the following problem: the customer sends approximately
40,000 messages from a business system to a file adapter between 10 and 11 a.m.
by using the Integration Server. These messages have to be delivered within one
hour, in other words, by 12 p.m. at the latest. However, by 12 p.m. half of the
messages are still missing in the file system.
Execution
By looking at the aggregated throughput of the performance monitoring of the
Runtime Workbench, the customer finds increasing latencies for the processed
messages.
A further analysis of the aggregated detail data shows that the sending step is
requiring more and more time.
Analysis
The customer first increases the number of qRFC queues from 5 to 20. However,
this makes the performance even worse.
The customer‟s second thought concerns the Adapter Engine and so he initiates an
output of the garbage collector of this Adapter Engine (requires a restart for the new
settings to take effect).
February 2011
279
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
Under load conditions, the garbage collector becomes highly active, consuming a
large amount of processing resources. The solution is to adjust the JVM parameter
MaxHeapSize, which was fairly low with only 512 MB to 2GB.
280
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
22 Integration of SAP Applications
Information About Integration of SAP Applications
Problem
You need more information about the integration of SAP applications (for example
MDM) with PI.
Solution
PI is often used for the integration of other SAP applications, for example MDM and
SRM. More information about configuration can be found in the integration guides
provided by the respective applications.
As almost all SAP applications are integrated using the PI proxy framework, see the
ABAP Proxy section for more information about troubleshooting and common errors
such as missing SLD entries, incorrect configuration of pipeline URL, unregistered
qRFC queues, and so on.
February 2011
281
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
23 Appendix
Useful Transactions for Troubleshooting
Here is some information about transactions for troubleshooting and where to find
basic information about your system:
SM21 – System log: Contains information about all errors that occurred in the ABAP
part of the system, for example dumps, deadlocks, work process restarts, and so on.
To download the system log entries, choose System log  Download.
ST22 – Dump analysis: Contains information about the ABAP dumps that occurred
in the system. To download the dump, choose System  List  Save.
SM50 – Work process overview: In this transaction you can see how many work
processes are available and what they are doing at the moment. You can activate
the trace for the work processes by choosing Process  Trace  Active
Components. To view the trace, choose Process  Trace  Display File. The trace
is written to the dev_w<x> file, this file can also be found in the operating system
directory \usr\sap\<SID>\DVEBMGS<System number>\work. Deactivate the trace by
choosing Process  Trace  Active Components  Default Values.
ST11 – Error log files: Contains trace files for the ABAP and Java part of the
system. Sometimes not all files are displayed. You can use transaction AL11 and
select the DIR_HOME directory to see all files within the work directory. The files are
in the operating system directory \usr\sap\<SID>\DVEBMGS<System number>\work.
SMICM – ICM monitor: The ICM monitor shows the status of the ICM and the
available threads. For more information about the ICM, see SAP Note 634006 - ICM
messages explanatory note.
Logs and Traces
Here is some information about important logs and traces for the PI system:
The most important logs can be found in the directory
\usr\sap\<SID>\DVEBMGS<System_number>\work\:
dev_w<x>:
Work process trace
dev_rfc<x>:
RFC traces
dev_icm:
ICM trace
dev_disp:
Dispatcher trace
282
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide
dev_ms:
Message server trace
dev_server<x>:
Java server trace
dev_deployment:
Deployment trace
std_server<x>.out:
Java server log
std_deployment.out:
Deployment log
log_bootstrap
Bootstrap log
Logs and traces for the Java Engine and Java applications can be found in the
operating system directory:
\usr\sap\<SID>\DVEBMGS<system_number>\j2ee\cluster\server<x>\log.
Use the Java Log Viewer to check these logs and traces.
SAP NetWeaver Support Service
Problem
You are concerned about the technical risks of your IT solutions involving your PI
system. Would you like to assess and compare your IT solution performance? Do
you need help to identify and reduce risks in technical implementations and
subsequent operations?
Solution
SAP Safeguarding is a portfolio of assessments, tools, and services that reduces
technical risk and costs in implementation, upgrade, migration, and operations of
your IT landscape. SAP Safeguarding services can help you manage your core
business processes and provide you with a risk management and service plan. Any
stage of an IT project can provide challenges. Whether you are planning an
implementation, running your operations, or are in the midst of a migration or an
upgrade, you must consider the various factors that affect the success of your
project.
We always recommend that your PI system is checked before you go live with our
remote service “GoingLive Check”. The SAP GoingLive check helps you manage
technical risks to ensure optimal performance, availability, and maintainability of your
SAP solution. It is best used during a new implementation or when you experience a
significant increase of data and/or user volume (for PI: message volume).
It proactively analyzes your core business processes within your solution landscape
to guide you to a smooth start of production and technically robust operations
afterwards.
Onsite services are offered for different types of areas, for enabling as well as
optimization with regard to Business Process Optimization, Volume Test
Optimization, System Administration, and Interface Management.
February 2011
283
SAP NetWeaver 7.3.1 – Process Integration Troubleshooting Guide
SAP Safeguarding offers the following services for your SAP NetWeaver
Implementation: http://service.sap.com/netweaverservices
For a detailed description of all available SAP Safeguarding services, see SAP
Service Marketplace at http://service.sap.com/safeguarding.
Checklist for Opening Customer Messages
When you create a customer message at SAP, you must provide all necessary
information. Use the following checklist to collect all information and check if the
necessary remote connections are maintained.
System information

System ID

Patch level
Short description of the scenario

Sender system

Receiver system
Repository objects:

Name, namespace, and software component version of the integration
process

Name, namespace, and software component version of the service interfaces
involved
Directory objects:

Name of the scenario

Name of the integration process

Name of the involved business systems
Adapter-specific information:

For the necessary adapter-specific information, see SAP Note 854536 - XI
3.0 / PI 7.0 AF: Information Required by SAP Support.
BPE specific information:
284
December 2011
SAP NetWeaver 7.30 – Process Integration Troubleshooting Guide

For the necessary BPE-specific information, see the BPE: Prerequisites for
Troubleshooting section.
Runtime information

The affected message GUIDs or a precisely defined time period in which
messages can be found
If possible, a step-by-step description of the problem
Involved logs and traces
System access

For the necessary remote connections, see SAP Note 769478 - Remote
Connection with XI Systems.

User/password to be provided in the secure area of the message, see SAP
Note 508140 - Customer Messages - Customer Logon Data.
February 2011
285
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising