3 Preparing to Install WebCenter Sites on Oracle WebLogic Application Server

This chapter contains information about configuring WebLogic Server to support your WebCenter Sites web application.This document contains the following sections:

• Section 3.1, "Quick Reference for Setting Up WebLogic Application Server"

• Section 3.2, "Step 1: Configuring WebLogic Application Server"

• Section 3.3, "Step 2: Integrating Oracle WebLogic Server with a Supported Web Server"

Note:

Before starting the procedures in this chapter, ensure you have completed the prerequisite steps described in Chapter 2, "Prerequisites for Installing WebCenter Sites."

3.1 Quick Reference for Setting Up WebLogic Application Server

This section contains the following topics:

• Section 3.1.1, "Summary of Steps"

• Section 3.1.2, "Paths and Directories Used in This Chapter"

• Section 3.1.3, "Start/Stop Commands for WebLogic Server"

3.1.1 Summary of Steps

Complete the steps below for each development, content management, and delivery environment on which you have installed the application server.

Step 1: Configuring WebLogic Application Server

1. Create a WebLogic domain, as shown in Section 3.2.1, "Creating a WebLogic Domain." This step requires you to create a domain with an admin server.

2. Configure the WebLogic domain as shown in Section 3.2.2, "Configuring the WebLogic Domain." This step requires you to:

   1. Create a machine for each physical server that will be running a WebLogic server. For instructions, see Section 3.2.2.1, "Creating Machines."

   2. If you are configuring a cluster environment, create and configure a cluster as described in Section 3.2.2.2, "Creating and Configuring a Cluster."

   3. Create and configure one or more WebLogic managed servers. For instructions, see Section 3.2.2.3, "Creating and Configuring Managed Servers."

   4. Create and configure a data source as described in Section 3.2.2.4, "Creating and Configuring a Data Source."

   5. Set Java options, as described in Section 3.2.2.5, "Setting Java Options."

   6. Set classpath, as described in Section 3.2.2.6, "Setting the Classpath."

   7. If you are configuring a multi-server environment, transfer any remote managed servers to their remote physical servers, as described in Section 3.2.2.7, "Transfer Remote Managed Servers."

Step 2: Integrating WebLogic Application Server with a Supported Web Server

If your environment requires a web server, you have the option to integrate WebLogic application servers with an Oracle, Apache, or IIS web server, as described in:

• Section 3.3.1, "Configuring the Oracle HTTP Server"

• Section 3.3.2, "Configuring the Apache HTTP Server"

• Section 3.3.3, "Configuring the IIS Web Server"

3.1.2 Paths and Directories Used in This Chapter

Table 3-1 lists paths and directories used in this chapter.

Table 3-1 Paths and Directories Used in Configuring WebLogic Application Server

Name	Description
<sites_install_dir>	Path to the directory where WebCenter Sites is installed; the path does not include the name of the WebCenter Sites application.
<shared_dir>	Path to the shared folder on the given system; the path includes the name of the shared folder.
<sites_deploy_home>	The projected path of the exploded WebCenter Sites web application. The WebCenter Sites installer uses a specified deployment directory (<deploy_home>) and a specified WebCenter Sites application name (<sites_app_name>), and explodes the web application into the path <deploy_home>/<sites_app_name>.
<weblogic_home>	Path to the directory where WebLogic is installed. The path includes the name of the directory.
<domain_home>	Path to the WebLogic domain. The path includes the domain name.
<apache_home>	Path to the directory where the Apache web server is installed. The path includes the name of the directory.

3.1.3 Start/Stop Commands for WebLogic Server

This section lists commands that are used in this guide for managing WebLogic Server.

Note:

We assume that you are using a UNIX-based system. For Windows-based installations, the commands end in either .cmd or .bat extensions.

• Start the admin server:

  <domain_home>/bin/startWebLogic.sh
  

• Stop the admin server:

  <domain_home>/bin/stopWebLogic.sh
  

• Start the node manager:

  <weblogic_home>/wlserver_10.3/server/bin/startNodeManager.sh
  

• Start a managed server:

  <domain_home>/bin/startManagedWebLogic.sh <managed_server_name> http://<admin_server_host>:<admin_port>
  

