Resolution:
Description:
============
After the installation of a hotfix package, Policy Agent, where custom policies have been implemented, fails to start up.

Environment
========
TIBCO ActiveMatrix(R) Policy Agent 3.1.0
  
  
Symptoms:
========
Start up of Policy Agent fails with an error which indicates the Custom Policy is defined in the list of actions but the system does not recognize it as a type of action.

======= Sample Error Trace
Error communicating with the intermediary.
The error was: The service started at http://policymanager:8981/eProxy/agent/agent/ can not be secured. It will not be activated: com.amberpoint.util.soa.utils.SecurityConfigurationException: Errors trying to secure service endpoints Found 19 errors and 0 warnings. ERROR:The element "ap:CustomLDAPAuth" was found in a list of actions. The system does not recognize this as a type of action. Check the spelling and namespace of this element to make sure it is correct. at node: /ap:compositeConfiguration[1]/ap:webServiceConfiguration[37]/ap:operationEvents[1]/ap:operation[1]/ap:input[1]/ap:receive[1]/ap:CustomLDAPAuth[1] ERROR:The element "ap:CustomLDAPAuth" was found in a list of actions. The system does not recognize this as a type of action. Check the spelling and namespace of this element to make sure it is correct. at node:
========


Cause:
=====
The hotfix installation process removes custom policy archive (jar) and entries in allmodules.xml .


Resolution:
==========
Restore these two files from a backup to the version/revision that existed before applying the hotfix.

* Custom Policy archive (Jar)

* <PA_Home>\instances\agent-<port>\tomcat\webapps\eProxy\WEB-INF\application\resources\allmodules.xml

Restart the Policy Agent.

After the installation of a hotfix package, Policy Agent, where custom policies have been implemented, fails to start up.