Using the IdcCommand Utility and Remote Access

3-30 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server 3. Open a command line window and change to the DomainHomeucmcsbin directory. 4. Enter the following command: Win32: BatchLoader.exe q nbatchloadfile Unix: BatchLoader -q -nbatchloadfile The Batch Loader processes the batch load file, but message boxes will not be displayed. 5. Correct any problems with the batch load. The following flags can be used with the BatchLoader command from the command line:

3.6.3.3.1 Win32 Example The following example shows the correct syntax to run the

Batch Loader from a Win32 command line, where the batch load file is c:batchingbatchinsert.txt: BatchLoader.exe q nc:batchingbatchinsert.txt

3.6.3.3.2 UNIX Example The following example shows the correct syntax to run the

Batch Loader from a UNIX command line, where the batch load file is batchingbatchinsert.txt: BatchLoader -q -nbatchingbatchinsert.txt

3.6.3.4 Using the IdcCommand Utility and Remote Access

Occasionally, you may need to use remote access when managing your Oracle Content Server instance. This does not necessarily mean that remote terminal access is required. However, you must have the ability to submit commands to the server from a remote location. Combining remote access with the IdcCommand utility provides a powerful toolset and an easy way to check in a large number of files to your instance. To take advantage of this functionality, you will need to properly set up the workstation to submit commands and be able to use the IdcCommand utility with a batch load command file. Caution: Run the Batch Loader using the same operating system account that runs the Oracle Content Server instance. Otherwise, the software might not process your files due to permissions problems. Flag Required? Description -q or q No Runs the Batch Loader in quiet mode in the background. If the Batch Loader is run from the command line without this flag, the Batch Loader screen will be displayed. -n or n Yes Batch Load File field value. -console No Echoes all output to the HTML Oracle Content Server log and to the console window that is running the Batch Loader. For details, see Section 3.6.3.6, Batch Loader -console Command Line Switch. Managing System Processes 3-31 This section covers the following topics: ■ Section 3.6.3.4.1, Batch Load Command Files ■ Section 3.6.3.4.2, Preparing for Remote Batch Loading

3.6.3.4.1 Batch Load Command Files A batch load command file contains a set of

commands for each file that is loaded. If you are loading a large number of files, the command file may contain hundreds of lines. Using an editing tool can simplify the task of creating the numerous required lines. For example, the procedure for Preparing for Remote Batch Loading shows how you can prepare a batch load command file using the editing and mail merge features of Microsoft Office. The following is an example Batch Load Command File: Properties LocalData IdcService=CHECKIN_UNIVERSAL doFileCopy=1 dDocTitle=thisfile dDocType=Native dSecurityGroup=Internal dDocAuthor=sysadmin primaryFile=filename primaryFile:Path=pathtothefile xComments=Initial Check In end EODProperties LocalData IdcService=CHECKIN_UNIVERSAL doFileCopy=1 dDocTitle=99.tif dDocType=Native dSecurityGroup=Internal dDocAuthor=sysadmin primaryFile=350.afp primaryFile:path=lofsinvoices350.afp xComments=Initial Check In end EOD

3.6.3.4.2 Preparing for Remote Batch Loading To perform batch loading from remote

