|
|
WebLogic Portal® incorporates Autonomy® search components to provide portal search features.
When considering system requirements for using Autonomy search, you should first refer to the WebLogic Server system requirements, see the WebLogic Server Supported Configurations Guide.
Autonomy’s system requirements are a subset of the WebLogic Server requirements.
This documents includes the following sections:
Autonomy's Intelligent Data Operating Layer (IDOL) server is the main component is required to use Autonomy search capabilities with WebLogic Portal. The IDOL server should be installed by a system administrator.
| WARNING: | Autonomy search engine and fetch processes might not start properly on Unix platforms due to missing linked libraries. |
| WARNING: | 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. |
| WARNING: | 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). |
For more information about using the Autonomy IDOL server, see the IDOL Server Guide.
For more information about configuring the IDOL server for use in your portal environment, the WebLogic Server Supported Configurations Guide.
The Autonomy DiSH (Distributed Service Handler) provides a central point from which you can manage Autonomy applications and/or portlets. Table 1 lists the system requirements for the Autonomy DiSH.
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.
For more information about configuring DiSH for use in your portal environment, see the WebLogic Portal Search Guide.
| WARNING: | Autonomy search engine and fetch processes might not start properly on Unix platforms if your server is missing linked libraries. |
| WARNING: | 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. |
| WARNING: | 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). |
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:
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:
For additional information about using HTTP Fetch, see the Autonomy DiSH Administrator’s Guide.
For additional information about installing the Autonomy Service Dashboard for use within your portal environment, see the WebLogic Portal Search Guide.
Autonomy portlets require the same system requirements as the application server from which they are run. For additional information, see the WebLogic Server Supported Configurations Guide.
HTTP Fetch is a connector the is used to index content from websites. 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 lists the system requirements for HTTP Fetch.
For additional information about using HTTP Fetch, see the Autonomy HTTP Fetch Administrator’s Guide.
For additional information about configuring HTTP Fetch for use within your portal environment, see the WebLogic Portal Search Guide.
| WARNING: | Autonomy search engine and fetch processes might not start properly on Unix platforms if your server is missing linked libraries. |
| WARNING: | 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. |
| WARNING: | 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). |
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 3 lists the system requirements for File System Fetch.
For additional information about using File System Fetch, see the Autonomy File System Fetch Administrator’s Guide.
For additional information about configuring File System Fetch for use within your portal environment, see the WebLogic Portal Search Guide.
| 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. |
| WARNING: | Autonomy search engine and fetch processes might not start properly on Unix platforms if your server is missing linked libraries. |
| WARNING: | 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. |
| WARNING: | 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). |
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 4 lists the system requirements for ODBC Fetch.
For additional information about using ODBC Fetch, see the Autonomy ODBC Fetch Administrator’s Guide.
For additional information about configuring ODBC Fetch for use within your portal environment, see the WebLogic Portal Search Guide.
| Notes: | ODBC Fetch also supports other POSIX UNIX versions on request. |
| Note: | 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. |
| Note: | 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. |
| Note: | 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. |
| WARNING: | Autonomy search engine and fetch processes might not start properly on Unix platforms if your server is missing linked libraries. |
| WARNING: | 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. |
| WARNING: | 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). |
|