To load a configuration file on an InfoHub from the shell, execute a command like:
$ $gtm_dist/mumps -run InfoHub --action=configure --file=<ConfigFileName> [--verbose[=filename]]
--file specifies the relative or absolute path to the location of the base InfoHub Configuration File.
--gbldir specifies the absolute path to the location of the global directory for InfoHub.
--verbose enables verbose output. If you specify --verbose=filename it sends the output to the specified file; --verbose alone sends the output to stdout. Use this option to debug configuration errors.
Attempting to configure a file that can't be opened for reading, or is defective, produces an IHBADFILE error. Attempting to configure an InfoHub with an improperly installed gtmposix plug-in may produce an IHGETTIMEFAIL error.
To load a configuration file on InfoHub from within GT.M, invoke the following entry point in the InfoHub API as an extrinsic function:
If the configuration file contains an InfoHub descriptor, the InfoHubID is optional and, if supplied, must match the one in the descriptor.
As IDs, and possibly Names, may have meaning for tools that report on ^InfoHubInfo data, the Infohub configuration processing rejects attempts to change the association between an ID and a Name. A user with sufficient understanding of, and access to, the InfoHub database can change such associations programmatically using GT.M code.
$ $gtm_dist/mumps -run InfoHub --action=configure --file=samples/SimpleMonitor.conf
This example uses the CLI for InfoHub to load an InfoHub Configuration File.
This example loads the server1.conf Configuration File on InfoHub.
GTM>if $$configure^InfoHub("","samples/SimpleMonitor.conf") Loading the configuration file samples/SimpleMonitor.conf GTM>if $$configure^InfoHub("","samples/SimpleMonitor.conf") Loading the configuration file samples/SimpleMonitor.conf Configuration unchanged GTM>
This example attempts to load the same SimpleMonitor.conf twice using 7421 as the InfoHub ID.