Monitoring (ABAP Stack)
Transaction code |
Description |
SXMB_MONI |
Integration engine message monitoring tools. |
SXI_MONITOR |
Message monitor entry. |
SXMB_MONI_BPE |
Integration process monitoring tools for Business Processing Engine (BPE) / ccBPM. |
SXMS_LMS_ CONF |
Configuration of user-defined custom search. |
SA38 SXMS_ EXTRACT_ MESSAGES |
(Re-)index messages after changing the user-defined custom search parameters. |
SMQ1 |
Monitor outbound message queue. |
SMQ2 |
Monitor inbound message queue. |
SMQR |
Check if queues are registered correctly. |
SM58 |
Transactional RFC monitoring. |
SMICM |
Internet Communication Manager (ICM) monitoring tools. |
SMGW |
SAP Gateway monitoring tools. |
ST06 |
Monitoring of system resources. For checking e.g. database space. |
Monitoring (Java Stack)
Path |
Description |
/pimon Adapter Engine Message Monitor |
AAE message monitoring. |
/pimon Adapter Engine Communication Channel Monitor |
New communication channel monitoring. |
/rwb |
Classic runtime workbench |
/mdt/channelmonitorservlet |
RWB-based channel monitoring. |
/MessagingSystem/monitor/monitor.jsp |
"Classic" message system monitoring. |
/mdt/amtServlet |
Java proxy runtime (JPR) monitoring |
/rwb/sub/cache_monitoring/status_table |
Cache monitoring status. |
/nwa/pi-bcgnd-proc |
Show status of background jobs (e.g. clean-up, ...) |
/nwa/scheduler |
Java scheduler monitoring. |
/AdapterFramework/scheduler/scheduler.jsp |
Pt. I - Java scheduler monitoring (fallback). |
/AdapterFramework/scheduler/monitorscheduler.jsp |
Pt. II - Java scheduler monitoring (fallback). |
/CPACache/monitor.jsp |
CPA cache monitoring. |
/MessagingSystem/monitor/locks.jsp |
View locked messages in Java stack. |
/nwa/logs |
AAE log viewer. |
/nwa/java-sys-reports |
Quick status overview of system logs. |
Paths on the left column, beginning with / have to be appended to the base uri of the PI/PRO system: http(s)://<hostname>:<port>
Administration Tools (Both Stacks)
Path |
Description |
/rep/support/public/LockAdminService |
View and remove ESR object locks. |
/nwa/locks |
View general Java locks. |
/useradmin |
User administration (Java). |
/nwa/identity |
Identity management and user administration. |
/nwa/start-stop |
Starting, stopping and re-starting of Java instances, services and processes. |
/nwa/key-storage |
Certificate handling and keystore administration. (Java) |
/nwa/destinations |
Configure and administrate destionations (e.g. HTTP, IDOC, etc.) in Java stack. |
/BC/VerifyJCE |
Tool to check supported keysize / encryption strength of PI. Needed e.g. for PGP. |
/xpi_inspector |
|
/CPACache/refresh?mode=delta |
Trigger CPA cache delta refresh. |
/CPACache/refresh?mode=full |
Trigger CPA cache full refresh. |
/ftpjdbc |
JDBC-, FTP- and XML-Parser test tools. Can be used to show JDBC driver version for example. (You need note 1085539.) |
Transaction code |
Description |
SU01 |
User administration (ABAP). |
STRUST |
Certificate handling and keystore administration. (ABAP) |
SM59 |
Configure and administrate destionations (e.g. HTTP, IDOC, etc.) in ABAP stack. |
SLDCHECK |
Test SLD connection. |
SLDAPICUST |
Configure SLD connection. |
SXMB_ADM |
Administration of Integration Engine. |
Paths on the left column, beginning with /, have to be appended to the base uri of the PI/PRO system: http(s)://<hostname>:<port>
Useful Reports (ABAP Stack)
Transaction code |
Description |
SXMS_EXTRACT_MESSAGES |
Re-indexes messages for user-defined custom search. |
RSXMB_CANCEL_NO_COMMIT_MSG |
Cancel non-restartable messages. |
RSXMB_CANCEL_NOT_REST_MESSAGES |
Cancel messages which are missing their commit
. |
RSBDCOS0 |
Execute a system command (OS level). |
RSPARAM |
Show profile parameters. |
Be aware: If you are not sure how the programs behave, you should open them first in SE38
or SE80
and check their source code. Only run them directly via SA38
if you know, what you are doing!
Configure system proxy (Both Stacks)
Stack |
How to |
Java |
|
ABAP |
Check & Configure:Open transaction SICF
and press F8
. Go to the Client-menu entry and then select Proxy-Settings. |
Readout Passwords (Both Stacks)
Passwords from SAP PI usersThere is no universal way to grab passwords from PI users, but as long as there is an interface, sending data to the PI via SOAP or HTTP there is a good chance of getting the password. Even here you have two options: Open the receiving SOAP sender channel in the Integration Directory/NWDS. Switch to the Modules-tab and add a parameter to the adapter's own module with the following values: Parameter Name= TraceHTTP
, Parameter Value= plain
. The resulting logs with all header data can be found in /nwa/logs. Search for the Authorization:
-header which should contain the user's password as Base64 string. If the adaptermodule isn't available, you could trace the incoming requests with /xpi_inspector. After creating the traces, search for the Authorization
-header as explained above. |
NWDS Lifesaver
Where can I get NWDS 7.5 quick and easy?
|
NWDS doesn't start and does not show anything while opening. The NWDS can't find a suitable JRE/JDK. Add the -vm
-paramter into the NWDS .ini-file.
|
NWDS throws an exception during the startup and then closes again. NWDS needs a 32-bit (x86) jdk. (Even if your Windows installation is x64!)
|
NWDS complains about a wrong JDK (non-SAP) version. Either click "cancel" and simply ignore the error or search in OneNote for the "JVM vendor not supported" article.
|
NWDS crashes with "Unhandled event loop exception - Java heap space" exception. Raise the values Xmx
and XX:MaxPermSize
in the NWDS .ini-file which lays beneath the NWDS-/Eclipse.exe file.
|
How to avoid the annoying re-login dialogs? Open NWDS and follow the menu path: Preferences PI Tools Configuration Tool-Specific Session-Timeout. Raise the timeout value.
|
How to set-up a Java mapping?
|
Using "XPath containing whitespaces" doesn't work. Be sure to just add one XPath by double-clicking. This is necessary to add the namespaces. (You can remove the added XPath after the action.)
|
Adapter Modules (Java Stack)
Module Name |
Description |
General beans |
DynamicConfigurationBean |
Mod.-Name: AF_Modules/DynamicConfigurationBean Used to append, edit or delete entries of the DynamicConfiguration section of the XI3.0 header. |
PayloadSwapBean |
Mod.-Name: AF_Modules/PayloadSwapBean Used to switch the main message payload with an message attachment, defined by the module's parameters. |
PayloadZipBean |
Mod.-Name: AF_Modules/PayloadZipBean Used to zip or unzip a payload. Whn unzipping an archive with multiple files, those will be added as attachments. Pro tip: Use the undocumented parameter gunzip to unzip .gz (GZip) files. |
MessageTransformBean |
Mod.-Name: AF_Modules/MessageTransformBean Used to transform messages, change the XML, add/edit MIME-types, etc. The module can load custom/external Java tranformation classes. |
StrictXml2PlainBean |
Mod.-Name: AF_Modules/StrictXml2PlainBean Used to convert XML payload to plain(text) files. Became obsolete in some way by the MessageTranformBean . |
TextCodepageConversionBean |
Mod.-Name: AF_Modules/TextCodepageConversionBean Used to swap the code page of the main payload of the XI message and also convert its content. |
XiHeaderValidationBean |
Mod.-Name: XiHeaderValidationBean Used to validate header information of outbound messages. |
XMLAnonymizerBean |
Mod.-Name: AF_Modules/XMLAnonymizerBean Used to anonymize XML elements/attributes by removing namespaces or namespace prefixes. Also the encoding attribute of the XML declaration can be changed. |
Sync-Async-Bridge beans |
RequestResponseBean |
Mod.-Name: AF_Modules/RequestResponseBean Used in async-sync bridges to convert the asynchronous request to a synchronous one. Used in combination with RequestOnewayBean. |
RequestOnewayBean |
Mod.-Name: AF_Modules/RequestOnewayBean Used in async-sync bridges to redirect a synchronous response to an sync interface. |
NotifyResponseBean |
Mod.-Name: AF_Modules/NotifyResponseBean Used in sync-async bridges to sent out (create) a response message. |
WaitResponseBean |
Mod.-Name: AF_Modules/WaitResponseBean Used in sync-async bridges to wait for a response message. |
IDOC Handling (Both Stacks)
Path |
Description |
/pimon Adapter Engine IDOC adapter monitor |
IDOC message monitoring. |
/pimon Adapter Engine IDOC adapter monitor Metadata monitor |
Maintenance of IDOC metadata. |
Transaction code |
Description |
IDX_NOALE |
Configuration (including suppression) of IDOC acknowledgements. |
IDX1 |
Maintenance of port configuration. |
IDX2 |
Maintenance of IDOC metadata. |
IDX5 |
IDOC message monitoring. |
WE02 |
Display IDOCs. |
WE05 |
List IDOCs. |
WE20 |
Configure partner agreements. (Mostly done on ERP system side, but nevertheless helpful.) |
To use the Java-stack IDOC monitoring, you need either the NWA_SUPERADMIN_PI_IDOC
or the NWA_READONLY_PI_IDOC
role. If Java-IDOC-monitoring doesn't show any messages, you have to activate it first. Go to /nwa Configuration Infrastructure Application Resources. Then choose "Resource adapters", then "JavaIdocAdapter" and then set the persistance-property to true.
IDOC Setup (Java Stack)
SAP PI to ERP (configuration on PI) Create default IDOC destination in /nwa with name scheme XI_IDOC_DEFAULT_DEST_<SID>_<CLNT>
. After creating the destination check it with the ping destination button. Use this destination in the IDOC receiver channels. |
SAP PI to ERP (configuration on ERP) Create a user for the SAP PI system, which can be used in the SAP PI destination. (As explained above.) Usually this user is named: Z_CPIC
. |
ERP to SAP PI (configuration on PI) You have to create a IDOC-resource-adapter on PI. Go to /nwa Configuration Infrastructure Application Resources. Click Create New Resource New Resource Adapter. Choose SAPJRATemplate and name the adapter like this: inboundRA_<SID>_<CLNT>
. Define the values for ProgramId, GatewayServer and GatewayService in the resource adapter's properties. Afterwards give those values to the ERP administrator. Use this resource adapter in the IDOC sender channels. |
ERP to SAP PI (configuration on ERP) Open transaction SM59
and create a destination of type T
. Set the fields ProgramId, GatewayServer and GatewayService with the values received from the SAP PI administrator. Activate Unicode in the destination's settings. Use the newly configured destination in the partner agreement/ALE configuration in transaction WE20
. |
Fight Timeouts (Both Stacks)
Where / What |
How to set? |
Soap-Adapter | Sender |
Open channel. Add parameter to the adapter's own module at the module tab. If Module Name is CallSapAdapter
name the parameter syncTimeout
. If Module Name is ...XISOAPAdapterBean
then name the parameter XI.Timeout
. Give the timeout in milliseconds as parameter value. |
Soap-Adapter | Receiver |
Open channel. Add parameter to the adapter's own module at the module tab. Use XMBWS.Timeout
as parameter name and set the timeout in milliseconds as parameter value. |
JDBC-Adapter | Receiver |
There are two points to configure timeout: 1 - module tab, 2 - Advanced Mode parameters. 1) Switch to module tab, add a paramter-set to the adapter's own module. Use syncTimeout
as parameter name and set the timeout in milliseconds as parameter value. 2) Switch to Advanced-tab, check Advanced Mode and add the following two parameters to the Additional Parameters-table: queryTimeout
with timeout in seconds (e.g. 600
for 10 minutes). sqlquerytimeout
with timeout in seconds (e.g. 600
for 10 minutes). |
Adapter Engine | Sender |
Introduction: Useful for sync ABAP proxy interface from ERP to Single Stack. SOAP Sender timeout only configures how long the sender channel will wait for response from PI pipeline. To define how long the SOAP sender channel will keep the connection to the sending ERP/ABAP proxy open, you can use the following setup.Go to /nwa Configuration Infrastructure Java System Properties Services. Choose the entry XPI Adapter: XI
, switch to its Properties
-tab and set the timeout in milliseconds for the parameter named xiadapter.inbound.timeout.default
. Be careful this affects all incoming synchronous SOAP/XI communication! To trigger the new parameter, restart the adapter. Therefore go to /nwa Operations Systems Start &Stop Java Services. Select XPI Adapter: XI
and click restart-button. |
Integration Engine | Receiver |
Introduction: If you're sending data from Integration Engine or ERP, etc. systems, usually the default ICM timeout is used. You have two options to raise this timeout.1) Open transaction sm59
, open the appropriate destination, switch to the Special Options-tab and configure the Set timeout
option. 2) Raise the global ICM timeout by opening transaction RZ11
, then open the parameter icm/conn_timeout
and change its value. In addition open the RZ11-parameter icm/server_port_<xx>
and set the parameter TIMEOUT=<timeout in s>
. Attention: This change is system-wide and needs a restart of the ABAP-stack afterwards. |
Integration Engine | Processing |
Introduction: Besides network timeouts also processing timeouts can occur when processing in IE/AAE takes longer than configured.To raise the global ICM processing timeout, open transaction RZ11
, then open the parameter icm/server_port_<xx>
and append the following value-pair to its parameter PROCTIMEOUT=<timeout in s>
. Attention: This change is system-wide and needs a restart of the ABAP-stack afterwards. Learn more over here: https://goo.gl/Sh5Jfp Hint: *If you want to test this changes without restart, you can make them temporary (until next restart) by opening transaction smicm
, opening "Services" ( Shift+F1
) and doing the changes there. |
Tools to rocket your productivity
Realcore Developer Suite for PI/PO: Helps to compare ESR object or create mapping or interface documentations. Available via SAP Appstore or Realcore Sales Team. |
Realcore Support Tools for PI/PO: Helps to quickly create support/error mails with payload attachments, download payloads to disk, solve SSL errors and much more. Available via Realcore Sales Team. |
SoapUI: Useful for SOAP webservice testing and for creation of SOAP/REST webservices (=mockup services). Choose OpenSource/Community edition. https://goo.gl/qD42Z9 |
|
|
Notepad++ (+ XML Tools): The XML swissknife/editor. Go to plugin manager and install "XML Tools". https://goo.gl/zAsd4N |
Fiddler: Sniffing proxy to view raw HTTP requests. Is even able to decrypt and view HTTPS traffic. Useful for analysis. https://goo.gl/rSWeFA |
Helpful Resources
Note: The entries above contain links to helpful web-resources. For better readability all links were shortened.
|
Created By
https://www.linkedin.com/in/raffael-herrmann
Metadata
Comments
No comments yet. Add yours below!
Add a Comment
Related Cheat Sheets