Description of problem: Our Installation Guide [1] states that the plugin should be installed in the rhq.ear folder inside deploy. However, if JON installation is not finished yet, the user will have only rhq.ear.rej folder. This should be changed. Please note that Installation Guide for JON 2.4.x is correct [2]. [1] http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.0/html/Installation_Guide/JON_Server_Running_The_Installer.html [2] http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/2.4/html/Installation_Guide/JON_Server_Running_The_Installer.html Version-Release number of selected component (if applicable): JON 3.0.x How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Per triage call, target doc fix for JON 3.1.0.
For 3.1, I moved the plugin install to the end, so there's no ear/ear.rej confusion. http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/Installation_Guide/JON_Server_Running_The_Installer.html
This will prevent the plug-ins from getting installed until the next time the server is started (i.e. restarted). Instead, before running the installer, the user should put all plug-in JARs in <RHQ_SERVER_HOME>/plugins. This directory is scanned and all plug-ins are installed in the correct location upon the server starting up during the installation.
Larry's comment is still valid. Fix for this would be move step 14. (Optional. Install any additional agent plug-ins.) before step 4. (Run the JBoss ON server:) Chapter 2.3.1. Using the GUI Installer (Red Hat Enterprise Linux) from http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/Installation_Guide/JON_Server_Running_The_Installer.html Plugins from jon-server-3.1.0.GA1/plugins/ directory are installed during server startup or on demand (Administration->Agent plugins->Scan for Updates). Not sure if there is any automatic scan scheduled??
Mass closure.