InfoSphere Information Governance Catalog: log files

-

Question

Where are the log files for IBM InfoSphere Information Governance Catalog found?

Cause

The log file names changed because InfoSphere Information Governance Catalog replaces IBM InfoSphere Business Glossary and IBM InfoSphere Workbench.

Answer

1. On the Services tier:


    a. If running WebSphere Application Server Liberty Profile - in .../IBM/InformationServer/wlp/usr/servers/iis/logs/:

      - igc.log (with any .1, .2, ...)

      - igc-admin-services.log (with any .1, .2, ...)

      - omd-importer.log (with any .1, .2, ...)

      - messages.log   
       // often helps with "unknown errors" in the user interface


    b. If running WebSphere Application Server Network Deployment - in .../IBM/WebSphere/AppServer/profiles/InfoSphere/logs/:

      - igc.log (with any .1, .2, ...)

      - igc-admin-services.log (with any .1, .2, ...)

      - omd-importer.log (with any .1, .2, ...)

      - server1/SystemOut.log (include all versions with timestamps in their names)  
       // often helps with "unknown errors" in the user interface

      - server1/SystemErr.log (include all versions with timestamps in their names)

 

2. On the Engine tier, everything under:

      - C:\IBM\InformationServer\Server\DSOMD\ logs

      - C:\IBM\InformationServer\Server\DSOMD\xml

Log files for istool commands for InfoSphere Information Governance Catalog are found:


For Microsoft Windows operating system environment

C:\Documents and Settings\<username>\istool_workspace\.metadata\.log

    where <username>is the name of the operating system account of the user who runs this command.
For UNIX or Linux operating system environment

<user_home>/ <username>/istool_workspace/.metadata/.log
    where <user_home> is the root directory of all user accounts, and <username>is the name of the operating system account of the user who runs this command.





Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more