Adding remote management for JMX tools

[ptc-2268933]

I've been trying to add remote management for JMX tools on the windchill server, and I get the errors in the attached files. I read through the java.sun.com instructions in the sys admin guide, and I feel like I'm missing a simple piece of instruction, or have incorrect syntax, but I don't know the answer.

The windchill server is running, but my company does not have a system admin. I'm trying to come in and learn as much as I can, and this issue I believe is halting any progress. Right now, when I access a JMX tool like Jconsole or VisualVM, I only have access to java management.

My process has been to open up command, navigate to the folder structure, and input "java -Dcom.sun.management.jmxremote.port=0, or 80, or any other available port. Same errors regardless.

Any ideas?

Thanks

Bryon

[MikeIbosh]

Bryon,
Try opening a Windchill Shell on the Windchill application server, and running this command: windchill wt.util.jmx.SMJconsole

Mike

[jessh]

As far as enabling remote JMX access to Windchill server processes,
that's really as simple as (in any recent release):

<property name="wt.manager.cmd.common.jmx.args" overridable="true"&lt;br"/> targetFile="codebase/wt.properties"
value="-Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.ssl.need.client.auth=false"/>
<property name="wt.manager.cmd.ServerManager.jmx.args" overridable="true"&lt;br"/> targetFile="codebase/wt.properties"
value="-Dwt.jmx.rmi.port=6049"/>

One can also use WCA to help in such configuration.

Note, however, that the configuration above allows anonymous access,
which is /not /what you want in anything but a demo, pilot, or
development system. [These properties were hoisted straight from my
development system's xconf file.]

The Windchill manuals / online-help provide further references to the
Java documentation on configuring JMX authentication, enabling SSL (if
desired), etc. This is in no way Windchill-specific -- /except/ that
when 'wt.jmx.rmi.port' rather than 'com.sun.management.jmxremote.port'
is specified recent versions of Windchill will not force the
jmxremote.password file to be read-only to all but the Windchill user
(as this can be a real pain to accomplish on Windows). There are other
advantages to using 'wt.jmx.rmi.port' as well, e.g. it avoids using
ephemeral ports.

Also note that Windchill provides a general remote-JMX-over-HTTP(S)
proxy if one needs to do JMX management from clients that only have
HTTP(S) access to the server. One still has to do remote JMX
configuration as above, but the proxy allows tunneling of the JMX RMI
over HTTP(S).

--
Jess Holle

[jessh]

That's a great approach for getting a JMX connection to the server
manager from the server itself.

Recent releases also support SMVisualVM in the same vein.

That's different than enabling /remote /JMX connections.

[ptc-2268933]

Thanks, that was really helpful. I've been jumping all over the place trying to find access to it. Much appreciated. My release didn't let me open VisualVM, but Jconsole popped up just fine.