Upgrading agent relays remotely
When you upgrade the server, be sure to always upgrade agents and agent relays.
Starting from IBM® UrbanCode® Deploy version 7.0.4.2, you can upgrade the agent relays remotely.
Important: Beginning in version 7.0.2, the IBM UrbanCode Deploy server and
agent relays require a Java™ Runtime Environment
(JRE) or Java Development Kit (JDK) version
11.
Important: After you upgrade to IBM UrbanCode Deploy version 6.2.2 or later, note these changes to agent relays:
- Users might notice that some agent relays are no longer listed in the user interface even though they were able to view relays before the upgrade. The new version includes updated security controls. The agent relays are still available to the users. However, System Team administrators can assign agent relays to teams and set the View Agent Relays permission for roles so that appropriate users can see the agent relays in the user interface.
- Users can install and use agent relays. However, the relays are not listed in the user interface for the user until a System Team administrator assigns the agent relay to teams and sets the View Agent Relays permission.
Note:
- If you are upgrading to version 7.0.5.1 or later, the custom JAVA_OPTS properties needs to be updated in the AGENT_RELAY_INSTALL_DIR\bin\worker-args.conf file. Starting with version 7.0.5.1, worker-args.conf file holds the JAVA_OPTS properties for WORKER thread.
-
During the upgrade, log4j.properties or log4j2.properties overrides the existing configuration to default values.
Example:-
On log4j2.xml file,
<DefaultRolloverStrategy max="2" fileIndex="min"/>
(where, 2 is the default value)
-
On log4j.properties file,
log4j.appender.file.MaxBackupIndex=2
(where, 2 is the default value)
-