Depending on whether you're able to correctly set up dynamic redirects for the nodes,
you will either start up the newly active system automatically or manually.
Starting Up Automatically
If you have correctly set up the dynamic redirects as described in the
Configuring Jive for High-Availability
section, after a failover, you would start up the new web application nodes by running
the jive start command on each enabled web
app node in the new system. Doing this will start up all of the other nodes and services in the new
configuration.
Starting Up Manually
If, for whatever reasons, you are unable to set up dynamic redirects, then, in the event of a
failure, you would need to manually do the following in the passive/now-active data center
before starting it up:
- On the web application nodes, edit the jive_startup.xml file to point to the new
data center as described in Configuring the
Web Application Servers for High-Availability.
- On the core application database nodes, edit the Activity Engine database
property (jive.eae.db.url) in the jiveProperty table to point to the new
Activity Engine database. For a connection string configuration example, see
Configuring
the Activity Engine Database for High-Availability.
- On the core application database nodes, edit the Analytics database property (__jive.analytics.database.serverURL)
in the jiveProperty table to point to the new Analytics database. For a connection string configuration example, see
Configuring the Analytics Database for High-Availability.
After you have manually performed the above tasks, start up the new web application nodes
by running the jive start command on each enabled
web app node. Doing this will start up all of the other nodes and services in the
newly active configuration.