Making secure instance of Sun Java Webserver Highly Available using Solaris Cluster
Solaris Cluster provides an agent to make Sun Java Webserver Highly Available. The agent can also work in zones. It also works with secure instance which requires the user to provide a PIN manually when the webserver is started. However this defeats the purpose of HA. To avoid the problem, create a file by name keypass with just the password in plain text (hardcoded 
can't change) in the Instance's config directory.
Currently the docs suggests placing the file in the Server Root directory which is not very clear if you are using the local FS for binaries and the global file system for instance.
i.e in the /global/web/<https-instance-name>/bin directory with appropriate permissions.
For what it is worth!