I've done a little more research myself and I'd like to share this information with you guys, in case someone is interested.
There are two methods to accomplish JMX monitoring of WLS 9.2. One is to use IIOP to access the runtime MBean servers directly. The other method is to access the Sun JVM with RMI (which I have previously used to successfully monitor Java CAPS). See http://www.performanceengineer.com/m...ng-jmx-2.html. I've tried both methods, and the one that worked best for me is to access the JVM itself.
I had to go through all this since 9.2 monitoring isn't supported in the current version of SilkPerformer. I've requested a roadmap from Borland Support, but they have not answered yet.
Here's a more detailed instruction that I posted to Borland Support. I might as well post it here too.
1. Ok, first of all, it's necessary to update the WebLogic start script with the following properties (options to the JVM):
Please note that it is critical that the above properties is set per server, not per domain. We don't want any port collissions.
2. Restart the WebLogic domain.
3. In Performance Explorer, add a new predefined data source:_Application Server - Sun - Sun JVM 1.5 (JMX Mbean Server).
4. Enter the host and port. User name and password is not needed.
5. Click the Server Configuration button and configure this:
JVM - Java home directory: Local installation directory of your JVM 1.5.
Connection - Registry lookup: JSR-160/RMI
URL postfix: jmxrmi
6. Check that the URL looks like this: service:jmx:rmi:///jndi/rmi://[host]:[port]/jmxrmi
7. Click OK and Next.
8. Go ahead and select the appropriate attributes. The easy way is to use the "WebLogic - Runtimes" query.