One question I had was whether we could manually start a job scheduler similar to a queue processor based on the point made in the design assessment options in the preceding link. In case there is a way, please let me know.
Hi @Pavan_kalyan: The one you highlighted in the academy says that Job schedulers will run based on the start up time configured and the transaction should be handled in the code.
Can you please help to understand what you refer to “whether we could manually start a job scheduler similar to a queue processor”?
Queue processors will start based on the availability of items queued to it. For job schedulers, you need to specify the schedule when it should run. If you need to run the Job scheduler manually, you can try to run the activity.
Thanks.
@Pavan_kalyan
Hello,
A Job Scheduler is just a scheduler. It will trigger the defined activity at the time defined in it.
So as mentioned previously, you might be willing to run the activity of the JS more than trying to run the JS (for which you would have to change the defined running time)
A QP itself can be up or down via Admin Studio. It’s a queue. When there’s a message, then it’s picked up and handled as per business logic.
Advanced agent is similar to JS. It will trigger an activity at the time you defined it to run.
Regards
Anthony
My understanding for transactional processing was different. I learned that the transactional logic that needs to be built is nothing but opening a case in job scheduler activity and completing the transaction with a commit on need basis.