Community
Vault Forum
Welcome to Autodesk’s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Job Processor Licensing

18 REPLIES 18
Reply
Message 1 of 19
pdauphin
1352 Views, 18 Replies

Job Processor Licensing

Hello,

 

I found this in a Job Processor White Paper:

 

--------------------------------------------

Job Processor Licensing
The Job Processor consumes one Vault server license during the time it connects to the server to reserve a job. The Job Processor is not continuously logged into the Vault server during the processing of a job and the Vault server license it acquired is released. If a Job being processed requires Inventor, an Inventor license is consumed while it is processing
the job and released when the job has completed.

---------------------------------------------

 

My question: If I use my own computer, the one I use with Inventor and Vault, as a job processor, when the Job processor starts or checks if there is something in the job queue, will it use another vault and Inventor license even if I'm already using Vault and Inventor on my Workstation?

 

Thanks.

 

18 REPLIES 18
Message 2 of 19
DarrenP
in reply to: pdauphin

from my understanding no since you already have inventor and vault installed and licensed

DarrenP
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature

Message 3 of 19
pdauphin
in reply to: pdauphin

Hello,

 

From my understanding, that's what I was expecting too.

 

But, this is not what happens. Or, I'm not testing correctly the behavior of the Job Processor.

 

I was hoping to be pointed at some more literature or to get a definitive answer.

 

thanks.

Message 4 of 19
herrerh
in reply to: pdauphin

If you login to the job processor using the same vault credentials you use for Vault Explorer or Inventor, then you will not use another license.

 

 

If you login to the job porcessor as a different user, it will check out a license.

 

 



Hywell Herrero
Data Management Support Specialist
Product Support
Autodesk, Inc.
Message 5 of 19
pdauphin
in reply to: herrerh

Ah!

 

I understand!

 

Didn't think of that one. Explains the behavior I was experiencing...

 

Thanks!

 

 

Message 6 of 19
pdauphin
in reply to: pdauphin

I now understand how it works but...

 

I can't help wondering why the Job Processor needs to pull a license to get the job done. This is problematic for us. I don't want to buy a license that will be used only for a Job Processor...

 

For our workflow, we need the Job Processor to use an Administrator account so that it is able to synchronize the properties when a file is released. I cannot be an Administrator in order to work with our lifecycles... So, to have a job processor on my machine or another one, I need a license to be available...

 

Any thoughts on this anyone? Any workaround?

 

I feel that automatic tools, that run in the background, should not require a license to be used. I'm I the only one?

 

Thanks.

Message 7 of 19
ihayesjr
in reply to: pdauphin

The Job Processor uses the same methods to connect and work with Vault as the Inventor add-in and Vault client.  It requires a license because it is performing a Read/Write operation to the Vault and a check-in/out just as a user is performing when they check-in or check-out a file.




Irvin Hayes Jr
Sr. Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
Message 8 of 19
pdauphin
in reply to: ihayesjr

I understand that.

 

But why do a "system operation" requires a license? It's not doing anything new. Just automating something I can do manually. Is there a technical reason? Is it so that we have to buy more licenses in order to use the Job Processor efficiently?

 

What are the "Best Practices" for using the job processor? Maybe I'm not planning my usage of that tool correctly.

 

So far, it looks like this: to use this feature, you need extra licenses.

 

Thanks.

Message 9 of 19
ihayesjr
in reply to: pdauphin

Although it is doing an automatic operation, it is not a "system operation".  It is just another client connecting to the server performing a read\write operation.  All read\write operations require a license.

 

The intent for the Job Processor is to have it run on a dedicated workstation, not on the same workstation that the designer is using during the day at the same time.  Or it can run at night on the designers workstation while they are not using it.  If it is running in the background while the designer is working they will experience a performance impact because an additional instance of Inventor will be launched in the background to perform the operation.

 

If you run the job processor at night, it will use the licenses that the designers would be using during the day, therefore you do not require additional licenses.

 

Hope this helps.




Irvin Hayes Jr
Sr. Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
Message 10 of 19
pdauphin
in reply to: ihayesjr

Ok. I understand.

 

But do you agree that if I want the Job Processor to run as an administrator during the day, on another machine or not, I need extra licenses?

 

When I release a file, I can't wait until the next day for the properties to be updated and the new visualization file to be created. So, what do I do?

 

Is my workflow incorrect?

 

I picked this way of doing things following this post on Brian's blog: Under the hood

 

