Agreed, this is not simply the documentation issue, but it also goes beyond Application Server/SDK installer issue. True, AS/SDK installer could once again catch up with admin documentation and modify jVM option in configuration files but this addresses only one segment of the problem since it would not help with any domains/node agents created after the fact or those GF/AS installation installed through distributions such as GlassFish, NetBeans, JCAPS, JES where installer does not offer the option to create Windows service.
The proper way of handling this would be to to either add full fledged Windows support to 'asadmin create-service' subcommand or to provide service creation options to 'create-domain' and 'create-node- agent' subcommands. That way installer would have reliable interface which could be called and user could also be able to easily create and manage appropriate Windows services at any point of product lifecycle.
[Message sent by forum member 'snjezana' (snjezana)]
http://forums.java.net/jive/thread.jspa?messageID=277920