Configuration Files and Locations

After installing Hub, the Configuration Directory will contain:

Sub-directories for storing files created by the IBM i Configuration Tool.
Files and directories, the contents of which can be altered to configure Hub. These are listed below.

When Hub runs, then files that are not intended to be manually edited are also created:

A runstate.json file will be created in the Configuration Directory. It is used by Hub to monitor the state of its pipelines.
Configurations created by the IBM i Configuration Tool are stored in the Configuration Directory.

Files and Directories with Content Intended to be Edited


Content	File/Directory	Purpose
ihubmain.json	File	Holds the configuration parameters for the Hub application.
kafka.json	File	Holds the configuration parameters for a kafka target.
logsettings.json	File	Holds the parameters for configuring the log files generated by Hub.
ui_logsettings.json	File	Holds the parameters for configuring the log files generated by the Hub configuration tool.
portal_logsettings.json	File	Holds the parameters for configuring the log files generated by Hub portal
pipeline	Directory	Contains the configuration files used to define Hub pipelines.
target	Directory	Contains the configuration files used to define Hub targets.
process	Directory	Contains the configuration files used to define Hub processes.
source	Directory	Contains the configuration files used to define Hub sources.

The Hub configuration files consist of JSON - that is sets of key/value pairs. The case sensitivity rules are as follows:

The keys are not case sensitive.
The values are generally case sensitive. Specifically:
- Values that are constrained to a small finite set are case sensitive. For example, in a Pipeline file the "FromType" field must be either "Source" or "Process."
- Any file system paths will be case sensitive on Linux, but not on Windows.
- Any Boolean values are case sensitive and must be entirely in lower case - that is "true" or "false."