Dr.

Julia Hambrock Active Global Support

Admin Check
A compilation of daily and weekly checks for the Exchange Infrastructure 3.0
05. Oktober 2005

XI Admin Check

Content:
1 Introduction.....................................................................................................................3 2 Daily Checks ...................................................................................................................4
2.1 Message monitoring ...................................................................................................................................4 2.1.1 XML messages on the Integration Server and Integration Engines.........................................................4 2.1.2 XML messages of the central and decentral Adapter Framework ...........................................................5 2.1.3 XML messages of the Partner Connectivity Kit (PCK) .............................................................................5 2.1.4 Combined monitoring of XML messages in the Integration Server, Integration Engines and Adapter Frameworks ( SPS12) ............................................................................................................................6 2.2 Adapter Monitoring .....................................................................................................................................6 2.2.1 Adapters on the central and decentral Adapter Framework ....................................................................6 2.2.2 Adapters in the PCK .................................................................................................................................7 2.2.3 Adapters on the Integration Server: IDoc Adapter ...................................................................................8 2.2.4 Adapters on the standalone J2SE Engine ...............................................................................................9 2.3 ccBPM Monitoring.....................................................................................................................................10 2.3.1 Monitoring of ccBPM processes.............................................................................................................10 2.3.2 Sync-Async Bridge .................................................................................................................................11 2.4 IDoc Packaging Monitoring......................................................................................................................12 2.5 ICM Monitoring ..........................................................................................................................................13 2.6 Gateway Monitoring..................................................................................................................................14 2.7 Queue Monitoring .....................................................................................................................................15 2.8 Job monitoring of housekeeping jobs....................................................................................................16 2.8.1 Jobs with a fixed job name .....................................................................................................................16 2.8.2 Jobs with a fixed ABAP program name..................................................................................................16 2.9 J2EE Monitoring........................................................................................................................................17 2.9.1 Monitoring exceptions and memory problems .......................................................................................17 2.9.2 Monitoring thread shortage ....................................................................................................................17 2.9.3 Monitoring memory consumption ...........................................................................................................18 2.10 Simple Performance Monitoring......................................................................................................19 2.10.1 Monitoring the overall performance.................................................................................................19 2.10.2 Monitoring the performance of specific (important) interfaces........................................................20 2.10.3 Monitoring System Performance.....................................................................................................23

3 Weekly checks ..............................................................................................................24
3.1 Number of entries in the tables used at runtime ...................................................................................24

Page

2

It is not only meant to detect problems in an early stage. provide. Integration Directory. respectively. This XI Admin Check focuses on the proactive monitoring that should help administrators in their daily and weekly tasks. Integration Server. The XI Admin Check does not include the following topics: CCMS and Alerting. Integration Repository.XI Admin Check 1 Introduction The SAP Exchange Infrastructure consists of the following functional components: Integration Builder. The communication and accessibility of these components can be checked using the XI Readiness Check (SAP Note 817920). Page 3 . Business Process Engine. The second. Adapter Engine. The checks of the XI Admin Check are structured into 2 groups: the first and main group describes daily tasks to be carried out on the Integration Server ABAP as well as on the J2EE Engine. the Readiness Check points at errors in and between the tools that might lead to errors in exchanged messages later on. much smaller group. Alerting) as well as proactive monitoring. but it does not specifically monitor an XI system for erroneous messages or performance problems. but seeks to provide a feeling for the system regarding its technical KPIs (Key Performance Indicators) and regarding critical technical steps in the runtime message processing. describes tasks that should be carried out on a weekly or monthly basis. These areas are expected to be already used for reactive monitoring. Integration Engine. Used daily it should help the administrator to make a statement regarding the health status of the XI system as well as enable him to analyze specific problems within the processing of a message. It is assumed that you have set up the automatic email / SMS alert for the functionalities that the CCMS and the Alerting. However. The administration of an XI system contains reactive monitoring (CCMS. Runtime Workbench (RWB) and System Landscape Directory (SLD).

In the fields for Day/Time enter the previous day (or any other interval that suits your daily work). i.1 XML messages on the Integration Server and Integration Engines Via your SAP GUI go to transaction SXMB_MONI -> Monitor for Processed XML messages. for Web AS 6. have retry mechanisms. Select at least “Message has error status on outbound side” and execute the transaction. use the legend button on the right side of the menu bar (or CTRL + F1). follow the troubleshooting guidelines of your company for messages in error status. it becomes necessary to analyze the underlying problem. Navigate to the column “Outbound Status” and check if problems in the outbound adapters of the Integration Server occurred. There you will find a field called “Outbound Status”. If you find messages in error status. If you are not sure what the symbols mean. You have to restart the selection and use the tab “Advanced Selection Criteria”. the message with only (!) an erroneous outbound adapter status will not be shown.1 Message monitoring Every message that runs into an error in the Adapter Framework and/or the Integration Server Pipeline gets persisted.XI Admin Check 2 Daily Checks 2. Until Support Package Stack (SPS) 12 the messages of the Adapter Framework and the Integration Server have to be monitored via two points of entry: 1) Transaction SXMB_MONI and 2) the Message Monitoring of the Runtime Workbench (RWB) 2. Both. If you have restricted your search to only erroneous messages. Check if there are any other status than the black-white flag. the IS pipeline and the Adapter Framework.40 systems that either send or receive XI messages via ABAP proxies. Try to get a feeling about the type and frequency of errors in your system. Page 4 . Repeat this action for Integration Engines of type “Application System”. but after the retries are done and the error still persists. If your XI machine is processing many messages per day restrict the number of messages via the field “Select Message By” by choosing Status Group “Errors”. In this way it is possible to monitor errors and to restart erroneous messages (asynchronous messages only). e.20 or 6.1.

