XI AdminCheck Version1

7/28/2019 XI AdminCheck Version1

http://slidepdf.com/reader/full/xi-admincheck-version1 1/24

Dr. Julia Hambrock

Active Global Support

Admin CheckA compilation of daily and weekly checks for theExchange 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



XI Admin Check

1 IntroductionThe SAP Exchange Infrastructure consists of the following functional components: Integration Builder,Integration Repository, Integration Directory, Integration Server, Integration Engine, Business ProcessEngine, Adapter Engine, Runtime Workbench (RWB) and System Landscape Directory (SLD).

The communication and accessibility of these components can be checked using the XI Readiness Check (SAP Note 817920). However, the Readiness Check points at errors in and between the tools that might leadto errors in exchanged messages later on, but it does not specifically monitor an XI system for erroneous

messages or performance problems.

The administration of an XI system contains reactive monitoring (CCMS, Alerting) as well as proactivemonitoring. This XI Admin Check focuses on the proactive monitoring that should help administrators intheir daily and weekly tasks. It is not only meant to detect problems in an early stage, but seeks to provide afeeling for the system regarding its technical KPIs (Key Performance Indicators) and regarding criticaltechnical steps in the runtime message processing. Used daily it should help the administrator to make astatement regarding the health status of the XI system as well as enable him to analyze specific problemswithin the processing of a message.

The XI Admin Check does not include the following topics: CCMS and Alerting. These areas are expectedto be already used for reactive monitoring. It is assumed that you have set up the automatic email / SMSalert for the functionalities that the CCMS and the Alerting, respectively, provide.

The checks of the XI Admin Check are structured into 2 groups: the first and main group describes dailytasks to be carried out on the Integration Server ABAP as well as on the J2EE Engine. The second, muchsmaller group, describes tasks that should be carried out on a weekly or monthly basis.



XI Admin Check

2 Daily Checks

2.1 Message monitoring

Every message that runs into an error in the Adapter Framework and/or the Integration Server Pipeline getspersisted. In this way it is possible to monitor errors and to restart erroneous messages (asynchronousmessages only). Both, the IS pipeline and the Adapter Framework, have retry mechanisms, but after theretries are done and the error still persists, it becomes necessary to analyze the underlying problem.

Until Support Package Stack (SPS) 12 the messages of the Adapter Framework and the Integration Serverhave to be monitored via two points of entry:

1) Transaction SXMB_MONI and

2) the Message Monitoring of the Runtime Workbench (RWB)

2.1.1 XML messages on the Integration Server and Integration Engines

Via your SAP GUI go to transaction SXMB_MONI -> Monitor for Processed XML messages. In the fields forDay/Time enter the previous day (or any other interval that suits your daily work). If your XI machine isprocessing many messages per day restrict the number of messages via the field “Select Message By” bychoosing Status Group “Errors”.

Check if there are any other status than the black-white flag. If you are not sure what the symbolsmean, use the legend button on the right side of the menu bar (or CTRL + F1).

If you find messages in error status, follow the troubleshooting guidelines of your company formessages in error status.

Navigate to the column “Outbound Status” and check if problems in the outbound adapters of theIntegration Server occurred. If you have restricted your search to only erroneous messages, themessage with only (!) an erroneous outbound adapter status will not be shown. You have to restartthe selection and use the tab “Advanced Selection Criteria”. There you will find a field called“Outbound Status”. Select at least “Message has error status on outbound side” and execute thetransaction.

Try to get a feeling about the type and frequency of errors in your system.

Repeat this action for Integration Engines of type “Application System”, i. e. for Web AS 6.20 or 6.40systems that either send or receive XI messages via ABAP proxies.



XI Admin Check

2.1.2 XML messages of the central and decentral Adapter Framework

Log into the client of the Integration Server and call transaction SXMB_IFR. This will bring up a browserwindow with a link to the RWB. Once logged in, go to “Message Monitoring” and select your central Adapter

Engine from the drop down menu. Enter the previous day (or any other interval that suits your daily work)and hit the “Start” button. If you process many messages per day via your Adapter Framework, restrict theselection by the status, e. g. all erroneous messages.

Check if there are any other status than “successful”.


Repeat this for every decentral Adapter Engine your are using.

2.1.3 XML messages of the Partner Connectivity Kit (PCK)

