Supported Configurations for Oracle WebLogic Server, WebLogic Portal and WebLogic Integration 10gR3 (10.3)

Autonomy Support

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:

• Support for Local Autonomy Installation
• Using a Remote Autonomy Installation

 

---

Support for Local Autonomy Installation

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:

 

See http://dev2dev.bea.com/wlportal/autonomy/index.html.

 

---

Using a Remote Autonomy Installation

The following sections provide information on using a remote Autonomy Installation:

• Support for Remote Autonomy Installation
• Requirements for Remote Autonomy Installation
• How to create a Remote Autonomy Installation
• Setting Up BEA Content Management Search

Support for Remote 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:

 

Requirements for 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:

Figure 6-1 Example Remote Autonomy Installation

 

How to create a Remote Autonomy Installation

Use the following steps to create a remote Autonomy installation:

Choose an alternate supported operating system (target OS) on which to run Autonomy.
Go to the BEA download site at http://commerce.bea.com/index.jsp.
Click on the link for BEA WebLogic.
Click on the link for BEA WebLogic Portal 10.3.
From the list of OS Platforms, select the installer for your target OS.
Install WebLogic Portal 10.3.
Optional, when the installation process is complete, you may remove any or all of the non-Autonomy related artifacts such as WebLogic Server, Workshop Runtime for WebLogic Platform, or WebLogic Portal.
Navigate to WL_HOME/portal/thirdparty/autonomy-wlp103/<operating_system_directory> and configure autonomy and BEACMRepoFetch as documented.
Use the instructions in Configuring Autonomy on Your Target Server in BEA WebLogic Portal 10.3 Integrating Search to configure your Autonomy installation.

Caution: Do not move or copy any Autonomy files from this installation.

Use the instructions in Setting up BEA Content Management Search in BEA WebLogic Portal 10.3 Integrating Search to configure the BEA Content Management Fetch.

Setting Up BEA Content Management Search

Use the following steps to utilize a shared file system to configure a BEA Content Management search:

Create a shared directory using the tools and instructions according to your target operating system platform(s) where shared_drive is the name of your shared drive.
On the Autonomy host, mount shared_drive.
For each Weblogic Portal 10.3 managed server in your cluster, mount shared_drive.

Note: Mount shared_drive with the same exact mapping on each managed server.

Set the WLP_SEARCH_OPTION environment variable to none on each managed server to prevent Autonomy from starting with WebLogic Portal instance.
Using the WebLogic Portal Administration Console, set the search.staging.area repository property to shared_drive after the WL_HOME environment 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.
If shared_drive on the Autonomy host is not WL_HOME/portal/thirdparty/autonomy-wlp103/internal/BEACMRepoTemp, use a text editor to modify the DirectoryPathCSVs variable under the BEACMRepoImport and BEACMRepoIDXImport to point to shared_drive/binary and shared_drive/nonbinary in the WL_HOME/portal/thirdparty/autonomy-wlp103/<operating_system_directory>/internal/BEACMRepoFetch/BEACMRepoFetch.cfg file.
Start the Autonomy components on the Autonomy host. See the autonomy.sh or autonomy.cmd file in WL_HOME/portal/thirdparty/autonomy-wlp103 for a sample start script.