Siebel Business Analytics Server Administration Guide > Setting Up Mobile Analytics >

Mobile Analytics Architecture (Server and Laptop)

Figure 16 illustrates the general architecture of Mobile 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 mobile machine. The difference between the enterprise server components and mobile server components is that the mobile components are configured for a single user.

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

• Cylinders represent files stored on disk.
• Rectangular text boxes represent processes related to Siebel Business Analytics.
• Solid single lines with arrows represent the normal flow of data for an Siebel Business Analytics configuration (on the mobile 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 mobile machine.

Figure 16. Mobile Analytics Architecture

Mobile Analytics Scenario

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

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

1. Siebel Business Analytics Web on the enterprise server sends a copy of the mobile repository to the Disconnected Analytics Application Manager that stores the mobile repository at the appropriate location on the mobile machine. The Disconnected Analytics Application Manager also changes the Analytics Server's configuration file (NQSConfig.INI) on the mobile machine to reference the mobile repository.
2. Siebel Business Analytics Web on the enterprise server sends a copy of the mobile Web Catalog to the Disconnected Analytics Application Manager. Shared content from the Web Catalog on the enterprise server is merged with the mobile Web Catalog and is stored in the mobile Web Catalog at the appropriate location on the mobile machine.
3. Siebel Business 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 mobile application on the mobile machine. Note, however, that although users can download multiple applications to their mobile machines, they can only run one application at a time. Mobile Analytics does not support many concurrently running applications. Therefore, starting a mobile application will result in shutting down any currently running mobile application.