locations, complete the following procedure. The procedure is written for a Microsoft Windows operating system. To Configure the Local Computer: 1. Open Windows Explorer. 2. Create a working directory for example, c:\working_dir. 3. In the working directory, create one or more directories for the various Oracle Content Server instances you will be accessing for example, c:\working_ dir\development and c:\working_dir\contribution. These directories can be referred to as DomainHomeName. 4. In each DonainHomeName directory, create a cmdfiles subdirectory. 5. From the remote Oracle Content Server instance, copy the following directories from Middleware\user_projects\domains\Domain_Name\ucm\cs into their respective DomainHomeName in this case C:\working_dir\development and C:\working_dir\contribution. ■ working_dir\DomainHomeName\ucm\cs\bin 3-32 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server ■ working_dir\DomainHomeName\ucm\cs\config 6. From the remote Oracle Content Server instance, copy the following directories and their files to your working directory: ■ working_dir\idc\bin ■ working_dir\idc\components copying the CSDms and NativeOsUtils component files should be sufficient ■ working_dir\idc\config ■ working_dir\idc\jlib ■ working_dir\idc\resources\core\lang ■ working_dir\idc\resources\core\table ■ working_dir\idc\resources\core\config 7. Using a text editor, open the DomainHomeName\ucm\cs\bin\intradoc.cfg file on your local system and update the IntradocDir configuration variable to match your directory structure. For example: IntradocDir=working_dir\DomainHomeName\ucm\cs, IdcHomeDir=working_dir\idc WeblayoutDir=working_dir\DomainHomeName\ucm\cs\weblayout 8. Using a text editor, open the working_ dir\DomainHomeName\ucm\cs\config\config.cfg file on your local system and verify the following settings are correct. IntradocServerPort=4444 IntradocServerHostName=HostMachineName 9. On the remote Oracle Content Server instance, add the IP address of the local computer to the Security Filter, using the SystemsProperties utility. 10. Restart the remote Oracle Content Server instance. To Test the Configuration for the Remote Workstation: 1. In the cmdfiles directory, create a file named pingservertest.hda and add the following lines: Properties LocalData IdcService=PING_SERVER end 1. Open a command prompt and change to your working bin directory for example, cd C:\working_dir\development\bin 2. Issue the following command: IdcCommand -f ..\cmdfiles\pingservertest.hda -u sysadmin -l ..\pingservertest.log -c server 1. Confirm the output. If you are successful, you will get the following message from the server. 32404: Success executing service PING_SERVER. You have completed your setup for remote commands. Managing System Processes 3-33 Create a Batch Load Command File: This procedure uses the editing and mailmerge features of Microsoft Office to create a batch load command file. 1. Create a file listing of your directory contents: a. Open a command prompt and change to the root directory representing the files you intend to load. b. Create a file listing, using the following command to redirect the output into a file: c. dir s b filelisting.txt d. Check your filelisting.txt file; it will look something like this: V:\policies\ADMIN\working_dir_Admin\AbbreviationList.doc V:\policies\ADMIN\working_dir_Admin\Abbreviations.doc V:\policies\ADMIN\working_dir_Admin\AbsencePres.doc V:\policies\ADMIN\working_dir_Admin\AdmPatientCare.doc V:\policies\ADMIN\working_dir_Admin\AdmRounds.doc V:\policies\ADMIN\working_dir_Admin\AdverseEvents.doc V:\policies\ADMIN\working_dir_Admin\ArchivesPermanent.doc V:\policies\ADMIN\working_dir_Admin\ArchivesRetrieval.doc V:\policies\ADMIN\working_dir_Admin\ArchivesStandardReq.doc 2. Edit the file listing to create your filename and title data: a. Open your filelisting.txt file in Excel.

b. Using Replace, remove all the directory information leaving only the file

name. Also look for and remove the line for filelisting.txt. c. Copy column A containing the file names to column B. In this example the file name is also used for the title and Column B will become the title.

d. Using Replace, remove the file extension from the names in column B.

e. Insert a new first line and enter filename in the first column and title in the

second. f. Save the file. 3. Create an hda file from the file listing using Mail Merge features: a. Open Word and create a new document with your set of batch load commands. The following example shows basic batch load commands. You must match your configuration settings when you create your batch load commands. Properties LocalData IdcService=CHECKIN_UNIVERSAL doFileCopy=1 dDocTitle= dDocType=Native dSecurityGroup=Internal Note: When working with batch loads, it is important to note that the file must exist on the server indicated by the primaryFile statement in the batch load command file. Optimally, you should use the same letter to map the directory of files to the server and to your local system. Alternatively, you can copy the directory of files to the server temporarily.