Tips for Installing WCSites11gR1on Exalogic

This paper can be downloaded by clicking: Installing WebCenter Sites on Exalogic Ver1.0

 

Tips for Installing WebCenter Sites 11gR1 on Exalogic

 

Background:

Recently I had the opportunity to install WebCenter Sites on Exalogic. Everything, including the database, was to be installed on the same Exalogic box. In this aspect the installation was different from a recommended WebCenter Sites install. Typically, WebLogic Application Server would be on Exalogic and Oracle Database server would be on Exadata.

This is not an installation document. To install the software, I was using the WebCenter Sites Installation Guide[1] and WebCenter Sites Installing & Configuring Supporting Software[2]. This document only lists the issues that I faced during installation.

Software Used:

 

  • WebCenter Sites 11gR1
  • WebLogic 11gR1
  • OHS 11gR1
  • Oracle Database 12c

 

Connectivity Issues:

1)      Accessing the Database and WebLogic Server

Exalogic systems may have limited front-end IPs. In our case, only two OHS servers had the front-end IP. To access any other server from outside, we had to SSH into OHS, and then tunnel into the systems. I was using Moba-XTerm Personal Edition Version 7.1[3] for this.

 

2)      Redirecting the output to Windows System

Since we do not connect to the database and WebLogic servers directly, the output of the installation process needs to be sent to the Windows laptop via the OHS Server. This made the graphical interface of the installation program very slow.

Moba-XTerm has the option to capture the output and send it to X-server running on the Windows laptop. I had set up the Moba-XTerm as follows:

MobaXTermConfig

Database Installation Issues:

 

3)      Creating Database User:

WebCenter Sites 11gR1 supports the Oracle 12c database, but its installation guide is written for Oracle Database 11g. WebCenter Sites requires a database user for installation and subsequently for accessing the database. To create the user, the installation guide uses the ‘emctl’ command, but Oracle 12c does not support the ‘emctl’ command.
To create the database user, I first set the ORACLE_HOME and then used SQL*Plus command as follows:

[oracle@vserver7 bin]$ export ORACLE_HOME=/u01/oracle/product/12.1.0/dbhome_1

[oracle@vserver7 bin]$ ./sqlplus sys/<password>@<db server backendIP>/ORCL as sysdba

 

SQL> CREATE USER “CSUSER” IDENTIFIED BY “<password>” DEFAULT TABLESPACE “USERS” TEMPORARY TABLESPACE “TEMP” ACCOUNT UNLOCK;

 

SQL>GRANT CONNECT, CREATE SESSION, CREATE TABLE, CREATE VIEW, UNLIMITED TABLESPACE TO “CSUSER”;

 

SQL>COMMIT;

 

WebLogic Server Installation Issues:

 

4)       No Space Error

While installing WebLogic Server, I received a “no space error”. This was due to the default size of the /tmp directory. I resolved it by making a tmp directory and specifying it in the command line:

mkdir /u01/oracle/tmp
java -Xms128m -Xmx256m -d64 -Djava.io.tmpdir=/u01/oracle/tmp-jar wls1036_generic.jar

This tmp directory can be removed after installation.

Oracle HTTP Server Installation Issues:

 

5) JRF Not Set Error
While installing OHS, I got the error “…JRF is not setup in specified domain”
JRFError

WebCenter Sites does not install JRF. To take care of this issue, please make sure that while “Configuring Components” in OHS, you deselect the checkbox “Associate Selected Components with WebLogic Domain”. See the screen below:

OHSConfig

 

6)      Virtual Hosts
While installing OHS, I ran into issues with setting up virtual hosts. In the end, I did not use ‘Virtual Hosts’, and configured the httpd.conf as follows:

 

  • In httpd.conf commented the lines for Virtual Host, and added an entry for listening at port 7777

#NameVirtualHost *:7777

# OHS Listen Port

Listen 7777

 

Note: I am not saying that you cannot use Virtual Hosts, but just that, for my requirement Virtual Hosts were not needed. It was much simpler to directly add entry for listening at port 7777.

  • In moduleconf folder created admin.conf:

# Admin Server and EM

<Location /console>

SetHandler weblogic-handler

WebLogicHost {specify web logic admin server internal ip address}

WebLogicPort {specify web logic admin server internal port}

</Location>

<Location /consolehelp>

SetHandler weblogic-handler

WebLogicHost {specify web logic admin server internal ip address}

WebLogicPort {specify web logic admin server internal port}

</Location>

<Location /em>

SetHandler weblogic-handler

WebLogicHost {specify web logic admin server internal ip address}

WebLogicPort {specify web logic admin server internal port}

