IBM Support

InfoSphere Information Governance Catalog: Manually Capturing OMD XML Files

Product documentation


Since IBM InfoSphere Information Server version 11.3, there is a background process (daemon) called "OMDMonApp" on the DataStage Engine that does the following tasks:
* Monitors the folder IBM/InformationServer/Server/DSOMD/xml, where the DataStage Engine places OMD XML files.
* Reads each XML file there one-by-one, enriches it, and sends it to InfoSphere Information Governance Catalog for persisting OMD in the metadata repository and for data lineage.
* When successful, the XML file gets deleted from the folder. Otherwise, ".reject" gets appended to the file name.

You might need to collect the XML files in the following cases:
* When researching problems in operational lineage, even when the above process claims 'success' and deletes them.
* In multi-lake scenarios, where OMD from multiple engines need to be copied to a central lineage server.
* When the active DataStage service layer and the IGC server are installed separately.

There is an option to capture both the XML that is produced by the InfoSphere DataStage Engine as well as the XML that is enriched and transferred to InfoSphere Information Governance Catalog (if not rejected).


How to preserve OMD XMLs

  1. In a command-line window on the services tier, go to the directory IBM/InformationServer/Server/DSOMD.
  2. Open the file omdmonapp.config.
  3. Remove the comment sign for the appropriate properties. For example:
    • OMDXMLBackupEnabled=1

      This property is for OMD XML as it arrives from the InfoSphere DataStage engine.
      Instead of deleting the file, this property will append ".bak" to the file name.
    • OMDFlowBackupEnabled=1

      This property is for OMD Flow XML as it gets enriched and passed to InfoSphere Information Governance Catalog.
      This property will save the enriched XML, with ".flow" appended to its file name.

How to stop or start the OMDMonApp daemon

  1. Go to the directory IBM/InformationServer/Server/DSOMD/bin.
  2. Do any of the following commands:
    • To check the status if the daemon runs or not, type -status
      If the status is 0, the OMDMonApp daemon is running. If the status is 1, the daemon is stopped.
    • To stop the daemon, type -stop
    • To start the daemon, type -start

Related information

Document information

More support for: InfoSphere Information Server
Information Governance Catalog

Software version: 11.3,,,, 11.5,

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Reference #: 7048248

Modified date: 25 October 2016

Translate this page: