The following diagram visualizes the overall architecture of One™ and its operational environment. In this picture several different flows between end users and One™ components can be distinguished:

1. Portal users can request One™ trading portlets. These HTTP(S)-based requests pass through the web server and then enter the portal server, which in turn will forward the requests to various portlets. The portlets will communicate with the trade execution engine to retrieve current status of the trade. The trade execution engine can either be the One-TradeEngine™, or a trade exectution product of a third party.
   
2. Portal users can also employ One ™ display portlets. These requests similarly pass through the web server and the portal server to end up with the various display portlets. These portlets may communicate directly with the One-DateEngine™ to retrieve data.
   
3. When portal users-request One™ Display portlets, streaming date updates will automatically be requested from the user's browser. These HTTP requests pass via the web server directly to the One-DataEngine™