Check if there are any other status than “successful”. all erroneous messages. go to “Message Monitoring” and select your central Adapter Engine from the drop down menu. Page 5 .1. If you find messages in error status. This will bring up a browser window with a link to the RWB. If you process many messages per day via your Adapter Framework.2 XML messages of the central and decentral Adapter Framework Log into the client of the Integration Server and call transaction SXMB_IFR. e. Repeat this for every decentral Adapter Engine your are using. Click on the link “Message Monitor” and enter an appropriate time interval.3 XML messages of the Partner Connectivity Kit (PCK) Open a browser and call the following URL: http://<host>:50000/pck/start. follow the troubleshooting guidelines of your company for messages in error status. 2.XI Admin Check 2. follow the troubleshooting guidelines of your company for messages in error status. g. If you find messages in error status. Repeat this for every PCK you are using. (50000 is the default port of the PCK. Enter the previous day (or any other interval that suits your daily work) and hit the “Start” button. if you installed the PCK with a different system number it is 5<sysnr>00) Check if there are any other status than “successful”. restrict the selection by the status.1. Once logged in.

Click on the button “Adapter Monitoring”.4 Combined monitoring of XML messages in the Integration Server.1 Adapters on the central and decentral Adapter Framework Procedure Until SP9: Open a browser window and call the URL: http://<host>:5<sysnr>00/AdapterFramework/monitor/monitor. display a green light. SOAP Adapter). by running transaction SXMB_IFR and using the link in the browser window) and navigate to “Component Monitoring”. Repeat the selection for decentral adapter engines if used. Log into the client of the Integration Server and call transaction SXMB_IFR. JMS. the general unavailability of adapters may go unnoticed. some of them run on the integration server (IDoc Adapter. go to “Message Monitoring” and select “Integration Server” from the drop down list.XI Admin Check 2. While your alerting framework (when set up) will inform you about failures during message processing. It was introduced in SP4 and extended in each of the subsequent SPs. Payload). Some of them run on the Adapter Framework (typically JDBC.jsp. restrict the selection by the status. 2. 2. Do not choose one of the sub-components (Integration Engine or Adapter Framework) since this will only list messages of one component. If you observe a red light. Repeat the selection for proxy runtimes you are using. Check that the Adapters that are in use. If you process many messages per day.2. Enter the previous day (or any other interval that suits your daily work) and hit the “Start” button. e. all erroneous messages. sorted by namespace. You may also use the J2SE standalone adapter engine or decentral adapter engines. SP9: Log on to the RWB start page (e. follow the troubleshooting guidelines of your company for messages in error status. g. File. Note that the content of this Adapter Monitor varies with the support package of your XI. Check if there are any other status than “successful”. This will bring up a browser window with a link to the RWB. Integration Engines and Adapter Frameworks ( SPS12) Procedure Since SPS 12 it is possible to monitor messages via one point of entry. have a look at the Error messages and inform the respective Application People. Page 6 . Once logged in. that is the Runtime Workbench (RWB).1. g.2 Adapter Monitoring With very few exceptions messages enter and leave the Exchange Infrastructure via adapters. You will see a list of Adapters. Choose display of all components and select the appropriate Adapter Engine. HTTP plain adapter). If you find messages in error status. the navigation to SMQ2 and the possibility to display the message details (Performance Header. You can still use the procedure for <SPS 12 since it offers additional features like for example the outbound adapter status.

