Installing BIRT iHub in a cloud : Setting up iHub to use the out-of-the-box (OOTB) PostgreSQL database : Accessing Information, Management, and Configuration Consoles
 
Accessing Information, Management, and Configuration Consoles
After the script finishes running, open a browser to log in to the following BIRT iHub consoles to perform user and administrator tasks:
*Information Console
Perform tasks such as accessing folders and viewing designs and documents.
To access Information Console, open a browser manually and enter the following URL, as shown in Figure 6‑3:
http://localhost:8900/iportal/
Figure 6‑3 Viewing Welcome to Actuate Information Console
*Management Console
Set up user accounts and schedule or run a design.
To access Management Console, open a browser manually and enter the following URL, as shown in Figure 6‑4:
http://localhost:8900/acadmin/
Figure 6‑4 Logging in to Management Console
*Configuration Console
Perform administrative operations, such as the following tasks:
*Add an Encyclopedia volume.
*Connect to a database.
*Make modifications to iHub parameters and server templates.
*Update the license.
To access Configuration Console for administering iHub, open a browser manually and enter the following URL, as shown in Figure 6‑5:
http://localhost:8900/acadmin/config/
Figure 6‑5 Logging in to Configuration Console
When starting PostgreSQL for BIRT iHub and Actuate BIRT iHub, the best practice is to start PostgreSQL, then iHub. When stopping these programs, stop iHub, then PostgreSQL, if necessary.
It is not necessary to shut down the database when starting and stopping iHub. iHub starts faster with the database already running and available in the background, which is particularly important in cluster and other high‑performance operations.
The following sections describe how to perform these operations in the recommended order.