Yes Jennifer, in retrospect, it makes perfect sense... just that during the implementation, when you have to get the guy who wrote the code on the phone to explain what needs to be installed, the documentation is lacking. Steve shared with us a slideshow from a conference that he presented at, that contained a nice visual of a "Typical" Oracle Retail installation. I would recommend that you have some documentation dedicated to Oracle Retail that explains the architecture instead of forcing customers to have half a dozen conference calls with various support engineers/implementation consultants to finally get a clear answer on what to install and where. :)
I think it is more terminology... we have a Unix agent, a database agent, and Oracle Retail Core.. why isn't it called an agent as well? So, when we were trying to ask questions, it was very frustrating.
And then within AE, you have an Oracle Retail Agent that connects to the Oracle Retail Core running on the server.
Everything else has a AE Agent object connecting to the Agent running on the server.
Luckily, someone on your end finally asked, "Did you install the Retail Core?" It's like we were magically supposed to know all the different "internal" terms you use for things.
But, it was a week of huge frustration as, until we got Steve on the phone, no one could tell us what we needed to do.
In the end, it all worked out and we're extremely happy with the results.