log4j Update

below is an overview of the process to upgrade an existing installation of link enterprise this must be performed for each link enterprise instance (ie link enterprise windows service) at the time of this writing, 2 17 1 is the latest log4j release in the future if new versions are to be utilized, change the version numbers in the below steps accordingly stop the gimmal link enterprise service take note of the "log on" tab if you are running the service under a named account download and move new log4j files (log4j core 2 16 0 jar, log4j api 2 16 0 jar) to /lib/log4j/ delete/rename old l4j file(s) go to /services folder uninstall the service start a windows cmd prompt as administrator in the cmd prompt run /services/uninstallservice bat refresh your windows service list to confirm it is no longer present if the link enterprise service still exists, please edit the uninstallservice bat file to reflect the correct service name edit installservice bat in the /services directory for upgrade from 1 2 15 delete the string "\lib\log4j\log4j 1 2 16 jar;" add a new entry "\lib\log4j\log4j core 2 16 0 jar;\lib\log4j\log4j api 2 16 0 jar;" this entry should proceed "\lib\connector service 6 5 7 fat jar" for upgrade from 2 16 0 or later replace the two instances of "2 16 0" \<or your current version> with "2 17 1" reinstall the service start a windows cmd prompt as administrator in the cmd prompt run the updated /services/installservice bat refresh your windows service list to confirm the service has been re installed note if you were running the service under a named account in the log on tab of the windows service, you must reapply those changes open the service txt log file with baretail start the gimmal link enterprise service view baretail and ensure link enterprise activity is being logged