File Records Actions Insert

Managing System Processes 3-13 ■ You want to remove a large number of specific files from the system. The Batch Loader performs actions that are specified in a batch load file, which is a text file that describes the action to perform and the metadata for each content item in the batch. A batch load file is a text file that tells the Batch Loader which actions to perform and what metadata to assign to each content item in the batch. This section covers these topics: ■ Section 3.6.1.1, File Records ■ Section 3.6.1.2, Actions ■ Section 3.6.1.3, Insert ■ Section 3.6.1.4, Delete ■ Section 3.6.1.5, Update ■ Section 3.6.1.6, Optional Parameters ■ Section 3.6.1.7, Custom Metadata Fields

3.6.1.1 File Records

A batch load file is made up of file records, which are sets of namevalue pairs that specify the action to perform, or the metadata for individual content items, or both. ■ Each file record ends with an EOD end of data marker. ■ A pound sign followed by a space at the beginning of a line indicates a comment. The comment character must be followed by a space. For example: primaryFile=test.txt works properly, but primaryFile=test.txt will cause errors. ■ The following is an example of a file record: This is a comment Action=insert dDocName=Sample1 dDocType=Document dDocTitle=Batch Load record insert example dDocAuthor=sysadmin dSecurityGroup=Public primaryFile=links.doc dInDate=8152001 EOD Note: For the Batch Loader utility to function correctly with an Oracle WebLogic Server instance, you must have JDBC connection settings configured. See Section 3.4.2, Running Administration Applications in Standalone Mode. Important: Field names and parameters are case sensitive. They must appear in the batch load file exactly as they appear in the following sections. For example, dDocName is not the same as ddocname, dDocname, or DDOCNAME. 3-14 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server

3.6.1.2 Actions

Valid actions for batch loading are Insert , Delete , and Update . ■ If no action is specified for a file, the system tries to perform an update. ■ Each file record can have only one action, but file records with different actions can be present in the same batch load file. ■ The logic process for each action is different.

3.6.1.3 Insert

The insert action checks a new file into the Oracle Content Server repository. If the Content ID dDocName already exists in the Oracle Content Server database, no action is performed. Figure 3–1 illustrates the insert action. Figure 3–1 The Insert Action Sequence for Checking In a New File

3.6.1.3.1 Insert Requirements The following table defines the fields required for

successful performance of an insert action. ■ Field Length: Maximum number of characters permitted in the field. ■ Carried Over: If the next record does not contain this field, the value of this field will be taken from the previous record. Note: Batch loaded revisions will not enter a workflow even if they meet the criteria for an active workflow. Important: If you have defined any custom metadata fields as required fields, those fields also need to be defined for an insert action. Managing System Processes 3-15

3.6.1.3.2 Insert Example The following code fragments show the batch load file syntax

for inserting files. This example shows two file records. The first file record includes all required fields and the action statement, Action=insert. The second file record does not list the required fields dDocType, dDocAuthor, or dSecurityGroup. However, the information for these items is taken from the previous record. Also, the second record does not specify an action, so the insert action is carried over. Therefore, if the Content ID HR003 does not exist, the file will be inserted. However, if the Content ID does exist, it will not be inserted because the action is insert and not update. ■ First record: Action=insert dDocName=HR001 dDocType=Form dDocTitle=New Employee Information Form dDocAuthor=Olson dSecurityGroup=Public primaryFile=hr001.doc dIndate=31597 EOD Required Items Field Length Carried Over Definition Action=insert NA Yes The command to insert a file. The term Action is case sensitive and must be initial capitalized. dDocName 30 No The metadata field named Content ID. dDocType 30 Yes The metadata field named Type. dDocTitle 80 No The metadata field named Title. dDocAuthor 30 Yes The metadata field named Author. dSecurityGroup 30 Yes The metadata field named Security Group. primaryFile NA NA The metadata field named Primary File. The Primary File name can be a complete path or just the file name. If a file name only is specified, the location of the file is determined as follows: ■ If the SetFileDir optional parameter has been set in this file record or any previous file record, the directory specified in SetFileDir will be used. ■ If the SetFileDir parameter has not been set, the batch load file path is used. The path is specified in the Batch Load File field on the Batch Loader Screen . dInDate NA No The metadata field named Release Date. ■ The dInDate must use the date format of the locale of the user executing the Batch Loader. For example, the US English date format is mmddyy hh:mm:ss ampm. ■ Time information is optional. If you specify the time, only the hh:mm part is required. The ss and ampm parts are optional. EOD NA NA Indicates the end of data for the file record. 3-16 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server ■ Second record: dDocName=HR003 dDocTitle=Performance Review primaryFile=hr003.doc dIndate=31597 EOD

3.6.1.4 Delete