Frequently Asked Questions

What are the minimal install instructions?

The following is a list of the basic instructions to get Nodechart up and running;
  1. Install Nodechart in your target database (see install.sql)
  2. Insert a row into NODECHART_NETWORK_METADATA to define a logical network
  3. Create a userid/password protected OracleAS DAD to serve Nodechart
  4. Point a browser to the "<DAD>/nodechart.listCharts" page.
Refer to the Reference Manual for detailed instructions.

[Top]

What browser do I need?

Browsers need to support Scalable Vector Graphics (SVG) 1.1 and also be javascript enabled. Current browsers/combinations that largely support SVG 1.1 are;

  • Firefox 1.5, 2.0
  • Opera 9.10
  • Internet Explorer 7 with the Adobe SVG Viewer (version 3 or 6)
There are some known issues with various browsers. Refer to the Reference manual (and this FAQ) for further details.

[Top]

Charting causes Firefox to lock up!

Mouse over tooltips (annotations), which is enabled by default, has been noted to cause Firefox 1.5, and 2.0, to occasionally freeze. Refer to the Reference Manual "Known issues" for a detailed explanation. There is a Nodechart global parameter that will disable all charting annotations to circumvent this problem.

[Top]

Why can't I add new chart nodes in Firefox?

Adding new chart nodes ("Add Node" popup screen) has been noted to leave the current chart in a status of "processing" and the new nodes do not appear whenever using Firefox 1.5, and 2.0. Refer to the Reference Manual "Known Issues" for a detailed explanation. As a workaround, reload the chart each time after adding new nodes.

[Top]

Menus get displaced after zooming in Opera

Zoom and Navigate functionality, of Nodechart v1.0.0, has been noted not to work correctly in Opera 9.10. There is no current workaround.

[Top]

Why are non-active network nodes displayed?

Nodechart provides Expansion/Search Filtering for node types, nodes costs, link types and link costs. Customised filtering based on other non-key attributes can be achieved by the use of database views. For example, if you are using SDO_NET node and link tables where an ACTIVE column is present you may wish to create database views that perform the desired filtering. Then construct Nodechart networks based on those views.

For example;

    create view MY_ACTIVE_NODES as select * from MY_NODES where ACTIVE='Y';

    create view MY_ACTIVE_LINKS as select * from MY_LINKS where ACTIVE='Y';

    insert into NODECHART_NETWORK_METADATA(NETWORK_ID, 
                                           NETWORK, 
                                           NODE_TABLE_NAME, 
                                           LINK_TABLE_NAME, 
                                           ....)
                                   values (1, 
                                           'My Network', 
                                           'MY_ACTIVE_NODES', 
                                           'MY_ACTIVE_LINKS', 
                                           ....);

  

[Top]

How do I define hierarchical networks?

Nodechart provides Expansion/Search Filtering for node types, nodes costs, link types and link costs. Customised filtering based on other non-key attributes can be achieved by the use of database views. For example, if you are using SDO_NET node and link tables where a LINK_LEVEL column is present you may wish to create multiple database views based on that column values. Then construct Nodechart networks based on those views. That is, a Nodechart network for each custom LINK_LEVEL that you have defined.

For example;


    create view MY_LINKS_LEVEL1 as select * from MY_LINKS where LINK_LEVEL=1;

    create view MY_LINKS_LEVEL2 as select * from MY_LINKS where LINK_LEVEL=2;

    insert into NODECHART_NETWORK_METADATA(NETWORK_ID, 
                                           NETWORK, 
                                           NODE_TABLE_NAME, 
                                           LINK_TABLE_NAME, 
                                           ....)
                                   values (1, 
                                           'My Network - level 1', 
                                           'MY_NODES', 
                                           'MY_LINKS_LEVEL1', 
                                           ....);

    insert into NODECHART_NETWORK_METADATA(NETWORK_ID, 
                                           NETWORK, 
                                           NODE_TABLE_NAME, 
                                           LINK_TABLE_NAME, 
                                           ....)
                                   values (2, 
                                           'My Network - level 2', 
                                           'MY_NODES', 
                                           'MY_LINKS_LEVEL2', 
                                           ....);

  

[Top]

What label actually gets displayed for the links?

This depends upon two things; a) If the metadata LINK_NAME_COLUMN is defined and b) the number of actual network links between any two given nodes. Assuming the metadata LINK_NAME_COLUMN has been defined, then in the case of a single network link between two nodes, the label that is displayed for the links is the value of the underlying metadata LINK_NAME_COLUMN. Otherwise, in the case of multiple network links between two given chart nodes, the sum (count) of the number of network links will be displayed. This is because any number of network links may actually exist between two given nodes and those links will be represented by a single line in the chart. Where the metadata LINK_NAME_COLUMN is not defined then the sum of the network links will always be displayed for all chart links. Sometimes this latter approach is preferable and annotation can be used to reveal the link names.

For example:

    insert into NODECHART_NETWORK_METADATA(....,
                                           LINK_NAME_COLUMN,
                                           LINK_ANNOTATION_EXPR,
                                           ....)
                                   values (....,
                                           NULL,
                                           'LINK_NAME',
                                           ....);
  

[Top]

What is the maximum chart size?

As an approximate guide, Nodechart is best suited to viewing charts of about 4000 nodes or less at a time. Whilst there are no actual limits imposed, browser response times are generally related to the overall number of nodes and links displayed at any one time.

[Top]

Why do charts contain nodes that are not part of the filter settings?

The Expansion/Search Filter settings are applied when an "Expand (filter)" is performed or when a "Search (filter)" is performed. The filter settings do not affect nodes that are already displayed in the chart. Whereas the links in the chart simply represent the network links that exist between the chart nodes.

[Top]


© 2007 Nodechart
Oracle is a trademark of the Oracle Corporation