• Stop a managed server:

  <domain_home>/bin/stopManagedWebLogic.sh <managed_server_name> http://<admin_server_host>:<admin_port>
  

3.2 Step 1: Configuring WebLogic Application Server

To configure the WebLogic application server, you will complete the following steps:

• Section 3.2.1, "Creating a WebLogic Domain"

• Section 3.2.2, "Configuring the WebLogic Domain"

3.2.1 Creating a WebLogic Domain

In the steps below, you will be creating a WebLogic domain and configuring an admin server. In a multi-server non-clustered environment, you may create a single domain and administer all local and remote servers from a single administration console, or create a domain for each standalone server. In a clustered environment, create the domain on the primary cluster member.

To create and configure a WebLogic Server domain

1. Change directories to <weblogic_home>/wlserver_10.3/common/bin and run config.sh (.cmd for Windows).

2. Create a domain:

   1. In the Welcome screen, select Create a new WebLogic domain and click Next.

   2. In the Select Domain Source screen, select Generate a domain configured automatically to support Basic WebLogic Server Domain (Figure 3-1) and click Next.

      Figure 3-1 Domain Source Selection

      
      Description of ''Figure 3-1 Domain Source Selection''
      
      

   3. In the Specify Domain Name and Location screen, enter the name and path of the WebLogic domain (Figure 3-2). Click Next.

      Figure 3-2 Domain Name and Location

      
      Description of ''Figure 3-2 Domain Name and Location''
      
      

      Note:

      The path to the domain will be referred to throughout this guide as <domain_home>.

   4. In the Configure Administrator Username and Password screen, enter a user name and password for the WebLogic domain (Figure 3-3). Click Next.

      Figure 3-3 Administrator User Name and Password

      
      Description of ''Figure 3-3 Administrator User Name and Password''
      
      

   5. In the Configure Server Start Mode and JDK screen, select Development Mode and the preferred SDK (in the WebLogic Supplied JDKs list box). See Figure 3-4. For production environments, the domain will be changed to Production Mode later in this guide in Section 6.7, "Switching WebLogic Application Server to Production Mode (Delivery Systems Only)." Click Next.

      Note:

      If a JRockit JDK is used, then you must create an optimization file containing the following:

      { match: [ "net/sf/ehcache/Cache.get*","com/fatwire/cache/ehcache/EhCacheObjectCache._get*","com/fatwire/cache/ehcache/EhCacheObjectCache.get*","net/sf/ehcache/Cache.isExpired*" ], hotspot : { enable : false },}
      

      This file needs to be copied to each physical server where a WebLogic server is run.

      Figure 3-4 Server Start Mode and JDK Configuration

      
      Description of ''Figure 3-4 Server Start Mode and JDK Configuration''
      
      

   6. In the Select Optional Configuration screen, select Administration Server (Figure 3-5). Managed Servers, Clusters, and Machines will be created and configured later in the guide. Click Next.

      Figure 3-5 Optional Configuration

      
      Description of ''Figure 3-5 Optional Configuration''
      
      

3. Configure the admin server (Figure 3-6):

   1. Enter the admin server's name, address, and port.

   2. If you want to use SSL, select SSL enabled and include the port for it to run on (recommended for Delivery).

   3. Click Next.

      Figure 3-6 Administration Server Configuration

      
      Description of ''Figure 3-6 Administration Server Configuration''
      
      

      Note:

      Throughout this guide, the values that you entered will be referred to as <admin_server_host> and <admin_port>.

4. Review the domain configuration (Figure 3-7) and click Create.

   Figure 3-7 Configuration Summary

   
   Description of ''Figure 3-7 Configuration Summary''
   
   

5. The domain installation begins (Figure 3-8). When the installation is complete, click Done.

   Figure 3-8 Domain Creation

   
   Description of ''Figure 3-8 Domain Creation''
   
   

3.2.2 Configuring the WebLogic Domain

In this section, you will complete the steps listed below:

• Section 3.2.2.1, "Creating Machines"

• Section 3.2.2.2, "Creating and Configuring a Cluster"

