Hubble 2016.1 - Hubble Suite On-premise Deployment - Upgrade Guide
Hubble Suite On-premise Deployment Upgrade Guide Version 2016.1
Document Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i Copyright . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i Version History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i Conventions Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
Chapter 1 - Upgrade Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Files Required for Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Chapter 2 - Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Hubble Application Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Stop Services and apply the new Hubble Package . . . . . . . . . . . . . . . . . . . . . . . . . 3 Update the Hubble Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Restart the Hubble Application Server Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Hubble Web Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 3 - Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Document Information | Notices
Document Information Notices Copyright Hubble® is a brand name of the insightsoftware.com Group. insightsoftware.com is a registered trademark of insightsoftware.com Limited. Hubble is a registered trademark of insightsoftware.com International Unlimited. Other product and company names mentioned herein may be the trademarks of their respective owners. The insightsoftware.com Group is the owner or licensee of all intellectual property rights in this document, which are protected by copyright laws around the world. All such rights are reserved. The information contained in this document represents the current view of insightsoftware.com on the issues discussed as of the date of publication. This document is for informational purposes only. insightsoftware.com makes no representation, guarantee or warranty, expressed or implied, that the content of this document is accurate, complete or up to date.
Disclaimer This guide is designed to help you to use the Hubble applications effectively and efficiently. All data shown in graphics are provided as examples only. The example companies and calculations herein are fictitious. No association with any real company or organization is intended or should be inferred.
Version History Date 26th July 2017
Software Version
Revision 1.0
Comments
2016.1
Customer Support For more information regarding our products, please contact us at http://gohubble.com/. For product support including Training, Documentation and Customer Support, visit our Hubble Community at https://community.gohubble.com/.
Page i
Document Information | Conventions Used
Conventions Used The icons below are used in Hubble documentation to indicate type of user, experience, deployment and the ERP system applicable to the document. Icon
User Type Explorer Explorer users can consume content and contribute to planning. Power Power users can consume or create content, administer and contribute to planning. Designer Designer users can consume, create and extend content, as well as build, administer and contribute to planning. Budgeting/Planning Users with this capability can do realtime budgeting and forecasting. Administrator Administrator users administer the Hubble Product.
Page ii
Icon
Experience/ Deployment
Icon
ERP Type
Desktop Experience
JD Edwards
Web Experience
Oracle
On-premise Deployment (for Web Experience) Cloud Deployment (for Web Experience)
Chapter 1: Upgrade Packages Before starting an upgrade, you should ensure you have all the files necessary to complete it.
Files Required for Upgrading Make sure that Hubble Customer Services have provided you with the following files: ●
Hubble Application Server package - this will be a file called HubbleApplicationServer.tar.gz (i.e. for JDE Release 34, this would be HubbleApplicationServer-2016.1.0.34.tar.gz). It will be used to update the Hubble Application Server.
●
Hubble Web Server Installer - this will be a file called Hubble_Web__<ERP>.exe (i.e. for JDE Release 34, this would be Hubble_Web_2016.1.0.34_JDE.exe). It will be used to update the Hubble Web Servers.
●
Hubble Suite and Web Reporting Software installer - this file will be provided through a Windows installer named HubbleSuite(64x)_.<ERP>.msi (i.e. for JDE Release 34, this would be HubbleSuite(64x)_2016.1.0.34.JDE.msi). This is the same software provided by Click Once, so you will not need it if you use Hubble exclusively through Click Once.
●
Hubble Accelerator OVA (optional) - this file will be provided as a hubble--rc<minor version>.ova file (i.e. hubble-1.1-rc20.ova). If you are already using a Hubble Accelerator, or will continue to use a direct connection to the ERP, you will not need to update/deploy the Hubble Accelerator (unless otherwise stated by Hubble Customer Services).
Once you have these files, you can proceed with updating the Hubble Application Server.
Page 1
Upgrade Packages | Files Required for Upgrading
Page 2
Chapter 2: Upgrade Steps Hubble Application Server Upgrade To upgrade a Hubble Application Server, you just need to apply a new HubbleApplicationServer.tar.gz package to your Linux server, as described in this section.
Stop Services and apply the new Hubble Package 1. Ensure that the previous version of the Hubble services is not running by entering: /etc/hubble/stop.sh && /etc/hubble/Configuration/stop.sh 2. Backup the previous release folder for safekeeping. This will provide a fall back in case there are problems with the new Application Server package. You can do this (for example) with a command such as this: # Assuming you are updating from Release 32 (HUBBLE_VERSION=2016.1.0.32 in the /etc/hubble/.version file) mv /etc/hubble/ /etc/hubble-release32 3. Extract the new package to /etc/hubble/ by using the following command: mkdir -p /etc/hubble && tar zxvf HubbleApplicationServer-.tar.gz C /etc/hubble
Update the Hubble Configurations You will always need to re-submit your configurations using these steps, even if there are no changes to apply. 1. Start the Hubble Configuration UI by running: /etc/hubble/Configuration/start.sh 2. Go to the Hubble Configuration form by accessing http://:3000/ in a browser. If you only have a web server machine, you can access the Configuration UI from there and so avoid having to move the resulting run-list.json file around.
3. Fill in the form with the configuration details of your server(s). 4. Once finished, press the "Submit and Download" button to obtain the run-list.json configuration file (i.e. the configuration file of the web server(s)). Keep this file in a convenient and secure location as it will be needed when deploying the Web Server(s). 5. You can now the stop the Hubble Configuration UI by running: /etc/hubble/Configuration/stop.sh
Page 3
Upgrade Steps | Hubble Application Server Upgrade
Restart the Hubble Application Server Services 1. You can now start the Hubble services again by running the starting script as follows: /etc/hubble/start.sh 2. The Deployment Verification Tests (DVTs) will then run automatically once the Hubble Services containers have been downloaded. Wait for the tests to complete in order to verify everything is working correctly:
When the tests are completed, the following should be displayed:
All tests must pass for a successful Application Server upgrade. 3. If the DVTs all pass, you can now proceed with updating the Webs Server(s). You must use the new "run-list.json" file for the Web Server(s) upgrade or it will not work.
Page 4
Upgrade Steps | Hubble Web Server Upgrade
Hubble Web Server Upgrade 1. In order to install Hubble Web, you must log into the Windows server machine as an Administrator or as a user that has Administrator rights. 2. Copy the installation file to the Windows server, either into a new directory or to the Downloads directory as required. The installation file is called: Hubble_Web__<ERP>.exe, ...where will be the current version and <ERP> will be the platform (i.e. JDE or EBS).
3. Run the new Hubble Web installer executable. This will update the deployment scripts, along with all the Hubble files necessary for the upgrade. a. When this prompt appears, click on Yes to install Hubble:
Page 5
Upgrade Steps | Hubble Web Server Upgrade
b. During the installer run, you will see a command prompt showing the current status of the process, similar to the screenshot below:
c.
When the installer finishes, there should now be files in C:\Insight\Hubble (you should now see a tools directory and a zip file):
Also, in the C:\chef directory, you should now see our installer script run.bat:
4. Copy the run-list.json file that was returned from the Hubble Configuration UI (see “Hubble Application Server Upgrade” on page 3) to the c:\chef\ directory.
Page 6
Upgrade Steps | Hubble Web Server Upgrade
5. Open a command prompt, navigate to c:\chef, and then execute our run.bat deployment script. This will update all the tools, files and services needed to run Hubble Web (e.g. IIS, Hubble services, clickonce, etc).
a. The deployment script will first run Deployment Verification Tests (DVTs) in a special prerequisites mode. This should run successful as these tests would have already been carried out during the initial deployment (during which they would have confirmed that the Windows machine fulfills the Minimal Technical Requirements). If the tests are now failing for any reason, ensure that the Hubble Application Server services have started successfully. You can do this by going to the Application Server and running the following commands: cd /etc/hubble/ && docker-compose ps All the services should show “Up” in the “State” column. If they do, give the containers a few more minutes to fully start, and run the DVTs again. If they are still failing after this, please contact Hubble Customer Services and seek help in unblocking the upgrade. b. Once the DVTs are successful, the script will proceed with updating the software. You can monitor the update progress by either following the command line output, or by checking the installation log file, C:\chef\solo.txt:
Page 7
Upgrade Steps | Hubble Web Server Upgrade
c.
Once the update is complete, a successful entry in the log file should show as follows:
If the chef run fails, you should have clear failure messages both in the command prompt output and in the log file. If this happens you should be able to use these to solve the issue (if possible,) or else contact Hubble Customer Services to unblock the installation.
Page 8
Upgrade Steps | Hubble Web Server Upgrade
6. The next step is to run the full Deployment Verification Tests (while pointing to the run-list.json configuration file), which will confirm that the upgrade has completed successfully, by running the following command from a PowerShell window: Deployment Verification Tests Command C:\Insight\DVT.ps1 all C:\chef\run-list.json
7.
You will now be able to see the Hubble Web UI by accessing the following address in your browser: http:///
Page 9
Upgrade Steps | Hubble Web Server Upgrade
The address will redirect you automatically if you are using HTTPS or a domain name, and you should then see a screen similar to this:
8. When you reach this stage, the Hubble Web Server update is complete. Remember that the RepositorySelection.xml file will be updated by this process. You will need to obtain the new version from C:\inetpub\wwwroot\Hubble\bin\ RepositorySelection.xml and send it to those users who required it. All the users that installed the Hubble Suite through msi installer, or who are running the Administrator tool will need this new file. Click Once users that only use the Designer client will not need the new file, as it is already included (but they might need to uninstall their current Click Once deployment using the Windows “Add / Remove programs” function before the change will be applied).
Page 10
Chapter 3: Glossary ●
Minimal Technical Requirements (MTRs) - the requirements (both for hardware and software) that must be met by the infrastructure provided by the customer.
●
Hubble Application Server - the machine that hosts the Hubble services (i.e. all the software needed to support Hubble Suite and Web). This must be a Linux machine supplied by the customer, with all services run in Docker containers. It is also the entry point for the Hubble Web UI as it performs the load balances between all the available Hubble Web Servers.
●
Hubble Web Server - a machine that hosts the Hubble Web UI. A Windows Server 2012 machine supplied by the customer to which we deploy our software through the Hubble Web Server Installer.
●
Hubble Accelerator - a virtual machine that contains our database accelerator and replication server. It is supplied by Hubble as an OVA and can be deployed through VMware.
●
Hubble Web UI - the page you can use to access Hubble Web through a browser.
●
Hubble Application Server Package - the file in a tar.gz format that contains all that is needed to deploy our Hubble services on the Hubble Application Server.
●
Pre-Requisites Tests - tests that are run before starting any of the Hubble installation/upgrade software to ensure that the MTRs are met. If any of these fail, the software upgrade won't proceed.
●
Deployment Verification Tests - tests that verify that all the Hubble services were started correctly. These will be carried out after all the other deployment steps are completed.
●
Hubble Configuration UI / Configuration Form - the web page used to create and update the configurations needed for the Hubble deployment. It runs in the Hubble Application Server and it is accessible (if started) at the following location: http://:3000/.
●
Hubble Web Server Installer - the web server installer. This is an executable that contains all the files and tools needed to install and configure Hubble Web to a Windows 2012 machine.
●
run-list.json - the file that contains the web servers configuration. It is an output created by the submission of the Hubble Configuration UI form.
●
run.bat - the Windows web server deployment script. This will run Chef with the configurations supplied in the run-list.json file.
●
Hubble Suite and Web Reporting Software - these are the desktop clients that are used for administration and reports creation. The clients can be provided either through an .msi installer or through Click Once deployments.
●
Hubble Customer Services - the Hubble representatives that are in contact with your company to support you during the installation/upgrade process.
Page 11
Glossary |
Page 12
Document Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i Copyright . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i Version History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i Conventions Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
Chapter 1 - Upgrade Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Files Required for Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Chapter 2 - Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Hubble Application Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Stop Services and apply the new Hubble Package . . . . . . . . . . . . . . . . . . . . . . . . . 3 Update the Hubble Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Restart the Hubble Application Server Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Hubble Web Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 3 - Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Document Information | Notices
Document Information Notices Copyright Hubble® is a brand name of the insightsoftware.com Group. insightsoftware.com is a registered trademark of insightsoftware.com Limited. Hubble is a registered trademark of insightsoftware.com International Unlimited. Other product and company names mentioned herein may be the trademarks of their respective owners. The insightsoftware.com Group is the owner or licensee of all intellectual property rights in this document, which are protected by copyright laws around the world. All such rights are reserved. The information contained in this document represents the current view of insightsoftware.com on the issues discussed as of the date of publication. This document is for informational purposes only. insightsoftware.com makes no representation, guarantee or warranty, expressed or implied, that the content of this document is accurate, complete or up to date.
Disclaimer This guide is designed to help you to use the Hubble applications effectively and efficiently. All data shown in graphics are provided as examples only. The example companies and calculations herein are fictitious. No association with any real company or organization is intended or should be inferred.
Version History Date 26th July 2017
Software Version
Revision 1.0
Comments
2016.1
Customer Support For more information regarding our products, please contact us at http://gohubble.com/. For product support including Training, Documentation and Customer Support, visit our Hubble Community at https://community.gohubble.com/.
Page i
Document Information | Conventions Used
Conventions Used The icons below are used in Hubble documentation to indicate type of user, experience, deployment and the ERP system applicable to the document. Icon
User Type Explorer Explorer users can consume content and contribute to planning. Power Power users can consume or create content, administer and contribute to planning. Designer Designer users can consume, create and extend content, as well as build, administer and contribute to planning. Budgeting/Planning Users with this capability can do realtime budgeting and forecasting. Administrator Administrator users administer the Hubble Product.
Page ii
Icon
Experience/ Deployment
Icon
ERP Type
Desktop Experience
JD Edwards
Web Experience
Oracle
On-premise Deployment (for Web Experience) Cloud Deployment (for Web Experience)
Chapter 1: Upgrade Packages Before starting an upgrade, you should ensure you have all the files necessary to complete it.
Files Required for Upgrading Make sure that Hubble Customer Services have provided you with the following files: ●
Hubble Application Server package - this will be a file called HubbleApplicationServer.tar.gz (i.e. for JDE Release 34, this would be HubbleApplicationServer-2016.1.0.34.tar.gz). It will be used to update the Hubble Application Server.
●
Hubble Web Server Installer - this will be a file called Hubble_Web__<ERP>.exe (i.e. for JDE Release 34, this would be Hubble_Web_2016.1.0.34_JDE.exe). It will be used to update the Hubble Web Servers.
●
Hubble Suite and Web Reporting Software installer - this file will be provided through a Windows installer named HubbleSuite(64x)_.<ERP>.msi (i.e. for JDE Release 34, this would be HubbleSuite(64x)_2016.1.0.34.JDE.msi). This is the same software provided by Click Once, so you will not need it if you use Hubble exclusively through Click Once.
●
Hubble Accelerator OVA (optional) - this file will be provided as a hubble--rc<minor version>.ova file (i.e. hubble-1.1-rc20.ova). If you are already using a Hubble Accelerator, or will continue to use a direct connection to the ERP, you will not need to update/deploy the Hubble Accelerator (unless otherwise stated by Hubble Customer Services).
Once you have these files, you can proceed with updating the Hubble Application Server.
Page 1
Upgrade Packages | Files Required for Upgrading
Page 2
Chapter 2: Upgrade Steps Hubble Application Server Upgrade To upgrade a Hubble Application Server, you just need to apply a new HubbleApplicationServer.tar.gz package to your Linux server, as described in this section.
Stop Services and apply the new Hubble Package 1. Ensure that the previous version of the Hubble services is not running by entering: /etc/hubble/stop.sh && /etc/hubble/Configuration/stop.sh 2. Backup the previous release folder for safekeeping. This will provide a fall back in case there are problems with the new Application Server package. You can do this (for example) with a command such as this: # Assuming you are updating from Release 32 (HUBBLE_VERSION=2016.1.0.32 in the /etc/hubble/.version file) mv /etc/hubble/ /etc/hubble-release32 3. Extract the new package to /etc/hubble/ by using the following command: mkdir -p /etc/hubble && tar zxvf HubbleApplicationServer-.tar.gz C /etc/hubble
Update the Hubble Configurations You will always need to re-submit your configurations using these steps, even if there are no changes to apply. 1. Start the Hubble Configuration UI by running: /etc/hubble/Configuration/start.sh 2. Go to the Hubble Configuration form by accessing http://:3000/ in a browser. If you only have a web server machine, you can access the Configuration UI from there and so avoid having to move the resulting run-list.json file around.
3. Fill in the form with the configuration details of your server(s). 4. Once finished, press the "Submit and Download" button to obtain the run-list.json configuration file (i.e. the configuration file of the web server(s)). Keep this file in a convenient and secure location as it will be needed when deploying the Web Server(s). 5. You can now the stop the Hubble Configuration UI by running: /etc/hubble/Configuration/stop.sh
Page 3
Upgrade Steps | Hubble Application Server Upgrade
Restart the Hubble Application Server Services 1. You can now start the Hubble services again by running the starting script as follows: /etc/hubble/start.sh 2. The Deployment Verification Tests (DVTs) will then run automatically once the Hubble Services containers have been downloaded. Wait for the tests to complete in order to verify everything is working correctly:
When the tests are completed, the following should be displayed:
All tests must pass for a successful Application Server upgrade. 3. If the DVTs all pass, you can now proceed with updating the Webs Server(s). You must use the new "run-list.json" file for the Web Server(s) upgrade or it will not work.
Page 4
Upgrade Steps | Hubble Web Server Upgrade
Hubble Web Server Upgrade 1. In order to install Hubble Web, you must log into the Windows server machine as an Administrator or as a user that has Administrator rights. 2. Copy the installation file to the Windows server, either into a new directory or to the Downloads directory as required. The installation file is called: Hubble_Web__<ERP>.exe, ...where will be the current version and <ERP> will be the platform (i.e. JDE or EBS).
3. Run the new Hubble Web installer executable. This will update the deployment scripts, along with all the Hubble files necessary for the upgrade. a. When this prompt appears, click on Yes to install Hubble:
Page 5
Upgrade Steps | Hubble Web Server Upgrade
b. During the installer run, you will see a command prompt showing the current status of the process, similar to the screenshot below:
c.
When the installer finishes, there should now be files in C:\Insight\Hubble (you should now see a tools directory and a zip file):
Also, in the C:\chef directory, you should now see our installer script run.bat:
4. Copy the run-list.json file that was returned from the Hubble Configuration UI (see “Hubble Application Server Upgrade” on page 3) to the c:\chef\ directory.
Page 6
Upgrade Steps | Hubble Web Server Upgrade
5. Open a command prompt, navigate to c:\chef, and then execute our run.bat deployment script. This will update all the tools, files and services needed to run Hubble Web (e.g. IIS, Hubble services, clickonce, etc).
a. The deployment script will first run Deployment Verification Tests (DVTs) in a special prerequisites mode. This should run successful as these tests would have already been carried out during the initial deployment (during which they would have confirmed that the Windows machine fulfills the Minimal Technical Requirements). If the tests are now failing for any reason, ensure that the Hubble Application Server services have started successfully. You can do this by going to the Application Server and running the following commands: cd /etc/hubble/ && docker-compose ps All the services should show “Up” in the “State” column. If they do, give the containers a few more minutes to fully start, and run the DVTs again. If they are still failing after this, please contact Hubble Customer Services and seek help in unblocking the upgrade. b. Once the DVTs are successful, the script will proceed with updating the software. You can monitor the update progress by either following the command line output, or by checking the installation log file, C:\chef\solo.txt:
Page 7
Upgrade Steps | Hubble Web Server Upgrade
c.
Once the update is complete, a successful entry in the log file should show as follows:
If the chef run fails, you should have clear failure messages both in the command prompt output and in the log file. If this happens you should be able to use these to solve the issue (if possible,) or else contact Hubble Customer Services to unblock the installation.
Page 8
Upgrade Steps | Hubble Web Server Upgrade
6. The next step is to run the full Deployment Verification Tests (while pointing to the run-list.json configuration file), which will confirm that the upgrade has completed successfully, by running the following command from a PowerShell window: Deployment Verification Tests Command C:\Insight\DVT.ps1 all C:\chef\run-list.json
7.
You will now be able to see the Hubble Web UI by accessing the following address in your browser: http:///
Page 9
Upgrade Steps | Hubble Web Server Upgrade
The address will redirect you automatically if you are using HTTPS or a domain name, and you should then see a screen similar to this:
8. When you reach this stage, the Hubble Web Server update is complete. Remember that the RepositorySelection.xml file will be updated by this process. You will need to obtain the new version from C:\inetpub\wwwroot\Hubble\bin\ RepositorySelection.xml and send it to those users who required it. All the users that installed the Hubble Suite through msi installer, or who are running the Administrator tool will need this new file. Click Once users that only use the Designer client will not need the new file, as it is already included (but they might need to uninstall their current Click Once deployment using the Windows “Add / Remove programs” function before the change will be applied).
Page 10
Chapter 3: Glossary ●
Minimal Technical Requirements (MTRs) - the requirements (both for hardware and software) that must be met by the infrastructure provided by the customer.
●
Hubble Application Server - the machine that hosts the Hubble services (i.e. all the software needed to support Hubble Suite and Web). This must be a Linux machine supplied by the customer, with all services run in Docker containers. It is also the entry point for the Hubble Web UI as it performs the load balances between all the available Hubble Web Servers.
●
Hubble Web Server - a machine that hosts the Hubble Web UI. A Windows Server 2012 machine supplied by the customer to which we deploy our software through the Hubble Web Server Installer.
●
Hubble Accelerator - a virtual machine that contains our database accelerator and replication server. It is supplied by Hubble as an OVA and can be deployed through VMware.
●
Hubble Web UI - the page you can use to access Hubble Web through a browser.
●
Hubble Application Server Package - the file in a tar.gz format that contains all that is needed to deploy our Hubble services on the Hubble Application Server.
●
Pre-Requisites Tests - tests that are run before starting any of the Hubble installation/upgrade software to ensure that the MTRs are met. If any of these fail, the software upgrade won't proceed.
●
Deployment Verification Tests - tests that verify that all the Hubble services were started correctly. These will be carried out after all the other deployment steps are completed.
●
Hubble Configuration UI / Configuration Form - the web page used to create and update the configurations needed for the Hubble deployment. It runs in the Hubble Application Server and it is accessible (if started) at the following location: http://:3000/.
●
Hubble Web Server Installer - the web server installer. This is an executable that contains all the files and tools needed to install and configure Hubble Web to a Windows 2012 machine.
●
run-list.json - the file that contains the web servers configuration. It is an output created by the submission of the Hubble Configuration UI form.
●
run.bat - the Windows web server deployment script. This will run Chef with the configurations supplied in the run-list.json file.
●
Hubble Suite and Web Reporting Software - these are the desktop clients that are used for administration and reports creation. The clients can be provided either through an .msi installer or through Click Once deployments.
●
Hubble Customer Services - the Hubble representatives that are in contact with your company to support you during the installation/upgrade process.
Page 11
Glossary |
Page 12
