Allow Vault installation/configuration to connect to an Instance not named AUTODESKVAULT
We have several separate vault servers (Professional) all connected to remate databases on an SQL cluster. The SQL people claim that they can only have one single instance called AUTODESKVAULT in their complete environment AND that instance names MUST follow their naming conventions
Actually, vault is the only software that I know of that requires a specific instance name
the goal is to run the job processor on many files that are spread accross several replicated servers.
the hurdle is that if you have the job processor logged into one server and it attempts to process a file that is currently owned by a different server, the task cannot be completed successfully. "error"...
we need to be able to allow for this in the job processor settings, whether it is to simply choose
1. "skip file that is not owned by your server", or
2. "run jobs on tasks with preference to one server over another". the job processor would be able to batch together a few hundred jobs for example, to complete on the local replicated server, then reboot itself (or log out and log into a different server) to run a few hundred files that are owned by the other server(s).
3. allow the job processor to run on files regardless of whether they are owned by another server, or
4. allow the option to choose: "if files are owned by a different server, then just run (several topions may be available here).
there may be easier ways to manage this but the job processor is going to be of much more use with some enhancement. (to be read in consideration with the several other requests for job processor improvements currently on the ideas station and discussion forumns).