JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 9.0p0 Hot Tips | CONFIDENTIAL | CodeSecure Inc |
The hub process is called cshub.exe on Windows systems, cshub otherwise. It runs in parallel, with one hub master process and up to 10 hub slaves. (This limit can be changed from the HTTP tab of the Settings page.)
| hub master |
A hub master is responsible for starting and stopping slaves,
and for logging.
Each hub master (along with its slaves) is associated with exactly one hub database. This association is set at the time that the hub is started, and cannot change while the hub process is running. Likewise, a hub database can be associated with at most one hub master at a time. |
|---|---|
| hub slave | The "unit of work" for a hub slave is a single HTTP connection, which can involve interacting with the hub database and with the analysis master. If a slave is connected to an HTTP client it is "busy", otherwise it is "idle". |
We recommend setting up your system so that the hub master is restarted at system startup.
| Windows | On Windows systems the hub can be run as a service, in which case Windows will restart the hub when the system starts up. For more information, see CodeSonar as a Windows Service. |
|---|---|
| Other Systems |
Arrange for a codesonar hub-start
command to be run at system startup. The exact mechanism used
to accomplish this will depend on the tools and commands
available on your system. Read your system documentation or
consult your system administrator for information and
instructions. Good candidates include
|