Supported Configurations for Oracle WebLogic Server, WebLogic Portal and WebLogic Integration 10gR3 (10.3)
WebLogic Portal uses certain products from Autonomy for searching unstructured or structured data, including content stored in the BEA Content Repository. The following sections provide information on support for local and remote Autonomy installations:
Where possible, the WebLogic Portal installer includes the required Autonomy components and is referred to as a local Autonomy installation. Local Autonomy is only supported on platforms using a 32-bit JDK. The following table provides the operating system and hardware where the WebLogic Portal supports local Autonomy installation:
The WebLogic Portal installer for certain platforms does not include these Autonomy components due to incomatibilities between the supported operating system, WebLogic Portal, and Autonomy. In these situations, you must choose an alternate supported operating system on which to run Autonomy. Remote Autonomy installations are supported for platforms using 32- bit and 64-bit JDKs. This installation is remote to your WebLogic Portal installation. The following table provides the operating system and hardware where the WebLogic Portal supports remote Autonomy installation:
In a configuration where WebLogic Portal is running on an operating system that is not supported by Autonomy, you must provide a shared file system that can be written to by each of your WebLogic Portal servers and is also accessible by the server that is hosting Autonomy. This allows the BEA Content Repository to continue to utilize Autonomy components for indexing and searching content. The following figure provides asimple example of a remote Autonomy installation using a shared file system:
/portal/thirdparty/autonomy-wlp103/<operating_system_directory>and configure autonomy and BEACMRepoFetch as documented.
shared_driveis the name of your shared drive.
WLP_SEARCH_OPTIONenvironment variable to
noneon each managed server to prevent Autonomy from starting with WebLogic Portal instance.
search.staging.arearepository property to
WL_HOMEenvironment variable is set. For more information on setting other Autonomy properties, see Adding Autonomy Properties to your BEA Repository in BEA WebLogic Portal 10.3 Integrating Search.
shared_driveon the Autonomy host is not
/portal/thirdparty/autonomy-wlp103/internal/BEACMRepoTemp, use a text editor to modify the
DirectoryPathCSVsvariable under the
BEACMRepoIDXImportto point to