Scanner Setup for Outlet

In an Outlet environment, two or more Outlets may choose to share an Apache server in order to reduce costs for hardware assets. This is easily done since Apache has a great deal of capacity, and can service multiple Web Listeners without taxing the server.

However, because there is data that is not shared between Outlets, scanning tickets at Outlet B presents some interesting challenges when web sales are resident at Outlet A.

If Outlet B wants to sell tickets online, they can choose to not have a web site and allow Outlet A to sell online under Outlet A. If that is the case, the tickets appear as part of Outlet A's sales (and therefore may be subject to commissions). This also means that Outlet B cannot scan tickets for their events.

The only way to accomplish scans at Outlet B is to have a Web Listener dedicated to Outlet B and setup scanning either for

• A single domain (using a separate Apache server for each Outlet), or
• A common domain (using a common Apache server for multiple Outlets), and set separate web sales folders for each Outlet.