thanks for all.
Are you local or managed hosted?
I have done the Oct 2014 to Q2 2016 in managed hosting and are currently working on the upgrade you mentioned in local hosting at the moment. I can send you some documentation.
Let me know.
we have local hosting.
Since this is your first time, remember to create a test system first. Make sure you have all upgrade steps figured out there, and only then attempt to upgrade production.
You should always make a backup of your database and your filesystem with the blackboard directory before doing an upgrade.
We completed that upgrade in December, fortunately, with no significant issues. The key thing to work out is getting your installer.properties file set up properly. I found the documentation to be severely lacking (if not completely misleading) for this. For us, we wound up starting with our full bb-config.properties file, removed the properties:
...and added a section with these properties (all set to = ##########)
Once we had the installer.properties file established, and a copy of our license in a safe location, we were able to successfully run the installer to upgrade our environment.
After running through the process in our test environment, we were able to compare pre/post to identify what customized configurations were changed by the installer, and what we needed to restore. Assume that any customization you've made to any of the config files will need to re-applied following the upgrade. Additionally, validate that all of your building blocks are compatible with Java 8, as that is another key component to the upgrade from Oct 2014 to Q2 2016.
I would also consider using the Q2 2016 CU4 installer, since that addresses a number of the issues that exist in the earlier versions.
Best of luck! I know it can be a frustrating process (and even applying a patch to a new CU has an increased frustration level now...we're going from CU3 -> CU4 next week, and it's nearly as much work as it was to go from Oct 2014 -> Q2 2016).
First of all you should be aware that this will be a 2-step upgrade, you cannot upgrade direct from Oct-2014 to Q4-2016-CU1, so you need first to go from Oct-2014 to Q2-2016 and then from Q2-2016 to Q4-2016-CU1.
You need to take snapshots for your DB-Server, app-Servers and Content Server, then run the full upgrade on the application Server that acts as a backend processor, and after that is done, start the Blackboard Services on that Server since the new installer will not start the Service Automatically as earlier installers, after that test if you are able to access the system, after that stop the Services on that Server and then run app-server install only on the other app Servers one a time.
Now it is time again to take a Second snapshot for your Servers.
you can follow the same steps to upgrade to Q4-2016-CU1
I've been posting some notes about our upgrade from 2015 Q4 to 2016 Q4 CU3 that you may find of interest here: Matt's Upgrade Blog
I'll be posting our finalised live implementation plan in the next week or two.
Retrieving data ...