This is just a quick introduction to batch loading content into content server with the Batch Loader application. The application can be run from the command line as well as in graphical mode. I normally run it in graphical mode.
I also like to put the check mark in the box to produce an errors file. This file is kind of neat, if anything fails it is placed in that file where you can tweak the metadata and then point batch loader at that file to attempt loading all the content that failed to load. Why might things fail? Perhaps you forgot one of the required fields like dSecurityGroup or perhaps you performed a check-in using a particular metadata value that did not exist in a validated list.
Usually you will need to add a setting to the intradoc.cfg file called Batch Loader User Name. This setting in your configuration might look like this:
I am sure you could come up with better values to put in this field besides sysadmin, but for the sake of this demonstration/test this should get you running pretty easily.
NOTE: intradoc.cfg, not config.cfg.
Now you must construct the batch load file. Nothing scary here, just a text file. This file contains key=value pairs one to a line of metadata and values and uses hash/pound characters (#) to begin lines that are comments, like this:
#This is a comment Action=insert dDoc dDocTitle=Product Details dDocAuthor=sysadmin dSecurityGroup=Public primaryFile=<path to file> dInDate=7/23/2008 dDocName=TestContentID <<EOD>>
What if you wanted to perform a metadata only check in? Try something like this:
#This is a comment Action=insert dDoc dDocTitle=Product Details dDocAuthor=sysadmin dSecurityGroup=Public #primaryFile=<path to file> dInDate=7/23/2008 dDocName=TestContentID createPrimaryMetaFile=true <<EOD>>