OVERVIEW
Caliach Vision has essentially three parts two it:
- Omnis Studio Executable – the program that runs on the computer.
- Caliach Vision Library – Caliach’s program interpreted by the executable above.
- Datafiles – that contain all the business data collected and generated in Caliach Vision operation.
In a multi-user environment, the data, of course, must be held on a central server so it is common to all users and the technology (network/server) must be capable of handling potential conflicts between users. Typically, 1 and 2 above are loaded onto the user’s computer with the datafiles on a server, but other configurations are possible in the right circumstances.
With V5 onwards, database connection depends on the client-server connection mechanism of the server engine involved. Prior to V5 there are two methods available to connect to the datafiles to accommodate different mixtures of user operating systems:
- Direct Attachment – this is simply connecting using the standard operating system file system and requires that the server operating system can handle the byte-range locking needed for corruption-free operation. Typically, this is when not using mixed machines, like Mac and Windows, or mixed operating system versions in the case of Macs alone. This is very easy to implement.
- Omnis Data Bridge (ODB) – with this method a separate program operates as a service on the server to handle interconnection between users and the datafiles, completely outside the server file system. The ODB service handle all record locking centrally and communications with users is by TCP (the networking communications of the Internet).
NOTE: You cannot reliably mix these two methods of connections. Either ALL users are on the Direct Attachment method, or ALL are on the ODB method.
Whichever, connection method you are using, this File Path Status window will list all the connections that the operating Caliach Vision is, or can, make to external files. The Path is the term used for the hierarchy of drive, folders (directories) and file expressed as a line of text with a character separating the levels. Depending on whether you are running on a Windows, Mac or Linux machine these are : and / respectively.
With the ODB specifically, the path to the datafiles will is different as it is not an file system path. It will appear in the form:
odb://192.168.1.68:5813:MainDataODBName
The “odb://” indicates and ODB connection followed by the IP address and port of the server followed by the ODB name of the datafile (set in the ODB config.xml file).
The first few entries in the File Path Status list cover the locations of the Omnis Studio executable, Caliach Vision library and other libraries that are open and the main data file (and segment) connections. Thereafter, the lines are reporting all the additional folders and files that the program needs to be able to access or could need to for particular functions. There are many optional configurations for these other files that can apply depending on the choices made. For example, the Extras folder containing the Caliach license and strings files can be held either locally to each user or centrally on the server (making re-licensing more manageable, for instance). The File Path Status analyser looks at all these optional locations and reports their status, so if some are shown not to exist, that doesn’t mean that anything is necessarily wrong – it depends on context.
The File Path Status list has three indicator columns as follows:
| Column name | Yes | No (X) |
| Connected now | This indicates whether the program is currently connected to the file. Many ancillary files are only temporarily accessed and then their data is held in memory so Connected now may not strictly be true in a technical sense but it indicates that the connection has been made and the data read, for example, Terminal settings and Caliach license files. | This indicates that the item is not currently connected. Folders, of course, cannot be connected to as such so are always X |
| Can connect | This normally indicates that the item can be seen by the program and therefore can be connected to. In some cases, such as functional additional datafiles and upgrade files are tested to see if connections are possible. Other than that, no test is made of whether the user has file/folder privileges to read.write files. | This generally means that the user program cannot “see” the item in the file system. |
| Exists | The folder or file exists on the file system by the program. | The folder or file cannot be “seen” by the program in the file system. |
NOTE: In the File description column, the term on server refers to the file or folder located centrally, either by being alongside the datafiles, or in the case of ODB datafile connection in the DirectPath. The term locally implies that the file or folder is in the user’s Vision library folder.
File Path
File > System Manager > Monitor window > click on the File Path Status button
This file path takes you to the File Path Status window.
Your Direct Path is:
The path to the first segment of the main datafile you are attached to. If prefixed with “odb://” you are using the Omnis Data Bridge.
Results List
Shows all operating system files that are, or could be, used in operations, excluding any for custom Features or manually selected import/export/printing files.
Refresh button
Click to refresh the status of all files.
| See also: | System Monitor |
Compiled in Program Version 6.00. Help date last modified on 28 November 2023.
Class wfilepathstatus (File Path Status) last modified 25 May 2022 FP: File > System Manager > Monitor > File Path Status button
