This article describes how to configure Ignite PI for continuous monitoring during an outage or failover situation. In a clustered environment, the repository database is installed in a SQL Server Active/Passive Cluster or Oracle RAC. The Ignite PI application server can co-exist with the Ignite's Repository database or it can be located on separate server(s). Figure 1 shows a SQL Server Active/Passive Cluster housing Ignite's repository with Ignite PI application server on same cluster with shared storage.

Shared Storage:

 Figure 1:

To implement Ignite in the above configuration:

1. Install Ignite software and repository on Node A (active) in the cluster.
2. In a failover situation, configure the Ignite PI service to shutdown on Node A.
3. Configure Ignite PI service to automatically startup on NODE B on failover.
4. In a fallback situation, shutdown the Ignite PI Service to shutdown on NODE B.
5. Configure Ignite PI service to automatically startup on NODE A.

Note: If using Oracle RAC, the above Ignite PI software configuration can be used if the Cluster shares disks to house the PI software. In an Oracle RAC configuration, since all nodes are active, Ignite PI should be configured to use the 'Shared or Load Balanced'  connect string to the Repository.

Non-Shared Storage For PI Software:

It is possible to have multiple installations of the Ignite PI software for failover purposes, if the software does not reside on shared storage. Figure 2 illustrates this configuration.

Figure 2:

To implement Ignite in the above configuration:

1. Install Ignite software and repository on Node A (active) of the cluster.
2. Install Ignite software on NODE B (passive).
3. Copy over the repo.properties file from NODE A to same location on NODE B.

•     Located in c:\Program Files\Confio\Ignite PI\iwc\tomcat\ignite_config\idc

4. In a failover situation, configure the Ignite PI service to shutdown on Node A .
5. Configure Ignite PI service to automatically startup on NODE B.
6. In a failback situation, shutdown the Ignite PI Service to shutdown on NODE B.
7. Configure Ignite PI service to automatically startup on NODE A.

Note: If using Oracle RAC, the above Ignite PI software configuration can be used if the servers in the cluster have local disks for housing software. In an Oracle RAC configuration, since all nodes are active, Ignite PI should be configured to use the 'Shared or Load Balanced'  connect string to the Repository. 

Listed below are other KB articles that may be of interest when installing and configuring Ignite.

Ignite PI Requirements Guide:  http://support.confio.com/kb/1529/  

Installing Ignite on Windows: http://support.confio.com/kb/1513/ 

Installing Ignite on UNIX or Linux Machines: http://support.confio.com/kb/1509