The picture below illustrates the installation scenario where Orchestra and Stat (and Business Intelligence) are all installed on separate servers:
For this scenario, you will need to run the Orchestra installation wizard twice. If you then also want to install Business Intelligence, as in the picture above, please see “Business Intelligence” .
The Orchestra installation wizard installs artefacts on two different servers.
Also, it runs the database scripts needed for Orchestra.
Then, you run the Orchestra wizard again so that it also installs the following, on Server B:
• JDK
• Wildfly 11
• Stat
• PostgreSQL (if used/needed)
Also, it runs the database scripts needed for Stat.
When the Orchestra installation is completed, it is time to run the Business Intelligence installation wizard, if wanted. See “Business Intelligence Installation Wizard” , which installs the following, on Server B:
• JDK
• Tomcat
• Pentaho
Also, it runs the database scripts needed for Business Intelligence.
Installation - Windows
Prerequisite:
For distributed systems, port 5445 needs to be opened in the firewall. For an instruction on how to open ports in the firewall, see “Enabling Ports in the Firewall” .
Installation - Separate BI Server
Follow these steps on the BI Server:
1. Open the application server configuration file. <installation directory>/app/wildfly-11.0.0.Final/standalone/configuration/standalone-full.xml, in your preferred text editor.
where {orchestra-server} is the IP-address or domain name of the Central Orchestra server.
4. Restart the BI application server.
Data Integration
For more information about Data Integration, please refer to “Hardware Monitoring - Data Integration” .
Preparation:
1. Copy the QP_Central__win_<type>-<version_number>.zip file and unpack the files to a suitable directory, such as tmp.
It is recommended that path names containing spaces should not be used.
2. Open the file install.properties, in the installation package (zip file).
3. Locate the following section:
standalone.stat.server.ip = 127.0.0.1
standalone.stat.server.port = 8080
standalone.stat.server.jms.username = jms
standalone.stat.server.jms.password = password
4. Edit the file so that you enter the correct ip address (standalone.stat.server.ip) and port (standalone.stat.server.port) of the server where you will be installing Stat.
Also, make sure that you use the same username and password for both installations.
When installing Orchestra, without selecting Stat, the installation program will read these properties from the install.properties file and automatically add them to the standalone-full.xml file. However, when installing your system and only selecting Stat, the installation program will read the properties from install.properties and create the user that is needed.
Configuration - Database
Prepare your database by running the scripts corresponding to your database (Oracle Database / Microsoft SQL / PostgreSQL).
If you are going to use PostgreSQL and will be installing it at the same time as installing Orchestra, this configuration can be skipped.
1. Open a database tool that allows you to run a database script (e.g. SQL Developer for Oracle Database, or SQL Server Management Studio for Microsoft SQL). For PostgreSQL see special instructions below.
2. Run the script corresponding to your database in a tool that can execute the script:
Microsoft SQL Server:
<tmp_dir>/db/central-mssql.sql
<tmp_dir>/db/stat-mssql.sql
Oracle Database:
<tmp_dir>/db/central-oracle.sql
<tmp_dir>/db/stat-oracle.sql
PostgreSQL:
1. Make sure the PostgreSQL bin folder is added to environment variables.
2. Open the command prompt in the <tmp_dir>/db/ directory.
3. Run the commands:
psql -U postgres -f central-postgres.sql
and:
psql -U postgres -f stat-postgres.sql
Installation
1. Open the Windows Task Manager and ensure that there is no application called “Services” running, see the picture below. If there is, close the Services application. This is done, to not cause any problems with starting and stopping the Orchestra service, during the installation procedure.
Using the Installation Wizard to install Orchestra means that all modules will automatically be installed. If you know for a fact that you will not be needing certain modules, you should rather use the install.properties file to select the wanted modules and then run the installation in silent mode, using the command install.bat -s for Windows, or install.sh -s for Linux.
Orchestra Installation Wizard - Orchestra and Stat on Separate Servers
The wizard contains the following steps:
1. Click Start to start the installation.
2. Select Install.
3. Enter the wanted installation path and External IP. Default is localhost.
It is also possible to enter a valid domain name, for example qmatic.com, or a host name, such as GOT-JOHSTA-001. This can also be updated post installation, in the file agent.conf.
The first time you run the installation wizard, select only Orchestra (as in the picture) and the second time select only Stat!
5. Select whether or not you already have an existing database server that you want to use. If you select Yes, you will need to enter the settings for your database server in the following pages. If you select No, PostgreSQL will be installed.
6. If you answered Yes in the previous step, select the wanted database here.
7. Enter your database settings (Hostname and Port for PostgreSQL and SQL Server, Hostname, Port, and SID for Oracle). It is also possible (not mandatory) to test the connection here.
For distributed systems, port 5445 needs to be opened in the firewall. For an instruction on how to open ports in the firewall, see “Enabling Ports in the Firewall” .
Installation - Separate BI Server
Follow these steps on the BI Server:
1. Open the application server configuration file. <installation directory>/app/wildfly-11.0.0.Final/standalone/configuration/standalone-full.xml, in your preferred text editor.
where {orchestra-server} is the IP-address or domain name of the Central Orchestra server.
4. Restart the BI application server.
Data Integration
For more information about Data Integration, please refer to “Hardware Monitoring - Data Integration” .
Preparation:
1. Copy the QP_Central__win_<type>-<version_number>.tgz file and unpack the files to a suitable directory, such as tmp.
It is recommended that path names containing spaces should not be used.
2. Open the file install.properties, in the installation package (tgz file).
3. Locate the following section:
standalone.stat.server.ip = 127.0.0.1
standalone.stat.server.port = 8080
standalone.stat.server.jms.username = jms
standalone.stat.server.jms.password = password
4. Edit the file so that you enter the correct ip address (standalone.stat.server.ip) and port (standalone.stat.server.port) of the server where you will be installing Stat.
Also, make sure that you use the same username and password for both installations.
When installing Orchestra, without selecting Stat, the installation program will read these properties from the install.properties file and automatically add them to the standalone-full.xml file. However, when installing your system and only selecting Stat, the installation program will read the properties from install.properties and create the user that is needed.
5. Login to the Orchestra Central server with a user with superuser rights.
6. Create a qmatic user:
#sudo adduser qmatic
7. Create Orchestra directory:
#sudo mkdir -p /opt/qmatic/orchestra/system
8. Grant rights for Orchestra directory to qmatic user:
#sudo chown -R qmatic:qmatic /opt/qmatic
9. Switch to qmatic user:
#sudo su - qmatic
10. Unpack Orchestra tgz file, to a tmp directory:
$ cd /<tmp_dir>
$ tar zxvf QP_Central_linux64-<version>.tgz
Configuration - Database
Prepare your database by running the scripts corresponding to your database (Oracle Database/Microsoft SQL/PostgreSQL).
If you are going to use PostgreSQL and will be installing it at the same time as installing Orchestra, this configuration can be skipped.
The scripts are designed for a rudimentary base installation of Orchestra, and should be reviewed and tuned by the database administrator to match the installation size and performance requirements.
1. Open a database tool that allows you to run a database script (e.g. SQL Developer for Oracle Database, or SQL Server Management Studio for Microsoft SQL). For PostgreSQL see special instructions below.
2. Run the script corresponding to your database in a tool that can execute the script:
Microsoft SQL Server:
<tmp_dir>/db/central-mssql.sql
<tmp_dir>/db/stat-mssql.sql
Oracle Database:
<tmp_dir>/db/central-oracle.sql
<tmp_dir>/db/stat-oracle.sql
The Oracle scripts will create required schemas in default user table-space. Please review the scripts and assign appropriate table-spaces for the schemas. Larger installations may require tuning of some Oracle instance parameters.
If you, for some reason, after having installed a complete system, need to redirect Stat to a separate server, please follow the instructions in “Installation Note - Configuration of stat on a separate server” .
