Oracle^® Business Intelligence Disconnected Analytics Administration and Configuration Guide > Preparing Applications for Oracle BI Disconnected Analytics > Step 3: Creating and Storing the Disconnected 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 Step 2: Creating and Testing Tables and Indexes in the SQL Anywhere Database this would be D:\OracleBIData\Disconnected\Retail\app. For a description of disconnected directories, see Step 1: Understanding the Directory Structure for Oracle BI Disconnected Analytics.

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

• Identify a machine to test the disconnected repository. This machine can either be an network server or a laptop.
• Install the Oracle BI Disconnected Analytics client on this machine. The installation creates a disconnected version of the Oracle BI 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 Oracle BI Server by updating the NQSConfig.INI file to point to the disconnected repository. For more information about the elements in the NQSConfig.INI file, see Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
• Use the Oracle BI Disconnected Analytics client to connect to the server (the default DSN name is Analytics Web) and view the schema.

  CAUTION:  Do not try to use Oracle BI Interactive Dashboards 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.