You stop and start iHub processes when performing tasks such as switching to a different database for storing volume metadata, applying a new license, or modifying certain properties in acserverconfig.xml, the shared configuration file. If you want to modify acserverconfig.xml for example, you stop the processes that iHub runs, modify and save acserverconfig.xml, then start the iHub processes again.
This section describes how to stop and start iHub processes for a cluster, and for a standalone iHub installation on a single machine.
3 Left-click the arrowhead icon next to a cluster and choose Edit, as shown in Figure 4‑3.
Figure 4‑3 Choosing to edit a cluster
Cluster Configuration appears. Figure 4‑4 shows a cluster named Company, containing one node, kozu.
Figure 4‑4 Editing a cluster
Stopping the cluster
Stop the cluster by taking the cluster offline in System Console. The following section describes this operation.
How to stop the cluster
1 On Cluster Configuration, left-click the arrowhead icon next to the gear icon to access the Manage Cluster menu, and choose Stop Cluster, as shown in Figure 4‑5.
Figure 4‑5 Stopping the cluster
2 From the Manage Cluster menu, choose Refresh, as shown in Figure 4‑6.
Figure 4‑6 Choosing Refresh to refresh the cluster status
When all the services appear in red, the cluster is offline, as shown in Figure 4‑7.
Figure 4‑7 The cluster is offline
Starting the cluster
Start the cluster by bring the cluster online in System Console. The following section describes this operation.
How to start the cluster
1 On Cluster Configuration, left-click the arrowhead icon next to the gear icon to access the Manage Cluster menu, and choose Start Cluster, as shown in Figure 4‑8.
Figure 4‑8 Starting the cluster
2 From the Manage Cluster menu, choose Refresh, as shown in Figure 4‑9.
Figure 4‑9 Choosing Refresh to refresh the cluster status
When all the services appear in green, the cluster is online, as shown in Figure 4‑10.
Figure 4‑10 The cluster is online
Stopping and starting iHub processes for a standalone iHub installation on a Windows machine
On a Windows machine, the process for stopping and starting iHub processes differs, depending on whether you installed iHub to run as Windows services. The following procedures describe how to stop and start iHub processes when iHub is running as Windows services, and when iHub is not running as Windows services.
How to stop and start the iHub processes when iHub was installed as Windows Services
1 Open Windows Services by choosing Windows Start➛Control Panel➛Administrative Tools➛Services.
2 Stop iHub processes by stopping the iHub service. Right-click the Actuate iHub 3.1 Service and choose Stop.
3 Start iHub processes by starting the iHub service. Right-click the Actuate iHub 3.1 Service and choose Start.
How to stop and start iHub processes when iHub was not installed as Windows services
1 Stop the iHub processes by entering s in the Actuate BIRT iHub3 command prompt and pressing Enter, as shown in Figure 4‑11. The command stops iHub processes but does not stop the out-of-the-box (OOTB) PostgreSQL database.
Figure 4‑11 Stopping iHub
2 Start iHub by double-clicking the Start iHub Platform icon on the desktop.
Stopping and starting iHub processes for a standalone iHub installation on a Linux machine
In a standalone iHub installation on a Linux machine, if you want to modify acserverconfig.xml for example, you stop iHub, modify and save acserverconfig.xml, then start iHub again.
How to stop and start iHub on a Linux machine
1 Navigate to <installation directory>/modules/BIRTiHub.
2 Shutdown iHub by executing the stopiHub.sh script using the following command:
sh ./stopiHub.sh
3 Start iHub by executing the startiHub.sh script using the following command:
