Application Configuration File
The following is an example of a generated configuration file.
<?xml version="1.0" encoding="utf-8" ?> <configuration> <configSections> <section name="joob" type="JadeSoftware.Joob.Configuration.JoobConfigurationSection, JadeSoftware.Joob" /> </configSections> <connectionStrings> <add name="myDefault" providerName="JadeSoftware.Joob.JadeConnection" connectionString="DataSource=C:/Jade7009/system/; ConfigFile=C:/Jade7009/system/jade.ini; SingleUser=False; Schema=BankingViewSchema; Application=DotNetConnection; IntegratedSecurity=true"></add> </connectionStrings> <joob defaultConnection="myDefault"> <installation directory="C:\Jade7009\bin" /> </joob> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/> </startup> </configuration>
Within the <configSections> element there is a joob section, which defines the JADE configuration and is required if you intend using JADE configuration parameters. Within the joob section are a number of options that enable you to customize your application.
In the <connectionStrings> section, specify the JADE database to which the connection is to be established. The <add> sub‑element has a connectionStrings attribute, which contains a series of comma‑separated values that define connection attributes for the JADE database.
-
DataSource. The location of the folder containing the database control file (_control.dat).
-
ConfigFile. The full path name of the JADE initialization file.
-
SingleUser. True or False, depending on the mode in which the database has been opened. The default value is False.
-
Schema. A user schema in the database.
-
Application. An application defined in the database. The default value is RootSchemaApp.
-
IntegratedSecurity. True or False, depending on whether the connection uses the current Windows identity established on the operating system thread to log on to JADE.
The default value is True. If you specify False, you must add UserName= and Password= values.
Specifying an application causes the JADE
Specifying an application causes the JADE initialize and finalize methods defined on that application to be invoked. (The default application, RootSchemaApp, does not have initialize or finalize methods defined.)