JVM startup parameters in start.ini for Program Files (x86)

[Rod Widdowson]

> 
> . Or wait until Rod's online and can answer. Or it's documented in the wiki already. But I'm fairly sure it isn't done with a file.

Which I'm not right now.  More tomorrow, but briefly.

- start.ini is not appropriate for configuring jetty (a.k.a doesn't work) when it's started by procrun (which is what the shibboleth idp package does).  

- Shibd_idpw is the way to go.

- until 3.3, headless installs do not work, I believe there is a note in the wiki about that, but basically in 3.3 the way to make them work is to not poke the hole in the firewall (because of a bug deep down in MISEXEC.EXE).

- you can probably poke the registry (it's somewhere under a wow64 key below HKLM, possible SOFTWARE\WOW64\Apache2.0\procrun2.0\java).  I'll check tomorrow when I'm back at my desk. However that location isn't one we control and so it may vary between releases.   I've not seen it change in 10 years, but it's important to understand that things may suddenly.

- there may be a way of providing a command line option to the idp installer to provide the max memory when doing a headless install, but again until such time as we document it, it will be non trustworthy 

More tomorrow..