Installers
Description
Environment
Activity
I'm going to mark this complete
Complete. More testing on V2V3 upgrades required.
I've tested jetty installs, same version upgrades and upgrades for '64 bits on 64 bits'.
I need to test '32 bits on 64 bit' installs and upgrades.
But I also want to add some missing function:
Collect the scope from the GUI
Further ant debugging (When ant fails during a windows installs things are a little difficult to debug, I intend adding logging to ant and to have the log file deleted during usual cleanup)
Depending on how the wider issue of LDAP configuration goes, I may add more LDAP configu capture.
Also documentation, particularly for non MSI users.
Current status
I've achieved a fair bit, but the "remaining to be done" list appears to be extending faster than I get things done
A skeleton Windows Installer has been build alongside scripts to build the source files. Minimal GUI.
Ant script to copy new files to distribution and to create initial configuration. Cases dealt with
V3 Install
V2 -> V3 upgrade
V3 -> V3 upgrade
... and MSI equivalents (the same function but no copying from distribution)
To be done:
GENERAL
Populate metadata on first install
With/without Back Channel?
Advance configuration:
LDAP
Optional stuff (like profile Interceptors)
Load (ANT) options from a file
Better mechanism to control changes to idp.properties.
Non MSI
Usability
(potential full/fast/noconfig install)?
Do something with keystore password?
MSI:
Jetty (as an optional add-on)
install
config
Service (including 32/64 bit selection)
ANT integration
v2 update (QI and non QI)
Advanced config (Mostly AD)
UI
Testing for upgrades (QI, V2, V3) -> V3
Other remarks
I'll add to the section, but only remove things we decide not to do.
Discussions on what and why are ongoing but I feel that we need
A merge module for jetty (and a way to automatically create this)
A merge module for apache procrun
A way to generate the include files from a zip install
Some sort of graphical UI.
Potted configuration for ActiveDirectory (as per quick install). We
do however want to avoid having local equivalents of config files
32 and 64 bit variants (needed for procrun)
Spot Old quick install and so "something" about making this an upgrade.