| Oracle® Distributed Document Capture/Oracle® Document Capture Administrator's Guide Release 10gR3 E13871-01 |
|
 Previous |
 Next |
| Oracle® Distributed Document Capture/Oracle® Document Capture Administrator's Guide Release 10gR3 E13871-01 |
|
Previous |
Next |
This section covers these topics:
For background information about Commit Server, see "About Commit Server".
Start the Commit Server from the list of programs on the Start menu.
Commit Server starts in an active state if there are scheduled jobs. However, Commit Server does not begin processing jobs for one minute, allowing you to pause the server if you do not want it to process any scheduled jobs.
Activate or pause the server as needed.
Choose Pause on the Server menu to make changes to settings or batch jobs. Choose Activate on the Server menu to enable scheduled batch jobs to process.
This section covers the following topics:
Follow these steps to specify a login user name and password so Commit Server will start up without requiring login information.
If needed, pause the server by choosing Pause from the Server menu.
Choose General Settings from the Setup menu.
On the Login tab, select the Unattended Login field.
Enter a username and password for login.
If you selected Windows domain security as your security model, use the format \\domain\userID in the User ID field (for example, \\domain2\jdoe) to specify the domain along with the user name. For unattended login, the user must be added as an individual Capture user. See "Add User or Group Screen (Windows Domain Security)".
Activate the server by choosing Activate from the Server menu.
If needed, pause the server by choosing Pause from the Server menu.
Choose General Settings from the Setup menu.
On the Email tab, select the Send On Error field.
Specify email server and authorization settings.
Identify email recipients, separating multiple email addresses with a semicolon (;).
Click the Test Email button to send an email message that tests the settings.
Activate the server by choosing Activate from the Server menu.
If needed, pause the server by choosing Pause from the Server menu.
Choose General Settings from the Setup menu.
On the Error Log tab, specify where you want error logs written in the Log File Path field.
Complete other settings on the Error Log tab.
Activate the server by choosing Activate from the Server menu.
Also see "Guidelines For Running Servers as Services".
If needed, pause the server by choosing Pause from the Server menu.
Choose General Settings from the Setup menu.
On the Login tab, specify unattended login options.
On the Services tab, specify the number of seconds (30-900) to wait for the service to shut down normally.
Open the Services applet from Administrative Tools in the Control Panel.
Select the Oracle Document Capture Commit Service, right-click and choose Properties.
On the General tab, change the Startup Type to Automatic.
On the Properties Log On tab, configure a logon account for a user with rights to access network resources.
This is needed only if the service will access network resources, such as sending emails on error conditions or committing to a network location.
This section covers these topics:
|
Note: Changes you make to a selected batch job affect all scheduled events that use the batch job. |
To process one or all file cabinets without special settings, schedule processing without creating a batch job, as described in "Adding an Event". Otherwise, follow these steps to add a batch job.
If needed, pause the server by choosing Pause from the Server menu.
Choose Batch Jobs from the Setup menu.
Click New.
A default batch job name of <Batch Job 1> displays in the Batch Jobs and Name fields.
Enter a batch name in the Name field.
You can type up to 50 alphanumeric characters, including spaces.
On the General tab, select the file cabinets whose batches you want the job to process.
On the Batch Criteria tab, optionally limit the batches to be processed based on batch prefix or status.
On the Processing Order tab, optionally specify if and how batches will be sorted before processing.
Click Save to save the batch job.
Follow these steps to delete batch jobs that are no longer used.
If needed, pause the server by choosing Pause from the Server menu.
Choose Batch Jobs from the Setup menu.
The Batch Job dialog box is displayed.
In the Batch Jobs dialog box, select the batch job you want to delete from the Batch Jobs field.
Click Delete to remove the batch job, then confirm the deletion.
In order for Commit Server to process batches, their scan profile must be set to use Commit Server.
From the Scan Administration screen, select a scan profile in the left pane.
Under the General Options, select 3 - Commit Using Commit Server from the Commit Method field.
Save the profile.
When a user sends batches after indexing with this profile, the batches will be marked for committing by a scheduled Commit Server job.
In order for Commit Server to process batches after indexing, their index profile must be set to use Commit Server.
In the Capture screen, choose Manage Index Profiles from the Indexing menu.
In the left pane, select an indexing profile.
On the Options tab, select the Use Commit Server field.
Save the profile.
When a user clicks Commit after indexing with this profile, the workstation will be immediately available for indexing, and the batch will be marked for committing by a scheduled Commit Server job.
Follow these steps to set the Recognition Server batch job to commit batches using Commit Server. When set to use Commit Server, Recognition Server marks each batch as ready to be committed by Commit Server after bar code recognition, instead of actually committing it.
If needed, pause the Recognition Server by choosing Pause from the Server menu.
Choose Batch Jobs from the Setup menu.
In the Batch Jobs field, select the job.
On the General tab, select the Use Commit Server field.
Save the batch job.
Follow these steps to set the Import Server batch job to commit batches using Commit Server. When set to use Commit Server, Import Server marks each batch as ready to be committed by Commit Server after importing, instead of actually committing it.
If needed, pause the Import Server by choosing Pause from the Server menu.
Choose Batch Jobs from the Setup menu.
In the left pane, select the provider.
In the right pane, double-click the job.
On the Processing tab, select the Commit Batches and Use Commit Server fields.
Save the batch job.
This section covers the following topics:
If needed, pause the server by choosing Pause from the Server menu.
Choose Schedule from the Server menu.
Click Schedule Event.
In the Event field, select the batch job or file cabinet you want the event to process.
You can choose a previously added batch job, a file cabinet, or all file cabinets.
In the Frequency field, select how often you want the job processed.
If you selected a frequency of Once, Every Day, or Every Week, specify frequency details.
Click OK, then Close.
Activate the Commit Server by choosing Activate from the Server menu.
Once processing begins, view statistics and error log messages in the Commit Server main screen.
Follow these steps to stop an event from processing.
If needed, pause the server by choosing Pause from the Server menu.
Choose Schedule from the Server menu.
Select the event you want to delete, click Remove Event, and confirm the deletion.
This section covers these topics:
Commit Server audits certain activities and saves the information in the ecAudit table of the Capture batch database. For more information about audit activities and tables, see "Auditing in Oracle Document Capture".
Follow these steps to schedule clearing out old log files using the predefined Delete Old Log Files event.
If needed, pause the server by choosing Pause from the Server menu.
Choose General Settings from the Setup menu and click the Error Log tab.
Select the Delete Old Log Files field.
In the Days to Retain Log Files field, enter the number of days you want to keep log files. Click OK.
Choose Schedule from the Server menu.
Click Schedule Event.
In the Event field, choose Delete Old Log Files.
In the Event Properties fields, select how often you want to delete old log files.
Click OK, then Close.
Follow these steps to schedule shutting down Commit Server using the predefined Shut Down event.
If needed, pause the server by choosing Pause from the Server menu.
Choose Schedule from the Server menu.
Click Schedule Event.
In the Event field, choose Shut Down.
Click OK, then Close.
As an option, use the Microsoft Task Scheduler to restart Commit Server. To prevent Commit Server from displaying a login screen, make sure unattended login settings are selected, as described in "Setting Up Unattended Login".
