Provisioning Oracle WebCenter Portal on Oracle Java Cloud Service


Options



Before You Begin

Purpose

This tutorial shows you how to use Oracle Java Cloud Service to provision multiple Oracle WebCenter Portal environments.

Time to Complete

5 hours

Background

With Oracle Java Cloud Service, you can quickly create and configure an Oracle WebLogic Server domain and set up your Java Platform Enterprise Edition (Java EE) application environment without worrying about infrastructure or platform details. All Oracle Java Cloud Service instances that you create are also preconfigured to use your Oracle Database Cloud Service (Database as a Service [DBaaS]) instance and an object storage container that you create in your Oracle Storage Cloud Service instance.

What Do You Need?

To provision the WebCenter Portal environment on an Oracle Java Cloud Service instance, ensure that you have the following:

  • A subscription for Oracle Storage Cloud Service.
  • A subscription for Oracle Database Cloud Service (DBaaS).
  • A subscription for Oracle Java Cloud Service.
  • A licensed on-premises WebCenter Portal installation.

To complete the installation and configuration of WebCenter Portal on your Oracle Java Cloud Service instance, you will need the following items. For details, see Setting Up Your Environment.

  • An SSH public key

    An SSH public key is used to connect to your VMs using a Secure Shell (SSH) client. When you connect, you must provide the private key that matches the public key.

    When you create an Oracle Database Cloud Service (DBaaS) instance and an Oracle Java Cloud Service instance, you must specify an SSH public key. You generate an SSH public/private key pair by using a standard SSH key generation tool. For more information, see Creating SSH Keys for Use with Oracle Cloud Services.

Process Overview

To complete the installation and configuration of WebCenter Portal on an Oracle Java Cloud Service instance, you need to:

  • Copy the WebCenter Portal, WebCenter Content, and WebCenter schemas (RCU) installation files to your Oracle Java Cloud Service virtual machine (VM).
  • Run the Oracle Fusion Middleware Repository Creation Utility (RCU) to create WebCenter schemas.
  • Install WebCenter Portal.
  • Install WebCenter Content.
  • Install SES files.
  • Extend the Oracle JRF (Oracle Java Required Files) domain for WebCenter Portal.
  • Configure WebCenter Portal with WebCenter Content.
  • Configure SES with WebCenter Portal and WebCenter Content.

Setting Up Your Environment

To set up your Oracle Java Cloud Service and Oracle Database Cloud Service (DBaaS) instances:

  • Create an Oracle Storage Cloud Service container
  • Create an Oracle Database Cloud Service (DBaaS) instance
  • Create an Oracle Java Cloud Service instance

Creating an Oracle Storage Cloud Service Container

Use the Oracle Storage Cloud Service to create an object storage container. This container will be used by the database when you create your Oracle Database Cloud Service (DBaaS) instance.

  1. When you subscribed for an Oracle Cloud account, you would have received an email with the details for signing in to My Services. Follow the link and use the credentials in that email to access your My Services Dashboard.

    Note: Remember to bookmark your My Services page, so that you can access it easily in future.

  2. On the My Services Dashboard, click View Details for Oracle Storage Cloud Service.
    My Services Dashboard
    Description of this image
  3. Make a note of your REST endpoint.
    Oracle Storage Cloud Service console
    Description of this image
  4. Enter the following command in the command shell to get an authentication token:

    curl -v -X GET -H 'X-Storage-User: Storage-domain:username' -H 'X-Storage-Pass: your_password' https://storage.data-region-code.oraclecloud.com/auth/v1.0

    In the preceding command:

    Storage-domain: Domain name of the subscribed Oracle Storage Cloud service

    storage.data-region-code: The full web address of the Oracle Storage Cloud data region

    username: Your Oracle Public Cloud Services username (typically the email address associated with your Oracle Cloud account)

    your_password: Your Oracle Public Cloud Services password

    For example:

    $curl –k -v -X GET -H 'X-Storage-User: Storage-MYDOMAIN:aaa@xyz.com' -H 'X-Storage-Pass:Oracle@1' https://storage.dc1.oraclecloud.com/auth/v1.0

    From the response, note the X-Storage-Url and X-Auth-Token values.

    For example:

    X-Storage-Url: https://storage.dc1.oraclecloud.com/v1/ Storage-MYDOMAIN
    X-Auth-Token: AUTH_tk209f7f2ea1265a0d3f29d28a2dc8ced6
              
  5. Create a container:
    curl -v -H 'X-Auth-Token: your_auth_token ' -X PUT https://storage.data-region-code.oraclecloud.com/v1/Storage-IdentityDomain/container_name
  6. Get a list of containers to verify that your container is created:
    curl -v -H 'X-Auth-Token: your_auth_token' 
    https://storage.data-region-code.oraclecloud.com/v1/Storage-IdentityDomain/

Creating an Oracle Database Cloud Service (DBaaS) Instance

The following section shows how to create the Oracle Database Cloud Service (DBaaS) instance.

  1. Sign in to the My Services application.
  2. On the My Services page, click

    Menu Icon and select Database Cloud Service.

    The Oracle Database Cloud Service (DBaaS) Console is displayed.

    My Services - Menu
    Description of this image
  3. On the Oracle Database Cloud Service page, click Create Service.
    Oracle Database Cloud Service console
    Description of this image
  4. On the Subscription Type page, select Oracle Database Cloud Service, and a billing frequency , and then click Next.
    Create Database Cloud Service Instance - Subscription screen
    Description of this image
  5. On the Software Release page, select Oracle Database 11g Release 2, and then click Next.
    Create Database Cloud Service Instance - Release screen
    Description of this image
  6. On the Software Edition page, select Enterprise Edition, and then click Next.
    Create Database Cloud Service Instance - Edition screen
    Description of this image
  7. On the Service Details page, configure the following settings, and then click Next:
    • In the Service Configuration section, enter or select the following:
      • Instance name
      • Description
      • Compute shape: This allows you to specify the number of OCPUs and RAM that your instance should have. Select OC3 – 1 OCPU, 7.5 GB RAM.
      • VM public key: Add the SSH key that you generated earlier.
        1. Click Edit and select the Key file name option.
        2. Click Browse to navigate to the folder where you saved the SSH public key.
        3. Select the SSH public key and then click Enter.
    • In the Database Configuration section, enter or select the following:
      • Usable Database Storage
      • Administrator Password: The administrator password that you provide is used for the SYS and SYSTEM database users, for the admin Oracle GlassFish Server user, and for the admin Oracle Application Express user.
      • DB Name: Make a note of the SID. You will need it later.
    • In the Backup and Recovery Configuration section, enter or select the following:
      • Backup Destination: Select Both Cloud Storage and Block Storage.
      • Cloud Storage Container: The container name should be of the format storageservicename-id_domain/container, where storage service name is the name of the Oracle Storage Cloud Service, id_domain is the name of the identity domain, and container is the name of the container.
      • Cloud Storage User Name
      • Cloud Storage Password

      Create Database Cloud Service Instance - Details screen
      Description of this image
  8. On the Confirmation page, review the information. If you are satisfied with the information, click Create.

    The Oracle Database Cloud Service (DBaaS) Instance is created.

    Oracle Database Cloud Service console
    Description of this image

Creating an Oracle Java Cloud Service Instance

  1. Sign in to the My Services application.
  2. On the My Services page, click

    Menu Icon and select Java Cloud Service.

    My Services Menu
    Description of this image
  3. On the Oracle Java Cloud Service Console, click Create Service.
    Oracle Java Cloud Service console
    Description of this image
  4. On the Subscription Type page, select Oracle Java Cloud Service – Virtual Image and a billing frequency, and then click Next.
  5. On the Software Release page, select Oracle Weblogic Server 11g (11.1.1.7), and then click Next.

    Create Oracle Java Cloud Service Instance - Release screen
    Description of this image
  6. On the Software Edition page, select Enterprise Edition, and then click Next.

    Create Oracle Java Cloud Service Instance - Edition screen
    Description of this image
  7. On the Service Details page, configure the following settings, and then click Next.
    • In the Service Configuration section, enter or select the following:
      • Instance name
      • Description
      • Cluster size: 1
      • Compute shape: This allows you to specify the number of OCPUs and RAM that each node on your instance should have. Select OC4 – 2 OCPU, 15 GB RAM.
      • VM public key: Add the SSH key that you generated earlier:
        1. Click Edit and select the Key file name option.
        2. Click Browse to navigate to the folder where you saved the SSH public key.
        3. Select the SSH public key and then click Enter.
    • In the WebLogic Administrator section, enter the user name and password that you want to use.
    • In the Database Configuration section, enter or select the following:
      • Name: The name of the Oracle Database Cloud Service instance that you created earlier.
      • Database Administration User Name: SYSTEM
      • Password: The Administrator password that you specified while creating the Oracle Database Cloud Service instance.
    • In the Load Balancer section, in the Provision Load Balancer field, select Yes.
    Create Oracle java Cloud Service Instance - Details screen
    Description of this image
  8. On the Confirmation page, review the information. If you are satisfied with the information, click Create. The Oracle Java Cloud Service instance is created.

    Oracle Java Cloud Service console
    Description of this image

Downloading the Installation Files

Download the following WebCenter Portal and WebCenter Content Software to your local machine:

  • Oracle WebCenter Portal (11.1.1.8.0).
  • Oracle WebCenter Content 11g R1 (11.1.1.8.0).

Download the required software from Oracle Technology Network

Accessing Your Oracle Java Cloud Service Instance Using SSH

After you have created your Oracle Java Cloud Service instance, log in to the machine using a secure shell (SSH).

  1. Sign in to the My Services application at http://cloud.oracle.com.
  2. In the My Services Dashboard, click Consoles, and select Oracle Java Cloud Service.
  3. In the Java Cloud Service Console, click the instance.
  4. The public IP address of the Administration Server is available in the Virtual Machines section. Make a note of the IP address.
  5. In a command shell, run the ssh utility:
    ssh -i private-key-file opc@vm-ip-address

    In this command, private-key-file is the path to the SSH private key that matches the public key used when your instance was created, vm-ip-address is the public IP address of the VM in x.x.x.x format, and opc is the user name.

  6. The first time you connect to the VM, the ssh utility prompts you to confirm the public key. Enter yes.
  7. At the prompt, enter the passphrase for the SSH key, if one was created.