</Location>

 

  • Also created wcsites.conf under /u01/oracle/Middleware_42/Oracle_WT3/instances/instance3/config/OHS/ohs3/moduleconf

 

# WebCenter Sites

<Location /cs>

SetHandler weblogic-handler

WebLogicHost {specify web logic managed server internal ip address}

WebLogicPort {specify web logic managed server internal port}

</Location>

<Location /cas>

SetHandler weblogic-handler

WebLogicHost {specify web logic managed server internal ip address}

WebLogicPort {specify web logic managed server internal port}

</Location>

WebCenter Sites Installation Issues:

 

7) Deploying Sites Server

Exalogic box has different URL for accessing the servers from inside Exalogic box, and for accessing the servers from outside.

In my case, access to WebLogic Admin & Managed Servers was through OHS. The internal address for OHS box was 192.168.0.39, and its external address was 10.128.39.179. OHS was listening on port 7777.

WebLogic server itself was installed on the server with internal ip address of 192.168.0.42. The admin server was running at port 7001 and the managed server was running at port 7003.

In short on Exalogic box, we had three different IP addresses:
* Internal IP address of the server where managed server in installed
* Internal IP address of the OHS server used to access WebLogic Managed Server
* External IP address of the OHS Server used to access WebLogic Managed Server

 

WebCenter Sites Installation Guide is not customized for Exalogic and the installation process does not differentiate between internal OHS address and external OHS address. Since the installation process runs on the Exalogic box, for installation we need to use the internal OHS IP address, as shown below:

HostName or IP Address of your application Server: This should be the INTERNAL IP Address of the OHS server used to access WebLogic Managed Server.

 

SitesHostNameURL

 

8) Deploying CAS Server

 

For deploying CAS the system asks for three different IP addresses, and we can specify them properly, as follows:

Enter Server Hostname: This is the EXTERNAL IP Address/host name of the OHS server used to access CAS Server (WebLogic Managed Server).

Enter Server Hostname of internally accessible CAS: This is the INTERNAL IP Address/host name of the OHS server used to access CAS Server (WebLogic Managed Server).

Enter Server HostName where CAS is actually deployed: This is the INTERNAL IP address of the CAS Server (WebLogic Managed Server).

CASURL

 

9)      Multicasting Not Enabled

 

Multicasting not enabled by default on Exalogic. If you are using ehCache with Sites, it requires multicasting to be enabled.

To add the multicast routing to Exalogic box, your first need to identify the network interface you want to use for the multicast communication (preferable, a IPoIB one, in my case 192.168.0.x):

$ # as root
$ ip add ls | grep 192.168.0 | awk ‘{print $NF}’
bond2

This gives us bond2 as the interface with an IP 192.168.0.x. To add the route, run:
$ # as root
$ route add -net 224.0.0.0 netmask 240.0.0.0 dev bond2

To make the change permanent, so multicasting is enabled every time system boots up, you need to create a file route-bond2 under /etc/sysconfig/network-scripts, as follows:

[root@vserver5 network-scripts]# echo “224.0.0.0/4 dev bond2” >> /etc/sysconfig/network-scripts/route-bond2

Post Installation Issues:

 

10)      Non-Trusted URL

During installation WebCenter Sites makes a list of trusted URLs. These are the URLs that are allowed to login to WebCenter Sites. The list of trusted URLs is kept in the {install directory}/bin/customBeans.xml. Since the installation was done using ‘internal’ ip address, this file contains the ‘internal’ ip address. The external ip address needs to be added to this to allow requests coming from a client browser to login to WebCenter Sites UI.

 

11) Wrong Web Root

During installation, one can choose to install the sample sites like AVI Sports & First Site II. If you installed these Sites, the Vanity URLs for these sites will all point to ‘internal’ URLs, as shown in the screen shot below.
WebRoot

To correct this, you need to login to WebCenter Sites Admin UI, and edit the Web Roots to use ‘External’ IP.

Summary:

 

This document is a listing of the issues I faced, and how I resolved them, in installing WebCenter Sites 11gR1 on an Exalogic system. At the moment, WebCenter Sites documentation does not cover installation on an Exalogic Server. Until WebCenter Sites documentation is updated, this documentation may help anyone who is trying to install WebCenter Sites on an Exalogic server.

I needed to install only one WebCenter Sites server. Typically, one will need to install a cluster. To add a cluster member, please follow the procedure given in WebCenter Sites Installation Guide[1].

 

References:

 

[1] http://docs.oracle.com/cd/E29542_01/doc.1111/e29632/toc.htm

[2] http://docs.oracle.com/cd/E29542_01/doc.1111/e29751/toc.htm

[3] http://mobaxterm.mobatek.net/download-home-edition.html

Add Your Comment