Siebel Analytics Server Administration Guide > Setting Up Disconnected Analytics >

Disconnected Analytics Architecture (Server and Laptop)

Figure 14 illustrates the general architecture of Siebel Disconnected Analytics. You will use two different analytics platforms, each with a set of components. One platform is on the enterprise server on your network and one is on the disconnected machine. The difference between the enterprise server components and disconnected server components is that the disconnected components are configured for a single user.

The following list describes the types of graphics in Figure 14:

• Cylinders represent files stored on disk.
• Rectangular text boxes represent processes related to Siebel Analytics.
• Solid single lines with arrows represent the normal flow of data for a Siebel Analytics configuration (on the disconnected machine or the enterprise server).
• Dashed single lines with arrows represent the flow of data during a synchronization operation from the enterprise server to the disconnected machine.

Figure 14.  Disconnected Analytics Architecture

Disconnected Analytics Scenario

Typically, a Disconnected Analytics user logs in to Siebel Analytics Web on the enterprise server, opens the disconnected page, and chooses a disconnected application to download. The Disconnected Analytics Application Manager starts on the disconnected machine and begins coordinating with Siebel Analytics Web (on the enterprise server) to download the disconnected application. Figure 14 illustrates this scenario.

The cylinder labeled Files for Disconnected Applications represents the location on the enterprise server for the disconnected repository, the disconnected Web Catalog, and the SQL scripts associated with the disconnected application. The numbers of the dashed lines in Figure 14 correspond to the numbers in the following list:

1. Siebel Analytics Web on the enterprise server sends a copy of the disconnected repository to the Disconnected Analytics Application Manager which stores the disconnected repository at the appropriate location on the disconnected machine. The Disconnected Analytics Application Manager also changes the Siebel Analytics Server's configuration file (NQSConfig.INI) on the disconnected machine to reference the disconnected repository.
2. Siebel Analytics Web on the enterprise server sends a copy of the disconnected Web Catalog to the Disconnected Analytics Application Manager which then stores the disconnected Web Catalog at the appropriate location on the disconnected machine.
3. Siebel Analytics Web on the enterprise server downloads the SQL Scripts and data files generated from the sourcing queries to the Disconnected Analytics Application Manager. The Disconnected Analytics Application Manager then executes the SQL scripts to create the SQL Anywhere tables and loads those tables from the data files.

If the synchronization operation completes successfully, the user can click the Disconnected Analytics Application Manager's Start button to start the disconnected application on the disconnected machine. Note, however, that although users can download multiple applications to their disconnected machines, they can only run one application at a time. Disconnected Analytics does not support many concurrently running applications. Therefore, starting a disconnected application will result in shutting down any currently running disconnected application.