Copying and Extracting the Installation Files

  1. After logging in to the administration VM using SSH, to create a directory for the WebCenter Portal installation, execute the following commands in the command shell:
    cd /
    sudo mkdir stage
    sudo chmod 777 stage
  2. Copy the installation files from the local host to the administration VM:
  3. scp -i private-key-file
    download_folder/*.zip opc@vm-ip-address:/Directory_on_VM
  4. Set permissions:
    sudo chmod –R 777 /stage
  5. Extract the installation files to the administration VM:
    sudo su – oracle
     cd /stage
     unzip ofm_wc_generic_11.1.1.8.0_disk1_1of1.zip -d wcp
     unzip ofm_wcc_generic_11.1.1.8.0_disk1_1of2.zip -d wcc
     unzip ofm_wcc_generic_11.1.1.8.0_disk1_2of2.zip -d wcc
     exit

Validating the TMP directory

Ensure that the TMP and TMPDIR directories are writable:

sudo chmod 777 $TMP
sudo chmod 777 $TMPDIR

Configuring X11 Forwarding

  1. On the administration VM execute the following command to edit the sshd_config file:
    sudo vim /etc/ssh/sshd_config
  2. Make sure that the following values are set in this file:
    AllowTcpForwarding yes
    X11Forwarding yes
    X11DisplayOffset 10
    X11UseLocalhost yes
  3. Restart sshd:
    sudo /etc/rc.d/init.d/sshd restart
  4. Execute the following command to check the ForwardAgent and ForwardX11 values in the local machine:
    vim /etc/ssh/ssh_config
  5. Make sure that the following values are set in the ssh_config file:
    ForwardAgent yes
    ForwardX11 yes
  6. Connect to the administration VM:
    ssh –Y -i private-key-file opc@vm-ip-address
  7. Verify that the DISPLAY variable isn't empty:
    echo $DISPLAY
    Localhost: 10.0
  8. Execute the following command to set up the display key on the administration VM:
    xauth list
  9. Locate the xauth entry that corresponds to the DISPLAY environment variable. For example:
    webcenter2-wls-1/unix:10  MIT-MAGIC-COOKIE-1  124a846155d948a20226a65e02586c65

    Make a note of this xauth entry.

  10. As the oracle user, add the xauth entry:
    sudo su – oracle
    xauth add webcenter2-wls-1/unix:10 MIT-MAGIC-COOKIE-1 124a846155d948a20226a65e02586c65 

    Note: You must update the xauth entry for the oracle user every time you log out and log in.

Configuring Your Oracle Database Cloud Service (DBaaS) Instance for WebCenter Schemas

  1. Locate your Oracle Database Cloud Service (DBaaS) instance details.

    When you created your Java Cloud Service instance, you provided details of the database where your Oracle Java Cloud Service instance created an Oracle Metadata Services (MDS) schema for its Weblogic Server Domain. You'll need those details to create the WebCenter Portal and WebCenter Content schemas and data sources.

  2. To find this information, log in to the My Services application and go to the Oracle Database Cloud service (DBaaS) Console.
  3. Click your instance to view its details. Make a note of the public IP address.
  4. Access your Oracle Database Cloud Service (DBaaS) instance.

    To access the resources on the VM hosting your Oracle Database Cloud Service (DBaaS) instance, use an SSH client to connect securely to the VM. Log in as the oracle user:

    ssh –Y -i private-key-file oracle@dbaas-vm-ip-address
  5. Oracle Database Cloud Service (DBaaS) creates database instances with default parameters. Update these parameters as required for the WebCenter Portal and WebCenter Content Server installations as follows:
    • Check if the ORACLE_HOME variable is set:
      echo $ORACLE_HOME

      The ORACLE_HOME variable should be defined as /u01/app/oracle/product/11.2.0/dbhome_1. If the value is incorrect, execute the following command:

      export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
    • Check if the PATH variable is set for ORACLE_HOME/bin:
      echo $PATH

      If the value is incorrect, execute the following command:

      export PATH=$ORACLE_HOME/bin:$PATH
    • Check if the ORACLE_SID variable is set for the database SID:
      echo $ORACLE_SID

      If the value is incorrect, execute the following command:

      export ORACLE_SID=Database SID
    • Check if the LD_LIBRARY_PATH variable is set for ORACLE_HOME/lib:
      echo $LD_LIBRARY_PATH

      If the value is incorrect, execute:

      export LD_LIBRARY_PATH=$ORACLE_HOME/lib
  6. Update the database process parameters and restart the database.

    To run the Oracle Fusion Middleware Repository Creation Utility (RCU), the minimum value of the processes parameter should be 300. To set this value, execute the following commands in the command shell that is connected to the Oracle Database Cloud Service (DBaaS) VM:

    sqlplus / as sysdba
    alter system set processes=300 scope=spfile;
    shutdown immediate
    startup
    show parameter processes

    The output should show that the value has been changed.

  7. Close the SSH connection:

Installing WebCenter Portal

Note: In the upcoming WebCenter Portal Installation and Configuration sections, the steps relating to Discussions and Portlets servers are optional and can be skipped if not required.

To start the WebCenter installation, connect to the Administration Server virtual machine:

ssh –Y -i private-key-file opc@vm-ip-address

Note: You're logged in as the opc user. To install the software, you must change to the oracle user. You must also update the xauth entry in the new command terminal.

sudo su – oracle

To install WebCenter, complete the following steps:

  1. Create WebCenter Portal and WebCenter Content Schemas
  2. Install WebCenter Portal
  3. Install WebCenter Content

Note: You must install Oracle WebCenter Portal before Oracle WebCenter Content.

Creating Oracle WebCenter Portal and WebCenter Content Schemas

  1. Start RCU from the bin directory inside the RCU_HOME directory:
    cd RCU_HOME/bin
    ./rcu
    

    Note: The default RCU_HOME is /u01/app/oracle/middleware/rcuHome/

  2. On the RCU Welcome page, click Next.
  3. On the Create Repository page, select Create, and then click Next.
  4. On the Database Connection Details page, enter the following, and then click Next:
    • Host name: name of the Oracle Database Cloud Service (DBaaS) instance
    • Port : 1521
    • Service Name: Your service name*
    • Username: SYS
    • Password: Your Admin password

      Note: The Role changes to SYSDBA by default.

    • * The service name is part of the string that is shown after the DB listen port in the Connect Descriptor. You can look up the Connect Descriptor in the Oracle Database Cloud Service (DBaaS) instance page.

    RCU - Database Connection Details screen
    Description of this image
  5. On the Repository Creation Utility - Checking Prerequisites page, click OK.
  6. On the Select Components page do the following, and then click Next:
    • In the Create a new Prefix field, Accept DEV as the default prefix value.
    • Expand AS Common Schemas and select Metadata Services.
    • Expand WebCenter Content and select WebCenter Content Server- Complete.
    • Expand WebCenter Portal. Select Spaces and Services, Portlet Producers, and Discussions.
    • Do not change any Schema Owners.
    RCU - Select Components screen
    Description of this image
  7. On the Repository Creation Utility - Checking Prerequisites page, click OK.
  8. On the Schema Passwords page, enter the password you want, and then click Next.
  9. On the Map Tablespaces page, accept the default values, and the click Next.
  10. On the Repository Creation Utility – Confirmation page, click OK.
  11. On the Repository Creation Utility - Creating Tablespaces page, wait till the tablespaces are created, and then click OK.
  12. On the Summary page, review the details. If anything is incorrect, click Back to return to the appropriate page to correct the error. Then click Create.
  13. After the repository is created, click Close.

Installing WebCenter Portal

  1. To start the installer, go to the directory where you unpacked the archive file and switch to the Disk1 directory:
    cd /stage/wcp/Disk1
  2. To run the installer, execute the following command. The installer requires the full path to the location of a Java Runtime Environment (JRE):
    ./runInstaller –jreLoc fmwhome/jrockit

    For example:

    ./runInstaller -jreLoc /u01/jdk -invPtrLoc /u01/app/oracle/middleware/oracle_common/oraInst.loc

    The installation wizard appears.

  3. On the Welcome page, click Next.
  4. On the Install Software Updates page, select Skip Software Updates, and then click Next.
  5. When the prerequisite checks are completed, click Next.
  6. On the Specify Installation Location page, enter /u01/app/oracle/middleware for Oracle Middleware Home, enter Oracle_WC for Oracle Home Directory, and then click Next.
  7. On the Application Server page, confirm that the WebLogic Server option is selected, and then click Next.
  8. On the Installation Summary page, review the installation details, and then click Install.
  9. When the installation is completed, click Next.
  10. Click Finish to close the installation wizard.

Installing WebCenter Content

  1. Navigate to the installation directory:
    cd /stage/wcc/Disk1
  2. To run the installer, execute the following command:
    ./runInstaller –jreLoc /jrockit

    For example:

    ./runInstaller -jreLoc /u01/jdk -invPtrLoc /u01/app/oracle/middleware/oracle_common/oraInst.loc

    The installation wizard appears.

  3. On the Welcome page, click Next.
  4. On the Install Software Updates page, select Skip Software Updates and click Next.
  5. When the prerequisite checks are completed, click Next.
  6. On the Specify Installation Location page, enter /u01/app/oracle/middleware for Oracle Middleware Home, enter Oracle_ECM for Oracle Home Directory, and then click Next.
  7. On the Application Server page, verify that WebLogic Server is selected, and then click Next.
  8. On the Installation Summary page, review the installation details and then click Install.
  9. When the installation is completed, click Next.
  10. Click Finish to close the installation wizard.

Extending the Oracle JRF Domain for WebCenter Portal

Each Oracle Java Cloud Service instance is a single WebLogic domain that consists of an Administration Server and a Managed Server. By default JRF is applied to the domain. You must extend this domain to include Oracle WebCenter Portal and Oracle WebCenter Content.

Shutting Down the Managed and Administration Servers

Follow these steps to shut down the Managed server and the Administration server:

  1. Sign in to the My Services application.
  2. On the My Services dashboard, click Consoles and select Oracle Java Cloud Service.
    My Services Dashboard
    Description of this image
  3. On the Oracle Java Cloud Service page, click the menu menu icon and select Open WebLogic Server Console.
    Oracle Java Cloud Service Console
    Description of this image
  4. Log in with your administrator credentials.
  5. In the Domain Structure pane, expand Environment, and select Servers.
    WebLogic Administration Console
    Description of this image

    The Summary of Servers page displays the name of the servers.

  6. Make a note of the name of the Administration Server and then click the Administration Server link.
    WebLogic Administration Console - Summary of Servers screen
    Description of this image
  7. To start an edit session, click Lock & Edit.
    WebLogic Administration Console
    Description of this image
  8. On server settings page, under the Configuration tab, click the Server Start subtab.
  9. In the Arguments field, change the value of Xms to 512m and Xmx to 1024m, and then click Save.
  10. After the settings are updated successfully, click Activate Changes.
    WebLogic Administration Console
    Description of this image
  11. In the Domain Structure pane, click Servers.
    WebLogic Administration Console
    Description of this image
  12. On the Summary of Servers page, click the Control tab.
  13. Select the Managed Server, click Shutdown and then select Force Shutdown Now.
    WebLogic Admninistration Console - Summary of Servers screen
    Description of this image
  14. Repeat the previous step to stop the Administration Server.

Applying the Required Patches

Apply the recommended patches for WebCenter Portal and WebCenter Content from MOS - available under section Oracle WebCenter 11g R1 dot8 (11.1.1.8.0).

Note:

  1. Do not apply WCP patch 11.1.1.8.7 (20425442) from this list. Apply WCP Patch 11.1.1.8.5 (19194669) instead.
  2. It is mandatory to apply the patch for FrameworkFolders support - 18387955.

Running the Fusion Middleware Configuration Wizard

Perform the following steps to run the Fusion Middleware Configuration Wizard:

  1. Start the Fusion Middleware Configuration Wizard:
    cd ORACLE_MIDDLEWARE_HOME/oracle_common/common/bin
    ./config.sh
  2. On the Welcome page, select Extend an existing WebLogic domain, and click Next.
  3. On the Select a WebLogic Domain Directory page, expand the /u01/data/domains directory, select your domain, and then click Next.
  4. On the Select Extension Source page, select the following, and then click Next:
    • Oracle WebCenter Spaces (Enterprise Manager and WSM Policy Manager should be selected by default.)
    • Oracle Universal Content Management - Content Server.
    • Oracle Universal Content Management - Inbound Refinery.
    Fusion Middleware Configuration Wizard - Select Extension Source screen
    Description of this image
  5. In the next page which is the Configure JDBC Data Sources page, no action is required. Click Next.
  6. In the next page which is the Test JDBC Data Sources page, no action is required. Click Next.
  7. On the Configure JDBC Component Schema page, enter the Java Database Connectivity (JDBC) connection details (obtained from the Oracle Database Cloud Service (DBaaS) instance details), and then click Next.
  8. On the Test JDBC Component Schema page, click Test Connections. Verify that a check mark appears next to each component schema. If the test is successful, click Next . Otherwise click Previous to return to the previous page and correct any errors.
  9. On the Select Optional Configuration page, select
    1. Managed Servers, Clusters and Machines
    2. Deployments and Services
  10. Click Next.
  11. On the Configure Managed Servers page, add a new Managed Server for Spaces WC_Spaces1 and provide a unique port. Click Next.
    Configure Managed Server
    Description of this image
  12. On the Configure Clusters page, add a new cluster spaces_cluster. Click Next.
    Configure Clusters
    Description of this image
  13. On the Assign Servers to Clusters page, assign the two 'spaces' managed servers to spaces_cluster. Click Next.
    Assign Servers to Clusters
    Description of this image
  14. On the Create HTTP Proxy Applications page, click Next.
  15. On the Configure Machines page, click Next.
  16. On the Assign Servers to Machines page, assign all servers to the machine that hosts the admin server, and click Next.
  17. In the Target Deployments to Clusters and Servers page, select the default JCS cluster instance in the Target pane. Under Deployments > Application, uncheck the check box next to wsm-pm.
    Uncheck wsm-pm
    Description of this image
  18. In the next page, which is Target Services to Clusters or Servers, apart from targeting opss-ds to managed servers, target opss-ds to spaces_cluster as well. In other words, individually select the cluster and the new managed servers that were added. Then, select the datasource under JDBC > JDBC System Resource > opss-ds. Click Next.
    Target Services to Clusters or Servers
    Description of this image
  19. Review your configuration and make any corrections or updates if required. Then click Extend to extend the JRF domain.
  20. After the domain extension is completed, click Done.

Starting Your Administration Server with the WebLogic Scripting Tool (WLST)

Node Manager is a utility for remote control of WebLogic Server instances. Using Node Manager, you can control and monitor Managed Servers and start, stop, and restart Administration Servers. WLST can connect to a Node Manager that is running on any machine and start WebLogic Server instances. You can execute WLST commands local to the VM.

  1. Connect to the administration VM as the opc user:
    ssh –Y -i private-key-file opc@vm-ip-address
  2. Switch to the oracle user:
    sudo su - oracle
  3. Set the domain environment by using the setDomainEnv.sh command. This command is in the /u01/data/domains/domain-name/bin directory:
    . ./setDomainEnv.sh

    Note: Use the period (.) to ensure that the environment variables are set in the current shell.

  4. Start WLST:
    java weblogic.WLST
  5. Execute the nmConnect command to connect WLST to a Node Manager:
    wls:/offline>nmConnect('username','password','nmHost', '5556', 'domainName','domainDir','SSL')
    Connecting to Node Manager ...
    Successfully connected to Node Manager.
    wls:/nm/domainName>
  6. Execute the nmStart command to start a server:
    wls:/nm/mydomain>nmStart(‘Administration Server Name’)
    starting server AdminServer
    ...
    Server AdminServer started successfully
    wls:/nm/mydomain>
    

Starting the New Managed Servers

  1. Sign in to the My Services application.
  2. On the My Services page, click Menu Icon and select Java Cloud Service.
    My Services Menu
    Description of this image
  3. In the Java Cloud Service Console, click the menu Menu Icon.
    Open WebLogic Server Console
    Description of this image
  4. Click Open WebLogic Server Console to open the console.
    Open WebLogic Server Console
    Description of this image
  5. Log in with the admin credentials.
  6. In the console’s navigation pane, expand Environment and select Servers.
    Select Servers
    Description of this image
  7. Select the Control tab on the Summary of Servers page.
    Summary of Servers Page
    Description of this image
  8. In the Servers table, click the check box next to IBR_server1, UCM_server1, WC_Collaboration, WC_Portlet, WC_Spaces and WC_Spaces1. Click Start.
    Servers Table
    Description of this image
  9. On the Server Life Cycle Assistant page, click Yes to confirm. When the start sequence finishes, the server state is indicated in the State column in the Server Status table. (Refresh the page to view the status updates).
    Life Cycle Assistant Page
    Description of this image

Opening Up Traffic to WebCenter Ports From Oracle Traffic Director(OTD) VM

To open up traffic to WebCenter ports from the OTD VM, follow the instructions below:

  1. Open the Java Cloud Service Console.
  2. Click Consoles. Select Compute Cloud Service.
    JCS Console
    Description of this image
  3. On the Compute Cloud Service page, select the Network tab to see the following screen:
    Networks Tab
    Description of this image
  4. Click the Protocols tab.
  5. On the Protocols page, click Create Protocol.
    Click Create Protocol
    Description of this image
  6. Enter the name of one protocol for each port or port range you need to open.

    Enter the following details for WebCenter Managed Servers and click Create:

    • Name: ora_wcp_mgdsvrs_http (any name will do)
    • Port Type: tcp
    • Port Range Start: 8888
    • Port Range End: 8890
    • Description: Permit Traffic to WebCenter Managed Server Ports
    • Create Protocol
      Description of this image
  7. You must create access rules to allow traffic to flow to these ports. Click the Access Rules tab.
    Click Access Rules Tab
    Description of this image
  8. On the Access Rules page click Create Access Rule.

    Enter the following values in the Create Access Rule dialog box and click Create.

    • Name: ora_wcp_p2_mgdsvrs_http (any name will do)
    • Protocol: ora_wcp_mgdsvrs_http (name of the protocol you created in the previous step)
    • Source: Network Groups: ora_otd
    • Destination: ora_ms
    • Description: Allow OTD access to WebCenter Managed Server Ports
    Create Access Rule Page
    Description of this image
  9. Similarly, create the other required 'protocol - access rule' combinations as follows:

    For the additional Spaces Managed Server added to the Spaces Cluster:

    Protocol:

    
    Name: ora_wcp_spaces1_http
    Port Type: tcp
    Port Range Start: 9888
    Port Range End: 9888
    Description: Permit Traffic to Spaces1 Managed Server Port
    
    

    Access Rule:

    
    Name: ora_wcp_p2_spaces1_http
    Protocol: ora_wcp_spaces1_http
    Source: Network Groups: ora_otd
    Destination: ora_ms
    Description: Allow OTD access to Spaces1 Managed Server Port
    
    

    For the UCM Managed Server Port:

    Protocol:

    
    Name: ora_wcp_ucm_http
    Port Type: tcp
    Port Range Start: 16200
    Port Range End: 16200
    Description: Permit Traffic to UCM Managed Server Port
    
    

    Access Rule:

    
    Name: ora_wcp_p2_ucm_http
    Protocol: ora_wcp_ucm_http
    Source: Network Groups: ora_otd
    Destination: ora_ms
    Description: Allow OTD access to UCM Managed Server Port
    
    

Configuring Oracle Traffic Director for WebCenter Portal and WebCenter Content

To configure Oracle Traffic Director for WebCenter Portal and WebCenter Content, follow the instructions below:

Creating a New Configuration

  1. In the Java Cloud Service Console, click the menu Menu Icon for your instance, and then select Open Load Balancer Console.
    Open LBR Console
    Description of this image
  2. Log in with your WebLogic administrator credentials.
  3. The Oracle Traffic Director Console Home Page is displayed.
    OTD Home Page
    Description of this image
  4. In the Common Tasks pane, click New Configuration.

    The New Configuration wizard starts.

    1. In the Name field, enter WebCenter_JCS.
    2. Accept default values for the rest of the fields, click Next.
      OTD New Configuration Wizard Step1
      Description of this image
  5. In the following screen, enter the Port and Server Name information. The listener port is the port through which requests to WebCenter Portal are served. The default port is 8080. If you provide any other port, note it down as it will be required later. Click Next.
    OTD New Configuration Wizard Step2
    Description of this image
  6. In the following screen, enter the details of a Spaces Managed Server host and port combination. Click Add Server. Click Next.
    OTD New Configuration Wizard Step3
    Description of this image
  7. In the next screen, target this configuration to the default Admin Server that is available with JCS OTD. Click Next.
    OTD New Configuration Wizard Step4
    Description of this image
  8. In the next screen, review the information entered so far. After review, click Create Configuration.
    OTD New Configuration Wizard Step5
    Description of this image
  9. In the Results page which is shown, confirm that the configuration is created successfully. Then click Close.
    OTD Configuration Wizard Results
    Description of this image

The configuration creation is now complete.

Creating New Origin Server Pools

To create new origin server pools, follow the instructions below:

  1. In the Configuration just created, select Server Pools in the left navigation pane.
  2. Click New Server Pool.
    Configuration Home Page
    Description of this image
  3. In the New Server Pool Wizard: Step 1: Server Pool Information, provide a name to the origin server pool, say WebCenterPortal, and accept the defaults for other parameters. Click Next.
    New Server Pool Step1
    Description of this image
  4. In Step 2 : Origin Server Information, enter the Host and Port details of the first Spaces Managed Server. For example, Host: wcpjcs3-wls-1 and Port: 8888. Click Add Server. Repeat this process to add the details of the second Spaces Managed Server host and port information. Click Next.
    New Server Pool Step2
    Description of this image
  5. In the Review page, review the information just entered and click Create Server Pool.
    New Server Pool Step3
    Description of this image
  6. A results page is shown with the confirmation of Server Pool Creation. Click Close.
    New Server Pools - Results
    Description of this image
  7. Repeat the steps above to create the rest of the server pools as shown in the image below:
    Server Pools
    Description of this image

Configuring Routing

The next step is to configure routing. To configure routing, follow the instructions below:

  1. Select Routes from the left navigation pane of the created configuration:
    Routes - Home Page
    Description of this image
  2. Click New Route.
  3. In the New Route wizard: Step 1 : Route Properties, provide a name to the route, say r_webcenterportal, choose WebCenterPortal from the Origin Server Pool drop-down menu. Click Next.
    New Route Step1
    Description of this image
  4. In the next page, Step 2 : Condition Information, add Value /webcenter to New Expression, and click OK.
    New Route - Step 2a
    Description of this image
  5. Repeat the above step to add the rest of URI values to the expression:
    /webcenterhelp
    /rest
    /rsscrawl
    /sesUserAuth
    /wcsdocs
    

    After all the URI values are added, review that the condition looks as follows; Click Next.

    New Route - Step2b
    Description of this image
  6. In the Review page, review the information just entered and click Create Route.
    New Route - Review
    Description of this image
  7. A results page is shown with the confirmation of Route Creation. Click Close.
    New Route - Results
    Description of this image
  8. Repeat the above steps to create additional routes as follows:

    The following URIs must be targeted to the UCM server pool:

    /cs /adfAuthentication

    The following URIs must be targeted to the Discussions server pool:

    /owc_discussions

    The following URIs must be targeted to the Portlets server pool:

    /wsrp-tools /pagelets

    After all the routes are created, review that the list of routes is available as follows:

    Routes List
    Description of this image
  9. Click Deploy Changes in the right pane to deploy the changes.
  10. Click Start/Restart Instances in the right pane to restart the instances.

This completes the OTD setup for WebCenter Portal and WebCenter Content in JCS.

Opening Up Traffic to OTD Listen Port From Public Internet

The steps executed in the section 'Open up traffic to WebCenter Ports from OTD VM' must be repeated to make the OTD Listen Port accessible to the public internet.

The following 'protocol - access rule' combination is required for enabling public internet access to the OTD Listen Port; The default value of the listen port is 8080, unless it was changed during configuration creation.

Protocol:


Name: ora_otd_listen_http
Port Type: tcp
Port Range Start: 8080
Port Range End: 8080
Description: Permit Traffic to OTD Listen Port

Access Rule:


Name: ora_otd_p2_listen_http
Protocol: ora_otd_listen_http
Source: IP Lists: public-internet
Destination: ora_otd
Description: Allow public access to OTD Listen Port

Accessing WebCenter Portal

  1. In a web browser, to connect to WebCenter Portal enter the following URL. The default port used for Oracle Traffic Director is 8080. http://ipaddress:8080/webcenter
  2. Log in with your administrator credentials. The WebCenter Portal Home page is displayed.

     WebCenter Portal Home Page
    Description of this image

Configuring WebCenter Portal with WebCenter Content

You can integrate WebCenter Portal and WebCenter Content so that you can access and use content from the content repository in your portal pages.

Refer to section 36.1.3.1 Attaching Security Policies for WebCenter Portal and Discussions Web Service Endpoints to attach Oracle Web Services Manager (OWSM) security policies for the WebCenter Portal Web service endpoint and the discussions authenticated Web service endpoint.

  1. Complete the steps in the following sections of the Fusion Middleware Administration Guide:
  2. Invoke the Repository Manager applet (Your domain/ucm/cs/bin/RepositoryManager) in standalone mode. Go to the Indexer tab and select Start : Collection Rebuild Cycle.
    • See section 3.5.2 Running Administration Applications in Standalone Mode
    • Setting up the Admin Applets to Run in Standalone Mode on an 11g Install (Doc ID 1265076.1)
    • Errors Occur when Launching Stand Alone Applets (Doc ID 1614502.1)

    Next, register the WebCenter Content repository with Oracle WebCenter Portal.

  3. Sign in to the My Services application.
  4. On the My Services dashboard, click Consoles, and select Oracle Java Cloud Service.

    My Services Dashboard
    Description of this image
  5. On the Oracle Java Cloud Service page, click the menu menu icon and select Open Fusion Middleware Control Console.

    Oracle Java Cloud Service Console
    Description of this image
  6. Log in with your administrator credentials.
  7. Go to Service Configuration pane. Expand the WebCenter, Portal, and Spaces nodes. Right-click WebCenter Portal (11.1.1)(WC_Spaces), select Settings, and then select Service Configuration.

    Oracle Enterprise Manager
    Description of this image
  8. In the Service Name pane, click Content Repository, and then click Add to add a new connection. Enter or select the following, and then click Test:
    • Connection Name: Any name of your choice
    • Repository Type: Oracle Content Server
    • Active Connection: Checked
    • Content Administrator: sysadmin
    • Root Folder: /RootFolder
    • Application Name: Any name of your choice
    • RIDC Socket Type: Socket (default value)
    • Server Host: vm-public-IP_address
    • Server Port: 4444
    • Web Server Context Root: /cs
    • Administrator User Name: sysadmin (default value)

    WebCenter Portal Service Configuration screen
    Description of this image
  9. After the success message is displayed, click OK.
  10. On the Add Content Repository Connection page, click OK. A confirmation page is displayed:

    WebCenter Portal Service Configuration screen
    Description of this image
  11. Restart the WC_Spaces and WC_Spaces1 Managed Servers.

Configuring WebCenter Portal with Discussions

Configuring WebCenter Portal with Portlet Producers

    From the WebCenter Portal Service Configuration screen in EM, if it is found that the portlet producers are not automatically configured, follow the instructions in chapters Managing Portlet Producers and Managing the Pagelet Producer of the book Fusion Middleware Administering Oracle WebCenter Portal.

Setting Up the JDeveloper Environment for Asset Development

Next, connect JDeveloper running on your local machine to WebCenter Portal running on your Oracle Java Cloud Service instance, so that you can use JDeveloper for to develop portal assets or custom components and test these on WebCenter Portal.

WebCenter Portal provides some default assets, such as skins and page templates, for people to use or modify. If your asset requirements extend beyond the browser-based editing capabilities of Portal Builder, you can further develop assets using the JDeveloper WebCenterSpacesResources project. This project provides everything you need to create, modify, and upload the WebCenter Portal assets.

  1. Before you start, complete the following steps:
    1. Download and install Oracle JDeveloper 11g (11.1.1.7.0). For details, see Section 2.2.1 — Installing Oracle JDeveloper

    2. Install the WebCenter Portal Extension for JDeveloper (11.1.1.8.0) For details, see Section 2.2.2 — Installing the WebCenter Portal Extension for JDeveloper

    3. Download the WebCenter Portal asset development ZIP file (DesignWebCenterSpaces_11.1.1.8.0.zip) from Oracle Technology Network → https://download.oracle.com/otndocs/tech/webcenter/files/DesignWebCenterSpaces_11.1.1.8.0.zip

    4. Extract the content locally, as described in section 55.1 of the following document → https://docs.oracle.com/cd/E29542_01/webcenter.1111/e63259/jpsdg_wcsres.htm#CIHIEEJC

    5. Create an SSH tunnel to port 9001 of your virtual machine. For details, see https://apex.oracle.com/pls/apex/f?p=44785:112:0::NO:112:P112_CONTENT_ID:10477l
  2. Set connection properties in the config.properties file. To enable direct updates from the JDeveloper WebCenterSpacesResources project, you must specify the host name and port where the WebCenter Portal application is running.
    1. Open the config.properties file, at: Unzip_Directory\DesignWebCenterSpaces\config.properties.

      For example:

      Jdeveloper\mywork\DesignWebCenterSpaces\config.properties
    2. Enter the following values:
      • jdeveloper.install.home.directory: Base directory where JDeveloper is installed.
      • wlst.executable: Either wlst.cmd (on Windows) or wlst.sh (on Linux).
      • wls.port: 9001
      • wls.host: Localhost
      • wc.host: vm-ip-address
      • wc.port: 8080 (default OTD listen port)
      • wc.protocol: http
      • wls.webcenter.app.target: WC_Spaces
      • webcenter.app.name: webcenter

      Note: The value for wls.host and wls.port is taken from step 1e above.

  3. To download assets directly from WebCenter Portal to JDeveloper, follow the instructions provided in section 55.1.5.1 of the following document: https://docs.oracle.com/cd/E29542_01/webcenter.1111/e27739/jpsdg_wcsres.htm#CIHBFCBC
  4. To upload assets directly to WebCenter Portal from JDeveloper, follow the instructions provided in section 55.1.6 of the following document: https://docs.oracle.com/cd/E29542_01/webcenter.1111/e27739/jpsdg_wcsres.htm#JPSDG8769

Installing the Required Patches

Install the IBR patch and any other required patches. Follow these instructions to install the IBR patch:
  1. Shutdown the UCM and IBR servers.
  2. Unzip the contents of the redist folder from the zip file to $MW_HOME/Oracle_ECM1/oit/linux/lib/contentaccess/.
  3. Start the UCM and IBR servers.

Performance Tuning Guidelines

Installing Oracle SES 11.2.2.2.0

Define Network Access Rules

The SES installation is done on the VM that hosts the OTD. The SES installation will use the database instance from DBaaS. However, the DB listener is not accessible from the OTD VM by default. To make the DB listener accessible to this VM, a network access rule must be defined using the Oracle Compute Cloud Service Console. Here, we shall be re-using the protocol for the DB listener port which is available out of the box.

Repeat the steps executed in the section Opening Up Traffic to WebCenter Ports From Oracle Traffic Director(OTD) VM to achieve this.

Here are the details of the access rule to be defined:


Name: ora_otd2db_dblistener (any name will do)
Protocol: ora_dblistener (name of the protocol you created in the previous step)
Source: Network Groups: ora_otd
Destination: ora_db
Description: Permits listener connection to database from OTD Node

Note: For more information on creating access rules, see section Opening Up Traffic to WebCenter Ports From Oracle Traffic Director(OTD) VM.

  1. The following prerequisites must be met for the existing database from the JCS setup to be re-used for the SES installation.

    All the required database patches for Oracle SES must be applied on the Oracle Database instance. For more information on applying the mandatory database patches, refer to section Installing Mandatory Oracle Database Patches in Oracle® Secure Enterprise Search Installation and Upgrade Guide 11g Release 2 (11.2.2.2) for Linux x86 (64-Bit).

    The database resource settings such as processes and sessions must be configured based on the number of WebLogic Servers to be run in a cluster. If these resource settings are not configured correctly, an error similar to the following may appear in the Oracle SES log file:

    For example, Oracle Database's default settings for maximum sessions and maximum processes are 247 and 150 respectively. These are not adequate to allocate database connections when more servers come online. To resolve this issue, you must increase the values for both these settings to about 1000.

    For more information about these database resource settings, refer to the section Database Initialization Parameters in the Oracle Secure Enterprise Search Administrator's Guide.

    The above configuration changes and patching require the database to be re-started. Before proceeding with the changes documented above, shut down any existing server that connects to this database instance.

  2. Download the SES Shiphome Oracle Secure Enterprise Search 11gR2 (11.2.2.2) from OTN.

    The zip files for this will be:

    ses_11_2_2_2_0_linux64_1of4.zip
    ses_11_2_2_2_0_linux64_2of4.zip
    ses_11_2_2_2_0_linux64_3of4.zip
    ses_11_2_2_2_0_linux64_4of4.zip

    Copy these zip files to the cloud-vm using the following command (where the SES Installation will be done):

    scp –i RSA_identity_file ses_11_2_2_2_0_linux64_xof4.zip remote_user@remote_vm:/shiphome_storage_location
  3. Unzip all the SES Shiphome files (ses_11_2_2_2_0_linux64_xof4.zip) in the shiphome storage location (for example, /stage).

  4. Navigate to the top-level directory of the Oracle SES software distribution where the zip archives were unzipped (/stage/ses_11_2_2_2_0_linux64 in this case).

  5. Run the following command:

    ./runInstaller
  6. Choose Install and Configure Oracle Secure Enterprise Search with Middle Tier (on an existing database) to install SES with its own WebLogic Server using an existing database.

  7. Provide the following details for the existing Oracle Database and for the new Oracle SES schema. Provide details for installing the middle tier. Follow the instructions in Install and Configure Oracle Secure Enterprise Search with Middle Tier (on an Existing Database) of Oracle® Secure Enterprise Search Installation and Upgrade Guide 11g Release 2 (11.2.2.2) for Linux x86 (64-Bit).

    Run the root script from OPC user when prompted by the installer. To do this, open a new terminal, connect to the VM (where SES is being installed), and execute sudo root_script_specified_by_the_installer

    Create a folder named /ses. Install SES on the folder /ses. Provide /ses/middleware for the SES Oracle Home during installation and /ses/sesOraInventory as the inventory directory.

    To perform this, log in to the VM and run the following commands:

    
    cd /
    sudo mkdir ses
    sudo chmod –R 777 /ses
    sudo su – oracle
                
  8. You must apply mandatory software patches to the Oracle SES 11.2.2.2 installtion. Follow the instructions in Mandatory Software Patches of Oracle® Secure Enterprise Search Release Notes 11g Release 2 (11.2.2.2). Each patch has its own readme associated with it.

    Before patching the SES, ensure that the appropriate DB patches are installed. Refer to section Installing Mandatory Oracle Database Patches in Oracle® Secure Enterprise Search Installation and Upgrade Guide 11g Release 2 (11.2.2.2) for Linux x86 (64-Bit).

Configuring Oracle SES

After the SES is installed, SES URLs will be shown in the installation completion screen. Make a note of the URLs.

They are of the following formats:

http://ses-host:ses-port/search/admin/index.jsp (SES Administration tool)
http://ses-host:ses-port/search/admin/index.jsp (SES Query)

For example:

http://slc402354.us.oracle.com:5720/search/admin/index.jsp
http://slc402354.us.oracle.com:5720/search/query

Note: Open up SES Port 5720 for public internet access. Follow the instructions in the previous section 'Opening Up Traffic to OTD Listen Port From Public Internet'.

Create the required 'protocol - access rule' combinations as follows:

Protocol:

Name: ora_wcp_ses_http
Port Type: tcp
Port Range Start: 5720
Description: Permit Traffic to SES PortProtocol: tcp

Access Rule:

Name: ora_wcp_p2_ses_http
Protocol: ora_wcp_ses_http
Source: IP Lists: public-internet
Destination: ora_otd
Description: Permit Traffic to SES Port

SES on JCS

To work around any problem with accessing SES Admin or SEARCHADMIN datasource post installation, remove the last five lines from the datasource SearchAdminDS. Follow these steps:

  1. Log in to the WebLogic Server Admin Console.
  2. Naviagte to Service > Datasources.
  3. Click Lock and Edit in the top left corner of the admin console.
    Lock and Edit Function
    Description of this image
  4. Edit the Data source.
  5. Go to the connection pool.
    Navigate to Connection Pool
    Description of this image
  6. Remove the following lines:
    • oracle.net.encryption_client=REQUESTED
    • oracle.net.encryption_types_client=(RC4_56,DES56C,RC4_40,DES40C)
    • oracle.net.crypto_checksum_client=REQUESTED
    • oracle.net.crypto_checksum_types_client=(MD5)
    • SetBigStringTryClob=true
  7. After making the changes, click Save.
    Navigate to Connection Pool
    Description of this image
  8. Click Release Configuration.

General Configurations

  1. You must configure Oracle SES with an identity management system to validate and authenticate users. This is necessary for secure searches, so searches return only results that the user is allowed to view based on access privileges. You can skip this step if WebCenter Portal is not associated with an identity store.

  2. To use Oracle SES to search spaces, lists, or pages, you must first create a crawl admin user in WebCenter Portal spaces and in your back-end identity management server (for example, mycrawladmin). You must create a crawl admin user only once. Alternatively, you can use user weblogic for this purpose.

  3. Run the following commands by connecting to the WebCenter Portal wlst prompt. The steps for this are:

    From Oracle_WC/common/bin run ./wlst.sh
    connect()
    username=”webcenter-portal-admin username”
    password=”welcome1”
    URL = t3s://wcp_admin_host:admin_port (use t3 if SSL is not enabled for admin console)
    grantAppRole(appStripe="webcenter",appRoleName="webcenter#-#defaultcrawl",principalClass="weblogic.security.principal.WLSUserImpl",principalName="your crawl-admin user");
                            
  4. For example, you can run the following commands:

    cd /u01/app/oracle/middleware/Oracle_WC/common/bin
    ./wlst.sh
    connect()
    username=weblogic
    password=welcome1
    URL = t3s://wcp_admin_host:admin_port (use t3 if SSL is not enabled for admin console)
    grantAppRole(appStripe="webcenter",appRoleName="webcenter#-#defaultcrawl",principalClass="weblogic.security.principal.WLSUserImpl",principalName=”weblogic”);
  5. Add Federation Trusted Entity

    Each Oracle SES instance must have a trusted entity for allowing WebCenter Portal end users to be securely propagated at search time. (A trusted entity allows the WebCenter Portal to authenticate itself to Oracle SES and assert its users when making queries on Oracle SES.) This trusted entity can be any user that either exists on the identity management server behind Oracle SES or is created internally in Oracle SES.

    You can do this either in WLST or in Oracle SES.

    This trusted entity name(for example "wcsearch") and password is required later as the appUser and appPassword properties on the WLST command createSESConnection.

    Important: Add the wcsearch user in the LDAP/Embedded LDAP being used. Follow the instructions in Section 31.3 Adding Users to the Embedded LDAP Identity Store to achieve the same.

    To do this with WLST, use the createFederationTrustedEntity command:

    createFederationTrustedEntity(appName='webcenter', sesUrl='http://mySEShost.com:sesPort/search/api/admin/AdminService', sesPassword='mySESAdminPassword',entityName='myTrustedEntityUser', entityPassword='myTrustedEntityUserPassword', desc='Trusted entity for WebCenterPortal', sesSchema='search_schema_used')

    For Example:

    createFederationTrustedEntity(appName='webcenter', sesUrl='http://mySEShost.com:7777/search/api/admin/AdminService', sesPassword='welcome1',entityName='wcsearch', entityPassword='welcome1', desc='Trusted entity for WebCenterPortal', sesSchema='searchsys')
    

    To do this in Oracle SES, follow these steps:

    1. In the Oracle SES administration tool, navigate to the Global Settings - Federation Trusted Entities page.
    2. Enter a name for a trusted entity. This is the name that WebCenter Portal uses to authenticate itself to Oracle SES at search time (before it propagates the end user identity to Oracle SES).
    3. To allow the entity to be authenticated through Oracle SES:
      1. Enter any user name (for example, wcsearch) and password (for example, myPassword1).
      2. Do not select the Use Identity Plug-in for authentication checkbox.
  6. Restart the WebCenter Portal Managed Server.

Configuring SES to Search Portals, Lists, Pages, and People

  1. Log in to the SES Administration tool http://ses-host:ses-port/search/admin/index.jsp

  2. Go to Home > Sources.

  3. From the Source Type dropdown list, select the Oracle WebCenter source type, and click Create.

    Select Source Type
    Description of this image
  4. If front-ended with OTD, the routes must be specified in the configuration in OTD for /rsscrawl and /sesUserAuth (along with existing routes like /webcenter).

    Note: Follow the instructions given previously in the document to open up ports for OTD.

    OTD Configuration - Routes
    Description of this image

    OTD Configuration - Routes
    Description of this image
    OTD Configuration - Routes
    Description of this image
  5. Enter the following source parameters:
    • Source Name: unique_name
    • Configuration URL: host:port_of_WebCenterSpaces/rsscrawl; for example, http://myhost:8888/rsscrawl

      If front-ended with OTD, you can add otd_host:otd_port_for_webcentermanaged_Server/sesUserAuth

    • Authentication Type: BASIC
    • User ID: Crawl admin user you registered (for example, weblogic)
    • Password: Password for the crawl admin user
    • Realm: jazn.com
    • Oracle SSO Login URL: Leave this field blank
    • Oracle SSO Action URL: Leave this field blank
    • Scratch Directory: Optional. Specify a directory on the system under which the Oracle SES instance resides
    • Number of connection attempts: Maximum number of connection attempts to access data feed or upload status feed
  6. Click Next.
  7. Create User Defined Source
    Description of this image
  8. Enter the following source parameters:

    On the Create User-Defined Source > Step 2 > Authorization page, the Plug-in Class Name, Jar File Name, and Authorization Endpoint are pre-populated on the page.

    Enter the following plug-in parameters:

    • Realm: jazn.com
    • Authorization endpoint: host:port/sesUserAuth

      If front-ended with OTD, you can add otd_host:otd_port_for_webcentermanaged_Server/sesUserAuth

    • User ID: Crawl admin user you registered (for example, weblogic)
    • Password: Password for the crawl admin user
    • Authorization User ID Format: Authentication attribute used in the active identity plug-in. To find this value, go to the Global Settings > Identity Management Setup page in Oracle SES. Enter the value of the Authentication Attribute under the Active Plug-in (for example, nickname or username or something else).

    Use nickname as default if using OID as authenticator.

  9. Click Create to complete the source creation.

  10. Create a source group that includes the WebCenter Portal services sources you created.

    1. Go to the Search > Source Groups page, and click Create. Provide a name for the source group.
    2. From the Select Source Type dropdown list, select Source Type as Oracle WebCenter. From the Available Sources listed for each source type, move the source you created for that source type into the Assigned Sources list.
    3. Click Finish.

    NOTE: Each type of source that will be created in the following sections (for example WebCenter Content, Discussions/Announcement) must be associated to this same source group similarly.

  11. From Oracle_WC/common/bin, run ./wlst.sh. Run the following commands by connecting to the WebCenter Portal wlst prompt:

    Note: Here the appUser is the Federation Trusted Entity created in the previous section.

    1. createSESConnection(appName='webcenter',name='MySesConnection1',url='http://ses-host:ses-port/search/query/OracleSearch',appUser='wcsearch',appPassword='welcome1',default=true)
    2. setSESConnection(appName='webcenter',name='MySesConnection1',url='http://ses-host:ses-port/search/query/OracleSearch',appUser='wcsearch',appPassword='welcome1',default=1)
    3. setSpacesCrawlProperties(appName='webcenter',fullCrawlIntervalInHours=168,spacesCrawlEnabled = true,documentCrawlEnabled=true,discussionsCrawlEnabled=true)
    4. setSESVersion('webcenter','http://ses-host:ses-port/search/api/admin/AdminService','searchsys','welcome1')
    5. setSearchSESConfig(appName='webcenter',dataGroup='datagroup_created_in previous_step')
    6. setSearchConfig(appName='webcenter',numResultsMain=100)
    7. setSearchConfig(appName='webcenter',executionTimeout=300000)
  12. Restart WebCenter Portal Managed Server.

Configuring SES to Search Documents

  1. Enable SESCrawlerExport in Content Server.

    To do this, log in to the content Server as admin. From the Administration drop-down menu, select Admin Server. Enable the component SESCrawlerExport and restart the Content Server.

  2. Configure the SESCrawlerExport component.

    1. Log on to the Content Server as system administrator. For example, http://host:port/cs.

    2. From the Administration dropdown menu, select Admin Server

      Ensure that security on authentication and authorization APIs provided by the SESCrawlerExport (that is, set Disable Secure APIs) is set to false. This is false by default. This lets security provided by the SESCrawlerExport to be done internally instead of by the content server.

      Additionally, in clustered environments only, the feedLoc parameter must specify a location on the shared disk accessed by the nodes of the Content Server, and they must each reference it the same way. For example, sharedDrive/dir1/dir2. Note that this is not the default location (relative path) provided.

    3. Restart Content Server
      Description of this image
      Restart Content Server
      Description of this image
      Restart Content Server
      Description of this image
  3. Take a snapshot of the Content Server repository.
    1. Log on to the Content Server as a system administrator. For example, http://host:port/cs
    2. Select SESCrawlerExport from the Administration dropdown menu.
    3. Select All Sources, and click Take Snapshot.

    It is important to take a snapshot before the first crawl or any subsequent full crawl of the source.

  4. Log in to the SES Administration tool http://ses-host:ses-port/search/admin/index.jsp.
  5. Follow each step of Section Setting Up Oracle SES to Search Documents in Oracle® Fusion Middleware Administering Oracle WebCenter Portal 12c Release 2 (12.2.1.0.0).

Note:

  • Keep all the sources created (for Webcenter and for content) under the same datagroup. To do this, navigate to Search > Source Groups and add both the sources under the same/relevant data group (for example, datagroup1).

  • Update the schedules as required for hourly/daily crawls and for crawling all the documents. To do this, navigate to Home > Schedules, and edit the respective schedule according to the requirement.

Configuring SES for Discussions and Announcements

Before performing the steps in this section, verify the following:

Note: These verifications are not required if you have a new installation of WebCenter Portal (with an Oracle database) and Oracle WebCenter Portal's Discussion Server.

  1. Verify that the Oracle WebCenter Portal's Discussion Server back end has been configured properly by noting that the MyPrefix_DISCUSSIONS user is installed in RCU.
  2. Then verify that the discussions crawler has been configured properly by noting that the MyPrefix_DISCUSSIONS_CRAWLER user is installed in RCU.

Follow the steps in the following section of the Fusion Middleware Administering Oracle WebCenter Portal guide:

Setting Up Oracle SES to Search Discussions and Announcements

Note: If you are not using external LDAP/OID, you can omit the Authorization User ID Format field which is specified in the document.

Additionally, you must also edit the Source Group created in a previous section to include all the sources created.

Enabling Faceted Search

  1. Enable Faceted Search for WebCenter Portal by creating Facets in SES.

    Do this only once per SES Instance. Facets are Oracle SES objects that let users refine searches by navigating indexed data without running a new search. You must first define facets (using the provided files) in Oracle SES. Facets defined in Oracle SES are picked up in WebCenter Portal though the Tools and Services > Search Administration page. WebCenter Portal provides the following input files to the Oracle SES Admin API command line interface:

    facet.xml: This configures facets in Oracle SES.

    searchAttrSortable.xml: This defines attributes for absolute sort.

    Locate these files in webcenter_portal_ses_admin.zip (usually under Middleware_Home/Oracle_WC/ses directory). Copy the webcenter_portal_ses_admin.zip file to the SES VM using the scp command. Unzip this file and follow the instructions in the readme.txt file. The two commands that must be executed are given in the readme.txt file. Execute these commands from Oracle_SES_Home (that is, from ses_mw_home/Oracle_SES/bin).

  2. After you run these files, you can view facets in the Oracle SES administration tool on the Global Settings > Facets page.

    Global Settings Facets Page
    Description of this image

  3. If you encounter an error or warning in this facets page, delete the facet from the page and recreate it from here if required.

  4. (Optional) To create a new facet, on the Global Settings > Facets page, click Create. Enter a name for the facet and the search attribute from which the Facet value is to be generated.

    For String facet types, you must also enter the path delimiter. This is a single character used for demarcation for displaying the facet tree hierarchy for the selected facet tree node on the query page, for example, tools/power tool/drills, where "/" is the path delimiter. You can set it to blank if the facet tree is one level deep; that is, if its nodes do not have child nodes.

    Note: The Scope GUID and Service ID facets are mandatory. Facet names are case-sensitive. You must have these exact facet names.

    Note: Optionally, configure the security filter lifespan. This refreshes the authorization policies for users in the system. It is best to have a short lifespan when user policies change frequently. This chapter uses Oracle Internet Directory identity plug-in as the example. For example, on the Global Settings > Query Configuration page, under Secure Search Configuration, enter 0 for Security Filter Lifespan (minutes). Valid values for the security filter lifespan are between 0 minutes (no cache) and 526500 minutes (cache for one year).

Want to Learn More?