Job processor: Inventor Server vs Full Inventor - Pros and Cons

[fredform]

Hi,

I've been looking for more information about using the Inventor Server as jobprocessor as opposed to using full Inventor. It is my understanding this can be done to handle Vault tasks such as dwf, pdf, dxf and stp-file creations but what are the limitations?

Currently our configuration of Vault Pro (2022) and job processor consist of a thirdparty add-on that handles the scripts/jobs being sent to our jobbprocessor which runs and occupies a full Inventor license. Part of the functionality in addition to exporting files as mentioned above is to attach pdf drawings back to the item they were created from (on lifecycle state: Released). Can these things be achieved with Inventor server?

Thank you in advance.

Best,

Fredrik

[Markus.Koechl]

JobProcessor running on VaultInventorServer (default) is able to consume custom jobs that use core Inventor without any dependency on graphic screen, UI, or user interactions.

It leverages translator add-ins (to create export formats) and iLogic rule execution.

To leverage VaultInventorServer the implementation of custom jobs is the supported way to go.

[fredform]

Hi Markus,

Okay so in terms of running the types of custom jobs that I described there's not really any limitations to using Inventor Server? If so, then why would anyone use full Inventor to run the jobprocessor?

/Fredrik

[Markus.Koechl · Accepted solution]

Hi Fredrik,

there are only a few specific task that require a full Inventor installation on job execution, like BIM content creation, or Inventor to Revit simplification workflows. There are others that are more flexible using Inventor compared to InventorServer like exporting images based on existing views: while Inventor could leverage saved views, InventorServer needs to create camera views during the runtime.

Overall - we see that using full Inventor for jobs should be an exception, using VaultInventorServer the standard. The benefit of licensing is one aspect, the other is performance: VaultInventorServer outperformes full Inventor as it loads only the core engines rather than the full application (even this is not visible).

[fredform]

Hi again,

Thank you for the clear answer! Then I will get to work on reconfiguring our jobprocessor. 😅

Best regards,

Fredrik

[jakub.krontorad]

Hi Markus,

is it possible to get access into BrowserFolder in BrowserPane/BrowserNode when I use server instead of full inventor?

BR,

Jakub Krontorad

[Markus.Koechl]

Hi @jakub.krontorad, I did not investigate in detail because, from our compliance perspective, VaultInventorServer must not use any UI-related object or user interaction. From my point of view, the Inventor Browser is a UI element that renders information available within the component definition or document objects; therefore, your job running on VaultInventorServer should leverage the latter only.