Table of Contents
Advertisement
Installing Lexmark Intelligent Capture
c
Install the load balancer.
d
If you are using one or more Microsoft Cluster Servers, then extend the database and load balancer to standby
nodes.
e
Install servers.
Note: Multiple servers should not be installed at the same time. Let each server installation complete
before beginning another server installation.
4
Change the administrator password. You can also change the administrator user name.
5
Temporarily set servers online to test function.
Notes:
•
The database requires the most system resources and disk I/O, and therefore should be installed on the fastest
hardware with the fastest disk I/O infrastructure available. Second in resource usage are the servers.
•
Lexmark Intelligent Capture components can be installed on virtual servers using VMware ESX 3.0.1 or later.
However, the best performance can be achieved only by using separate physical servers.
Using Oracle database with Lexmark Intelligent Capture
If you are using Oracle as the back-end database, then make sure:
•
The Oracle database 10g or later is completely installed before proceeding with the Lexmark Intelligent Capture
installation.
•
Lexmark Intelligent Capture system components are not installed on the server running Oracle.
•
The internal Lexmark Intelligent Capture database is not installed.
For Lexmark Intelligent Capture to work with Oracle, six databases should be created before the load balancer and
server are installed. To help the database administrator create these databases, Lexmark Intelligent Capture includes
the following in the installation package:
•
Database templates—These are Database Configuration Assistant (DBCA) templates used to create databases. Your
database administrator can launch these templates through DBCA, and then configure parameter settings as
needed.
•
Scripts—These are user configuration scripts for adding users. Users are added to access and manage Lexmark
Intelligent Capture databases.
•
Pfiles—These files contain information about the database configuration parameters. The values of database
configuration parameters may vary, except the parameter value for nls_timestamp_format and
nls_timestamp_tz_format of the MONITOR database.
These parameters should have the following values:
nls_timestamp_format string YYYY-MM-DD HH24:MI:SS:FF3
nls_timestamp_tz_format string YYYY-MM-DD HH24:MI:SS:FF3
Note: Make sure to follow the correct time‑stamp format when configuring time‑stamp parameters.
33
Advertisement
Table of Contents