Open a browser and call the following URL: http://<host>:50000/pck/start. Click on the link “Message

Monitor” and enter an appropriate time interval. (50000 is the default port of the PCK, if you installed the PCKwith a different system number it is 5<sysnr>00)



Repeat this for every PCK you are using.



XI Admin Check

2.1.4 Combined monitoring of XML messages in the Integration Server, IntegrationEngines and Adapter Frameworks ( SPS12)

Procedure

Since SPS 12 it is possible to monitor messages via one point of entry, that is the Runtime Workbench

(RWB). You can still use the procedure for <SPS 12 since it offers additional features like for example theoutbound adapter status, the navigation to SMQ2 and the possibility to display the message details(Performance Header, Payload).Log into the client of the Integration Server and call transaction SXMB_IFR. This will bring up a browserwindow with a link to the RWB. Once logged in, go to “Message Monitoring” and select “Integration Server”from the drop down list. Do not choose one of the sub-components (Integration Engine or AdapterFramework) since this will only list messages of one component. Enter the previous day (or any other intervalthat suits your daily work) and hit the “Start” button. If you process many messages per day, restrict theselection by the status, e. g. all erroneous messages.



Repeat the selection for proxy runtimes you are using.

Repeat the selection for decentral adapter engines if used.

2.2 Adapter Monitoring

With very few exceptions messages enter and leave the Exchange Infrastructure via adapters. Some of themrun on the Adapter Framework (typically JDBC, File, JMS, SOAP Adapter), some of them run on theintegration server (IDoc Adapter, HTTP plain adapter). You may also use the J2SE standalone adapterengine or decentral adapter engines. While your alerting framework (when set up) will inform you aboutfailures during message processing, the general unavailability of adapters may go unnoticed.

2.2.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.jsp. You will see a list of Adapters, sorted bynamespace. SP9: Log on to the RWB start page (e. g. by running transaction SXMB_IFR and using the linkin the browser window) and navigate to “Component Monitoring”. Choose display of all components andselect the appropriate Adapter Engine. Click on the button “Adapter Monitoring”.

Check that the Adapters that are in use, display a green light. If you observe a red light, have a lookat the Error messages and inform the respective Application People. Note that the content of this

Adapter Monitor varies with the support package of your XI. It was introduced in SP4 and extendedin each of the subsequent SPs.



XI Admin Check

2.2.2 Adapters in the PCK

Procedure

Open a browser window, call the URL http://<host>:50000/pck/start and click on the link „Adapter Monitoring“(50000 is the default port of the PCK, if you installed the PCK with a different system number it is5<sysnr>00).

Check that the Adapters that are in use, display a green light. If you observe a red light, have a lookat the Error messages and inform the respective Application People.



XI Admin Check

2.2.3 Adapters on the Integration Server: IDoc Adapter

Procedure

Log in to your integration server and call transaction SM58. Choose an appropriate time interval, e. g. thelast day, and set the user to ‘*’. Please note that this transaction only shows outgoing tRFC calls. For

problems with incoming IDocs it is necessary to check the sending systems. This is not the scope of thisdocument. (The only feature that can be checked is the IDocs received by the XI Integration Server viatransaction IDX5, but this transaction is mainly used for tracking messages, not for monitoring).

This transaction does not show successful transmissions, that means that an empty screen is a goodcheck. If you find entries, check the Status Text and react as defined by your internal supportstrategy.

If the execution shows many entries, hit “Refresh” a few times and check if the Date/Time of the firstentry changes. Is the processing fast enough?



XI Admin Check

2.2.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 alreadygives you the overview over the adapters.

Check the traffic lights at the end of each line. A working adapter without any problems shows agreen light.

If you find a red light, navigate to the log of this adapter by clicking on the name. Check the protocolfor the error and react to it as described in your internal support guidelines.



XI Admin Check

2.3 ccBPM Monitoring

2.3.1 Monitoring of ccBPM processes

ccBPM (cross component Business Process Management) is a new feature of XI 3.0 that uses the workflow

and runs in the so-called Business Process Engine (BPE). During the post-installation steps a job for therestarting of erroneous Business Processes has been created, but the active alerting of problems is currentlyrestricted (see SAP Note 855865).

Procedure

Log in to your Integration Server, call transaction SXMB_MONI_BPE and navigate to “Diagnosis Processeswith Errors”. Select an appropriate time interval (e. g., last 7 days) and open the tree structure once thetransaction has been executed.