Here is what I read:

-------------------------------------------

This a good place to pause for a best practice. I suggest creating an Administrative account in your Vault for this called Job User. This account would be similar to any Administrative account, part of a Vault Admin group, and have access to all files in all lifecycle states and folder regardless of the security level. This allows for that account to perform tasks on files in Released or otherwise secured states.

--------------------------------------------

 

Thanks again. I greatly appreciate the help.

Message 11 of 19
ihayesjr
in reply to: pdauphin

I agree that if you are running the Job Processor during the day that you need an additional license.  We do have other customers that cannot wait until the next day for the visualization file to be created or the properties to be updated.

You workflow is correct.

 

But I do not recommend running it on the same workstation as you are using.  Large assemblies could really impact your performance.




Irvin Hayes Jr
Sr. Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
Message 12 of 19
DarrenP
in reply to: ihayesjr

also a good point

DarrenP
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature

Message 13 of 19
pdauphin
in reply to: ihayesjr

The performance issue, that is not a problem right now for me.

 

My problem is that I will not be able to use the Job Processor without buying a new license or new licenses.

 

I need to find a workaround or a new workflow.

 

The other clients that can't wait, what are they doing about this?

 

Do you have any other workflow that you could propose? Are the other companies all buying extra licenses to benefit from this tool that looks great when used properly?

 

Thanks.

 

Message 14 of 19
ihayesjr
in reply to: ihayesjr

Some have purchased additional licenses and hardware while others run it only on the workstation where the designer has admin rights.




Irvin Hayes Jr
Sr. Product Manager
Autodesk, Inc.

Vault - Under the Hood Blog
Message 15 of 19
pdauphin
in reply to: ihayesjr

Ok.

 

Thanks.

 

I'll see what I can do.

 

Maybe I can figure something out with "part time usage" of some licenses... or run the job processor at night.

 

Thank you for your help.

Message 16 of 19
cbenner
in reply to: ihayesjr


@ihayesjr wrote:

Although it is doing an automatic operation, it is not a "system operation".  It is just another client connecting to the server performing a read\write operation.  All read\write operations require a license.

 

The intent for the Job Processor is to have it run on a dedicated workstation, not on the same workstation that the designer is using during the day at the same time.  Or it can run at night on the designers workstation while they are not using it.  If it is running in the background while the designer is working they will experience a performance impact because an additional instance of Inventor will be launched in the background to perform the operation.

 

If you run the job processor at night, it will use the licenses that the designers would be using during the day, therefore you do not require additional licenses.

 

Hope this helps.


I am running the job processor on my machine, at night as suggested above (Vault Pro 2011).  Any thoughts, anyone, on what would make it hang up roughly ten minutes after I leave the building?  I have the power settings on my machine set to none, so it will not kill the display or go into sleep mode.  Should I do the same for the server as well?  If the server goes to sleep will that freeze the JP?

 

I also noticed that while JP is running, or after it has hung up like that,... Inventor acts all goofy, hanging at the splash screen.  Any ideas?

Message 17 of 19
hans.martin.haga
in reply to: pdauphin

Try to explain a company with 1-2 users of Inventor and Vault that they need to purchase an additional Inventor and Vault license to run the Job Processor.

 

I consider synchronizing properties a system task, regardless of how this is implemented by Autodesk.

 

Message 18 of 19
pdauphin
in reply to: ihayesjr

I totally agree with you and that was exactly my point in my previous posts.

 

But you saw Autodesk's answer... To me, the job processor is parctically useless because of that.

 

I created a workaround where management people have an account that they use only to synchronize the properties of released or read only files. It really isn't user friendly but that's the only way we can release files and access them right away without having to wait for the Job Processor...

 

And there is no way that we are going to buy an extra Inventor or Vault WG license just to run the Job Processor. To me, it's a feature that I can not use even if I paid for it.

Message 19 of 19
Clarkeng09
in reply to: pdauphin

We recently upgraded to Collaboration 2013 and are running into licensing issues because the job processor is using them.  We have a replicated server so we are running two job processors and I need to have it set so they run at night so our engineers can actually work during the day.

 

I don't think it is right that you purchase software and then need to purchase additional features just to get it to work correctly.

Windows 7 x64 -24 GB Ram
Intel i7-3840QM @ 2.8GHz
nVidia Quadro K5000M - 4GB
Inv 2013 SP2 Update 4
Vault Collaboration 2013 Update1

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report