This content has been marked as final. Show 5 replies
Would you just have a switch join? What do you mean by 8 different "applications"
If all the data is just unioned together, you can use CAS (follow the pattern in the product catalog integration module for the deployment template)
If you have more complex joins, alternatively you can do the join in the database which can have a perf benefit over joining in forge.
If you're going to ultimately use 1 MDEX, it doesn't seem like you want to go down the path of 8 different "applications"
Create a database "view" which does all the work of getting the data from the 8 different tables. Now getting the data into Endeca should be simplier.
Thanks for a quick reply!
Yes, creating 8 applications doesnt seems a good idea and I am more focussing on the second approach -
"Create a pipeline with 8 record adapters that fetch the data from tables and then I will do a switch join and provide it to mapper"
Do you foresee any issues in the above approach?
I am less familiar with how CAS works at the moment. Can you please guide me to the correct document or just brief the approach you suggested.
Thanks a ton for your reply!
The quick start guide that Saleh refers to is definitely the best starting place. Then also check out the doc for the product catalog integration module : http://docs.oracle.com/cd/E35827_01/ToolsAndFrameworks.310/pdf/ProductCatalogDTGuide.pdf