Make ISPN's start script name configurable

[mcimbora]

Currently hardcoded as clustered.sh/standalone.sh. There may be a need to start servers in domain mode.

[rvansa]

Make sure to try out domain mode (additional support might be handy), not just add one option...

[mcimbora]

Contributions are welcome.

[alanfx]

This is definitely required, since clustered.sh has been removed in Infinispan 8.x. The startup scripts may be changing names again as well. standalone.sh can be used for now, since RadarGun passes a configuration file to the script.

[alanfx]

I have been working on this some. I don't have a PR ready yet, but I want to document the changes that I have figured out so far.

• Handling starting in domain mode is relatively easy. It requires using the name of the startup script to also find the domain configuration file.
• Domain mode also adds an additional configuration file for hosts. This host configuration file is not being shown in the report yet
• The JavaProcessService plugin needs updates to deal with domain mode though. It currently assumes that if the process launched by the service is not a JVM, then the first child JVM process is. This breaks down in domain mode. The first process launched is the shell running domain.sh which spawns the "Process Controller" JVM process. The "Process Controller" spawns the "Host Controller" JVM which then spawns the actual "Server" JVM processes based on the host configuration. For the InfinispanServerService we need to be able to specify which processes (The "Server" processes) we care about and want to attach to via JMX. I am thinking this means that the JavaProcessService needs to be able to get all the children processes spawned from the initial process including the command line, and then the service can configure a RegEx string to find in the commands. The shell scripts should be able to do this with some refactoring, or pgrep may have options to do this.

That's all for now!