Question,

We upgrade from AVP 5.1 to AEP 7.0 last year.

We converted all the apps with Orchestration Designer, but still have an issue with error handling of SOAP messages.
I found out this started when we switched from AVP 5.1 to AEP 7.0.

I suspect we are missing certain .jar files or components that can handle SOAP exception correctly.
In the documentation of 7.0 there reference of what should be there, if you check out the 7.1 / 7.2 Getting Started document they are stating the below page 17 in the document. However they state "Some Examples Are"??? bit strange they should give you the full list to make it clear.
----------------------------------------------
***Remove Older Jar files after upgrade. After upgrading, ensure that you do not have old versions of jar files on the application server: Some examples are:
commons-httpclient-3.1.jar
commons-logging-1.1.1.jar
log4j-1.2.15.jar
wss4j-1.5.8.jar
---------------------------------------------------

Does anyone have an overview of what files should be present on the Tomcat server Lib directory?
And what should be available in Orchestra Designer?

Kind regards,

Dirk

If you use the export wizard in the OD Eclipse environment to export the runtime support package, the resulted zip file will give you the whole list of the files you need to deploy onto the Tomat's lib directory. Also if you are running Axis 1.4 for your previous web service operations, you would need to specific the Axis 1.4 option in on of export wizard steps.