Transport phase

If sync_export_list or syncreplica puts packets in storage bays (–ship option), you must run shipping_server to process these packets.

If you do not use –ship, but want to implement a retry-on-failure capability, you must schedule regular invocations of shipping_server. The shipping server attempts to retransmit any outgoing packets that remain in any of the storage bays because one or more previous attempts have failed.

With the –poll option, sync_export_list invokes shipping_server –poll to process shipping orders located in all storage bays defined in the shipping.conf file (Linux and the UNIX system) or in the MultiSite Control Panel (Windows).

For example, this job invokes shipping_server every day at 04:00 local time:
Job.Begin
       Job.Id: 19
       Job.Name: "Shipping Server Poll"
       Job.Description.Begin:
Every night at 4AM, run the shipping server to send any outstanding orders.
       Job.Description.End:
       Job.Schedule.Daily.Frequency: 1
       Job.Schedule.FirstStartTime: 04:00:00
       Job.DeleteWhenCompleted: FALSE
       Job.Task: 13
       Job.Args: -quiet 1 -poll
Job.End
The following job implements a more aggressive retry-on-failure capability. The shipping server is run every half hour from midnight to 04:00 local time:
Job.Begin
       Job.Id: 20
       Job.Name: "Shipping Server Poll"
       Job.Description.Begin:
Every half hour from midnight to 4AM, run the shipping server to send
any outstanding orders.
       Job.Description.End:
       Job.Schedule.Daily.Frequency: 1
       Job.Schedule.FirstStartTime: 00:00:00
       Job.Schedule.StartTimeRestartFrequency: 00:30:00
       Job.Schedule.LastStartTime: 04:00:00
       Job.DeleteWhenCompleted: FALSE
       Job.Task: 13
       Job.Args: -quiet 1 -poll
Job.End