• Section 3.2.2.3, "Creating and Configuring Managed Servers"

• Section 3.2.2.4, "Creating and Configuring a Data Source"

• Section 3.2.2.5, "Setting Java Options"

• Section 3.2.2.6, "Setting the Classpath"

• Section 3.2.2.7, "Transfer Remote Managed Servers"

3.2.2.1 Creating Machines

A machine is a logical representation of a physical server that hosts one or more WebLogic servers. The Administration Server uses a machine definition with Node Manager to start remote servers.

To create machines:

1. Start the administration server.

   <domain_home>/bin/startWebLogic.sh
   

2. Log in to the WebLogic Server Administration Console:

   http://<admin_server_host>:<admin_port>/console
   

3. In the tree on the left, expand Environment and click Machines.

4. For each physical server that will have a WebLogic server running complete the following steps:

   1. Click New.

   2. Enter a Name.

   3. Select an OS.

   4. Click Next.

   5. If you want to use a secure listener, select SSL, otherwise select Plain.

   6. Enter a Listen Address.

   7. Modify the port as needed.

   8. Click Finish.

3.2.2.2 Creating and Configuring a Cluster

In a cluster environment, all WebLogic servers belong to a cluster, and communication between the servers is managed by the application server.

1. From the Administration Console, expand Environment and click Clusters.

2. Create a cluster:

   1. Click New.

   2. Enter a cluster name.

   3. Select Multicast.

   4. Modify the Multicast Address as needed.

   5. Enter an unused port for Multicast Port.

   6. Click OK.

3. (Optional) Enable Session Persistence:

   1. Click the newly created cluster and select the Replication tab.

   2. For Cross-cluster Replication Type, select MAN (Synchronous) HTTP Session State Replication.

   3. Leave Remote Cluster Address blank.

   4. For Replication Channel, enter a name for the channel to be used for replication traffic. This name should be unique for each cluster in the domain. Later in the guide, a network channel with this name will be created for every server in the cluster.

   5. Click Save.

4. Continue to Section 3.2.2.3, "Creating and Configuring Managed Servers."

3.2.2.3 Creating and Configuring Managed Servers

For each server that will be managed by this Administration Console (all servers in a cluster environment), complete the steps below:

To create and configure managed servers:

1. From the Administration Console, expand Environment and click Servers.

2. Create a Managed Server:

   1. Click New.

   2. Enter a Server Name, Server Listen Address, and Server Listen Port.

   3. If the server is part of a single-server or multi-server load balanced environment, select No, this is a stand-alone server. If the server is part of a cluster environment, select Yes, make this server a member of an existing cluster and select the name of the cluster created in Section 3.2.2.2, "Creating and Configuring a Cluster."

   4. Click Next.

   5. Click Finish.

3. Associate the server with a Machine:

   1. Click the newly created server.

   2. For Machine, select the machine corresponding to the physical server this WebLogic server will be running on.

   3. Click Save.

4. In order to manipulate a server and its deployments using the weblogic. Deployer and weblogic.Admin utilities, tunneling must be enabled.

   Enable Tunneling:

   1. Click the Protocols tab.

   2. Select the Enable Tunneling checkbox.

   3. Click Save.

5. Create the Replication Channel:

   Note:

   If this is not a cluster environment or session persistence will not be used, skip this step.

   1. From the Protocols tab, click the Channels tab.

   2. Click New.

   3. Enter the name of the replication channel specified in step 3 in Section 3.2.2.2, "Creating and Configuring a Cluster."

   4. For Protocol, select http.

   5. Click Next.

   6. Leave the addresses blank and the default ports.

   7. Click Finish.

3.2.2.4 Creating and Configuring a Data Source

This section explains how to create a data source for any of the supported databases using the Administration Console.

