Multiple Instances of Autoloader

• 

  Brian Schanen joined Autodesk in 2005 as a Product Designer and currently is a Customer Success Engineer for Autodesk’s Data Management products. Brian has taught at Autodesk University numerous times and has authored white papers on Vault and Productstream. He works with customers to implement a complete digital prototyping solution specializing in Autodesk Inventor, Autodesk Vault and Productstream. Brian lives near Detroit, Michigan.

  About Brian

Latest Post

• Add to Bookmarks Send to Peer

  Multiple Instances of Autoloader
  June 11, 2008, 09:51 PM Brian Schanen

  Today we'll outline the steps to set up a 'farm' of machines - each with Autoloader - to populate Autodesk Vault or Productstream. For review, Autoloader 2009 is included with each seat of Vault and Productstream. By default, only one instance of Autoloader can be run against a server at a time, and starting Autoloader on another machine returns an error.

  

  Being a bulk upload utility, one Autoloader is usually enough.  For those who have a tight schedule with large amounts of data for the upload, follow these steps to upload from more than one machine:

  1. Run Autoloader once to establish the folder names, structure, and create the Inventor .ipj. This also creates a hidden file called the BUU.xml. This file holds the Workspace, Libraries, and Project file names.
  2. Wihile logged in to Autoloader on the first machine, Open the Vault, go to Tools> Options, and check the Show hidden files option.

   

  3. Find the buu.xml in the root of Vault Explorer ($ )and Undo Checkout on the first machine.

  

  4.   Now, log in to Autoloader to the same Vault, from a second machine. Undo the Checkout of the buu.xml only if a third machine is needed.
  5. Select an upload folder and scan files on the first machine.
  6. Repeat the folder selection and scan of files on the second machine.
  7. Map folder on the first machine, then Undo Checkout of the Designs.ipj on the first machine, This is the Inventor Project file that Autoloader provides for you. The name may be different on your machine.
  8. On the second machine, Map folders and Undo the Checkout of the .ipj only if additional machines are needed.
  9. Proceed to upload files on all machines.

  It is recommended to use this multiple Autoloader method to upload separate datasets that do not overlap files. You may have assemblies that share common library components, and this is typical.

  

  The final progress window and report will display these as Identical files as seen in the above image. This ability to create a farm of Autoloader machines can save time during your Vault or Productstream implementation.

  -Brian Schanen

  0 Comment | Add Comment Under The Hood >

Comments