net use d: \\server\share /user:Accounts\User1
Harddisk receive channel
The harddisk receive channel allows the connection of a directory on a hard disk. Files from the stored directory are imported as messages into eBiss and placed in the messagebox (incoming).
Note: A Harddisk receive channel lends itself to be monitored with the File event listener.
| Properties | |
|---|---|
| Name | Description |
| Name | The name of the channel |
| Channel type name | The Type of the channel |
| Message direction | For receive channels the direction of the received message (but require also for send channels) |
| Message box | The message box |
| Public | True if the channel should be visible in the sub node |
| Input path | Path of the input directory on the hard disk, e. g. C:\eBiss_Test\Harddisk\Receive or. \Harddisk\Receive |
| Input file mask | Here you can define a mask to be used for importing only certain files, e. g. *. dat. |
| File handling | Move: Move the original message file to the specified directory (also specify file name). Copy: Copy the original message file to the specified directory, also specify file names. Delete: Delete original message file. none: Do not perform any action. |
| Move to path | Path of the storage directory on the hard disk, e. g. C:\eBiss_Test\Harddisk\Messages or. \Harddisk\Messages |
| Move relative to file directory | Move relative to the fetched file path, which can differ from the input path, e.g. in case of case of sub directories or file mask. |
| Dir mask | A mask to fetch sub directories, e.g. L.*/INVOIC/ will find directory L1/INVOIC, L_20/INVOIC, etc. |
| Fetch sub directory levels | The number of subdirectories that are read in exclusive lock mode during a read cycle.. See also optionLockExclusive. |
| Change logs | The changes to the element are logged. The logging is activated in the System settings, which is possible if a versioning license is available. |
| Properties (advanced) | |
| Name | Description |
| Sender validation | How the sender address should be validated |
| Default sender | The default sender |
| Recipient validation | How the recipient address should be validated |
| Default recipient | The default recipient |
| Immediate retries | Retries, used by send channels. For some receive channels, the number of pickup attempts. |
| Auto uncompress | Check if receipt data are compressed and then uncompress them |
| Semaphore file | Here you can enter a relative path (. /HD/In/Lock. dat) or absolute path (C:\eBiss\HD\In\Lock. dat) including. filename can be entered. If this file has just been created by an external application (ERP-system/merchandise management), the read access by eBiss file system reception channel is prevented. The external application can output files to this directory. If the lock file is created by the eBiss file system receiving channel, this prevents an external application from accessing the directory by writing to it, so that the files cannot be changed from outside during the reading process by eBiss. This option can be used independently of the LockExclusive option. |
| Lock exclusive | In this mode, the channel tries to lock the files to be read exclusively. If the files are currently being written by an external application (ERP system/merchandise management), the lock cannot be set and the hard disk receiver channel will not read this file until the next read cycle. Conversely, no external application can modify the files that are currently being read by the hard disk receiver channel. This option can be used independently of the SemaphoreFile option. In this mode, only LockExclusiveMaxFiles (see below) files are read in during a read cycle. |
| Identify partner by sub directory | Allows you to find the partner within the subdirectories. |
| Sort order of read files | Sequence in which the received data are read and processed. |
| Max KB per running job | Max KB to fetch on each Run; other files will to 'touched' so the eventlistener does not ignore them afterwards |
| Max file size (KB) | Max file sive in KB to fetch, other larger files will be ignored |
| Set Attachment's Directory Property | Write the Directory to the Attachment's Directory Property, so when delivering later it can reproduce the Directory in Harddisk Send Channel (synchronising directory trees) |
Note: The filesystem receive channel is designed to read from local directory paths.
If you want to read from a UNC path, you have to make sure that it is accessible by the eBiss Service without registration, or you have to use the command “net use1)”.
1)
Example: