OS4X Core - understand the queueing system

When sending a file in batch mode, you should enqueue a file into the OS4X send queue. In order to do this, you have several possibilities:

• use the web interface
• use the command line interface

In fact, you could also insert values into the MySQL database table "<tableprefix>send_queue", but when doing this you should contact an OS4X developer because the schema of the table could change.

When a file is enqueued into the send queue, the OS4X send queue daemon is responsible for sending this file to a partner. Some rules are set for sending files:

• the file must be readable by the process running OS4X (which may be configured here)
• the entry must be in the state "new in queue"
• the entry must fit to the OS4X server ID running the process (see documentation on parallel installations)
• the target partner entry must be active if an "active" row is configured here
• a defined media must be set for that partner (see configuration here and here)
• The maximum sending channels for this partner is not reached. This parameter is either globally configurable here or on a per-partner basis via this parameter.

If all these pre-conditions are met, an additional time is being slept (defined through the parameters documented here, in which the send queue entry is in the state "taken by send queue". If the following connection try fails, all send queue entries send try of that partner are raised by one. If the connection is properly set up and the file is transfered correctly, the entry of the send queue may be removed if this flag is enabled, otherwise it changes to "successfully sent".

So called "end to end responses" are possibly sent by the remote side, on which OS4X reacts. You may enable this switch for not to wait until an EERP is received in an OFTP1 session for setting the entry to "successfully sent" or remove it (see above).