System Map Files
The logical entity representing a database file, sometimes referred to as a map file in JADE, provides a convenient way of separating the user’s view of data from some of the practical considerations associated with storing that data on disk. (For details about viewing and maintaining class map files, see "Using the Class Maps Browser", in the following subsection.)
The read-only system map files listed in the following table store persistent system objects.
| Map File | Description |
|---|---|
| _jadeapp.bin | Contains JADE development environment application data |
| _jadedef.bin | Default map file for JADE development environment objects |
| _sysdef.bin | Default map file for system objects |
| _sysdev.bin | Contains system meta data objects defined in the JadeSchema schema and JadeToolsSchema schema; that is, the JADE development environment, code coverage, and XML Metadata Interchange (XMI) |
| _sysgui.bin | Contains GUI data for system schemas |
| _sysint.bin | Contains system internationalization data |
| _system.bin | Contains meta data objects defined in the RootSchema schema |
| _systools.bin | Contains meta data objects defined in the JadeMonitorSchema schema |
| _sysxrf.bin | Contains system schema cross-references |
The system files are as follows.
-
JADE development environment system files are _sysdev, _jadeapp, and _jadedef
-
Tools system files are _systools and _monitor
-
Deployment system files are _system, _sysgui, _sysxrf, _sysint, and _sysdef
When deploying a JADE system, you can optionally:
-
Mark development system files offline, if you want to prevent users from using the JADE development environment.
-
Mark development system files offline and do not deploy them, to prevent users from using the JADE development environment. When the JADE development environment is required, put these files in the deployed system and mark them as online.
The separation of runtime and development files is not intended to stop unlicensed users running the JADE development environment but to enhance development mid-release without affecting run time environments. However, if a JADE system had a production (non-development) licence applied, JADE will not allow you to apply a free developer licence. If the JADE system already has a development licence, users can apply the additional development system files.
-
When providing a system to customers, mark the development system files offline and do not include them in the installer. This prevents customers from using the JADE development environment and other tools.
-
When applying JADE patch releases, customers do not need to deploy the development or tools system files, thereby minimizing risk to their deployed system.
Marking _sysdev, _jadeapp, and _jadedef system files offline prevents the JADE development environment from being used.
Marking _systools and _monitor system files offline prevents the JADE Monitor, code coverage, and XML Metadata Interchange (XMI) from being used. For details, see the jdbutilb batch JADE Database utility
The default database map files listed in the following table store persistent objects in your JADE schemas.
| Map File | Description |
|---|---|
| _control.dat | Database control file |
| _environ.dat | Maintains environmental objects (for example, system, session, node, and process objects) |
| _monitor.dat | Used by the JADE Monitor |
| _rootdef.dat | Default map file for user objects (note that this is a user data file) |
| _stats.dat | Used for storing statistics information |
| _userdev.dat | Contains user development-time non-schema data |
| _usergui.dat | Contains user GUI data (for example, skins information and ActiveX controls) |
| _userint.dat | Contains user internationalization data |
| _userscm.dat | Contains user schema definitions |
| _userxrf.dat | Contains user schema cross-references |
