You must use one of the following upgrade options:
Once you finish upgrading the Agent Manager hosts, restart each of the agents that were deactivated.
3 |
Edit the “new” {{state/default/config/fglam.config.xml}} file, and replace the {{<config:id> ... </config:id>}} value with that obtained from the “existing” FglAM installation. |
4 |
Edit the “new” {{state/default/config/fglam.config.xml}} file, and replace the {{<config:host-display-name> ... </config:host-display-name>}} value with that obtained from the “existing” FglAM installation. |
Agent Manager upgrades for multiple state instances may fail in certain situations. A detailed description of this issue and a workaround is provided in FglAM vm.config file migration fails under multi-state installations.
You may encounter issues in the following situation when upgrading the Agent Manager: Upgrade from an Agent Manager version earlier than 5.5.4.
1 |
2 |
Note that the vm.config settings were migrated. |
3 |
4 |
5 |
Migrate the java.vm config option. |
6 |
Once migration is complete, and you have validated that all config settings are in their new locations, delete the vm.config file and restart the FglAM process. |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center