MarketWide Architecture
- Former user (Deleted)
- Alex Burns (Unlicensed)
- Former user (Deleted)
MarketWide System Architecture
Clients connect to the host through the internet or local network. The host then connects to the client's database through the local network connection. Query results are maintained on the host, until requested by client.Â
MarketWide Host Architecture
The Transaction Server and the Report Server on the MarketWide host runs as a service on either a single machine or multiple networked machines. Communications between the host and the client are done using TCP/IP, through a configurable port.
Transaction Server
The Transaction Server Acts as the host's "traffic cop". It will accept user requests, dispatch tasks, manages saved queries and result sets.
Report Server
The Report Server connects to the database through an OLEDB connection. It also runs SQL tasks/queries and performs campaign segmentation.
MarketWide Client Architecture
The MarketWide client is a Windows-based, "thin client" application (no database connectivity layer). Campaigns and reports are launched from the MarketWide Main Window as separate windows executables.
