|  |
MBeanInspector for WebSphere Application Server
A Java Management Extensions (JMX) management browser for WebSphere 5.
Date Posted: October 8, 2003
|
|
|
|
|
|
The operation you are trying to invoke expects an unsupported data type as a parameter. MBeanInspector knows how to provide many commonly used data types, but not all.
| | |
|
MBeanInspector 2.0 provides a plug-in facility for supporting new data types. This facility will be the future of an upcoming developerWorks article that will document the API and provide examples of how to write MBeanInspector plug-ins.
| | |
|
By default, the Deployment Manager's SOAP connector binds to port 8879; and 8880 is the default SOAP connector port for a base Application Server.
Finding the correct port can be somewhat tricky because there are no hard and fast rules about what port the servers use. The best thing to do is read through the SystemOut.log file for the server in question; it usually states what connector is being started on which port.
You can also use netstat -p TCP (on Windows) to list ports on which your system is listening. SOAP connectors are usually bound to ports in the 8880+/- range, while RMI connectors are bound to ports in the 2809+/- range.
| | |
|
No; MBeanInspector "persists" certain preferences and uses them at start-up to initialize things such as connection properties, MBean feature filtering, and trace settings.
| | |
|
This is a known issue that should be fixed in a future release. Until that time you can move the mouse pointer over most fields with very long values to bring up a tool-tip containing the text (or at least more of the text).
| | |
|
This is a known problem and is under investigation. In the meantime, you should be able to delete the existing value and enter a new one.
| | |
|
This is a known problem with the invocation table. In order for your input to take effect, press the Enter key when you are finished editing a parameter-value cell.
| | |
|
Please post ideas for features and enhancements on the forum; that way, everyone can see and discuss them. Your great idea might trigger another great idea from someone else, which will make MBeanInspector a better tool in the long run.
| | |
|
Please e-mail bug reports directly to the developer. If you are sending a bug report, please include as much information as possible. You should be able to copy the contents of any error windows that pop up. Likewise, in the Help menu there is a diagnostic trace option; using that option, you can view diagnostic traces and even export them for attachment in an email.
No formal mechanism is available at this time. | | |
|
MBeanInspector is a side project, so time for it is somewhat limited. Bug fixes will get the most attention, particularly critical issues that prevent MBeanInspector from working in the desired manner. Bugs that have work-arounds will likely be deferred until a new-feature release.
Requests for new features and enhancements are ranked according to community interest and feasability. The best way to get your idea into MBeanInspector is to get lots of people to ask for it! New releases will be available as often as possible.
| |
|
|
|
|
| |
|
