Oracle Imaging and Process Management Services Installation Guide

System Requirements

Refer to the Oracle I/PM Release Documents in the help file ReleaseDocs.CHM for hardware and software requirements. If there are hardware limitations (not meeting the system requirements or recommended configuration), installation differs and functionality may be limited. Oracle recommends the first configuration listed above with more servers as a minimum configuration rather than the more limited second configuration.

NOTE
The following limitation effects the installation of any Oracle I/PM system that uses more than one machine for any service:

• 
  Web Service can not reside with any other Oracle I/PM Services
  
• 
  The Full-Text Server should not be installed with other Oracle I/PM Services for optimal performance in a production environment.
  

Limited hardware configurations (i.e., too few machines, too little RAM, etc.) are not recommended since the limited hardware may adversely impact software performance. If you decide to operate a limited hardware configuration, be sure to mention this when discussing your system with Oracle personnel.

Network and Database Installation

NOTE
Refer to the ReleaseDocs.CHM for information regarding supported database platforms including specific OLE DB provider and driver versions. Customizations of the database definitions are not supported.

NOTE
Do not run Oracle I/PM services on the same machine where the SQL backend database is installed. This configuration will function in an acceptable manner only in very limited environments, such as for demonstration purposes or for very low volume systems.

Prior to the installation of Oracle I/PM, a supported SQL database must be installed. Oracle recommends the database be tested from another workstation through third party database communications software prior to installation of the product. For instructions on installing a SQL database, please consult the documentation provided from the database vendor. Contact the database vendor for the appropriate method for backing up the entire Oracle I/PM database. The default system administrator password for a SQL database is blank. Oracle strongly recommends that this default password be changed prior to installing Oracle I/PM.

The Information Broker Server must have MS SQL Server 2000 SP 4 with Hotfix 2187 or MS SQL Server 2005 installed. For additional information about required versions see ReleaseDocs.CHM.

If implementing Oracle I/PM Full-Text, the SQL Server where the Oracle I/PM Full-Text database will reside must have the Full-Text component installed.

The 1999/2000 split must be set to the same year for all database software. This means that Information Broker, the Query Processor, the Database Servers and the clients must all be set to the same year 2000 cut off date. When these are not synchronized, searching problems for certain dates can occur, even when typing a four-digit year.

In addition, these instructions assume a network is installed, tested and operational. It is recommended a network communications tool such as PING be used to verify all servers can communicate with one another.

Database User Ids and Rights

Use the following section as a guide to setting up User IDs and associated rights.

SQL Server

1. 
   Create separate users for Imaging (Information Broker and Audit Server), Process and BPEL Injector.
   

For example, in Imaging:

• 
  User = ibpm
  
• 
  Server Role = Database Creator
  

2. 
   Log in as ibpm to create the database to be used. Oracle recommends allocating sufficient space in the database files to avoid fragmentation prior to Imaging implementation.
   

For example, in Process:

User = padmin

Server Role for database creation and running Process Database Wizard:

• 
  Access to the target database instance.
  
• 
  Create table privileges.
  
• 
  Not a DBA user.
  

2. 
   Log in as padmin to create the database to be used. Oracle recommends allocating sufficient space in the database files to avoid fragmentation prior to Process implementation. .
   

For example, in BPEL Injector:

• 
  User = bpelinj
  
• 
  Server Role = Database Creator
  

4. 
   Log in as bpelinj to create the database to be used. Oracle recommends allocating sufficient space in the database files to avoid fragmentation prior to BPEL Injector implementation.
   
5. 
   To set the compatibility level for SQL Server 2005, perform these steps.
   

• 
  Run MS SQL Server Management Studio.
  
• 
  Click database.
  
• 
  Right click on properties.
  
• 
  Click options.
  
• 
  Compatibility level is the third option down. Set to desired compatibility level.
  
• 
  Click OK.
  

Oracle

1. 
   Create separate tablespaces for each Oracle I/PM elements. Create separate users (schemas) with these new tablespaces as default.
   

CAUTION
DO NOT USE SYSTEM OR SYS OR INTERNAL to create the Oracle I/PM database.

DO NOT USE THE SYSTEM TABLESPACE as the default for any Oracle I/PM user.

For Oracle 10g, Grant Create Any View to the Oracle I/PM database user.

For example, in Imaging:

• 
  User = ibpm
  
• 
  Server Role = connect resource
  

2. 
   Log in as ibpm to create the database to be used. Oracle recommends allocating sufficient space in the database files to avoid fragmentation prior to Imaging implementation.
   

For example, in Process:

• 
  User = padmin
  
• 
  Server Roles (for database creation and running Process Database Wizard) = connect resource, dba.
  

Log in as padmin to create the database to be used. Oracle recommends allocating sufficient space in the database files to avoid fragmentation prior to Process implementation.

For example, in BPEL Injector:

• 
  User = bpelinj
  
• 
  Server Role = connect resource
  

2. 
   Log in as bpelinj to create the database to be used. Oracle recommends allocating sufficient space in the database files to avoid fragmentation prior to BPEL Injector implementation.