This content has been marked as final. Show 4 replies
EAC uses soap. I think.
So any thing you do which results in communications between different Endeca components uses soap.
Treat this as you would any http status of 404. Which in most cases is the http server running, but the appliication not being found. In this case it is the WSDL which is not being found.
The ATG integration exports data into Endeca via CAS Record Stores. These Record Stores are created via the Deployment Template Module for Product Catalog Integration. Did you use the Deployment Template to deploy the appropriate Endeca application and then run the initialize_services script in the deployed Endeca app?
You will need to start three RecordStore components on the CAS:
./component-manager-cmd.sh create-component -n ATGen_en_data -t RecordStore
./component-manager-cmd.sh create-component -n ATGen_en_schema -t RecordStore
./component-manager-cmd.sh create-component -n ATGen_en_dimvals -t RecordStore
It is better to use product catalog template, it created all these components.
Edited by: Narinder Garg on Nov 11, 2012 9:43 PM
Edited by: Narinder Garg on Nov 12, 2012 12:29 AM
In case of ATG, You can also check in DataDocumentSubmitter.properties file: endecaBaseApplicationName=app_name_without_en