Skip to Content

Last week SAP NetWeaver MDM development released a pretty cool new tool called “MDM Info Collector”. It speeds up message processing quite a bit. It’s goal is to make customers’ lives much easier when they face a problem and need to report a SAP customer message

The tool supports MDM 7.1 SP3 and higher – so customers being on this release level can use it immediately for their message creation needs. As a result of discovering a problem with SAP NetWeaver Master Data Management (MDM), the customer would like to send information that is related to his system to SAP Customer Support so that an offline analysis of the problem can be performed.

The new MDM Info Collector can be run either interactively or in a command line mode. The tool creates a snapshot of MDM for offline failure analysis – once it’s finished its work, a zip file containing all collected information (e.g. INI-files, logs, repository data and so on) has been created and can then be attached to the customer message. This “one step” information collection saves a lot of time on both sides (customer and SAP) for the message processing – SAP immediately has all the initial information to start analyzing the problem.

In the SAP Note 1522125 there are download instructions for the software itself plus a How-To Guide describing how to set it up. Configuration is fairly simple and doesn’t require more than one screen to make the required settings for the collector (see below).

Configuration screen of the Info Collector 

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Mike Malloy
    Any idea how to fix this error I keep getting?

    ‘Collecting Wily Introscope agent log files…Not executed. Reason: Could not find SMD agent using port: 59818 ‘

    (0) 
    1. Klaus David Post author
      The good news is that this isn;t an error.

      The “Not executed” means the tool “skipped” the collection of this info.

      The possible reasons are:
      If the SMD (Wily Introscope) agent is not installed on your machine, this can be expected behavior. If it is installed, check that the SMD service is running and that the value of the SMD Agent port in the MDM configuration file for the SMD Agent is correct (for example: C:\usr\sap\MDM\MDS00\config\ncs.conf file with the line agent_port=59718).

      (0) 
  2. Varun Dikshit
    Klaus, thanks for sharing info about this seemingly useful tool.
    Can I recommend you to alter the title to use “OSS/CSN message” since “..speeds up message processing dramatically..” can be mistook as MDM-XI/PI message processing unless someone reads through the blog content 🙂
    (0) 

Leave a Reply