- INTRODUCTION
Dualog File Transfer allows automatic file transfer between ship and shore regardless of the ship’s communication equipment.
Configuration can be done from shore. Each ship’s configuration is centrally managed with changes distributed and implemented automatically.
Full reporting of file delivery is available on shore using the Traffic Manager, and optionally using automatic e-mail notifications in case of delivery problems.
End-to-end file transfer between folders on the ship and folders in the office can be achieved using the File Transfer office client.
- SHORE TO SHIP
Connection Suite will automatically validate messages coming from shore to see if they match definition of datasync job. If the system regards the message to match a datasync definition the system will detach the attachment and put it into a defined folder.
The fields marked with a red asterisk are mandatory. However, the more fields are filled up and the more capillar the file transfer job will be.
| Inactive | Tick this box to activate/deactivate the current File Transfer job. |
| Application name | Name of the application that should be supported. It is just a name and has no impact on the system behaviour. |
| Message subject | The subject of the message that will be sent. |
| Message sender |
When validating an incoming message, the message sender will be compared to this field. |
| E-mail receiver | The email address the message will be sent to. |
| Destination directory | If the incoming message is recognized as a legitimate File Transfer job, the attached file(s) will be put in this folder. |
| Username | If the destination directory requires a login ID, add it here to allow access to the remote folder. |
| Password | If the destination directory requires a password, you may add it here to allow access to the remote folder. |
| Backup directory | If the incoming message is recognized as a datasync job, a copy of the file attachment will be put in this folder. |
| Overwrite existing file | Specify a backup directory should the existing file be overwritten in the Destination directory. |
| Notify receiver | Specify an email address should a notification be sent to the receiver of the message/job. |
| Run executable attachments | If the attachment is an executable, you can execute it automatically by ticking this box. |
| Separate backup | If a backup directory is given, the system can put the backup file(s) in subfolders making sure no previous backups are overwritten. |
| Failure notification – Ship | Select a stationary email account on the ship to be notified in case the file transfer job fails. |
| Failure notification – Shore | Select a shore email account to be notified in case the file transfer job fails. |
- SHIP TO SHORE
The fields marked with a red asterisk are mandatory. However, the more fields are filled up and the more capillar the file transfer job will be.
| Inactive | Tick this box to activate/deactivate the current File Transfer job. |
| Application name | Name of the application that should be supported. It is just a name and has no impact on the system behaviour. |
| Source directory | The folder in which the system is looking for files to send. |
| Username | If the destination directory required a login ID, add it here to allow access to the remote folder. |
| Password | If the destination directory requires a password, you may add it here to allow access to the remote folder. |
| Backup directory | When the system finds a file it regards as a datasync job a copy of the sent file will be put in the backup directory. |
| Message subject | If specified , it needs to match exactly the subject of the message sent from shore. |
| Message Sender | Requires sender email address to be added when the file transfer will be sent from shore. |
| E-Mail Receiver | The email address the message will be sent to. |
| File mask | Describes which file type should be used when the system will decide if a file should be regarded a datasync job. |
| Message body | Indicates the content of the message. |
| E-Mail priority | 3 types of priority can be set: Low, Normal or High. |
| Multiple file per message | Decides whether more than one file can be sent in a single message. |
| Needs approval | Decides if the message must be approved before it is sent to shore. |
Comments
Please sign in to leave a comment.