Creating of XML application

To create a new application click on the button Create New Application (or right-click on Application and choose an item New application).
To modify the existing application click on the button Modify Application (or right-click on the application name and choose Edit item from pop-up menu).
After that, select a proper platform in dialog box Select platform. When you select platform and click OK the following dialog box will open.

Application name

Name of new application.

Appl. description

Description of application, it can be used in print outputs.

DB Driver, Engine name

Database access driver. As regards XML application it is omitted.

Startup

Way of application start up:

• Automatic - application will activate during an operation system starting up
• Manual - application must start up manually through the process D2000 Application Manager
• Disable - starting up of the application is disabled

Path for executable

Path pointing to process D2Start including parameters that will be given to process D2000 Server.

Allow service to interact with the desktop

Makes the processes D2Start and D2000 Server visible on the desktop.

Note 1: After the application with configuration in XML files is created the subdirectory "SysCfg_XML" will be automatically created in the application's directory.

Note 2: Name of application is allowed to be changed only when the new application is being configured. In case of modifying the option is disabled.

After the new application has been created the dialog window for archive configuration is opened.

Embedded system

An Embedded system is D2000 system without connection to a database. When it is starting it loads a configuration in the form of XML files. This configuration may be acquired by action XML Export of complete configuration from D2000 CNF. A directory SysCfg_XML is created. It must be copied to a directory of an application which will be started as Embedded system.

The changes of D2000 System configuration are not persistent.

All the actions which started the SQL commands generate the errors when they are trying to read or write data into database:

• creating, deleting, renaming and editing of the objects
• automatic configuration of bitmaps
• XML Import
• editing of a dictionary
• other changes of configuration

Other implications:

• a log database does not exist
• a history of object changes is allowed neither to import nor export (there is no connection to database)

Warning: Embedded system does not work for Thin Client and JAVA applications.