Chapter 5. Installing the Agent from RPM
5.1. About Agent RPMs
- System user and group settings with appropriate permissions already set
- System services to start, stop, and restart the agent
- System service to change the agent's configuration
- Upgrades using system tools
5.1.1. Differences Between JAR and RPM Installations
rpmis run or the user account (root) who initiated it.
Table 5.1. Some Differences Between JAR and RPM Installations
|Configuration Area||JAR Value||RPM Value|
|Agent user||Set to the system user who installs it||jbosson-agent user, jbosson group|
|Agent service||Not set||jon-agent|
|Environment variables||installDir/bin/rhq-agent-env.sh|| |
|Home directory location||Wherever the JAR is installed||/usr/share/jboss-on-3.2.0.GA/agent/|
|agent-configuration.xml location|| In the ||/etc/jboss-on/agent/[a]|
|Java preferences location||~/.java/default (system user Java preferences)||/var/lib/jboss-on/agent/prefs/.java/.userPrefs/rhq-agent/default/|
|Data directory location||agentInstallDir/data||/var/lib/jboss-on/agent/data/|
|Log directory location|| In the ||/var/log/jboss-on/agent/[b]|
[a] symlinked to /usr/share/jboss-on-3.2.0.GA/agent/conf
[b] symlinked to /usr/share/jboss-on-3.2.0.GA/agent/logs
5.1.2. The JBoss ON User
jon-agentuser and the
jbossongroup when it is installed. The user and group are not removed if the RPM is uninstalled.
5.1.3. Service Tools and Init Script
chkconfigis configured so that the agent starts when the system starts and runs as a daemon.
kill, which forces the agent process to stop
config, which runs through the agent configuration wizard again and refreshes the agent configuration with new settings
statuscommands are available when the agent is manually configured to run as a service, as described in Section 4.4, “Running the JBoss ON Agent as a Service”. However, the
configcommands are only available with the init script provided with the agent RPM.
/etc/init.d/jon-agent, sets the environment variables that are set in the
rhq-agent-env.shfile with a JAR installation. This init script defines the agent system user and group, the log and data directory locations, and Java options. Editing the init script can, for example, allow the agent to run as a different user or to start with different JVM settings.
configcommand or by editing the init script. Editing the
rhq-agent-env.shfile or other configuration files directly is not supported.
5.1.4. Update Differences
agent-configuration.xmlfile that tells the agent to check for upgrades. The agent then polls the server, and if the JBoss ON server version is newer than the agent version, the agent requests updated binaries from the server.
agent-configuration.xmlfile is turned off, to disable attempts at an autoupgrade and to allow the local system to manage the agent packages.
<entry key="rhq.agent.agent-update.enabled" value="false" />
5.1.5. Available Channels
Table 5.3. Available Channels for the Agent RPM
|Product Name||Product Version||Channel Name|
|JBoss Enterprise Application Server (EAP)||5, x86||jbappplatform-5-i386-server-6-rpm|
|JBoss Enterprise Application Server (EAP)||5, x86_64||jbappplatform-5-x86_64-server-6-rpm|
|JBoss Enterprise Application Server (EAP)||6, x86||jbappplatform-6-i386-server-6-rpm|
|JBoss Enterprise Application Server (EAP)||6, x86_64||jbappplatform-6-x86_64-server-6-rpm|