1. (DB2 Only) Add the IBM DB2 Driver jar files to the domain classpath.

   1. Stop the administration server.

      <domain_home>/bin/stopWebLogic.sh
      

      Note:

      db2jcc4.jar is not supported.

   2. Copy the db2jcc.jar and db2jcc_license_cu.jar from DB2 to a location that can be added to the domain classpath.

   3. Open <domain_home>/bin/setDomainEnv.sh in a text editor and search for the following line:

      # ADD EXTENSIONS TO CLASSPATHS
      

   4. Add the following line after it:

      PRE_CLASSPATH="<path_to_db2jcc.jar>:<path_to_db2jcc_license_cu.jar>:${PRE_CLASSPATH}"
      

   5. Save the changes.

      Note:

      In order to create a DB2 data source, you must first download and apply WebLogic Patches 13536596 and 13870996.

   6. Start the administration server.

2. From the Administration Console, expand Services and click Data Sources.

3. Create a Data Source:

   1. Click New and select Generic Data Source.

   2. For JNDI name, enter a name. Throughout this guide, the value entered will be referred to as <jndi_name>.

   3. For Database Type, select one of the supported databases: Oracle, MS SQL Server, or DB2.

   4. Click Next.

      Figure 3-9 New JDBC Data Source - JNDI Name and Database Type

      
      Description of ''Figure 3-9 New JDBC Data Source - JNDI Name and Database Type''
      
      

   5. For Database Driver, select the option below that corresponds to the type chosen for step c:

      Oracle - Oracle's Driver (Thin) for Instance connections;  Versions:9.0.1 and later
      MS SQL Server - Oracle's MS SQL Server Driver (Type 4) Versions:7.0 and later
      DB2 - Other (IBM DB2 Universal JDBC Type 4 Driver will be used)
      

      Note:

      XA Data Sources are not supported by WebCenter Sites.

   6. Click Next.

   7. Check that Supports Global Transactions and One-Phase Commit are selected, and click Next.

   8. For Connection properties, enter values for Database Name, Host Name, Port, Database User Name, and Password.

      For DB2, only User Name and Password can be entered.

      Figure 3-10 New JDBC Data Source - Connection Properties

      
      Description of ''Figure 3-10 New JDBC Data Source - Connection Properties''
      
      

   9. Click Next.

   10. (DB2 Only) For Driver Class Name, enter com.ibm.db2.jcc.DB2Driver. For URL, enter the following:

       jdbc:db2://<db_host>:<db_port>/<db_name>. For Properties, enter user=<db_user_name>
       

   11. Verify that the data source information is correct, and click Test Configuration. If the test fails, review your data source information and try again. When the test succeeds, click Next.

       Figure 3-11 Data Source Information Verification

       
       Description of ''Figure 3-11 Data Source Information Verification''
       
       

   12. Select the administration server as well as all managed servers that require access to the data source. In a cluster environment, select the cluster instead of selecting individual managed servers.

   13. Click Finish.

4. Configure the Connection Pool Size:

   1. Click the newly created data source.

   2. Click the Connection Pool tab.

   3. For Initial Capacity, enter 10 and for Maximum Capacity, enter 100.

      Note:

      These are recommended values that may be changed as your environment requires.

      Figure 3-12 Configuration - Connection Pool

      
      Description of ''Figure 3-12 Configuration - Connection Pool''
      
      

   4. Click Save.

3.2.2.5 Setting Java Options

This section explains how to set memory arguments as well as add Java options required by WebCenter Sites.

Note:

If a JRockit JDK will be used, you must create an optimization file containing the following:

{ match: [ "net/sf/ehcache/Cache.get*",
"com/fatwire/cache/ehcache/EhCacheObjectCache._
get*","com/fatwire/cache/ehcache/EhCacheObjectCache.get*",
"net/sf/ehcache/Cache.isExpired*" ], 
hotspot : { enable : false },}

1. Stop the administration server.

2. Set Memory Arguments

   1. Open <domain_home>/bin/setDomainEnv.sh in a text editor and search for the following:

      WLS_MEM_ARGS
      

   2. Set the value for WLS_MEM_ARGS_64BIT or WLS_MEM_ARGS_32BIT for both Sun and JRockit. The recommended value is -Xms2048m -Xmx16834m.

   3. Save the changes.

