Need to test this update when an agent is installed as a windows service or a UNIX boot-time daemon process. Unless the layout of the agent changes drastically, I don't think this affects a previously installed Windows Service - i.e. a previously installed Windows Service should still run the agent, even though the agent has been updated to a new version. Because a UNIX boot-time agent process will probably use the rhq-agent-wrapper.sh script in the initd structure, its possible users may still have to do something manual (i.e. update the old initd wrapper script file with the changes that are found in the updated agent). This could be a problem - we may have to write the agent wrapper in a way that we should guarantee in the future it will never change.
http://support.rhq-project.org/display/RHQ/Design-AgentAutoUpdate#Design-AgentAutoUpdate-UpdatingAgentRunningAsAWindowsService%2FUNIXBootTimeProcess
Whatever we come up with, we need to make sure we test: 1) deployed as a Windows Service and we added a *.inc file (I'm not sure but I think this might require us to remove then re-install the service). 2) deployed as an init.d script on UNIX. We need to find out how to deploy the agent as a boot-time startup process that still supports being auto-updated. 3) updating an agent that has customized -env scripts (we will not support customized rhq-agent-wrapper.sh/bat or customized rhq-agent.sh/bat files - you customize the environment by changing the -env files only
re: #1, the Windows Service is configured to start this command: C:\path\to\rhq-agent\bin\wrapper\windows-x86_32\wrapper.exe -s C:\path\to\rhq-agent\bin\\wrapper\rhq-agent-wrapper.conf set.RHQ_AGENT_HOME=C:\path\to\rhq-agent set.RHQ_AGENT_INSTANCE_NAME=rhqagent-HOSTNAME set.RHQ_AGENT_JAVA_EXE_FILE_PATH=C:\path\to\java\bin\java.exe set.RHQ_AGENT_OS_PLATFORM=windows-x86_32 set.RHQ_AGENT_WRAPPER_LOG_DIR_PATH=C:\path\to\rhq-agent\logs So, unless the agent's home directory changes, the agent windows service can remain intact and not needed to be removed/re-installed. The only issue is the Java executable. If the Java executable moved, the agent will need to be re-installed. We would have to ship the agent with an embedded JRE to get around this issue.
See : http://support.rhq-project.org/display/RHQ/Design-AgentAutoUpdate#Design-AgentAutoUpdate-RestartingtheAgent "Therefore, we will assume that the person initially provisioning the agent into a production environment will: * setup all the required environment and command line settings in rhq-agent-env.[sh,bat] * start the agent via the rhq-agent-wrapper.[sh,bat] launcher script" I think if we require rhq-agent-wrapper to be the agent start script for production environments, we'll be ok. still need to test this but it will be as part of the agent-auto-update testing in general.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1041 This bug is related to RHQ-1108 This bug is related to RHQ-1189