SJAS

JSAS and JMX

Steps for connecting MC4J to JSAS

Choose "Sun JSAS" (available in the drop down box) as the server connection type - Give an appropriate name for this connection, say "SJSAS"

If necessary, alter host and port (the complete URL is also displayed in the server's log, search for JMXServiceURL in the server.log)
Enter the admin user name in the 'Principle' field of the MC4J connection wizard
Enter the admin password in the 'Password' field of the MC4J connection wizard
Click on the 'Next' button
Complete the wizard by clicking on 'Finish' button
Now the MC4J console will be connected to the SJS Application Server. To use J2SE jconsole use the advance connection tab and enter the above information in the appropriate text boxes.
The Domain "amx" and the "amx" mbeans make up the exposed JSR77 interface for SJSAS. Monitoring of the SJSAS can be turned on which will exposed monitoring mbeans in the "amx" domain that can be used in MC4J's console. Resources for more information:

On SJSAS 's exposed "amx" domain: http://docs.sun.com/source/819-0217/dgmbean.html

On SJSAS's monitoring: http://docs.sun.com/source/819-0215/monitor.html

On JSR77 specification: http://www.jcp.org/en/jsr/detail?id=77

On general SJSAS topics http://docs.sun.com/app/docs/prod/entsys#hic

On SJSAS product line: http://www.sun.com/appserver

On java.net J2EE project: https://j2ee-sdk.dev.java.net/index.html

NOTE: ** If you are using the 8.1 SE/EE version of SJSAS, you will need to disable the internal JMX security mechanism that is enabled by default. To do this, you can navigate the Admin GUI to the the "Configurations->xxx-config->Admin_Service->system" window and un-check the "Security:" Enabled check box. You will also need to disable the Node-Agents JMX security by navigating the Admin GUI to "Node_Agents->xxx", click the "JMX" tab and un-check the "Security:" Enabled check box. The "xxx" in the preceding navigation is to be substituted for the components name. The whole configuration will need to be restarted for theses changes to take effect. The propagation of the secure communication channel is slated to be altered in SJSAS8.1U1, so this step will not be required. WARNING: The actions described above will make your configuration less secure than it will be running in the default secure mode. This action is not recommended for production configurations or for configurations where untrusted personnel can gain/has access to the network.