Job Processor Server Additional Tools

[bmatthews8LS6L]

The Job Server / Processor should:

1. Display the Job Queue  
2. Access to all command line switches implemented as menu selections
3. View the Job Processor Log directly from the dialog box
   • when multiple Servers are in use, each Log would display
4. Allow Vault configurations needed to control publishing accessible from the Job Processor without Vault Client application running
5. Show a count down timer for when the next queue access will happen

[bmatthews8LS6L]

It would also be great if you could make the Job Processer application respond to a maximize when minimized to the task bar.

Brian 

[v.dobreaA3C4X]

Can Job Processor window be integrated on Job Server Queue? 

This will reduce the number of windows opened and can also see the current runing job together with the pending jobs and those with errors.

[ihayesjr]

In the Job Queue, you can see all of the information that is in the Job Processor. What is missing? 

[v.dobreaA3C4X]

I would like to have the posibility to pause/resume from the same interface! 

This taking into consideration that JobProcessor is running on the machine!

[ihayesjr]

Can you discuss the problems you are trying to solve by remotely pausing and resuming a Job Processor?

[v.dobreaA3C4X]

I know that we can sett the time interval  for Job Processor to look for queued jobs but this will load more the machine running the job server! This can be handy when you need to process more data like lets say migrated drawings (aproved outside Vault). If no trafic is made on the Job Processor I would like to be able to see the queued jobs and if needed to jumpstart the JobProcessor at request!

[ihayesjr]

So your real request is to remotely control the Job Processor, correct?

[v.dobreaA3C4X]

Yes but again with the remark: when (special cases) user needs more quick reaction from it! 

[Anonymous]

Hey Brian, 

That would be helpfull 

[bmatthews8LS6L]

In our implementation, the job processor is a standalone PC that is only accessible by IT and Vault Admins.  Pretty standard method.  The Users however don't see any of the additional work that the job processor, in our case coolorange processor, is also doing.   Any user interaction can be helpful, but there are some limits.