Mea culpa. My first issue with Pulse is common to both Locator and Launcher. Blame either Chrome's cache or operator error.
Here's the rub with it though. When I go into gfsh and connect to my Locator, Tomcat fires and everything is peachy.
Sadly the point of the exercise was to eliminate gfsh, so I'm looking for the reason it doesn't do this for me.
I already had both of these properties set in a futile effort to force my desired behaviour:
-Dgemfire.jmx-manager=true
-Dgemfire.jmx-manager.start=true
Although I understood that the first was the default for a Locator anyway.
My second issue is my seeming inability to pass in a list of locators (or gemfire.properties) to the LocatorLauncher. We run multiple discrete grids with (at least) two standalone Locators in each. I need to have them all play nice with one another and unless I'm mistaken I need to pass in the list of locators that are common to have this happen.