Hubble 2018.0 - Hubble Suite On-premise ... AWS
Hubble Suite On-premise Deployment Upgrade Guide Version 2018.0
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Restart the Hubble Application Server Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 After the Upgrade has Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Hubble Web Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Run the Hubble Web Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Hubble Accelerator Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Upgrade steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Upgrade the Actian Vector database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 3 - Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
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
Software Version
Revision
16th Nov 2017
1.0
2018.0
27th Nov 2017
1.1
2018.0
Comments
Amendments to Hubble Accelerator Upgrade topic
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)
SAP
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).
●
Hubble Accelerator SquashFS package (optional) - this will be provided as a hubble-rc<minor version>.squashfs file (i.e. hubble-1.1-rc20.squashfs). Replaces the Hubble Accelerator OVA if you already have an Accelerator. 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. Running commands Some of the following commands require you to be a root / privileged user. If you are running as a unprivileged user, you can avoid problems by running these steps as root (i.e. using the "sudo -i" command). If you really want to run them as a normal user, please prefix the commands with "sudo" as necessary. Backup It is strongly recommended that a backup is performed prior to an upgrade. Refer to the backup documentation for instructions. Before starting the upgrade If you are upgrading from a version before the 2018 major version (and upgrading to 2018), as a pre-requisite you will need to upgrade the version of docker to 17.06* before starting the upgrade.
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. After downloading the Application package to the application server extract the new package to /etc/ hubble/ by using the following command: # This command assumes you are in the same folder as the HubbleApplicationServer-.tar.gz file mkdir -p /etc/hubble && tar -zxvf HubbleApplicationServer-.tar.gz -C /etc/hubble
Page 3
Upgrade Steps | Hubble Application Server Upgrade
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
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:
Page 4
Upgrade Steps | Hubble Application Server Upgrade
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).
After the Upgrade has Completed If you are upgrading from a version before the 2018 major release, you will need to manually increment the repository version in the database. 1. Execute the following to start the 'psql' command within the repository docker container: docker exec -it -u postgres hubble_hubble_repository_1 psql hubble_repository 2. Now execute the following SQL code to update the version to the correct value: UPDATE public.repositories SET settingvalue= '12' WHERE repository = 'hubble' AND section = 'Versions' AND item = 'MinorVersion' AND settingvalue = '11' \g 3. After executing this you should see the following output to the console, which suggests that the update has taken effect: UPDATE 1
Page 5
Upgrade Steps | Hubble Web Server Upgrade
Hubble Web Server Upgrade Prerequisites Your web servers will need to match the following prerequisites as they did during the initial installation. There can be small changes to the prerequisites (i.e. a required windows patch), but nothing that has a large impact unless upgrading to a new major version. Note that these requirements will be tested by the Hubble Web Server installer and the upgrade will not proceed until they are all met.
Elevated Permissions Administrator privileges/elevated permissions are required for the user installing Hubble Web on the Windows web server machine as the deployment package, which installs Chef and deploys installation files, requires permission from an Administrator or Administrator user to install on a machine. Elevated permissions are also required to run the batch file (run.bat, located within the Chef directory), as Chef will check during the configuration of Hubble Web whether or not the correct Windows features are installed, and this check (and any required installs), requires Administrator level permissions.
Anti-Virus/Anti-Malware Software Any installed and running anti-virus/anti-malware software will need to be temporarily disabled before installing Chef via the deployment package and then configuring Chef via the batch file. The reason for this is that during the checks of installed Windows features, any automatic scan being performed by the anti-virus/ anti-malware software will slow down theses checks and the configuration of Hubble Web due to the amount memory being used by the process. Once configuration is complete and Hubble Web is installed on the windows web server, the anti-virus/antimalware software can be enabled again and if necessary a scan of the machine can then be performed to make sure nothing untoward is present.
Page 6
Upgrade Steps | Hubble Web Server Upgrade
Add Roles and Features Below are the Roles and Features that need to be installed as a minimum before Hubble Web can be installed on the Windows machine: Server Roles ●
Web Server (IIS)
○
●
Web Server
■
■
■
Common HTTP Features
◊
Default Document
◊
Directory Browsing
◊
HTTP Errors
◊
Static Content
Health and Diagnostics
◊
HTTP Logging
◊
Request Monitor
Performance
◊ ■ ■
.NET Framework 3.5 Features
○ ●
●
.NET Framework 3.5 (includes .NET 2.0 and 3.0)
.NET Framework 4.5 Features
○
.NET Framework 4.5 (already installed in Windows Server 2012 R2)
○
ASP.NET 4.5
Windows PowerShell
○
Windows PowerShell 4.0 (already installed in Windows Server 2012 R2)
○
Windows PowerShell 2.0 Engine
○
Windows PowerShell ISE
Static Content Compression
Security
◊
○
Features
Request Filtering
Application Development
◊
.NET Extensibility 3.5
◊
.NET Extensibility 4.5
◊
ASP.NET 3.5
◊
ASP.NET 4.5
◊
CGI
◊
ISAPI Extensions
◊
ISAPI Filters
Management Tools
■
IIS Management Console
■
Management Service
When installing the above Windows features, it is likely that the web server feature will not have been installed yet, meaning that the Server Roles features will require configuration in the Add Roles and Features Wizard, as follows: 1. In the Add Roles and Features Wizard, when you enter the Features part of the Wizard, the screen below is displayed.
Page 7
Upgrade Steps | Hubble Web Server Upgrade
Install the IIS Management Console by leaving the Include management tools (if applicable) checkbox ticked. Then click on Add Features.
2. The screen below is then displayed (note that the Web Server Role (IIS) heading will have been added to the list of parts of the wizard on the left of the screen under Features). Click Role Services.
Page 8
Upgrade Steps | Hubble Web Server Upgrade
3. The screen then displays the list of role services. Check the checkboxes for the required role services. The minimum required services are listed at the beginning of this topic. 4. Once all roles and features are selected, install them (either through download from Microsoft or from provided windows files).
Internet Access Internet access is required in order to configure S3/AWS (Amazon Web Service) access at the end of the Hubble Web installation, and may also be required for downloads from Microsoft when installing the Windows features listed above.
Windows Updates After the minimum Microsoft components and minimum roles and features have been installed as described above, all Windows updates will need to be installed, as updates to the .NET Framework are required, including .NET Framework 4.5.2.
Minimum Microsoft Components Required As well as the Roles and Features required, there are some additional Microsoft Components which need to be installed before Hubble Web can be accessed successfully. After all the available Windows updates are installed, please check whether the following are installed, and install them manually if not: ●
KB 2919355 - This should come with the latest updates. If not, you can get if from: https://www.microsoft.com/en-us/download/details.aspx?id=42334)
●
KB 3021910 - This should come with the latest updates. If not, you can get if from: https://www.microsoft.com/en-us/download/details.aspx?id=46824)
●
KB 2999226 - This may not be installed with the latest updates. If so, you can get it from: https://www.microsoft.com/en-us/download/details.aspx?id=49063.
Run the Hubble Web Installer 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,
Page 9
Upgrade Steps | Hubble Web Server Upgrade
...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 10
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:
Page 11
Upgrade Steps | Hubble Web Server Upgrade
4. 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).
Prerequisites Tests At this point the prerequisites tests will run again. Normally, the prerequisites won't change between the original install and a upgrade, but it might happen on some occasions (i.e. new windows patches required, new service tested, etc.). If that happens, you may need to update the web server(s) to match the new requirements.
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 12
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. 5. 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 update has completed successfully. Proceed as follows: a. Open a PowerShell window.
Page 13
Upgrade Steps | Hubble Web Server Upgrade
b. Change directory to C:\Insight: cd C:\Insight c.
Execute the following command: C:\Insight\DVT.ps1 all C:\chef\run-list.json
6.
You will now be able to see the Hubble Web UI by accessing the following address in your browser: http:///
Page 14
Upgrade Steps | Hubble Accelerator 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:
7. When you reach this stage, the Hubble Web Server update is complete.
Hubble Accelerator Upgrade Hubble Accelerator updates are independent from the rest of the Hubble Suite upgrade. You can therefore upgrade the rest of the Hubble Suite without upgrading the Accelerator, and vice-versa. New versions of Hubble Accelerator are released less frequent than Hubble Suite releases and we recommend only upgrading the Accelerator firmware in special circumstances.
To perform a Hubble Accelerator upgrade, you need to apply a new hubble--rc<minor version>.squashfs firmware file to your server. You can do so by following the steps in this section.
Upgrade steps 1. Copy the new firmware sqashfs file to your Hubble Accelerator. You can do this using a program such as WinSCP or by using the scp (Linux) or pscp (Windows) command line tools. For example, if using scp you can run the following command (the syntax is exactly the same for pscp): scp rootfs-1.1-rc<minor version>.squashfs root@:/ tmp 2. Log in to the Accelerator via the ssh client of your choice (e.g. putty).
Page 15
Upgrade Steps | Hubble Accelerator Upgrade
3. Check the firmware partitions to identify which is the most suitable one for the new firmware. You can list all the firmware partitions by running the yblsfw command as follows:
The firmware may list up to 5 partitions, starting with /dev/sdh3 and ending with /dev/sdh7. If there are less than 5 partitions, you just need to use the next device available. In the example above, this would be /dev/sdh4. a. If the list shows 5 partitions, you will need to overwrite the oldest one that is not a bootstrap partition.
In the example above the oldest firmware version installed is /dev/sdh4, so it should be the one to overwrite. b. If there is only a single partition listed when you run the yblsfw:
...then run the lsblk command to list the partitions available to use. The output should be something like this:
Choose a partition that isn't being used. From the above example partition sda5 is not being used. 4. Write the firmware into the partition you determined in the previous step. You can do that by running: dd if=<path_to_squash_file>hubble-.squashfs of=<partition to use> bs=10M For example, if you are upgrading to firmware version 1.1-rc29 and you are writing it to the /dev/sdh4 partition, you should run the following command: dd if=/tmp/hubble-1.1-rc29.squashfs of=/dev/sdh4 bs=10M 5. Check that the firmware was installed correctly by running the yblsfw command again. The new firmware should now be shown in the selected partition. Page 16
Upgrade Steps | Hubble Accelerator Upgrade
6. Update the configuration with the firmware version that you just installed. To do this open the configuration file with a text editor (i.e. nano or vi): nano /config/config/config.xml Change the version to the recently installed firmware (as it is shown on the output from the yblsfw command) in the section of the configuration XML file. For firmware version 1.1-rc29, you would write: 1.1-rc29 7. Stop all the necessary services and tasks before reboot. You'll need to follow our Hubble Accelerator shutdown procedure: a. Stop all replication tasks from the replication console web front end. If you don't have access to the replication console, login into the Accelerator through VMWare console, directly or via ssh: /opt/attunity/replicate/bin/repctl gettasklist % Execute the above command. It will return all tasks that are currently running. Once they are all listed, run: /opt/attunity/replicate/bin/repctl connect\; stoptask \; disconnect ...replacing with a real task name. To confirm all tasks are stopped, execute: ps aux | grep repctl This should only return two repctl processes. b. Once all tasks have been stopped, propagate all in memory changes and roll the changes log. To do this, log in to the database, by executing: sql db -u<user> ...replacing <user> with your replication user. e.g.: sql db -ujde Once in the database, execute: CALL VECTORWISE(COMBINE);\g This command might take a while to complete. Once it is complete, commit all changes by executing: COMMIT;\g After the changes have been propagated, roll the logs. To do so, execute the following commands in the database session: CALL VECTORWISE(CONDENSE_LOG);\g ...and then: Page 17
Upgrade Steps | Hubble Accelerator Upgrade
COMMIT;\g Once both commands have finished, exit the session by typing "\q" and pressing ENTER. c.
Turn off the replication server by executing: /etc/init.d/S65areplicate stop
d. Turn off the database by executing: /etc/init.d/S60ingresVW stop 8. Reboot the machine by running: reboot; logout 9. Check the firmware is running after the reboot. You can do this by running: ls /etc The output should include an entry with the firmware name (e.g. yb-firmware-version-1.1-rc29). If it does, you have successfully installed the new Hubble Accelerator firmware version. 10. To finish up, you will need to re-enable all the attunity tasks by running the following command for each of them (you can re-obtain them by running: /opt/attunity/replicate/bin/repctl gettasklist % ): /opt/attunity/replicate/bin/repctl connect\; execute 3 Flags=0\; disconnect
Upgrade the Actian Vector database Only run the following steps if the new firmware version includes a new version of the Actian Vector database. If you are unsure, do not run these steps and contact your Hubble Customer services representative.
1. Initialize the Vector database by running the following command: ybinitvw 2. Now run the upgrade tool by executing this command: upgradedb db 3. If the above step fails, run the following command to check if the Vector Server is running or not: /etc/init.d/S60ingresVW status If the Server is not running you will see something like this:
Start the VW vector server by executing the following commands: sql db \q 4. You will now need to reboot for the changes to take effect: reboot; logout You have now finished deploying the new Hubble Accelerator version.
Page 18
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 19
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Restart the Hubble Application Server Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 After the Upgrade has Completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Hubble Web Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Run the Hubble Web Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Hubble Accelerator Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Upgrade steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Upgrade the Actian Vector database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 3 - Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
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
Software Version
Revision
16th Nov 2017
1.0
2018.0
27th Nov 2017
1.1
2018.0
Comments
Amendments to Hubble Accelerator Upgrade topic
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)
SAP
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).
●
Hubble Accelerator SquashFS package (optional) - this will be provided as a hubble-rc<minor version>.squashfs file (i.e. hubble-1.1-rc20.squashfs). Replaces the Hubble Accelerator OVA if you already have an Accelerator. 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. Running commands Some of the following commands require you to be a root / privileged user. If you are running as a unprivileged user, you can avoid problems by running these steps as root (i.e. using the "sudo -i" command). If you really want to run them as a normal user, please prefix the commands with "sudo" as necessary. Backup It is strongly recommended that a backup is performed prior to an upgrade. Refer to the backup documentation for instructions. Before starting the upgrade If you are upgrading from a version before the 2018 major version (and upgrading to 2018), as a pre-requisite you will need to upgrade the version of docker to 17.06* before starting the upgrade.
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. After downloading the Application package to the application server extract the new package to /etc/ hubble/ by using the following command: # This command assumes you are in the same folder as the HubbleApplicationServer-.tar.gz file mkdir -p /etc/hubble && tar -zxvf HubbleApplicationServer-.tar.gz -C /etc/hubble
Page 3
Upgrade Steps | Hubble Application Server Upgrade
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
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:
Page 4
Upgrade Steps | Hubble Application Server Upgrade
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).
After the Upgrade has Completed If you are upgrading from a version before the 2018 major release, you will need to manually increment the repository version in the database. 1. Execute the following to start the 'psql' command within the repository docker container: docker exec -it -u postgres hubble_hubble_repository_1 psql hubble_repository 2. Now execute the following SQL code to update the version to the correct value: UPDATE public.repositories SET settingvalue= '12' WHERE repository = 'hubble' AND section = 'Versions' AND item = 'MinorVersion' AND settingvalue = '11' \g 3. After executing this you should see the following output to the console, which suggests that the update has taken effect: UPDATE 1
Page 5
Upgrade Steps | Hubble Web Server Upgrade
Hubble Web Server Upgrade Prerequisites Your web servers will need to match the following prerequisites as they did during the initial installation. There can be small changes to the prerequisites (i.e. a required windows patch), but nothing that has a large impact unless upgrading to a new major version. Note that these requirements will be tested by the Hubble Web Server installer and the upgrade will not proceed until they are all met.
Elevated Permissions Administrator privileges/elevated permissions are required for the user installing Hubble Web on the Windows web server machine as the deployment package, which installs Chef and deploys installation files, requires permission from an Administrator or Administrator user to install on a machine. Elevated permissions are also required to run the batch file (run.bat, located within the Chef directory), as Chef will check during the configuration of Hubble Web whether or not the correct Windows features are installed, and this check (and any required installs), requires Administrator level permissions.
Anti-Virus/Anti-Malware Software Any installed and running anti-virus/anti-malware software will need to be temporarily disabled before installing Chef via the deployment package and then configuring Chef via the batch file. The reason for this is that during the checks of installed Windows features, any automatic scan being performed by the anti-virus/ anti-malware software will slow down theses checks and the configuration of Hubble Web due to the amount memory being used by the process. Once configuration is complete and Hubble Web is installed on the windows web server, the anti-virus/antimalware software can be enabled again and if necessary a scan of the machine can then be performed to make sure nothing untoward is present.
Page 6
Upgrade Steps | Hubble Web Server Upgrade
Add Roles and Features Below are the Roles and Features that need to be installed as a minimum before Hubble Web can be installed on the Windows machine: Server Roles ●
Web Server (IIS)
○
●
Web Server
■
■
■
Common HTTP Features
◊
Default Document
◊
Directory Browsing
◊
HTTP Errors
◊
Static Content
Health and Diagnostics
◊
HTTP Logging
◊
Request Monitor
Performance
◊ ■ ■
.NET Framework 3.5 Features
○ ●
●
.NET Framework 3.5 (includes .NET 2.0 and 3.0)
.NET Framework 4.5 Features
○
.NET Framework 4.5 (already installed in Windows Server 2012 R2)
○
ASP.NET 4.5
Windows PowerShell
○
Windows PowerShell 4.0 (already installed in Windows Server 2012 R2)
○
Windows PowerShell 2.0 Engine
○
Windows PowerShell ISE
Static Content Compression
Security
◊
○
Features
Request Filtering
Application Development
◊
.NET Extensibility 3.5
◊
.NET Extensibility 4.5
◊
ASP.NET 3.5
◊
ASP.NET 4.5
◊
CGI
◊
ISAPI Extensions
◊
ISAPI Filters
Management Tools
■
IIS Management Console
■
Management Service
When installing the above Windows features, it is likely that the web server feature will not have been installed yet, meaning that the Server Roles features will require configuration in the Add Roles and Features Wizard, as follows: 1. In the Add Roles and Features Wizard, when you enter the Features part of the Wizard, the screen below is displayed.
Page 7
Upgrade Steps | Hubble Web Server Upgrade
Install the IIS Management Console by leaving the Include management tools (if applicable) checkbox ticked. Then click on Add Features.
2. The screen below is then displayed (note that the Web Server Role (IIS) heading will have been added to the list of parts of the wizard on the left of the screen under Features). Click Role Services.
Page 8
Upgrade Steps | Hubble Web Server Upgrade
3. The screen then displays the list of role services. Check the checkboxes for the required role services. The minimum required services are listed at the beginning of this topic. 4. Once all roles and features are selected, install them (either through download from Microsoft or from provided windows files).
Internet Access Internet access is required in order to configure S3/AWS (Amazon Web Service) access at the end of the Hubble Web installation, and may also be required for downloads from Microsoft when installing the Windows features listed above.
Windows Updates After the minimum Microsoft components and minimum roles and features have been installed as described above, all Windows updates will need to be installed, as updates to the .NET Framework are required, including .NET Framework 4.5.2.
Minimum Microsoft Components Required As well as the Roles and Features required, there are some additional Microsoft Components which need to be installed before Hubble Web can be accessed successfully. After all the available Windows updates are installed, please check whether the following are installed, and install them manually if not: ●
KB 2919355 - This should come with the latest updates. If not, you can get if from: https://www.microsoft.com/en-us/download/details.aspx?id=42334)
●
KB 3021910 - This should come with the latest updates. If not, you can get if from: https://www.microsoft.com/en-us/download/details.aspx?id=46824)
●
KB 2999226 - This may not be installed with the latest updates. If so, you can get it from: https://www.microsoft.com/en-us/download/details.aspx?id=49063.
Run the Hubble Web Installer 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,
Page 9
Upgrade Steps | Hubble Web Server Upgrade
...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 10
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:
Page 11
Upgrade Steps | Hubble Web Server Upgrade
4. 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).
Prerequisites Tests At this point the prerequisites tests will run again. Normally, the prerequisites won't change between the original install and a upgrade, but it might happen on some occasions (i.e. new windows patches required, new service tested, etc.). If that happens, you may need to update the web server(s) to match the new requirements.
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 12
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. 5. 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 update has completed successfully. Proceed as follows: a. Open a PowerShell window.
Page 13
Upgrade Steps | Hubble Web Server Upgrade
b. Change directory to C:\Insight: cd C:\Insight c.
Execute the following command: C:\Insight\DVT.ps1 all C:\chef\run-list.json
6.
You will now be able to see the Hubble Web UI by accessing the following address in your browser: http:///
Page 14
Upgrade Steps | Hubble Accelerator 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:
7. When you reach this stage, the Hubble Web Server update is complete.
Hubble Accelerator Upgrade Hubble Accelerator updates are independent from the rest of the Hubble Suite upgrade. You can therefore upgrade the rest of the Hubble Suite without upgrading the Accelerator, and vice-versa. New versions of Hubble Accelerator are released less frequent than Hubble Suite releases and we recommend only upgrading the Accelerator firmware in special circumstances.
To perform a Hubble Accelerator upgrade, you need to apply a new hubble--rc<minor version>.squashfs firmware file to your server. You can do so by following the steps in this section.
Upgrade steps 1. Copy the new firmware sqashfs file to your Hubble Accelerator. You can do this using a program such as WinSCP or by using the scp (Linux) or pscp (Windows) command line tools. For example, if using scp you can run the following command (the syntax is exactly the same for pscp): scp rootfs-1.1-rc<minor version>.squashfs root@:/ tmp 2. Log in to the Accelerator via the ssh client of your choice (e.g. putty).
Page 15
Upgrade Steps | Hubble Accelerator Upgrade
3. Check the firmware partitions to identify which is the most suitable one for the new firmware. You can list all the firmware partitions by running the yblsfw command as follows:
The firmware may list up to 5 partitions, starting with /dev/sdh3 and ending with /dev/sdh7. If there are less than 5 partitions, you just need to use the next device available. In the example above, this would be /dev/sdh4. a. If the list shows 5 partitions, you will need to overwrite the oldest one that is not a bootstrap partition.
In the example above the oldest firmware version installed is /dev/sdh4, so it should be the one to overwrite. b. If there is only a single partition listed when you run the yblsfw:
...then run the lsblk command to list the partitions available to use. The output should be something like this:
Choose a partition that isn't being used. From the above example partition sda5 is not being used. 4. Write the firmware into the partition you determined in the previous step. You can do that by running: dd if=<path_to_squash_file>hubble-.squashfs of=<partition to use> bs=10M For example, if you are upgrading to firmware version 1.1-rc29 and you are writing it to the /dev/sdh4 partition, you should run the following command: dd if=/tmp/hubble-1.1-rc29.squashfs of=/dev/sdh4 bs=10M 5. Check that the firmware was installed correctly by running the yblsfw command again. The new firmware should now be shown in the selected partition. Page 16
Upgrade Steps | Hubble Accelerator Upgrade
6. Update the configuration with the firmware version that you just installed. To do this open the configuration file with a text editor (i.e. nano or vi): nano /config/config/config.xml Change the version to the recently installed firmware (as it is shown on the output from the yblsfw command) in the section of the configuration XML file. For firmware version 1.1-rc29, you would write: 1.1-rc29 7. Stop all the necessary services and tasks before reboot. You'll need to follow our Hubble Accelerator shutdown procedure: a. Stop all replication tasks from the replication console web front end. If you don't have access to the replication console, login into the Accelerator through VMWare console, directly or via ssh: /opt/attunity/replicate/bin/repctl gettasklist % Execute the above command. It will return all tasks that are currently running. Once they are all listed, run: /opt/attunity/replicate/bin/repctl connect\; stoptask \; disconnect ...replacing with a real task name. To confirm all tasks are stopped, execute: ps aux | grep repctl This should only return two repctl processes. b. Once all tasks have been stopped, propagate all in memory changes and roll the changes log. To do this, log in to the database, by executing: sql db -u<user> ...replacing <user> with your replication user. e.g.: sql db -ujde Once in the database, execute: CALL VECTORWISE(COMBINE);\g This command might take a while to complete. Once it is complete, commit all changes by executing: COMMIT;\g After the changes have been propagated, roll the logs. To do so, execute the following commands in the database session: CALL VECTORWISE(CONDENSE_LOG);\g ...and then: Page 17
Upgrade Steps | Hubble Accelerator Upgrade
COMMIT;\g Once both commands have finished, exit the session by typing "\q" and pressing ENTER. c.
Turn off the replication server by executing: /etc/init.d/S65areplicate stop
d. Turn off the database by executing: /etc/init.d/S60ingresVW stop 8. Reboot the machine by running: reboot; logout 9. Check the firmware is running after the reboot. You can do this by running: ls /etc The output should include an entry with the firmware name (e.g. yb-firmware-version-1.1-rc29). If it does, you have successfully installed the new Hubble Accelerator firmware version. 10. To finish up, you will need to re-enable all the attunity tasks by running the following command for each of them (you can re-obtain them by running: /opt/attunity/replicate/bin/repctl gettasklist % ): /opt/attunity/replicate/bin/repctl connect\; execute 3 Flags=0\; disconnect
Upgrade the Actian Vector database Only run the following steps if the new firmware version includes a new version of the Actian Vector database. If you are unsure, do not run these steps and contact your Hubble Customer services representative.
1. Initialize the Vector database by running the following command: ybinitvw 2. Now run the upgrade tool by executing this command: upgradedb db 3. If the above step fails, run the following command to check if the Vector Server is running or not: /etc/init.d/S60ingresVW status If the Server is not running you will see something like this:
Start the VW vector server by executing the following commands: sql db \q 4. You will now need to reboot for the changes to take effect: reboot; logout You have now finished deploying the new Hubble Accelerator version.
Page 18
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 19