3. Add the required Java options to WebCenter Sites:

   1. Open <domain_home>/bin/startWebLogic.sh in a text editor and search for the following line (located below the Start Derby section):

      JAVA_OPTIONS="${SAVE_JAVA_OPTIONS}" 
      

   2. Modify the line by adding the following Java options:

      • -Dfile.encoding=UTF-8

        This option specifies UTF-8 file encoding.

      • -Dnet.sf.ehcache.enableShutdownHook=true

        This option enables the Ehcache shutdown hook.

      • -Djava.net.preferIPv4Stack=true

        This option specifies the use of IPv4 addresses.

      • -Duser.timezone=UTC

        This option is used to set the time zone for the JVM. It is recommended to set the value to UTC across all WebCenter Sites installations. However, you can set any preferable time zone as long as this value is the same for all WebCenter Sites installations.

      • -Djava.io.tmpdir=<path_to_sites_tmpdir>

        This option specifies which temporary directory the JVM uses. The value should be the path to the directory created in Section 2.1, "Before You Begin."

      • (JRockit JDK only) -XX:+UnlockDiagnosticVMOptions -XX:OptFile=<path_to_optimization_file>

        These options are required when using a JRockit JDK. They signal the JVM to use the optimization file that was created in Section 3.2.1, "Creating a WebLogic Domain."

        Note:

        If Shift-JIS characters will be used, add the following option: -Dcs.useJavaURLDecoder=false

      After making the above changes, the modified line should look as follows:

      JAVA_OPTIONS="-Dfile.encoding=UTF-8  -Dnet.sf.ehcache.enableShutdownHook=true -Djava.net.preferIPv4Stack=true -Duser.timezone=UTC -Djava.io.tmpdir=<path_to_sites_tmpdir> ${SAVE_JAVA_OPTIONS}"
      

   3. Save the changes.

3.2.2.6 Setting the Classpath

This section explains how to add paths required for WebCenter Sites to the application server classpath. To ensure a class is loaded first, it is added to the PRE_CLASSPATH variable.

1. Add the required paths to CLASSPATH for WebCenter Sites.

   1. Open <domain_home>/bin/startWebLogic.sh in a text editor and search for the following line (located below the Start Derby section):

      CLASSPATH="${SAVE_CLASSPATH}" 
      

   2. Modify the line by adding the following path:

      <sites_install_dir>/bin
      

      This path contains the required WebCenter Sites and CAS configuration files. Without this path, the CAS web application will not start and the System Tools node in the Admin tab of the WebCenter Sites Admin interface will have reduced functionality.

   3. Save the changes.

2. Add the required paths to PRE_CLASSPATH for WebCenter Sites.

   1. Open wlserver_10.3/server/bin/startNodeManager.sh in a text editor and search for the following line:

      # Get PRE and POST environment
      if [ ! -z "${PRE_CLASSPATH}" ]; then
        CLASSPATH="PRE_CLASSPATH="<sites_deploy_home>/WEB-INF/lib/commons-lang-2.4.jar:${PRE_CLASSPATH}"${CLASSPATHSEP}${CLASSPATH}"
      

   2. Add the following line after it:

      PRE_CLASSPATH="<sites_deploy_home>/WEB-INF/lib/commons-lang-2.4.jar:${PRE_CLASSPATH}"
      

      This JAR is located in the lib directory of the exploded WebCenter Sites web application. For the WebCenter Sites Contributor interface to load properly, this JAR must be loaded to the classpath prior to the other versions of its classes.

      Note:

      This changes affects all domains.

   3. Save the changes.

3.2.2.7 Transfer Remote Managed Servers

This section explains how to transfer any remote managed servers that were created using the administration console, to the physical servers they will be running on.

1. Make sure that all servers in the domain are shutdown.

2. Create a template from the domain that was created on the primary server. Run the following command from <weblogic_home>/wlserver10.3/common/bin:

   ./pack.sh -managed=true -domain=<domain_home> -template=<template_creation_location>/<template_name>.jar -template_name="<template_name>"
   For example:
   ./pack.sh -managed=true -domain=/opt/Oracle/Middleware/user_projects/domains/SitesDomain -template=/opt/Downloads/SitesDomainTemplate.jar -template_name="SitesDomainTemplate"
   

