Dashboard Components Overview
|
|
 |
Dashboard components are discrete elements of functionality, which can be driven by a web data feed or reference a PROIV Task or Function, and are placed into the PROIV Aurora Framework. They can be user-defined or one of the core components shipped with the framework. Their implementations differ depending on their operation, but they are all driven by the same RSS architecture.
Dashboard Components and Desktop Interaction
When a user successfully logs on to PROIV Aurora, the application determines what components the currently authenticated user is allowed to interact with, and then creates a representation of the workspace to render in the browser. See the JAAS Authentication section below for more information.
Once the response to the login has been sent to the browser, the client-side JavaScript executes and processes the model generated by the PROIV Aurora Framework. At this time, only the basic screen display has been sent to the browser. It is the client-side JavaScript which populates the browser through DOM manipulation. Java objects representing the components (and their managers) to be rendered in the browser are created within the server for each Aurora session. The components are based on the Dojo JavaScript toolkit.
The client-side JavaScript uses a remote procedure call mechanism (RPC) to interact with the server-side representation of the component objects via jabsorb, which is a framework which allows you to call Java web applications from JavaScript code.
As part of the browser-side implementation of PROIV Aurora, the client-side JavaScript processes the model to obtain the components structure. Each component then asks for its data from the Aurora server (via jabsorb) and subsequently renders it. Once all the components are rendered, the user can interact with the desktop.
Section Links
Topic ID: 810005