Installation: Hub Setup: Hub Configuration

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.

If you access the manual through the hub's Web GUI, the functionality will not be suppressed because the hub is a web server.
Alternatively, your browser may allow you to explicitly disable the security setting that suppresses functionality. See the CodeSonar FAQ for more information.

If you have created a new hub or upgraded an existing hub, this is a good time to inspect the hub configuration and make any required changes.

You can do this while waiting for a signed license to be delivered, or after you have finished the licensing process.

CodeSonar SaaS Note: if you are using CodeSonar SaaS, your hub has already been configured for you. Go on to Installation: Finishing Up.

We recommend that you perform at least the following hub configuration steps soon after creating or upgrading a hub. You can make additional changes to the Administrator account or hub settings now, or return to the Settings page to make changes later.

If the CodeSonar Web GUI is not already open, open it now.
http://host:port/

If you are not already signed in as Administrator, sign in now.

Click the Sign In link (at the top right of the page).
CodeSonar will open a page for you to enter credentials.
Enter Administrator in the Username field.
Enter the Administrator password in the Password field.
(If you have just started a new hub, you will have set a password for Administrator as part of that process.)
Click Sign In.

If this is the first time the Administrator account has been used, you will be asked to specify an email address for the account.

Click the Settings link (at top right) to open the Settings page.

If you haven't already configured an SMTP server for the hub, do it now:

Change to the SMTP tab.
Fill in the form fields on the tab as necessary to configure the hub to use your organization's SMTP server.
Click Update.

Configure a public URL for the hub (otherwise email messages sent by the hub may contain invalid URLs).

Change to the HTTP tab.
In the Public URL field, enter a suitable base URL for the hub to use when referring to individual GUI pages in email to users. This should have the form
http://hostname:port
Click Update.

Decide whether or not the hub will allow different projects to share warning annotations.

Change to the Analysis tab.
If necessary, edit the Share annotations between projects checkbox so that it reflects your decision.
Click Update to save your changes.

Important Note: we strongly recommend that this setting be decided early in the hub's lifetime, and then kept unchanged. Changing the setting back and forth as projects are analyzed can result in a mixture of hub- and project-scoped warning groups that leads to user confusion.

Step through the other tabs on the the Settings page to familiarize yourself with the contents.

In particular, the HTTP tab allows you to view and change a number of hub properties, including various hub process thresholds which can affect hub performance.

You can make additional changes to the Administrator account or hub settings now, or return to the Settings page to make changes later.

If you have already finished setting up the hub license, go on to Installation: Finishing Up.
Otherwise, go to Hub Setup: Hub License and finish setting up the license.