Installing OFML data |
  
|
Installing OFML data |
|
The pCon.update DataClient can be used for the installation and the update of OFML Data. The DataClient determines automatically which files need an update and only loads down the actual needed files. During the installation the dependences of the OFML series are regarded.
That the DataClient can identify and update correctly existing OFML Data some specifics has to be noted:
Before being able to update your OFML Data with pCon.update, please check the following points:
•There must be at least one application which can process OFML Data, otherwise the pCon.update DataClient refuses to install the OFML Data.
•If there are no OFML Data on your system yet, you can now directly install OFML Data with the DataClient. If necessary, the DataClient requests the directory in which to install the OFML Data. This request is done only once, the directory cannot be modified later any more.
•If OFML Data are already available on your system, you have to run the program pCon.update Migration once before using the pCon.update DataClient. This program prepares your installations for pCon.update. (On some rare occasions, using pCon.update Migration is not necessary. Your OFML Data installation program provider informs you of these exceptions.)
If you want to use pCon.update to update your OFML Data, you can continue to install OFML Data with CDs. Please note, however, that these CD installations are only compatible with pCon.update if they carry the Web Enabled logo.
|
Web Enabled logo |
If you use installations without this logo, your system will not be compatible with pCon.update any more. In many cases, compatibility can be restored by executing pCon.update again. However, some cases require manual intervention.
Furthermore, it is recommended not to install OFML Data manually because pCon.update does not recognize manually installed data.
The following paragraph provides technical information on how to install OFML Data with pCon.update. This information is intended for advanced users and can, for example, facilitate troubleshooting.
When using pCon.update, OFML Data are installed as follows:
All OFML Data are located in a central directory which is collectively used by all applications. The directory can be either located locally or on a network drive. Excluded are OFML libraries of the namespaces ::egr and ::ofml, which are further located in the application directories.
The installation database serves to recognize which OFML libraries are installed in which version. If no or an incomplete installation database is available, existing OFML Data are not recognized. The installation database is located in the file install.db in the data directory.
All data licenses (DLMs) are located in the subdirectory dlm in the data directory. Excluded therefrom are only program-specific DLMs such as obk*.dlm as well as DLMs of the libraries with the namespaces ::egr and ::ofml.
All data profiles are located in the subdirectory profiles in the data directory. For each manufacturer exactly one data profile must exist. The data profiles are to be named with the file extension .cfg like the DSR key manufacturer.
The data profiles are collectively used by all applications. If individual series should be loaded in certain applications only, this can be implemented by using the DSR key visibility (from DSR version 2.16.0 on).
The [libdef:] section is not to be used any more in the data profiles. The [libdef:] section is obsolete, if the dependencies of the packages are sufficiently maintained.
Excluded are the data profiles of the namespaces ::egr and ::ofml, too. These data profiles are located in the application directories and are also allowed to use the [libdef:] section.
The data profiles are registered within the file default.profiles, which is located in the subdirectory profiles in the data directory. The file default.profiles contains only the key app.gf.data.profile, which lists the data profiles to be loaded. Within the file etc/startup.cfg in the particular application directories the file default.profiles is referenced within the key app.gf.data.profile.registration.
According to that, the registration of the data profiles is done concertedly for all applications. If a manufacturer should not be loaded in all applications, the DSR key visibility has to be used.
Excluded are the data profiles of the namespaces ::egr and ::ofml, too. Since these libraries are located within the application directories, their data profiles have to be registered in the file etc/startup.cfg of the particular application within the key app.gf.data.profile.
It has to be made sure in the applications by respective entries in the file etc/startup.cfg that the OFML Data in the central data directory are used.
