Architectural overview

I had some original thoughts to split the installer into smaller sub parts, but it turns out that on further code reading the current implementation is no too far from OK. The way it is exposed (via an ant task) sucks and as per we can get much of where we want to just by replacing that.

The core of how the Installer (and here I also include build.sh) works is a class which contains (and captures where needed) the implementation. Thing like source directory, target directory detailed configuration (for new installs). Currently this class is populated

• From System Properties

• From an supplied property file

• And from the command line (if neither of the above two provide the required value)

The first two bullets have proven popular with people bundling the IdP.

The proposal is to keep this but to add to it with proper command line qualifiers

• Probably one for each property we have

• And we will add properties for things we some add (like HttpClient bean names or aes key sizes), but not for other CLI things (like spring bean files)

• We will do away with the special logback file for the installer and replace it with the standard command line thing

• I think we can get rid of the input property - you can only install from the distribution and it suffices to make that the input

Note that when I say “property driven” below this means via this class which encapsulates the above 4 bullets (so if configured, take from the command line/property file/system properties otherwise ask)

Current implementation

As the time of writing (the first pass of changes for completed the code does this.

Initial Populate

• Update only: Tidy

  • delete bin/lib

  • delete dist (save for the plugin stuff)

  • unprotected system

• Copy webapp to dist\webapp (not overwriting)

• Copy bin/lib to bin/lib (overwriting)

• copy system to system (not overwriting)

Configure

• Version handling

  • Write the version to a the version file in dist

  • check idp.properties for forbidden properties

  • Check plugin conformance

• New Install Only:

  • Enable idp.Core

  • Create key material (property driven)

  • Run property changing over idp.properties, ldap.properties (property driven)

  • create secret.properties (prooperty driven)

• Update only

  • check edit-webapp\WEB-INF\web.xml for badness

• enable modules

  • Update: The ones already defined

  • (TODO) V4-V5 update: plus any new ones ( )

  • New Install Only: from a fixed list (if not property driven)

• Clean up detritus

• New Install Only: Create metadata (driven from idp.properties)

Build war

(this is part of the install but also needs to be its own command line)

• delete webapp (why?)

• create webapp.tmp

  • populate from dist\webapp

  • overlap from dist\plugin-webapp

  • overlap from edit-webapp

• create war\idp.war from webapp.tmp

• delete webapp.tmp

Windows

This is actually not much different

• Initial Populate is handled by the Windows MSI installer

• Configure and Build war are run as java programs inside the installer

• … Plus a whole lot of stuff to do with Jetty which will be exbedded ( or something else)

Properties & Qualifiers used to drive the Install