All the pub.scheduler services support providing inputs to the scheduled service. The bummer is that the Administrator UI doesn’t provide any way to set them.
The TN Console makes use of this facility for firing scheduled delivery tasks associated with queues. The caveat is that once you set the schedule using TN Console or the pub.scheduler services, you cannot use Administrator to edit them–otherwise you’ll lose the inputs.
I do not know for certain, but I believe the inputs are stored in the repository. If the IS is in an IS cluster, then the shared repo will hold the inputs so that the scheduled tasks will operate correctly, whichever IS instance runs the task.
#webMethods#Integration-Server-and-ESB#Flow-and-Java-services