Page 7 . If you observe a red light. call the URL http://<host>:50000/pck/start and click on the link „Adapter Monitoring“ (50000 is the default port of the PCK.XI Admin Check 2.2 Adapters in the PCK Procedure Open a browser window. have a look at the Error messages and inform the respective Application People.2. display a green light. if you installed the PCK with a different system number it is 5<sysnr>00). Check that the Adapters that are in use.

and set the user to ‘*’.2. If you find entries.3 Adapters on the Integration Server: IDoc Adapter Procedure Log in to your integration server and call transaction SM58. (The only feature that can be checked is the IDocs received by the XI Integration Server via transaction IDX5. Is the processing fast enough? Page 8 . e. g. If the execution shows many entries. check the Status Text and react as defined by your internal support strategy. For problems with incoming IDocs it is necessary to check the sending systems. hit “Refresh” a few times and check if the Date/Time of the first entry changes.XI Admin Check 2. that means that an empty screen is a good check. but this transaction is mainly used for tracking messages. the last day. not for monitoring). This transaction does not show successful transmissions. Choose an appropriate time interval. This is not the scope of this document. Please note that this transaction only shows outgoing tRFC calls.

XI Admin Check 2. A working adapter without any problems shows a green light. Check the protocol for the error and react to it as described in your internal support guidelines. navigate to the log of this adapter by clicking on the name. Page 9 .2. Check the traffic lights at the end of each line. If you find a red light.4 Adapters on the standalone J2SE Engine Procedure Call the URL of your J2SE Engine: http://<host>:8200 (port 8200 is the default port). The start page already gives you the overview over the adapters.

3. Procedure Log in to your Integration Server. If the transaction returns an empty list there are no errors in the chosen time interval. Select an appropriate time interval (e.1 Monitoring of ccBPM processes ccBPM (cross component Business Process Management) is a new feature of XI 3.3 ccBPM Monitoring 2. but the active alerting of problems is currently restricted (see SAP Note 855865).0 that uses the workflow and runs in the so-called Business Process Engine (BPE). If you see nodes. g. During the post-installation steps a job for the restarting of erroneous Business Processes has been created. last 7 days) and open the tree structure once the transaction has been executed. Page 10 . call transaction SXMB_MONI_BPE and navigate to “Diagnosis Processes with Errors”.. Inform the appropriate users as described in your internal support strategy.XI Admin Check 2. expand the tree and double click on the entries to see the error.

Procedure Log in to your Integration Server.2 Sync-Async Bridge The Sync/Async Bridge (Bridge between synchronous and asynchronous communication) is used if for example a synchronous request needs the information of an asynchronous function module. Page 11 .3. call transaction SXMB_MONI and navigate to “Status Monitor for Sync/Async Communication” (or directly to SXMS_SAMON).XI Admin Check 2. g. e. Technically it is realized via ccBPM. inform the right person or cancel the process. Check if there are messages with the status Error (red light in first column) and react correspondingly. It is not possible to call it directly and thus you have to define a sync/async bridge.

