When in doubt, start fresh from an installer and start over. That is my lesson from this mess.
Another lesson, Good intentions with little knowledge will cost you more resources to fix.
I knew these lessons, ones that I have used quite often with APM, but I was out of the office the majority of November, with vacation and CA World 2015 (which rocked) and thought my very simple directions, tech notes and guidance was more than enough, guess not.
Come to find out one of the Jr.s on the team went full bore on trying to align our 9.6 java agent configuration with the 10.0 agent. With very bad results...well no results being metrics.
So, I pulled a full /core/config directory for all application servers, went through and copied the entire websphere-typical.pbl tree. In the toggles-typical.pbd, commented out the NIO since with WebSphere it generates hundreds of thousands of socket connections daily and in the past has caused metric explosions.
Found a test instance that I could restart the JVM without impacting too many people, deleted the pbd/pbl/profile from the <apm agent home>/core/config, copied in the new config file set, insured the EM host was set to my MOM, fired it up.
Accessed the websphere console, since the JVM was the deployment manager, and instantly saw the front end metrics.
So, if you hit a problem like this, compare what you are trying to debug with a clean copy from the installer and rule out if someone's good intentions, to take initiative, to find someone constructive to work on, is your problem.
Thanks to everyone,
Billy