Siebel Analytics Server Administration Guide > Setting Up Disconnected Analytics > Creating and Storing the Disconnected Analytics Repository >

Testing and Storing the Disconnected Repository

Test the disconnected repository, and then store it in the disconnected application metadata directory for the appropriate application. For the retail business scenario in Creating and Testing Tables and Indexes in the SQL Anywhere Database this would be D:\SiebelAnalyticsData\Disconnected\Retail\app. For a description of disconnected directories, see About the Disconnected Directory Structure.

The following is a list of high-level steps that you might use to help you test your disconnected repository:

• Identify a machine to test the disconnected repository. This machine can either be an network server or a laptop.
• Install the disconnected client on this machine. The installation creates a disconnected version of the Siebel Analytics Server that is scaled for single use.
• Create the disconnected database on this machine by using dbisqlc.exe to manually create the tables.
• Deploy the disconnected repository on the enterprise server by editing the nqsconfig.ini file to point to the disconnected repository. For information on the NQSConfig.INI file parameters, see Siebel Analytics Installation and Configuration Guide.
• Use the disconnected client to connect to the server (the default DSN name is Analytics Web) and view the schema.

  CAUTION:  Do not try to use Siebel Analytics Web yet.

• Run a sample logical SQL report based on the Presentation layer. No data will be returned because you have not populated the tables. However, this task allows you to test the integrity of your repository.