Siebel Analytics Server Administration Guide > Setting Up Disconnected Analytics > Creating the Disconnected Application Configuration File >

Creating the Application Configuration File for Disconnected Analytics

This section contains two examples for you to use when creating your application configuration files in XML format. One is an example of a simple application configuration file structure. In this example, there is one data set for fact table data and one data set for dimension table data.

A second example is of a completed application configuration file.

Application Configuration File Structure Example

The general structure of the application configuration file is in the following example:

Begin Configuration File

Application: My Sales Application

Component Webcatalog: SalesApp.webcat

Component repository: SalesApp.rpd

Component postdbschema: SalesApp.sql

Data

Data set Name: Sales Facts

Table: Facts1

Component sourcing report: facts1 SR

Table: Facts2

Component sourcing report: facts2 SR

Data set Name: Sales Dimensions

Table: ComDims

Component sourcing report: facts3 SR

End Configuration File

Application Configuration File Example

The following example of an application configuration file is provided with the installation:

<remotecfg>

<application name="ServiceRequests" displayname="Service Requests" dir="app">

<webcatalog name="ServiceRequest.webcat" />

<repository name="ServiceRequest.rpd" />

<postdbschema name="SRFlatpostdb.sql" />

</application>

<data dir="data" catalogfolder="/shared/Disconnected">

<data set name=="Service Requests" rank="1" validitytype="date-based" expiry="2003-12-12" syncdefaultfirsttime="true" syncdefaultsubsequenttimes="true" subjectarea="ServiceRequest">

<table name="SRFlat">

<sourcingreport name="ServiceRequest" file="SR_Flat.csv" />

<tablesql name="SRFlat.sql" />

<indexsql name="SRFlatindex.sql" />

</table>

</data set>

</data>

</remotecfg>

XML Tags for Disconnected Analytics Application Configuration Files

Table 22 contains a list of the XML tags used most frequently in application configuration files. All tags and properties must be in lowercase.

Table 22.  XML Tags for Disconnected Analytics Application Configuration File
File Tag
Properties
Values or Description
Type
Optional
<application>
</>
name
Name of the application. This is not exposed to the mobile user
String
No
 
displayname
Display name of the application. This is the descriptive name that is exposed to the mobile user through the Disconnected Analytics Application Manager
String
No
 
dir
Name of the folder under which the application files are stored. Files include the repository, the Web Catalog and DDL files
String
No
<webcatalog>
</>
name
Disconnected Web Catalog name. This Web Catalog is used by the disconnected Analytics Web to store dashboards and reports.
String
No
<repository>
</>
name
Disconnected Analytics Server reads the metadata from this repository
String
No
<postdbschema>
</>
name
Any SQL that will be executed for cleanup and maintenance.
String
No
<data dir>
</>
name
Name of the directory that is used by the Analytics Server to place the data for each user.
String
No
 
catalogfolder
Full path of the Analytics Web Catalog folder that contains the sourcing reports
String
No
<dataset>
</>
name
Data Set name
String
No
 
rank
Defines the order in which the data set is loaded
Number
No
 
validitytype
Required for all data sets. The following is a list of values:
  • date-based
  • rolling-period
Keyword
No
 
start
Gives start date in yyyy-mm-dd format only. Only used if validitytype is date-based. Cannot be set to blank.
Date
Yes
 
expiry
End date of the data set (Only used if validitytype is date-based)
Date
Yes
 
period
Number of period units (Only used if validitytype is "rolling-period")
Number
Yes
 
periodunit
The unit in which the period is defined. Must be one of: "year", "quarter", "month", "week" and "day"
Keywords
Yes
 
dependson
Name of another data set on which this data set depends
String
Yes
 
syncdefaultfirsttime
Synchronizes the data set the first time by default. Values must be True or False
Boolean keyword
Yes
 
syncdefaultsubsequenttimes
Synchronizes the data set every single time. Values must be True or False.
Boolean keyword
Yes
 
syncmode
Available value is online. Users can get data online while connected.
Keyword
Yes
 
forcesync
"yes" causes the data set to be synchronized regardless of whether the user chooses to do so
Boolean keyword
Yes
 
subjectarea
Required for every data set
String
No
<table>
</>
name
Table name in the SQL Anywhere database
String
No
<sourcing report>
</>
name
Name of the analytical query that generates the data
String
No
 
file
This is the file name used for storing data on disk for the given sourcing report. In case the sourcing report is left NULL, then file can be pointed to an external data file on the disk
String
No
<filterables>
</>
 
A child tag of <sourcing report>Specifies a list of filterable columns for each table for the stated sourcing report.
String
Yes
<formula>
</>
 
Child tag of <filterables>. The column in the subject area in which to filter the data.
String
Yes
<tablesql>
</>
name
Name of the SQL file that contains the DDLs to create the tables in the database
String
No
<indexsql>
</>
name
Name of the SQL file that contains the DDL that sets up the indexes
String
No

 Siebel Analytics Server Administration Guide
 Published: 11 March 2004