Installing ClassiX® simply means executing the setup program. It provides two setup types, "Complete installation" and "Network installation" (you will find a description of these types further below). The following directory is the result of a Complete installation:
| ClassiX® System Root Directory | |
| root directory of the project "Evaluate" (or of a customer/mandator) | |
| AppsWarehouse | |
| required system files and print layouts etc. to import | |
| universally exported transaction descriptions and business processes | |
| project-specific transaction description and business processes | |
| universally exported report tool print layouts | |
| project-specific report tool print layouts | |
| universal QA test framework files | |
|
|
project-specific test files |
| project- / customer-specific modules and derivations | |
| binary files (.exe, .dll) | |
|
|
DLLs from version 4.4 |
|
|
ACE and TAO-DLLs (Corba interface) |
|
|
in case of a ClassiX program crash, all these files create so-called stack traces |
| Bitmaps, Icons | |
| Icons with 16x16 pixels | |
| Icons with 20x20 pixels | |
| project- / customer-specific bitmaps | |
| local customer-specific help files in HTML format | |
| InstantWeb files | |
| InstantWeb libraries | |
| project- database, -start batch files, -main menu file, -changes_log.xls | |
| data that has been imported by the customer (data from the old system, minutes of meetings) | |
| system files | |
| project- / customer-specific system files |
You have specified the root directory name during installation; 'CLASSIX' is default option of the installation program. Names of the other directories shouldn't be changed to not prevent ClassiX® from finding specific components.
A complete setup covers the entire ClassiX® System with online help and documentation. This setup type helps installing a stand alone system on the one hand, for example for an evaluation or test system, running completely with its own database. On the other hand, a complete setup can be used as a server setup, which then provides the ClassiX® System, the documentation and the database for the users (clients). A stand alone installation looks as follows:

All client computers require this setup type to access ClassiX® on a server. A Network installation only includes the ObjectStore client and several links to the ClassiX® application start on the server. This certainly requires a complete installation on the network server. A network installation combined with the complete installation on the server looks as follows:

This setup type is not yet supported by the setup program. Here, ClassiX® and the database are installed on separate servers. This setup type is suitable for large setups (50 and more clients). The exact configuration of distributed components can be controlled easily, making it possible to swap online help and documentation on a separate server. The recommended configuration looks as follows:
