2 Requirements for Integrating Autonomy Search

This chapter discusses Autonomy version requirements and system requirements for integrating Autonomy search with Oracle WebLogic Portal.

When considering requirements for using Autonomy search, you should first refer to the Oracle WebLogic Server system requirements, see "Oracle Fusion Middleware Supported System Configurations."

Autonomy's system requirements are a subset of the Oracle WebLogic Server requirements.

This chapter includes the following sections:

Section 2.1, "Autonomy Version Requirements"
Section 2.2, "IDOL Server System Requirements"
Section 2.3, "DiSH System Requirements"
Section 2.4, "Autonomy Service Dashboard Requirements"
Section 2.5, "Autonomy Portlet System Requirements"
Section 2.6, "HTTP Fetch System Requirements"
Section 2.7, "File System Fetch System Requirements"
Section 2.8, "ODBC Fetch System Requirements"

2.1 Autonomy Version Requirements

To integrate Oracle WebLogic Portal with Autonomy, you must add the Autonomy sample search implementation—created by Oracle software developers—to the portal enterprise application. The Autonomy sample search implementation is only compatible with Autonomy version 4.6.0. For this reason, you should use only Autonomy 4.6.0 with Oracle WebLogic Portal. Note that you must obtain the binaries from Autonomy Corporation at http://www.autonomy.com to use in conjunction with the sample Autonomy integration code.

2.2 IDOL Server System Requirements

Autonomy's Intelligent Data Operating Layer (IDOL) server is the main component that is required to use Autonomy search capabilities with Oracle WebLogic Portal. The IDOL server should be installed by a system administrator.

2.2.1 Supported Platforms

Microsoft Windows NT4, 2000, XP and 2003
Linux (all versions) kernel 2.2, 2.4 and 2.6
Sun Solaris for SPARC versions 5 - 9
Sun Solaris for Intel version 9
AIX version 4.3, 5 and 5.1
HP-UX for PA-RISC version 10, 11 and 11i
HP-UX for Itanium version 11i
Tru64 version 5.1
IDOL server also supports other POSIX UNIX versions on request.

Note:
Autonomy search engine and fetch processes might not start properly on Unix platforms due to missing linked libraries.
Autonomy executable files and shared libraries require certain system libraries to be installed and accessible, via the library path, in order to start properly. If your target server does not have these libraries, one or more of the following processes might not start: AutonomyDiSH.exe, AutonomyIDOLServer.exe, content.exe, category.exe, community.exe, agenstore.exe, BEACMRepoFetch.exe, FileSystemFetch.exe, HTTPFetch.exe.

For the processes which failed to start, validate the linked libraries by using the unix ldd command. If any issues are found, obtain and install the missing library file(s).

2.2.2 Minimum Hardware Requirements

1 Gb RAM
30 Gb Disk
1.5 GHz CPU

2.2.3 Recommended Hardware Requirements

A dedicated SCSI disk
4 Gb RAM
100 Gb Disk
A minimum of 2 dedicated CPU - XEON 3 GHz or above

2.2.4 Additional Requirements

You cannot run IDOL server with restricted file system permissions (for example disk quotas, file handle limits or memory limits).
Your file system must permit file locking (this means that you cannot run IDOL server on an NFS mount, for example).
Your network must support TCP/IP.
If you upgraded to Oracle WebLogic Portal 10.3.4, the Autonomy license that is delivered with Oracle WebLogic Portal allows you to index 500,000 pieces of content. A single IDOL server can hold an approximate maximum of 8 million document sections (depending on the functionality and performance required). However, the license included with previous versions of Oracle WebLogic Portal allows only 500,000. The current version of Oracle WebLogic Portal does not include an Autonomy license.
If you are running anti-virus software on the machine that hosts IDOL server, you should ensure that it does not monitor the IDOL server directories as this can have a serious impact on IDOL server's performance.

2.2.5 Additional Documentation

For more information about using the Autonomy IDOL server, see the IDOL Server Guide, published by Autonomy Corporation. Contact WebLogic Portal Customer Support to obtain a copy of this guide.

For more information about configuring the IDOL server for use in your portal environment, see "Oracle Fusion Middleware Supported System Configurations."

2.3 DiSH System Requirements

The Autonomy DiSH (Distributed Service Handler) provides a central point from which you can manage Autonomy applications and/or portlets. Table 2-1 lists the system requirements for the Autonomy DiSH.

2.3.1 Additional Documentation

For more information about using the Autonomy DiSH and the Autonomy Service Dashboard which is used to monitor the DiSH, see the Autonomy Distributed Service Handler (DiSH) Administrator's Guide, published by Autonomy Corporation. Contact WebLogic Portal Customer Support to obtain a copy of this guide.

For more information about configuring DiSH for use in your portal environment, see Section 7.2.2, "Configuring the Autonomy DiSH.".

Table 2-1 System Requirements for DiSH

Supported Platform	Minimum Server Requirements
Microsoft Windows 98, NT 4, and 2000	200 MHz Pentium processor 64 MB RAM 1 GB hard disk recommended
Unix	128 MB of RAM 1 GB hard disk recommended
Solaris	128 MB of RAM 1 GB hard disk recommended

Note:

Autonomy search engine and fetch processes might not start properly on Unix platforms due to missing linked libraries.

Autonomy executable files and shared libraries require certain system libraries to be installed and accessible, via the library path, in order to start properly. If your target server does not have these libraries, one or more of the following processes might not start: AutonomyDiSH.exe, AutonomyIDOLServer.exe, content.exe, category.exe, community.exe, agenstore.exe, BEACMRepoFetch.exe, FileSystemFetch.exe, HTTPFetch.exe.

For the processes which failed to start, validate the linked libraries by using the unix ldd command. If any issues are found, obtain and install the missing library file(s).

2.4 Autonomy Service Dashboard Requirements

To run Autonomy Service Dashboard you need a third party application server that is J2EE 1.3 compliant. You also need a Java Development Kit (JDK) installation, version 1.4.

Note:

If you are using a web server that is separate from your application server, you must ensure that they are configured to run together.

Autonomy Service Dashboard runs with the following application servers:

JRun 4.0 or higher
Tomcat 4.0.0 or higher
Resin 2.1.1 or higher
ServletExec 4.2 or higher
WebLogic 6.1 or higher
WebSphere 5

These application servers all include an internal web server component that Autonomy Service Dashboard can operate with. Alternatively, you can integrate your application server with an external web server such as:

Microsoft IIS version 5 and higher
Apache 2 version 5 and higher

2.4.1 Additional Documentation

For additional information about using HTTP Fetch, see the Autonomy DiSH Administrator's Guide, published by Autonomy Corporation. Contact WebLogic Portal Customer Support to obtain a copy of this guide.

For additional information about installing the Autonomy Service Dashboard for use within your portal environment, see the Section 7.7, "Installing Autonomy Service Dashboard,".

2.5 Autonomy Portlet System Requirements

Autonomy portlets require the same system requirements as the application server from which they are run. For additional information, see "Oracle Fusion Middleware Supported System Configurations."

2.6 HTTP Fetch System Requirements

HTTP Fetch is a connector the is used to index content from web sites. HTTP Fetch should be installed by the system administrator as part of a larger Autonomy system (a system that includes Autonomy IDOL server and an interface for the information stored in IDOL server). Table 2-2 lists the system requirements for HTTP Fetch.

2.6.1 Additional Documentation

For additional information about using HTTP Fetch, see the Autonomy HTTP Fetch Administrator's Guide, published by Autonomy Corporation. Contact WebLogic Portal Customer Support to obtain a copy of this guide.

For additional information about configuring HTTP Fetch for use within your portal environment, see Section 7.2.4, "Configuring HTTP Fetch."

Table 2-2 System Requirements for HTTP Fetch

Supported Platform	Minimum Server Requirements
Microsoft Windows NT and 2000 (Intel)	200 MHz Pentium processor 64 MB RAM 2 GB hard disk recommended
Unix	128 MB of RAM 2 GB hard disk recommended 2.2.12 kernel
Solaris 2.5 (Sun Sparc)	128 MB of RAM 2 GB hard disk recommended

Note:

Autonomy search engine and fetch processes might not start properly on Unix platforms due to missing linked libraries.

For the processes which failed to start, validate the linked libraries by using the unix ldd command. If any issues are found, obtain and install the missing library file(s).

2.7 File System Fetch System Requirements

File System Fetch should be installed by the system administrator as part of a larger Autonomy system (that is a system that includes Autonomy IDOL server and an interface for the information stored in IDOL server). Table 2-3 lists the system requirements for File System Fetch.

2.7.1 Additional Documentation

For additional information about using File System Fetch, see the Autonomy File System Fetch Administrator's Guide, published by Autonomy Corporation. Contact WebLogic Portal Customer Support to obtain a copy of this guide.

For additional information about configuring File System Fetch for use within your portal environment, see Section 7.2.5, "Configuring File System Fetch."

Table 2-3 System Requirements for File System Fetch

Supported Platform	Minimum Server Requirements
Microsoft Windows NT 4, 2000 and XP	200 MHz Pentium processor 128 MB RAM 200 MB hard disk
Solaris	128 MB of RAM 2 MB hard disk
Linux	128 MB of RAM 2 GB hard disk

Note:

This specification is dependent on the amount of data to be fetched. Due to substantially different disk usage patterns. File System Fetch also supports other POSIX UNIX versions on request.

Note:

Autonomy search engine and fetch processes might not start properly on Unix platforms due to missing linked libraries.

For the processes which failed to start, validate the linked libraries by using the unix ldd command. If any issues are found, obtain and install the missing library file(s).

2.8 ODBC Fetch System Requirements

ODBC Fetch is used to index content from ODBC-compatible databases. ODBC Fetch should be installed by the system administrator as part of a larger Autonomy system.

Table 2-4 lists the system requirements for ODBC Fetch.

2.8.1 Additional Documentation

For additional information about using ODBC Fetch, see the Autonomy ODBC Fetch Administrator's Guide, published by Autonomy Corporation. Contact WebLogic Portal Customer Support to obtain a copy of this guide.

Table 2-4 System Requirements for ODBC Fetch

Supported Platform	Minimum Server Requirements
Microsoft Windows NT 4 and 2000	200 MHz Pentium processor 64 MB RAM 2 GB hard disk
Solaris	128 MB of RAM 2 GB hard disk
Linux	128 MB of RAM 2 GB hard disk

ODBC Fetch also supports other POSIX UNIX versions on request.
This specification is dependent on the amount of data to be fetched. Due to substantially different disk usage patterns it is beneficial to run fetch and DRE processes on separate drives or partitions.
You must have ODBC version 2.0 (or higher) drivers for the target database type(s). The Server also needs to have an appropriate Data source set up for each database containing content. This is done via the Control Panel. Data sources should be configured as System-wide (the "System DSN" tab) to ensure that they are accessible to all users.
The ODBC Fetch requires an underlying ODBC Driver in order to connect to the data source. For example, if you want to run the ODBC Fetch on Solaris to access an Oracle 8.0 server running on the same or another platform, you must use an Oracle 8.0 compatible ODBC Driver for Solaris.