If the transaction returns an empty list there are no errors in the chosen time interval.

If you see nodes, expand the tree and double click on the entries to see the error. Inform theappropriate users as described in your internal support strategy.



XI Admin Check

2.3.2 Sync-Async Bridge

The Sync/Async Bridge (Bridge between synchronous and asynchronous communication) is used if forexample a synchronous request needs the information of an asynchronous function module. It is not possibleto call it directly and thus you have to define a sync/async bridge. Technically it is realized via ccBPM.

Procedure Log in to your Integration Server, call transaction SXMB_MONI and navigate to “Status Monitor forSync/Async Communication” (or directly to SXMS_SAMON).

Check if there are messages with the status Error (red light in first column) and reactcorrespondingly, e. g. inform the right person or cancel the process.



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 byone to the receiving system.

Procedure

Log in to your Integration Server and call transaction IDXP.

Check if there are problems with any of the packages. This is indicated by a red light (Queuestopped due to errors) or a red cross (queue entry missing).

By hitting refresh make sure that packages that are currently being worked on, get processed. Apackage that is being processed is marked by a yellow light (Message stopped, waiting for apackage job) or a yellow cube (Message packaged, waiting in a queue).



XI Admin Check

2.5 ICM Monitoring

ICM is the Internet Communication Manager. It is responsible for all incoming and outgoing HTTP calls andthus of high importance for the Exchange Infrastructure.

Procedure

Log in to your Integration Server and call transaction SMICM.

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.

Check if the ICM Status is Running / green

Open the log file (Shift + F5 or GoTo -> Trace File -> Show All) and check for Errors.

Repeat the procedure for every application server you are using.



XI Admin Check

2.6 Gateway Monitoring

The Exchange Infrastructure mainly uses the gateway of the Web Application Server to communicate withthe J2EE Engine. At the gateway, several programs of the J2EE Engine are registered, the most importantbeing “AI_RUNTIME_<SID>”, the program used for mapping requests.

Procedure Log in to your Integration Server and call transaction SMGW.

Check for red entries and entries for “Last req” that have an old time stamp.

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 forErrors.

Repeat the procedure for every application server you are using.



XI Admin Check

2.7 Queue Monitoring

Queues (qRFC inbound queues) are the core of the Integration Server. Within queues all messages areprocessed, including the Logical Routing, the Technical Routing, the Mapping and the call of the appropriateadapter. Queues are thus a neuralgic point for the XI: either if they are blocked or if they don’t process fastenough.

Procedure

Log in to your Integration Server, call transaction SMQ2 and execute. If you are running ABAP proxies ondifferent clients, enter ‘*’ for the client.

Check the number of queues and the number of entries. Hit refresh a few times to check if thenumbers increase / decrease / remain the same. An increase of queues and/or entries points at abottleneck and should be monitored!

Select the Alarm Bell (Change View) push button once to see only queues with an error status.

Mark the queues and press the button “Display Selection”. Check the Status of the queues in thenew screen. If you observe an erroneous status, react as described by your internal support

strategy.

Try to get a feeling of how many queues and how many entries your system usually uses. If thenumber should increase over a period of time, this points to either a bottleneck or an increase inactivity on your XI. In this case your reaction is required, i. e. tuning of the Integration Server.



XI Admin Check

2.8 Job monitoring of housekeeping jobs

The housekeeping jobs for XI ensure a smoothly running Exchange Infrastructure. They do not only carry outthe archiving and deletion, but also care for performance data and retry mechanisms. Although you haveplanned them, it may happen that during their execution a problem occurs.

2.8.1 Jobs with a fixed job name

Procedure

Log in to your Integration Server and call transaction SM37. If you have used a dedicated user for allhousekeeping jobs, enter this user. If you have used different users, search for the job names provided in thefollowing checklist. For each job have a quick glance at the job log.

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, only if used)

Only if ccBPM used:

ARV_WORKITEM_WRP<date> (archiving of work items, only if ccBPM used)

ARV_WORKITEM_DEL<date> (deletion of archived work items, only if ccBPM used)

SWWERRE (restart of erroneous ccBPM process, only if ccBPM used)

SWWDHEX (monitors deadlines of ccBPM processes, only if ccBPM used)

SWWCLEAR (deletion of job logs, only if ccBPM used)

