33 requesting that it launches the Schedule Send executable at the correct time |
33 requesting that it launches the Schedule Send executable at the correct time |
34 with the packaged information. When the task scheduler launches the Schedule |
34 with the packaged information. When the task scheduler launches the Schedule |
35 Send executable, it unpacks the schedule information and uses the messaging |
35 Send executable, it unpacks the schedule information and uses the messaging |
36 client API to request the Server MTM to perform an operation. </p> <fig id="GUID-F3664A22-1E9F-586B-84B1-CDA7987C3894"> |
36 client API to request the Server MTM to perform an operation. </p> <fig id="GUID-F3664A22-1E9F-586B-84B1-CDA7987C3894"> |
37 <title> Schedule Send architecture </title> |
37 <title> Schedule Send architecture </title> |
38 <image href="GUID-628A90FC-35F9-51D0-853E-9BECB3C91B59_d0e280334_href.png" placement="inline"/> |
38 <image href="GUID-628A90FC-35F9-51D0-853E-9BECB3C91B59_d0e276648_href.png" placement="inline"/> |
39 </fig> <p>The executable to run by the Task Scheduler is specified in the |
39 </fig> <p>The executable to run by the Task Scheduler is specified in the |
40 schedule send settings. This allows different executables for different message |
40 schedule send settings. This allows different executables for different message |
41 types, as a set of schedule send settings are defined for each message type |
41 types, as a set of schedule send settings are defined for each message type |
42 that uses the schedule send support. The executable is normally the schedule-send |
42 that uses the schedule send support. The executable is normally the schedule-send |
43 exe (<filepath>schsendexe.exe</filepath>). </p> <p>Each task contains some |
43 exe (<filepath>schsendexe.exe</filepath>). </p> <p>Each task contains some |