Understanding the TXT Driver Dialog Box, Version 4.6.6.6


This is the maintenance dialog box for the TXT Driver, featuring a set of icons on the toolbar with functionalities akin to those found in other PIS components. The initial icons allow for the external saving of the Driver.


Following these are five icons corresponding to various maintenance tasks for the Driver within the metadata. Two icons represent different methods of listing metadata, while the "Refresh List" button updates the list, and the "Presentation and Filter" button facilitates the presentation and filtering of existing Drivers.



Concerning the data required for the TXT Driver, it is relatively minimal, as elaborated upon in the preceding video. However, it's essential to underscore the significance of specifying the file location.


There are two areas designated for inputting the file location: the first when the "Front Server" checkbox is unchecked, and the second when it's selected. The distinction between these two areas is pivotal. To grasp this concept comprehensively, let's revisit the slides to elucidate the functioning of the directory where CSV files are stored.


In the scenario where all PIECE components are installed on the same machine, configuring the driver properties with the "Front Server" option unchecked and specifying the directory as "C:\temp" results in the metadata recording the file location as "C:\temp" on the hard drive. Consequently, when the process is executed, the server retrieves the directory path from the metadata and searches for it on its own hard drive.


Now, consider a different scenario where the client's hard drive contains the "C:\temp" directory, but the server's doesn't. In this case, if the server attempts to locate the directory based on the metadata, it will fail. Conversely, if the situation is reversed, and the client's hard drive lacks the directory, but the server's has it, the process will succeed.


So, what's the purpose of the "Front Server" option? Imagine the server as a cloud instance, where you lack direct access to its machine. Despite this limitation, there exists a mandatory directory called "Properties."


This directory serves as a physical folder, and while its complete path may not be known in advance, a relative position is ascertainable. By selecting the "from server" option and choosing a path like "//Public//Test," you're instructing the driver to search for files under the "Properties" directory and the "public test" subfolder.


But how do you know what folders exist under the "Properties" directory? If you click "Select," an Explorer-type dialog box appears, allowing navigation of the server's directory structure, always starting from the "Properties" directory.


In conclusion, when you select a path with the "from server" option unchecked, the focus remains on the server's hard drive. However, when you enable the "from server" option, you're leveraging the existence of the "Properties" directory on the server, even without direct access to it.


This flexibility enables the selection of a server location without necessitating remote access to the server machine. By understanding and effectively utilizing these functionalities, seamless integration of file locations into the PIECE environment is achievable.