Procedure Log in to your Integration Server and call transaction IDXP. A package that is being processed is marked by a yellow light (Message stopped. waiting in a queue). This is indicated by a red light (Queue stopped due to errors) or a red cross (queue entry missing). By hitting refresh make sure that packages that are currently being worked on. Page 12 . get processed.XI Admin Check 2.4 IDoc Packaging Monitoring IDoc Packaging can be used to collect outbound IDocs and to send them in a package rather than one by one to the receiving system. Check if there are problems with any of the packages. waiting for a package job) or a yellow cube (Message packaged.

Page 13 . Repeat the procedure for every application server you are using. Procedure Log in to your Integration Server and call transaction SMICM. It is responsible for all incoming and outgoing HTTP calls and thus of high importance for the Exchange Infrastructure.5 ICM Monitoring ICM is the Internet Communication Manager.XI Admin Check 2. Check if the ICM Status is Running / green Open the log file (Shift + F5 or GoTo -> Trace File -> Show All) and check for Errors. Check if the Current and Peak numbers for the “Created Worker Threads”. the “Connections Used” and the “Queue Entries Used” is lower than the defined Maximum.

XI Admin Check 2.6 Gateway Monitoring The Exchange Infrastructure mainly uses the gateway of the Web Application Server to communicate with the J2EE Engine. Check for red entries and entries for “Last req” that have an old time stamp. several programs of the J2EE Engine are registered. the program used for mapping requests. At the gateway. Procedure Log in to your Integration Server and call transaction SMGW. Repeat this for Logged on Clients (Navigate to Goto -> Logged on clients) Open the Log File (CTRL + Shift + F10 or Goto -> Trace -> Gateway -> Display File) and check for Errors. Page 14 . Repeat the procedure for every application server you are using. the most important being “AI_RUNTIME_<SID>”.

If you are running ABAP proxies on different clients. Procedure Log in to your Integration Server. react as described by your internal support strategy. An increase of queues and/or entries points at a bottleneck and should be monitored! Select the Alarm Bell (Change View) push button once to see only queues with an error status. enter ‘*’ for the client. Check the number of queues and the number of entries. this points to either a bottleneck or an increase in activity on your XI. Page 15 . In this case your reaction is required. e. If you observe an erroneous status. call transaction SMQ2 and execute. Check the Status of the queues in the new screen.7 Queue Monitoring Queues (qRFC inbound queues) are the core of the Integration Server. the Mapping and the call of the appropriate adapter. Mark the queues and press the button “Display Selection”. Hit refresh a few times to check if the numbers increase / decrease / remain the same. Queues are thus a neuralgic point for the XI: either if they are blocked or if they don’t process fast enough. If the number should increase over a period of time. including the Logical Routing.XI Admin Check 2. Try to get a feeling of how many queues and how many entries your system usually uses. the Technical Routing. i. tuning of the Integration Server. Within queues all messages are processed.

only for Idoc adapter and ccBPM processes) SXMSALERT_PROCESS_DATA_GET (for the alerting framework) Page 16 . It is sufficient to look at one or two of them. only if ccBPM used) SWWERRE (restart of erroneous ccBPM process. If you have used a dedicated user for all housekeeping jobs. enter this user.8 Job monitoring of housekeeping jobs The housekeeping jobs for XI ensure a smoothly running Exchange Infrastructure. 2. only if ccBPM used) 2. For each job have a quick glance at the job log.2 Jobs with a fixed ABAP program name Procedure Log in to your Integration Server and call transaction SM37. If you have used different users. If you have used different users. SAP_BC_XMB_DELETE_<client> (deletion of XML messages if not archived) SAP_BC_XMB_HIST_DELETE_<client> (deletion of history entries) ARV_BC_XMB_WRP<date> (archiving of XML messages if not deleted) ARV_BC_XMB_DEL<date> (deletion of archived XML messages if not deleted) SXMS_DELAYED_MSG_PROC<client> (job for delayed message processing. but also care for performance data and retry mechanisms. only if used) Only if ccBPM used: ARV_WORKITEM_WRP<date> (archiving of work items. Although you have planned them.XI Admin Check 2.1 Jobs with a fixed job name Procedure Log in to your Integration Server and call transaction SM37. enter this user. search for the ABAP program names provided in the following checklist. only if ccBPM used) SWWCLEAR (deletion of job logs. it may happen that during their execution a problem occurs. If you have used a dedicated user for all housekeeping jobs.8. search for the job names provided in the following checklist. only if ccBPM used) ARV_WORKITEM_DEL<date> (deletion of archived work items. They do not only carry out the archiving and deletion. RSWWWIDE (deletion of work items if not archived. only if ccBPM used) SXMS_PF_AGGREGATE (aggregates performance data) SXMS_PF_REORG (reorganizes performance data) SXMS_REFRESH_ADAPTER_STATUS (refresh of outbound adapter status. This is needed because the choice of the job name is free for these jobs. only if ccBPM used) SWWDHEX (monitors deadlines of ccBPM processes. only for ccBPM) RSWF_XI_INSTANCES_DELETE (deletion of archived work items. RSXMB_RESTART_MESSAGES (restart of erroneous.8. asynchronous messages). For each job have a quick glance at the job log.

Was there an out of memory problem shortly before? 2. The purpose of monitoring here is not the availability.…. Search for the strings “Exception”.1. Search for the string “is starting” to find restarts of your J2EE Engine. Also check the maximum value in the lower part of the window and the history.9. The full text looks like: “SAP J2EE Engine Version 6.out (n=0 for the first server node. See also the weekly tasks for GC analysis. you can of course look at the file on OS level.. the application threads and the system threads. Search for the string “Memory” to check if your J2EE Engine had out of memory problems. On the right side navigate first to Kernel -> Application Threads Pool and then to Kernel -> System Threads Pool Check if the ThreadPoolCapacityRate is below 100% for both. n=0.2. It does not only carry out the mapping. investigate the reason for the 2 restart. but the stability and memory consumption. 2.9 J2EE Monitoring The J2EE Engine is as important as the ABAP part of the Exchange Infrastructure during runtime.i if you have i nodes).2 Monitoring thread shortage Procedure Start the Visual Administrator of your J2EE Engine and navigate to Server -> services -> monitoring.”. Navigate to the work folder (DIR_HOME) and open the file std_server<n>. This should occur once per file.XI Admin Check 2. Has the thread usage increased during the last days/weeks? Repeat the Procedure for the Dispatcher and carry out the same check Page 17 . but also hosts the adapters used to receive or send messages.313 is starting. “Error” and “Fatal” to check if any exceptions occurred. Alternatively. If nd you see it more than once.1 Monitoring exceptions and memory problems Procedure Log in to your Integration Server and call transaction AL11.9..40 PatchLevel 95034.

XI Admin Check 2.3 Monitoring memory consumption Procedure Start the Visual Administrator of your J2EE Engine and navigate to Server -> services -> monitoring. On the right side navigate to Services -> Memory Check if the AllocatedMemoryRate is below 100%. Also check the maximum value in the lower part of the window and the history. Has the memory usage increased during the last days/weeks? Page 18 .9.

Leave the display at the default (that is. The aggregation interval of 1 hour gives you the best idea of the throughput and peak times. e. In the browser window follow the link to the Runtime Workbench. Check the number of messages per interval (column “Number”. Please note that you have to plan the respective jobs to see processing times. and not “Rate[msg/h]!).0 msg/hour – although these 4 message might have been processed within 5 seconds. Also..1 Monitoring the overall performance Procedure Log in to your Integration Server and call transaction SXMB_IFR. Identify the peak times and compare them with the last days/weeks: has the number of messages increased? Check the processing time (5 column). Click “Start” to start the selection. In there. choose the display “overview single”.10 Simple Performance Monitoring The health of an XI system can be monitored indirectly by watching the throughput of your messages. g. aggregated overview) and choose an appropriate time interval.10. Do all message have an increased processing time or only a specific interface? th Page 19 . it tells you if your developers or application people have increased the number of messages or added an interface without informing the basis group.XI Admin Check 2. Does the processing time meet your requirements? If it is a lot higher than expected. the last day. click “Performance Monitoring”. enter the time interval in which the processing time was so high and restart your selection. then the throughput will be 4. 2. This can eventually lead to the necessity of adding additional hardware resources to ensure that the KPIs (Key Performance Indicators) are still met. Choose “Free Entry” from the drop down list if you want to use your own time interval. Please also note that the Rate [msg/hour] can be misleading: if 4 messages have been processed within a specific hour.

Check the time difference between the steps.2 Monitoring the performance of specific (important) interfaces This type of monitoring should be used if a specific interface turns out to be very long running and you do not know the reason for it. You will now see in the lower part a split of the processing time into the single steps.10. The total processing time consists of the processing time in the XI Integration Server.. Long “processing” times for these steps could point to a shortage of queues. For this selection you have to enter the details of the specific interface you want to monitor. processing time for the Business Process Engine (if ccBPM is used) as well as processing time in the Adapter Framework (if adapters except IDoc. Page 20 . respectively. e. the last day. g. In there. Procedure for Integration Server processing time Log in to your Integration Server and call transaction SXMB_IFR. It can also be used for highly important interfaces that have a high requirement regarding processing time. click “Performance Monitoring”. because a call to the J2EE Engine from the ABAP pipeline is needed. In the browser window follow the link to the Runtime Workbench. Change the display to “Detailed Data Aggregated” and choose an appropriate time interval.XI Admin Check 2. until a message is finally processed. plain HTTP or proxies are used). Is the DB_ENTRY_QUEUEING or the DB_SPLITTER_QUEUEING taking up the most time? These values simply count the waiting time in inbound and outbound queues. Does any step take longer than during the last days / weeks? Which step takes the longest time? Is it reasonable that this step has a higher processing time? Keep in mind that for example mappings do need a lot more time than a simple Interface Determination.

in the details (front screenshot) it can be seen that the processing in the adapter ends later. and press “display”. click “Message Monitoring”. In the browser window follow the link to the Runtime Workbench. For illustration. please look at the screenshot below: the message has a start time of 18:06:36 and an end time of 18:06:42 (background screenshot). Select one message via the radio button and press “Details” Calculate the difference between the first time stamp and the last time stamp.XI Admin Check Procedure for Adapter Framework processing time Log in to your Integration Server and call transaction SXMB_IFR. However. that is only at 18:06:50. Do the above calculation for the inbound as well as the outbound messages. Which step takes the longest time? Is it the time until a message is retrieved from the queue or rather the processing time in the adapter itself? Has the processing time increased over the last days/weeks? Could that be related to a higher load for the respective interface? Page 21 . choose “Adapter Engine <host>” from the drop down list. Please note that the start and end time (before clicking “Detail”) does not reflect the total processing time in the Adapter Framework. Enter your interface details and “Start” the selection. In there.

navigate to the column “outbound” or “inbound” and click on “PE”. Adjust your selection in a way that you select one or more messages of the respective interface. Which step takes up most of the processing time? Is there a reason for this long processing? Page 22 .XI Admin Check Procedure for ccBPM processing time Log in to your integration server and call transaction SXMB_MONI. Calculate the time difference between the first and the last entry. Once the messages are listed.

i. then navigate to “Detailed Analysis Menu” and check the values “CPU”. Procedure Log in to your Integration Server and call transaction ST06. Snapshot view: Is the idle time at a reasonable value. “Memory”. Previous hours view: try to get a feeling if the CPU and amount of memory were sufficient over the period of a day. However. “SWAP” for the previous hours. Did the values increase during the last days / weeks? Page 23 . it should be mentioned shortly to complete the performance section. around 20% or higher? Snapshot view: Is there considerable paging? Paging can have a negative influence on your J2EE Engine. this can be seen in long GC times as described in the weekly tasks. e. If it does. Take a look at the snapshot that is provided on the entry screen.XI Admin Check 2.10.3 Monitoring System Performance This area is probably already covered by typical basis administration tools / jobs.

you have to check SXMSPHIST2 as well For all tables check if the number of entries remains roughly constant. Procedure Log in to your Integration Server and call transaction SE16. SXMSCLUR / SXMSCLUP (cleaned up by XML message archiving / deletion). In the following screen simply press the button “Number of Entries”. Page 24 . SWWWIHEAD (cleaned up by workitem archiving / deletion). If you use the switch procedure. The most important tables are: SXMSPMAST (cleaned up by XML message archiving / deletion). Enter the table names as listed below and execute.1 Number of entries in the tables used at runtime Some of the tables of the Exchange Infrastructure grow very quickly and can cause severe problems if no archiving / deletion takes place. Furthermore. erroneous messages remain in the database if not handled correctly. This will become visible by regular checking of the number of entries. SXMSPFRAWH and SXMSPFRAWD (cleaned up by the performance jobs).XI Admin Check 3 Weekly checks 3. SXMSPHIST (cleaned up by the deletion of history entries). If you use the switch procedure. you have to check SXMSPMAST2 as well. you have to check SXMSPCLUR2 and SXMSCLUP2 as well. If you use the switch procedure. start troubleshooting why the size of the tables constantly increases. In case the message volume increases the retention times have to be adjusted according to the available database space. If that’s not the case.