3. For each remote server, complete the following steps:

   1. Copy the newly created template to the remote server.

      Note:

      The remote server should already have WebLogic server installed.

   2. Unpack the managed server and required domain files from the copied template.

      The domain will be created in the same location as the primary server.

   3. Run the following command from <weblogic_home>/wlserver10.3/common/bin directory:

      ./unpack.sh -domain=<domain_home> -template=<template_location>/<template name>.jar
      

      For example:

      ./unpack.sh -domain=/opt/Oracle/Middleware/user_projects/domains/SitesDomain -template=/opt/Downloads/SitesDomain.jar
      

   4. Copy the <domain_home>/bin/startWebLogic.sh and <domain_home>/bin/setDomainEnv.sh files from the primary server to the <domain_home>/bin directory of the remote server. The modified files are not included in the template.

   5. Modify the files and make any changes to reflect differences in the paths or options added in Section 3.2.2.5, "Setting Java Options" and Section 3.2.2.6, "Setting the Classpath."

   6. Save the changes.

3.3 Step 2: Integrating Oracle WebLogic Server with a Supported Web Server

This chapter provides guidelines for integrating WebLogic Server with your choice of supported web servers.

This chapter contains the following sections:

• Section 3.3.1, "Configuring the Oracle HTTP Server"

• Section 3.3.2, "Configuring the Apache HTTP Server"

• Section 3.3.3, "Configuring the IIS Web Server"

3.3.1 Configuring the Oracle HTTP Server

Follow these steps to configure Oracle HTTP Server with the mod_wl_ohs plugin for use with WebLogic.

1. Open <ohs_instance>/config/OHS/<server_name>/mod_wl_ohs.conf in a text editor and add the following before the commented Location tag:

   Single Server Environment

   <IfModule mod_weblogic.c>
      WebLogicHost {weblogic_host}
      WebLogicPort {weblogic_port}
   </IfModule>
   
   <Location /{sites_context_root}>
     SetHandler weblogic-handler
   </Location>
   
   <Location /cas>
     SetHandler weblogic-handler
   </Location>
   

   Multi Server Environment

   <IfModule mod_weblogic.c>
       WebLogicCluster {weblogic_host1}:{weblogic_port1},{weblogic_host2}:{weblogic_port2}
   </IfModule>
   
   <Location /{sites_context_root}>
     SetHandler weblogic-handler</Location>
   
   <Location /cas>
     SetHandler weblogic-handler
   </Location>
   

2. Save the changes.

3. Restart the web server.

3.3.2 Configuring the Apache HTTP Server

This section explains how to configure Apache 2.2.x HTTP server with the mod_wl plugin to use this plugin with WebLogic.

To configure the mod_wl plug-in

1. Ensure that mod_so.c is enabled. Run <apache_home>/bin/apachectl –l. If mod_so.c is not in the list that is printed, you must rebuild your Apache with the –enable-module=so option.

2. Copy the mod_wl_22.so file from <weblogic_home>/wlserver_10.3/server/plugin/<os_type>/<os_version> to <apache_home>/modules.

3. Open <apache_home>/config/httpd.conf in a text editor and add the following at the end of the file:

   Single Server Environment

   <IfModule mod_weblogic.c>
     WebLogicHost {weblogic_host}
     WebLogicPort {weblogic_port}
   </IfModule>
   
   <Location /{sites_context_root}>
     SetHandler weblogic-handler
   </Location>
   
   <Location /cas>
     SetHandler weblogic-handler
   </Location>
   

   Multi Server Environment

   LoadModule weblogic_module modules/mod_wl_22.so

   <IfModule mod_weblogic.c>
     WebLogicCluster {weblogic_host1}:{weblogic_port1},{weblogic_host2}:{weblogic_port2}
   </IfModule>
   
   <Location /{sites_context_root}>
     SetHandler weblogic-handler
   </Location>
   
   <Location /cas>
     SetHandler weblogic-handler
   </Location>
   

4. Save the changes.

5. Verify the syntax of the httpd.conf file with the following command:

   <apache_home>/bin/apachectl -t
   

6. Restart the web server.

3.3.3 Configuring the IIS Web Server

