log4j Update

1min
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
﻿
SAP Code Vulnerability Analyzer (CVA)