XPI Inspector -- New Tool to Troubleshoot XI/PI Problems


You might be familiar with Web Diagtool (or Web Trace Collector), which lets you increase trace level on certain components and collects them as a zip file. XPI Inspector is a similar tool specifically designed for troubleshooting problems on XI or PI


XPI Inspector has pre-defined set of examples to make trace collection simpler. Here is the list.

  Example 1   (CPA Cache):
  Example 2   (Module Processor):
  Example 3   (AFW Security):
  Example 4   (TREX):
  Example 5   (SOAP Adapter):
  Example 6   (JDBC Adapter):
  Example 7   (File Adapter):
  Example 8   (Mail Adapter):
  Example 9   (RFC Adapter):
  Example 10  (JMS Adapter)
  Example 11  (Authentication & SSL)
  Example 12  (Performance Monitoring)
  Example 13  (ISpeak Adapters)
  Example 14  (SR & UDDI)
  Example 15  (MarketPlace Adapter)
  Example 16  (BC Adapter)
  Example 17  (Axis Adapter)
  Example 18  (RWB)
  Example 19  (Mapping Runtime)
  Example 20  (HTTP Adapter)
  Example 21  (IDOC Adapter)
  Example 50  (By Channel)
  Example 100 (Custom)

In addition to collecting trace information XPI Inspector can also perform configuration checks. The configuration checks are optional and can be controlled by the option "Collect just traces (do not perform additional checks)". The tool also extracts information that SAP usually asks you when dealing with XI/PI specific OSS messages (example: Component Info). You can also specify if the tool has to collect debug trace on XI messaging system by selecting "Collect debug traces from XI Messaging System".

Download the tool from SAP Note 1514898. After you have deployed the ear file, you can call XPI Inspector from http(s)://<host>:<port>/xpi_inspector to diagnose XI/PI problems.

For more details read how_to_inspect.pdf

Update:
A new version (v3.3) of this tool have been released. Some new examples included are:

- XI Message
- Default Trace
- Performance Problem
- JEE Service
- JEE Application

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are created i
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,
Read more