2.8.2 Jobs with a fixed ABAP program name

Procedure

Log in to your Integration Server and call transaction SM37. If you have used a dedicated user for allhousekeeping jobs, enter this user. If you have used different users, search for the ABAP program namesprovided in the following checklist. This is needed because the choice of the job name is free for these jobs.For each job have a quick glance at the job log.

RSXMB_RESTART_MESSAGES (restart of erroneous, asynchronous messages). It is sufficient tolook at one or two of them.

RSWWWIDE (deletion of work items if not archived, only for ccBPM)

RSWF_XI_INSTANCES_DELETE (deletion of archived work items, 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, only for Idoc adapterand ccBPM processes)

SXMSALERT_PROCESS_DATA_GET (for the alerting framework)



XI Admin Check

2.9 J2EE Monitoring

The J2EE Engine is as important as the ABAP part of the Exchange Infrastructure during runtime. It does notonly carry out the mapping, but also hosts the adapters used to receive or send messages. The purpose ofmonitoring here is not the availability, but the stability and memory consumption. See also the weekly tasksfor GC analysis.

2.9.1 Monitoring exceptions and memory problems

Procedure

Log in to your Integration Server and call transaction AL11. Navigate to the work folder (DIR_HOME) andopen the file std_server<n>.out (n=0 for the first server node, n=0,1,2,…,i if you have i nodes). Alternatively,you can of course look at the file on OS level.

Search for the strings “Exception”, “Error” and “Fatal” to check if any exceptions occurred.

Search for the string “Memory” to check if your J2EE Engine had out of memory problems.

Search for the string “is starting” to find restarts of your J2EE Engine. The full text looks like: “SAP

J2EE Engine Version 6.40 PatchLevel 95034.313 is starting...”. This should occur once per file. Ifyou see it more than once, investigate the reason for the 2

ndrestart. Was there an out of memory

problem shortly before?

2.9.2 Monitoring thread shortage

Procedure

Start the Visual Administrator of your J2EE Engine and navigate to Server -> services -> monitoring. On theright side navigate first to Kernel -> Application Threads Pool and then to Kernel -> System Threads Pool

Check if the ThreadPoolCapacityRate is below 100% for both, the application threads and the

system threads. Also check the maximum value in the lower part of the window and the history.

Has the thread usage increased during the last days/weeks?

Repeat the Procedure for the Dispatcher and carry out the same check



XI Admin Check

2.9.3 Monitoring memory consumption

Procedure

Start the Visual Administrator of your J2EE Engine and navigate to Server -> services -> monitoring. On theright side navigate to Services -> Memory

Check if the AllocatedMemoryRate is below 100%. Also check the maximum value in the lower partof the window and the history.

Has the memory usage increased during the last days/weeks?



XI Admin Check

2.10 Simple Performance Monitoring

The health of an XI system can be monitored indirectly by watching the throughput of your messages. Also, ittells you if your developers or application people have increased the number of messages or added aninterface without informing the basis group. This can eventually lead to the necessity of adding additionalhardware resources to ensure that the KPIs (Key Performance Indicators) are still met.

2.10.1 Monitoring the overall performance

Procedure

Log in to your Integration Server and call transaction SXMB_IFR. In the browser window follow the link to theRuntime Workbench. In there, click “Performance Monitoring”. Leave the display at the default (that is,aggregated overview) and choose an appropriate time interval, e. g., the last day. The aggregation interval of1 hour gives you the best idea of the throughput and peak times. Choose “Free Entry” from the drop downlist if you want to use your own time interval. Click “Start” to start the selection. Please note that you have toplan the respective jobs to see processing times. Please also note that the Rate [msg/hour] can bemisleading: if 4 messages have been processed within a specific hour, then the throughput will be 4.0msg/hour – although these 4 message might have been processed within 5 seconds.

Check the number of messages per interval (column “Number”, and not “Rate[msg/h]!). Identify thepeak times and compare them with the last days/weeks: has the number of messages increased?

Check the processing time (5th

column). Does the processing time meet your requirements? If it is alot higher than expected, choose the display “overview single”, enter the time interval in which theprocessing time was so high and restart your selection. Do all message have an increasedprocessing time or only a specific interface?



XI Admin Check