This section explains how to configure IIS versions 7.0 and later with the IIS plugin to use this plugin with the WebLogic server.

To configure the IIS plug-in for IIS 7.0 and later versions

1. Go to the <wl_home>/wlserver_10.3/server/plugin/ directory and copy the correct OS version and type plugin folder to the server where you installed IIS (referred to as the <IIS_plugin_dir> directory). For example: C:\inetpub\win\x64.

2. Access the IIS Manager. In the Connections navigation pane, expand root server, then expand Sites.

   1. Right-click the Default Web Site node and select Manage Web Site then select Advanced Settings (Figure 3-13).

      Figure 3-13 Connections - Manage Web Site

      
      Description of ''Figure 3-13 Connections - Manage Web Site''
      
      

   2. In the Advanced Settings window, change the value of the Physical Path field to the <IIS_plugin_dir> directory (from step 1). For example, C:\inetpub\win\x64. Then, click OK.

3. In the Default Web Site Home screen, double-click ISAPI Filters.

   1. Right-click anywhere in the ISAPI Filters screen and click Add from the context menu.

      The Add ISAPI Filter window opens.

   2. Populate the following fields with the appropriate information for your system. For example:

      • Filter name: wlforward

      • Executable: C:\inetpub\win\x64\iisforward.dll

   3. Click OK.

4. Click Default Web Site to return to the Default Web Site Home screen. In the Default Web Site Home screen, double-click Handler Mappings.

   1. In the Handler Mappings screen, right-click anywhere and select Add Script Map from the context menu.

      The Add Script Map window opens.

   2. Fill in the following fields with the appropriate information for your system (Figure 3-14). For example:

      • Requested Path: *

      • Executable: C:\inetpub\win\x64\iisproxy.dll

      • Name: IISProxy

        Figure 3-14 Edit Script Map Dialog Box

        
        Description of ''Figure 3-14 Edit Script Map Dialog Box''
        
        

   3. Click Requested Restrictions. In the Request Restrictions window, deselect the Invoker handler mapping option (if checked), as shown in Figure 3-15.

      Figure 3-15 Request Restrictions Dialog Box

      
      Description of ''Figure 3-15 Request Restrictions Dialog Box''
      
      

   4. Click Yes (Figure 3-16).

      Figure 3-16 Edit Script Map Dialog Box

      
      Description of ''Figure 3-16 Edit Script Map Dialog Box''
      
      

5. Click the root server node to access the IIS Home screen, then double-click ISAPI and CGI Restrictions.

   1. In the ISAPI and CGI Restrictions screen, right-click anywhere and select Edit Feature Settings from the context menu.

   2. In the Edit ISAPI and CGI Restrictions Settings window, check both the Allow unspecified CGI modules option and the Allow unspecified ISAPI modules option (Figure 3-17).

      Figure 3-17 Edit ISAPI and CGI Restrictions Settings Dialog Box

      
      Description of ''Figure 3-17 Edit ISAPI and CGI Restrictions Settings Dialog Box''
      
      

   3. Click OK.

6. In the Physical Path folder (<IIS_plugin_dir> directory, from step 1 ), create a file named iisproxy.ini and populate it with the appropriate information for your system.

   • For a non-clustered environment, use the following example:

     WebLogicHost=<hostname> 
     WebLogicPort=<port> 
     ConnectRetrySecs=5
     WLForwardPath=/<cs_context_root>,/<cas_context_root>
     

   • For a clustered environment, use the following example:

     WebLogicCluster=<member1_hostname>:<member1_port>,
     <member2_hostname>:<member2_port>,<membern_hostname>:
     <membern_port>
     ConnectRetrySecs=5
     ConnectTimeoutSecs=25
     WLForwardPath=/<cs_context_root>,/<cas_context_root>
     

     For detailed information about these parameters, refer to the vendor documentation.

     Note:

     Only include /cas if both Sites and CAS are running on the same server, if CAS is located on a separate server then you will need new entries for it that are unique to that environment.

7. Start your IIS Server and Default Web Site.

8. You are now ready to install WebCenter Sites. For instructions, continue to Chapter 6, "Procedures for Installing WebCenter Sites."