O3 Browser has an architecture that enables it to be executed in two different ways:
- Desktop (Client/Server): Installed in a PC or workstation using O3 Browser as a client of O3 Server, to which it logs on to be authenticated and open the cube you wish to analyze.
- Standalone: Independent execution, installed in a PC or notebook with no access to O3 Server.
In this mode, the user uses O3 Browser to open cubes local to their PC, or maybe in some shared LAN location.
Depending on the type of licensing purchased, you may count on one or both execution modes in the same installation.
Standalone Execution Mode
In Standalone Execution mode, cubes or views are processed locally in the client. All queries are handled locally by O3 Browser. This execution mode is ideal for mobile users, as they may install a copy of the cube in their PC or personal notebook.
This mode is not recommended for use within a local network, as cube administration, their updating and size may require more attention than expected.
Unlike the client / server execution mode, Standalone only counts on the resources of the equipment where it is working, which may be insufficient to work with large-sized cubes.
Desktop Execution Mode (Client/Server)
In client / server execution mode, O3 Browser works as a client of O3 Server, which operates as an engine, dealing with the queries made by the user and sending the result to O3 Browser, so that such component adds the necessary processing at the time of presenting information to the user.
Communication between O3 Browser and O3 Server is established through OTP protocol.
In order to work in client / server mode, after starting O3 Browser, the user must log on to O3 Server using the option "Open" in the "File" menu. After identifying themselves, the user receives the list of cubes he can access, according to the previously defined security policy.
Some of the advantages offered by this execution mode are:
- Ease of administration, either in the publishing or updating of the cubes as they are used in a centralized manner.
- Cube access control, with the possibility to restrict information checked by different user groups.
- Improved performance, as a result of using the server's resources.