Skip to main content
Skip table of contents

FTP location

FrmMain_MobileRemarkGroup_TabPublication_FTP.png

Output format

Specifies for which client the message file should be created for. The following options are available:

  • Default (a message file for the IBI-aws Client will be created)

  • Web (a message file for the IBI-aws WebClient will be created)

General

With IBI-aws WebClient

Only available if output format is Web

Specifies wheather the IBI-aws WebClient should also be written to the specified publication target.

Authentication

Anonymous authentication

The FTP-server is accessed anonymously.

Authentication with credentials

The FTP-server is accessed with the entered Login.

Connection settings

Use SSL

SSL is used while accessing the FTP-server.

Encryption mode
Explicit

An unencrypted connection is established first, which is later upgraded to an encrypted one.

Implicit

An encrypted connection is established immediately.

Ignore certificate errors

While accessing the FTP-server, certificate errors are ignored.

Use passive mode

While accessing the FTP-server, passive mode is used.

While using passive mode, all connections to the FTP-server are established from the client-computer. This means, that there are no incoming data connections, which could lead to firewall problems.

Expired messages

Publication offset

Specifies how long a message should be published after the end time has been reached.

Message tags

Only available if output format is Web

Write to message file

This option specifies whether the tags of the messages to be published should be written to the web output.

Privacy

Only available if output format is Default

Encrypt data

If this option is activated, the message file is not written in plaintext, but encrypted.

Extended

Script execution

Scripts entered here are automatically executed using the Windows command line during the publishing procedure.

Examples

Powershell script
BASH
powershell "C:\scripts\myscript.ps1"
Batch script
BASH
C:\scripts\myscript.cmd

Error handling

If a script is not executed properly (ExitCode ≠ 0), the publication fails. The previously executed actions (script before publishing or writing the message file) are not reverted in case of an error.

Before publishing

Scripts entered here are executed before writing the message file.

After publishing

Scripts entered here are executed after writing the message file.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.