Automation of data loading, batch

If you use drivers in the Palstat system that enables manual importing of data into the system, eg. InSpec, Q-DAS, Impact, Trimos, Kern or one of the others, it is possible to automate this process by applying  the following procedure.

This procedure is intended for IT administrators and only they should apply the procedure.

1. You have obtained or already have a driver named "Palstat.Drivers.*.Dll" from Palstat (driver nam in place of the asterisk)
2. Retrieving data. Wait a few seconds and try to cut or copy again.
3. In the ./CONFIG/SCHEDULER directory, rename SMSpclmportDriver.xml.example to SMSpclmportDriver.xml, the file defines which drivers are to be processed and in which path t search for data files. The sample xml file is set for the Q-DAS and INSPEC driver. In the case of automation of another driver it is necessary to know what to insert in the "Driver" parameter. Next, edit the "Path" here, ie where data automation is to be loaded, it must be loaded to the Palstat./PROCESS/DATA directory. Furthermore, the "Mask" parameter defines which extension is to be processed. Sample file below.
4. Rename the sample batch ./PROCESS/batch.data.process.bat.example to batch.data.process.bat
5. Edit the batch, find the value DEBUG=false  at the beginning of the batch and set it to DEBUG=true, the batch will not import anything, but will display all settings, check the basic parameters. It must not be terminated with the ERROR status, in this case see which step in the batch does not pass the inspection conditions and make an adjustment ot contact the Palstat s.r.o service department. After successfully testing the batch, return DEBUG=false
6. Test the batch run directly from the command line and try to import the sample data you have in ./PROCESS/DATA directory. Caution, the process will also process subdirectories!!! Therefore, fill the DATA directory with nothing other that the files you want to process. The script may run longer or behave unexpectedly.
7. Check the import result.
   • Imported data must be found in the Palstat system.
   • The batch moves the imported data to the ./PROCESS/DATA_IMPORTED directory
   • The import process is logged in ./PROCESS/LOG
8. After successful testing, set the batch scheduler in the task scheduler. Pay attention to the user under which the batch will be run. In most cases, it is advisable to run as a user SYSTEM. Start at the required interval, it is recommended every hour. It is not advisable to run the batch too often.
9. End the whole process by manual start from the scheduler and evaluate according to point 7.
10. We recommend checking the LOG directory from time to time , it is erased after 30 days according to the batch settings.

example file SMSpcImportDriver.xml

<?xml version="1.0"?>
<Settings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <Batches>
    <Batch Name="LINE1" Driver="Q-DAS" Path="D:PalstatPROCESSDATA" PartPrefix="" Mask="*.DFQ" Enabled="true" />
    <Batch Name="LINE2" Driver="INSPEC" Path="D:PalstatPROCESSDATA" PartPrefix="" Mask="*.TXT" Enabled="false" />
  </Batches>
  
  <Regulation>1</Regulation>
  <UseLastRegulation>false</UseLastRegulation>
  <DimensionSampleSize>1</DimensionSampleSize>
  <DimensionCardSize>25</DimensionCardSize>
  <ControlLimitsPp>1.33</ControlLimitsPp>
  <AutoCreateParts>true</AutoCreateParts>
  <AutoCreateDimensions>true</AutoCreateDimensions>
  <RenameFiles>true</RenameFiles>
  <DatabaseId></DatabaseId>
</Settings>

Successful testing in DEBUG mode	Error status: