Runtime Options

Use this option when:

you run actions manually
you schedule actions within the application to run either periodically or whenever there is a file to send.
you use application as an "always live" server to receive files (for example, AS2)

Running the UI, installing as a Windows service or run as a Unix daemon, and running from the command line are not mutually exclusive.

Use this option when:

you schedule actions within the application to run either periodically or whenever there is a file to send.
you use application as an "always live" server to receive files (for example, AS2)

See Auto starting the VersaLex daemon in UNIX environments.

Running the UI, installing as a Windows service or running as a Unix daemon, and running from the command line are not mutually exclusive.

Note: By default, Windows services run under a SYSTEM user and do not see mapped drives. If the application is installed as a service on Windows, use full network path names for the directories and ensure proper user authorization. If necessary, change the service to log on under a different account.

Use this option when:

you run actions manually
a 3^rd-party software application (for example, a translator) runs actions

Use this option when:

a remote computer needs to run an action

See Running from the command line.

To run an action remotely via command line, the application must be installed and/or running as a service/daemon on the target computer.

Note: By default, Windows services run under a SYSTEM user and do not see mapped drives. If the application is installed as a service on Windows, use full network path names for the directories and ensure proper user authorization. If necessary, change the service to log on under a different account.

Use this option when:

a remote computer needs to run an action

See Using Autorun.

To run an action remotely via autorun, the UI must be running or the application must be installed and/or running as a service/daemon on the target computer.