JVM heap size adjustments

[Rod Widdowson]

To back fill a bit on this conversation.

The settings which the installer makes are drawn entirely and are intended
to mirror the wiki page.  If they do not match then that is a bug which can
and will get fixed.

Both the installer and the wiki pages are aimed as of being useful to anyone
who consumes metadata from any of the federations who are Consortium
Members.  .  I'm pretty sure that the number Scott quotes are sufficient for
the UKFed or InCommon metadata, but if they are not (or they do not match
the wiki) we'll change that for the next release.

The design centre for the Windows Installer has always been for the small
institution with a Microsoft-centred infrastructure and with heavily
overloaded IT staff whose need to be able to swap from installing an IdP to
maintaining exchange and then hoovering coffee out of the Senior Dean's
laptop.  In the UK that has been the FE/HE with a handful of hundreds of
students but who need an IdP (in house or our sourced) in order to gain
journal access for their students.

The assumption is, and will remain, that as soon as you need anything "out
of the box" you will be installing you own container.  The counter to this
is that if the box doesn't fit someone who is working within the boundaries
of a Consortium Member's environment then that is a bug.

My own personal observation is that the Java VM fits in so badly with the NT
Kernel and Win32 that at any sort of scale one would need to seriously
consider running in a Unix of some sort, not matter how hostile that might
be to the rest of the environment.

Meanwhile shibd_idpw is the way to configure the jetty install (it can be
useful for debugging) but that will be wiped by any upgrade.  The *ONLY*
configuration which survives an upgrade is conf\* flows\* messages\* views\*
edit-webapp\* and jetty-base\start.d\idp.ini (I think static\* is left alone
as well).

HTH

Rod