Details
| Participant | Role | Time Spent | Comments | Latest Comment |
|---|---|---|---|---|
| Author & Moderator | 31m | 5 | because it might not always contain such things, now its fin... | |
| Reviewer - 3% complete | 1m | |||
| Reviewer - 0% complete | ||||
| Reviewer - 0% complete | ||||
| Reviewer - 100% complete | 40m | 9 | this method call is unnecessary here | |
| Total | 1h 12m | 14 |
- Files: 18
- Linked Issue:
Objectives
The installer for the Tomcat policy agent changes the default Tomcat classloader behaviour. The setclasspath.sh script is updated so that all of the tomcat class files are included on the CLASSPATH manually. The standard Tomcat bootstrap behaviour is disabled. This causes problems with class loading in applications and breaks the whole Tomcat class loading module. The PA cannot break/change core tomcat behaviour as part of it's installation.
The solution is as follows:
$TOMCAT_HOME/bin/setclasspath.sh
remove this line, . "/opt/soft/tomcat6/bin/setAgentclasspath.sh"
then copy the following from the J2EE Policy Agent directory:
cd $TOMCAT_HOME/lib
cp $J2EE_PA_HOME/locale/* .
cp $J2EE_PA_CONF/Agent001/config/* .
cp $J2EE_PA_HOME/lib/agent.jar .
cp $J2EE_PA_HOME/lib/openssoclientsdk.jar .
TOMCAT_HOME points to where Tomcat is installed and J2EE_PA_HOME points to where the J2EE PA zip file was extracted. J2EE_PA_CONF is where the J2EE Policy Agent configuration was created; eg: /opt/j2ee_agents/tomcat_v6_agent/Agent_001/
The tomcat installer and uninstaller all needs work to resolve this issue.