This KB includes the instructions on how to remove log4j.jar from Web Agent Option Pack (WAOP) since it is not used by the Federation Web Services
WAOP 12.52.x
There are 2 options to remove the log4j.jar from Web Agent Option Pack(WAOP) as follows:
OPTION1: In case of existing Deployment of affwebservices.
1. Stop the running affwebservices (WAOP) application from its deployment.
2. Navigate to affwebservices/WEB-INF/lib
3. Find log4j.jar and remove it.
4. Start the affwebservices application.
5. Make sure http://fqhn:port_number/affwebservices/assertionretriever is working fine.
For example:
http://myhost.ca.com:81/affwebservices/assertionretriever
If FWS/affwebservices is operating correctly, the following message is displayed:
Assertion Retrieval Service has been successfully initialized.
The requested servlet accepts only HTTP POST requests.
OPTION2: In the case of new deployments of affwebservices.
1. Stop the running affwebservices (WAOP) application from its deployment.
2. Un-Deploy the affwebservices application from the deployment.
3. Navigate to affwebservices folder that came with the installation of WAOP.
4. Go to affwebservices/WEB-INF/lib
5. Find log4j.jar and remove it.
6. Re-Create the affwebservices.war file as per WAOP documentation.
7. Deploy the affwebservices application to the location from where you have un-deployed at step 2.
8. Start the affwebservices application according to the deployed server.
9. Make sure http://fqhn:port_number/affwebservices/assertionretriever is working fine
For example:
http://myhost.ca.com:81/affwebservices/assertionretriever
If FWS/affwebservices is operating correctly, the following message is displayed:
Assertion Retrieval Service has been successfully initialized.
The requested servlet accepts only HTTP POST requests.