InfoSphere Information Governance Catalog: How to increase or decrease the number of displayed nodes in the lineage report graph

-

Question

How can I increase or decrease the number of nodes that are displayed in the lineage report graph?

Cause

InfoSphere Information Governance Catalog has a default limit for maximum visible nodes of 500. Although this number is appropriate for many use cases, it can be configured to meet the needs of your enterprise. Factors in choosing the suitable value are consumability and performance.

Answer

Use Case #1: Too many nodes in the graph make it difficult to track the data flow

First, consider using data lineage filters to hide uninteresting nodes so that the graph becomes more compact.
Alternatively, lower the number of maximum visible nodes. When that number is reached, the graph branches are truncated. You can resume lineage from any truncated node by clicking the arrow symbol on top of that node.

Use Case #2: The graph is truncated too early and I do not see enough nodes

First, look at using data lineage filters to hide uninteresting nodes, so that you see more of the graph overall.

A second option is to resume lineage from any truncated node by clicking the arrow symbol on top of that node.

A third option is to raise the threshold of maximum visible nodes.

Warning

Raising the maximum visible nodes limit beyond 1000 (one thousand) might impact performance:

  • It will take the server longer to lay out the graph, thus increasing the response time before the graph is displayed.
  • The browser client might become less responsive while panning or zooming the graph after it is displayed.


Procedure to change the number of displayed nodes

1. In the command shell, go to installation_directory\ASBServer\bin directory, where installation_directory is the directory where InfoSphere Information Server was installed.


    Operating system Installation directory
    Microsoft Windows C:\IBM\InformationServer
    UNIX /opt/IBM/InformationServer
2. Run the command to allocate number_of_nodes, where number_of_nodes is the maximum number of nodes to display in reports.


    Operating system Search results to display
    Microsoft Windows iisAdmin.bat -set -key com.ibm.iis.gov.vr.setting.maxVisibleGraphNodes -value number_of_nodes
    UNIX iisAdmin.sh -set -key com.ibm.iis.gov.vr.setting.maxVisibleGraphNodes -value number_of_nodes

    It is not necessary to restart WebSphere Application Server, but it might take a minute or so before subsequently requested reports pick up the change.

--
Thank You.

Regards,
Guru





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