Setting up BIRT iHub and accessing modules
After installing System Console and one or more BIRT iHub module, use System Console to create a cluster containing a single node. The cluster enables the system administrator to license the modules and monitor the iHub usage. For information about configuring BIRT iHub applications and databases, see BIRT iHub System Administration Guide.
Accessing System Console
During the command-line installation on Windows, System Console opens in a browser. The other installation programs do not open System Console, so to open System Console, double-click the System Console icon on a Windows desktop or open a browser manually and enter the following URL:
http://localhost:8500/sysconsole
On Windows, to provide access to System Console from another system, use the Windows Firewall advanced settings to open the port 8500 to TCP inbound traffic.
To access System Console from another system, open a browser manually and enter a URL similar to the following one, where servername is the name of the machine where you installed System Console:
http://servername:8500/sysconsole
Log in to System Console using the following default system administrator credentials:
*Username: sysadmin
*Password: system11
You can change the default system administrator login name and password in System Console—Settings—System Admin Users. System Console initially displays the 7-day monitoring overview, as shown in Figure 3‑1.
The login password for the postgres user in the default PostgreSQL RDBMS is postgres.
Figure 3‑1 Viewing System Console
A system administrator uses System Console to configure BIRT iHub System, including specifying the settings for the following items:
*Create and configure a cluster
*Connect to a database
*Add a volume
*Tune services and processes
*Specify ports
*Manage resources
*Viewing Logging and Monitoring System (LMS)
*Configure alerts
*Review and update license options
For more information about using System Console, see BIRT iHub System Administration Guide. For more information about administering the PostgreSQL RDBMS, see the vendor documentation at:
http://www.postgresql.org/docs