2 Installation Prerequisites

This chapter provides software requirements, as well as environmental and third-party software prerequisites for Oracle WebCenter Interaction. You must read this chapter and meet the prerequisites before proceeding to the installation.

Complete the following basic steps to prepare your network and host computers for deployment:

1. Download the most up-to-date documentation from the Oracle Technology Network in the Oracle WebCenter Interaction 10g Release 4 (10.3.3.0.0) documentation set.

2. Read the product release notes for information on compatibility issues, known problems, and workarounds that might affect how you proceed with your deployment.

3. Provision host computers for your deployment and install prerequisite software. For details, see Software Requirements.

   Note:

   If you are running Microsoft Internet Information Server (IIS) 7, you must install the IIS 6 Management Compatibility suite (this option is available when installing IIS 7.

4. Ensure that you have administrative access to the resources you must complete installation and configuration tasks. For details, see Administrative User Requirements.

5. If you are installing the .NET portal on a 32 bit system, you must enable the /3GB switch in the Boot Configuration Data (BCD) store (for Windows 2008) or in the boot.ini file (for Windows 2003) on the Oracle WebCenter Interaction host computer. For details, see Virtual Memory Requirements for .NET Portals.

6. If you are using Oracle Database in your deployment, set the Oracle environment variables. For details, see Setting Oracle Environment Variables.

7. If you are using Oracle WebLogic Server in your deployment, disable Basic Authentication. For details, see Preparing Oracle WebLogic Server for Oracle WebCenter Interaction.

8. If you are using Microsoft Internet Information Services 7.0 in your deployment, you must install the IIS 6.0 Management Compatibility Components. For details, see Preparing Microsoft Internet Information Services 7.0 for Oracle WebCenter Interaction.

9. If you are installing Oracle WebCenter Interaction Content Service for Documentum, you must first install the Documentum DFC Runtime Environment. For details, see Configuring the Documentum DFC Runtime Environment.

10. If you are installing Oracle WebCenter Interaction Content Service for Windows Files, register your .NET extensions in Microsoft Internet Information Services. For details, see Configuring Microsoft Internet Information Services for Oracle WebCenter Interaction Content Service for Windows Files.

11. If you are installing Oracle WebCenter Interaction Content Service for Microsoft Exchange, install a supported version of the Microsoft Outlook or Microsoft Exchange client, and create and configure a Windows user for use with this service. For details, see Creating a Domain User for Oracle WebCenter Interaction Content Service for Microsoft Exchange.

Software Requirements

For the latest information on supported operating systems, application servers, databases, and browsers, see the Oracle WebCenter Interaction page at http://www.oracle.com/technetwork/middleware/webcenter-interaction/index.html, open the Oracle WebCenter Interaction 10g Release 4 Certification Matrix spreadsheet, and refer to the WebCenter Interaction 10.3.3 worksheet.

For more information on recommended configurations based on the size of your implementation, see the section about provisioning computers in the Oracle Fusion Middleware Deployment Planning Guide for Oracle WebCenter Interaction.

Administrative User Requirements

This section describes the administrative user permissions required to install Oracle WebCenter Interaction components on Microsoft Windows.

Table 2-1 Administrative User Permissions

User	Permissions
Local Host Administrator Account	The installing user must have local administrative rights. You must log in to the host computer as the local administrator.
Valid NT User	The installer requests the domain, user name, and password for a valid NT user.
Portal Database and Portal Administrative User Accounts	To configure the required portal database and portal administrative objects, you must provide the user name and password for the appropriate administrative user accounts.

Virtual Memory Requirements for .NET Portals

If you run your portal on .NET, you must enable the /3GB switch in the Boot Configuration Data (BCD) store (for Windows 2008) or in the boot.ini file (for Windows 2003) on the Oracle WebCenter Interaction host computer. The /3GB switch configures the user mode virtual address space available to each process.

To enable the /3GB switch for Windows 2008:

1. Log in to the Oracle WebCenter Interaction host computer as a user with Administrator privileges.

2. Open an elevated command prompt.

3. Run the following command:

   BCDEDIT.EXE /Set IncreaseUserVa 3072
   

4. Reboot the portal host computer.

Note:

You must add the /3GB flag to the BCD store correctly; editing the BCD store incorrectly might negatively affect the stability of your portal computer. For this reason, we strongly advise that you refer to appropriate documentation at http://msdn.microsoft.com when performing this procedure. If you experience technical difficulties, contact Microsoft support.

To enable the /3GB switch for Windows 2003:

1. Open the boot.ini file, which is located in the C: directory.

   The boot.ini file is hidden and read-only, so you must configure Windows to make hidden files visible and enable write privileges on the boot.ini file.

2. In the boot.ini file, add a /3GB flag to the end of the multi line, which specifies the partition to boot. For example:

   multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003, Standard" /3GB /fastdetect /NoExecute=OptOut
   

3. Reboot the portal host computer.

Note:

You must add the /3GB flag to the boot.ini file correctly; editing this file incorrectly might negatively affect the stability of your portal computer. For this reason, we strongly advise that you refer to appropriate documentation at http://msdn.microsoft.com when performing this procedure. If you experience technical difficulties, contact Microsoft support.

Setting Oracle Environment Variables

This table describes the Oracle Environment variables that must be set when installing Oracle WebCenter products to instances of Oracle9i or Oracle Database 10g.

Environment Variable	Description	Example Values
ORACLE_BASE	Must be set to the root directory of your Oracle installation.	C:\oracle
ORACLE_HOME	Must be set to the home directory of your Oracle installation.	C:\oracle\ora92
ORACLE_SID	Must be set to the system ID (SID) of the portal database instance.	(Oracle9i) PLUM (Oracle Database 11g) PLUM11 Note: PLUM or PLUM10 are expected by the SQL scripts. If you set your SID to a value other than these example values, you must edit the SQL scripts to reflect this change.

Preparing Oracle WebLogic Server for Oracle WebCenter Interaction

This section describes how to configure Oracle WebLogic Server for use with the Oracle WebCenter Interaction portal application.

WebLogic Basic Authentication must be disabled for the Oracle WebCenter Interaction portal application on Oracle WebLogic Server. To do this, in the Oracle WebLogic Server config.xml for the Oracle WebCenter Interaction portal, set <enforce-valid-basic-auth-credentials> to false.

1. Disable WebLogic Basic Authentication for the Oracle WebCenter Interaction portal application.

   1. Open WebLogic_home\user_projects\domains\domain\config\config.xml in a text editor, where WebLogic_home is your Oracle WebLogic installation directory.

   2. In the <security-configuration> section, set <enforce-valid-basic-auth-credentials> to false.

      If <enforce-valid-basic-auth-credentials> is already defined in this section, change its value to false.

      If <enforce-valid-basic-auth-credentials> does not exist in this section, add the following line before the </security-configuration> line as shown below:

      <security-configuration>
      ...
          <enforce-valid-basic-auth-credentials>
          false
          </enforce-valid-basic-auth-credentials>
      </security-configuration>
      

2. Increase the JVM's MaxPermSize.

   A MaxPermSize of 256m is recommended. If MaxPermSize is set too low, you will see java.lang.OutOfMemoryError: PermGen space when attempting to start the portal.To increase MaxPermSize, edit the setDomainEnv.sh script for your domain. Find where MaxPermSize is being set for your JAVA_VENDOR, and set it to 256m.

   For example:

   if [ "${JAVA_VENDOR}" = "HP" ] ; then
       #MEM_ARGS="${MEM_ARGS} -XX:MaxPermSize=128m"
       MEM_ARGS="${MEM_ARGS} -XX:MaxPermSize=256m"
       export MEM_ARGS
   fi
   

Preparing Microsoft Internet Information Services 7.0 for Oracle WebCenter Interaction

This section describes configuration of Microsoft Internet Information Services 7.0 required before the installation and deployment of Oracle WebCenter Interaction.

1. In the Start menu, click All Programs, then Administrative Tools, then Server Manager.

2. In the left pane of the Server Manager, expand the node for Roles, right-click Web Server (IIS), then click Add Role Services.

3. In the Role Services list, select IIS 6 Management Compatibility.

4. Click Next.

5. Click Install.

Configuring the Documentum DFC Runtime Environment

If you are installing Oracle WebCenter Interaction Content Service for Documentum, you must first install the Documentum DFC Runtime Environment. For details on installation of Documentum products, refer to Documentum documentation.

After you install the Documentum Desktop Client on the Remote Server host computer, configure the dmcl.ini file for the client as follows:

• Set the host to the docbroker that will be used by all users of this Remote Server. To allow more than one docbroker, you must install a Remote Server for each docbroker.

  [DOCBROKER_PRIMARY]
  host = YOURDOCBROKER
  

• Set your max session count to a value comfortably above the number of sessions you expect to be opened by the Oracle WebCenter Interaction Content Service for Documentum content Web services (1 connection per user per content Web service) but comfortably within this computer's performance limitations and well below the maximum number of concurrent sessions allowed by your Documentum server. For more information, refer to Advanced Configuration: Tuning Documentum Server.

  [DMAPI_CONFIGURATION]
  cache_query = T
  connect_pooling_enabled=T 
  connect_recycle_interval=100 
  max_session_count=
  Docbroker_search_order=RANDOM
  

Configuring Microsoft Internet Information Services for Oracle WebCenter Interaction Content Service for Windows Files

If you are installing Oracle WebCenter Interaction Content Service for Windows Files, you must configure Microsoft Internet Information Services (IIS) to work with your installation.

Registering .NET Extensions in IIS

The Oracle WebCenter Interaction Content Service for Windows Files installer expects .NET extensions to be registered and allowed in IIS.

To register .NET extensions from the command line, run the following:

<.net_directory>\aspnet_regiis.exe -i

To allow ASP.NET extensions:

1. Open IIS Manager. In the Start menu, click Programs, then Administrative Tools, then Internet Information Services Manager.

2. In the left pane of the IIS Manager, expand the node for the Web server and click Web Service Extensions.

3. In the right pane, view a list of Web service extensions and the status (Prohibited or Allowed) for each. Right-click the extension name and select Allow to enable it.

Creating a Domain User for Oracle WebCenter Interaction Content Service for Microsoft Exchange

If you are installing Oracle WebCenter Interaction Content Service for Microsoft Exchange, create and configure a Microsoft Windows domain user for use with this service:

1. Create a Microsoft Windows domain user named ali-exchangecs-user and provision an account for this user on the Microsoft Exchange Server. This administrative user runs the crawl jobs, so you should create the account for this purpose only.

2. On the remote server host computer, log in as ali-exchangecs-user, open Microsoft Outlook and dismiss any initialization screens.

3. Configure Microsoft Outlook as the default mail client for ali-exchangecs-user, and select the option to save the password.

4. Using the Microsoft Windows security policy manager, add the ali-exchangecs-user to the Act as part of the operating system policy.

5. Ensure that the ali-exchangecs-user can access all the Microsoft Exchange folders you want to crawl.

6. To test connectivity between the Microsoft Outlook client and the Microsoft Exchange Server, send mail from ali-exchangecws-user to ali-exchangecs-user.

   Note:

   Oracle WebCenter Interaction Content Service for Microsoft Exchange does not send or receive mail. This step is only a test.