2.10.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 notknow the reason for it. It can also be used for highly important interfaces that have a high requirementregarding processing time. The total processing time consists of the processing time in the XI IntegrationServer, processing time for the Business Process Engine (if ccBPM is used) as well as processing time in

the Adapter Framework (if adapters except IDoc, plain HTTP or proxies are used).

Procedure for Integration Server processing time

Log in to your Integration Server and call transaction SXMB_IFR. In the browser window follow the link to theRuntime Workbench. In there, click “Performance Monitoring”. Change the display to “Detailed DataAggregated” and choose an appropriate time interval, e. g., the last day. For this selection you have to enterthe details of the specific interface you want to monitor.

You will now see in the lower part a split of the processing time into the single steps. Check the timedifference between the steps. 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 InterfaceDetermination, because a call to the J2EE Engine from the ABAP pipeline is needed.

Is the DB_ENTRY_QUEUEING or the DB_SPLITTER_QUEUEING taking up the most time? Thesevalues simply count the waiting time in inbound and outbound queues, respectively, until a messageis finally processed. Long “processing” times for these steps could point to a shortage of queues.



XI Admin Check

Procedure for Adapter Framework processing time

Log in to your Integration Server and call transaction SXMB_IFR. In the browser window follow the link to theRuntime Workbench. In there, click “Message Monitoring”, choose “Adapter Engine <host>” from the dropdown list, and press “display”. Enter your interface details and “Start” the selection. Select one message viathe radio button and press “Details”

Calculate the difference between the first time stamp and the last time stamp. Please note that thestart and end time (before clicking “Detail”) does not reflect the total processing time in the AdapterFramework. For illustration, please look at the screenshot below: the message has a start time of18:06:36 and an end time of 18:06:42 (background screenshot). However, in the details (frontscreenshot) it can be seen that the processing in the adapter ends later, 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 orrather the processing time in the adapter itself?

Has the processing time increased over the last days/weeks? Could that be related to a higher loadfor the respective interface?



XI Admin Check

Procedure for ccBPM processing time

Log in to your integration server and call transaction SXMB_MONI. Adjust your selection in a way that youselect one or more messages of the respective interface. Once the messages are listed, navigate to thecolumn “outbound” or “inbound” and click on “PE”.

Calculate the time difference between the first and the last entry. Which step takes up most of the

processing time? Is there a reason for this long processing?



XI Admin Check

2.10.3 Monitoring System Performance

This area is probably already covered by typical basis administration tools / jobs. However, it should bementioned shortly to complete the performance section.

Procedure

Log in to your Integration Server and call transaction ST06. Take a look at the snapshot that is provided onthe entry screen, then navigate to “Detailed Analysis Menu” and check the values “CPU”, “Memory”, “SWAP”for the previous hours.

Snapshot view: Is the idle time at a reasonable value, i. e. around 20% or higher?

Snapshot view: Is there considerable paging? Paging can have a negative influence on your J2EEEngine. If it does, this can be seen in long GC times as described in the weekly tasks.

Previous hours view: try to get a feeling if the CPU and amount of memory were sufficient over theperiod of a day. Did the values increase during the last days / weeks?



XI Admin Check

3 Weekly checks

3.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 noarchiving / deletion takes place. In case the message volume increases the retention times have to beadjusted according to the available database space. Furthermore, erroneous messages remain in thedatabase if not handled correctly. This will become visible by regular checking of the number of entries.

Procedure

Log in to your Integration Server and call transaction SE16. Enter the table names as listed below andexecute. In the following screen simply press the button “Number of Entries”. The most important tables are:

SXMSPMAST (cleaned up by XML message archiving / deletion). If you use the switch procedure,you have to check SXMSPMAST2 as well.

SXMSCLUR / SXMSCLUP (cleaned up by XML message archiving / deletion). If you use the switchprocedure, you have to check SXMSPCLUR2 and SXMSCLUP2 as well.

SXMSPHIST (cleaned up by the deletion of history entries).

SXMSPFRAWH and SXMSPFRAWD (cleaned up by the performance jobs).

SWWWIHEAD (cleaned up by workitem archiving / deletion). If you use the switch procedure, youhave to check SXMSPHIST2 as well

For all tables check if the number of entries remains roughly constant. If that’s not the case, starttroubleshooting why the size of the tables constantly increases.

XI AdminCheck Version1

Documents

Transcript of XI AdminCheck Version1