HA setup : Deployment Procedure
  

Deployment Procedure

Prerequisites

The following ports need to be opened up in the firewall:
• 40010
• 40020
For more information on how to open up ports, see “Enabling Ports in the Firewall” .

Procedure

1. Setup databases using scripts provided with Orchestra installation.
2. Install Orchestra on one application server.
3. Open the following files, located under <orchestra install dir>/conf/ :
• ehcache-central.xml
• ehcache-calendar.xml
• ehcache-jiql.xml
4. Follow the instructions in each file and enable the applicable sections ("Enable this section when using HA mode"). Also, replace the <ip-host-A> and <ip-host-B> parameters with the ip addresses of your nodes.
5. Test installation.
6. Adjust JMS bridge configuration. For this, follow the instructions in “Installation Note - Configuration of Stat on a Separate Server” .
7. Either clone existing application server, or install Orchestra again on second server, pointing to the same databases. The second installation must be made to the exact same path as the first.
8. Test second installation.
9. Install and configure Load Balancer / reverse proxy.
10. Configure both Orchestra systems with the address to the Load Balancer /reverse proxy, where necessary:
• The JVM parameter agent.ipAddress in the startscript (standalone.conf.bat on Windows and standalone.conf on Linux) for the Wildfly application server is used to configure certain hardware, e.g. Cinematic, and should be the address to the Load Balancer /reverse proxy. This file is located in <Orchestra install>\app\<application server>\bin\ .
• The address configured in the file <Orchestra install>\pentaho-solutions\system\security.properties is used for browser navigation between Business Intelligence and Orchestra. The parameter central.orchestra.url needs to be changed to the Load Balancer address.
• The address configured in the file <Orchestra install>\pentaho-solutions\system\score.properties is used by Business Intelligence to perform authorization towards Orchestra. If Business Intelligence is setup on a separate server, the parameter security.url needs to be changed to the Load Balancer address.
• All connected hardware should connect to the Load Balancer. If hardware was connected to the system before the Load Balancer was set up, it is necessary to change that configuration both in the hardware and in Orchestra
• Test access via Load Balancer from browser.
11. Test access via Load Balancer for hardware.
12. Test failover, stop Orchestra service on primary, confirm users re-directed to secondary. (Users will have to re-login, as session data is not replicated. Hardware should loose connection and re-connect automatically).