Installing and Configuring Oracle WebCenter Content 11gR1

Installing and Configuring Oracle WebCenter Content 11gR1 (formerly Enterprise Content Management)

Oracle WebCenter Content, an Oracle Fusion Middleware component, is an integrated suite of products designed for managing content.

The process of installing and configuring Oracle WebCenter Content includes these high-level tasks:

  1. Preparing your system environment for installation
  2. Creating schemas for applications
  3. Installing an Application Server and Oracle Fusion Middleware
  4. Installing Oracle WebCenter Content
  5. Configuring Oracle WebCenter Content
  6. Installing and configuring an external LDAP-based identity store
  7. Performing Postinstallation Configuration
  8. Verifying the Configuration

Before performing any installation, you should read the system requirements and certification documents to ensure that your environment meets the minimum installation requirements(available on OTN) for the products you are installing.

  1. Install RHEL5.5 64-bit OS, configure Kernel parameters and install required RPMs for this installation on DB and App nodes.
  2. Install Oracle Database software 11.2.0.1 64-bit and create a database
  3. Install WebCenter Schema using RCU 11.1.1.6.0 utility on the database created as in step 2
  4. Install Oracle WebLogic Server 10.3.6 Generic
  5. Install Oracle WebCenter Content 11.1.1.6.0
  6. Preparing to Configure Oracle WebCenter Content Applications

After you have successfully run the Oracle Fusion Middleware 11g Oracle WebCenter Content Installer and created application schemas, you can deploy and configure the following Oracle WebCenter Content products as applications:

  • Oracle WebCenter Content (which includes Oracle WebCenter Content Server)
  • Oracle WebCenter Content: Inbound Refinery
  • Oracle WebCenter Content: Imaging
  • Oracle Information Rights Management
  • Oracle WebCenter Content: Records

Complete documentation is available on Oracle site here

Advertisements

Oracle IDM 11gR1 (11.1.1.6.0) Installation and Configuration

  1. Review and Make Note of Your Operating System Capabilities (32-bit or 64-bit): I have 64-bit Virtuals
  2. Review the Certification, System Requirements, and Interoperability Information without fail
  3. Understand the Types of Oracle Fusion Middleware Installers. I will be concentrating on Identity Management Installation in this post.
  4. Download the required softwares (if you are on oAS 10g, you need to upgrade to 11g now, not covered in this post)
    1. Download the Oracle database software: I am using Oracle Database 11.2.0.1
    2. Download the Oracle RCU : I am using Repository Creation Utility 11g Release 1 (11.1.1.6.0)
    3. Download 64-bit, Sun DDK 1.6.0_24/ Oracle JRockit SDK 1.6.0_24
    4. Download the Oracle Weblogic Server Software: I am using Oracle WebLogic Server 11g (10.3.6) Generic
    5. Download the Oracle Identity Management 11g Release 1 (11.1.1.6.0)
    6. There are patches available for an existing Oracle Fusion Middleware installation: The IDM 11g patchset 5 (11.1.1.6.0) 13516867 is now available and is required if you are on 11.1.1.x.0 where x=2,3,4,5).

Start -> Install Database 11.2-> Run RCU 11.1(Install IDM schema)-> install JDK -> Install Oracle Weblogic 10.3 -> Install (do not configure) Oracle FMW 11.1 products-> Run the Patchset installer to update the software to 11g, if available -> Configure and create IDM domains and Managed servers – > Done

Operating system is RHEL 5.5 64-bit, kernel parameters adjusted accordingly and 64-bit RPMs required for this Fusion Middleware 11g installation has been installed both on Database node and Application node. Hardware and Software has met the minimum requirements as per Oracle recommendations.

Installing Sun JDK 1.6.0_24 64-bit

[oracle@mpoojari java]$ ls -ltr
total 1395588
-rw-r--r-- 1 oracle oinstall 1068506707 Feb 24  2012 wls1036_generic.jar
-rw-r--r-- 1 oracle oinstall   84909359 Feb 24  2012 jdk-6u24-linux-x64.bin
[oracle@mpoojari java]$ chmod +x jdk-6u24-linux-x64.bin
[oracle@mpoojari java]$ ls -ltr jdk-6u24-linux-x64.bin
-rwxr-xr-x 1 oracle oinstall 84909359 Feb 24  2012 jdk-6u24-linux-x64.bin
[oracle@mpoojari java]$ ./jdk-6u24-linux-x64.bin
...
[oracle@mpoojari java]$ ls -ltr
total 4
drwxr-xr-x 10 oracle oinstall 4096 Feb 20 19:28 jdk1.6.0_24
[oracle@mpoojari bin]$ pwd
/u01/java/jdk1.6.0_24/bin
[oracle@mpoojari bin]$ ./java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)

You can include the JAVA_HOME/bin in the $PATH to invoke java.

Install Weblogic server 10.3.6

[oracle@mpoojari media]$ java -jar wls1036_generic.jar
[oracle@mpoojari ~]$ cd /u01/app/oracle/Middleware/
[oracle@mpoojari Middleware]$ ls -ltr
total 176
drwxr-xr-x 7 oracle oinstall  36864 Feb 20 19:53 modules
-rw-rw---- 1 oracle oinstall    133 Feb 20 19:53 domain-registry.xml
drwxr-xr-x 8 oracle oinstall   4096 Feb 20 19:54 utils
-rw-r--r-- 1 oracle oinstall    623 Feb 20 19:54 ocm.rsp
-rw-r--r-- 1 oracle oinstall 108926 Feb 20 19:54 registry.dat
-rw-r--r-- 1 oracle oinstall   1957 Feb 20 19:54 registry.xml
drwxr-xr-x 2 oracle oinstall   4096 Feb 20 19:54 logs
drwxr-xr-x 8 oracle oinstall   4096 Feb 20 19:54 wlserver_10.3
drwxr-xr-x 6 oracle oinstall   4096 Feb 20 19:54 coherence_3.7

To use WebLogic Server with 64-bit JVM’s on Linux and Solaris or to use WLS on other supported platforms, use the WebLogic Server generic installer, however it does not include a JVM/JDK.

Oracle JRockit 1.6.0_24 JDK is included in WebLogic Server installers for the Windows and Linux platforms.

Note: Oracle Fusion Middleware 11g Release 1 (11.1.1.6.0) is not supported on Oracle WebLogic Server 12c (12.1.1).

Install Oracle Database 11.2.0.1

Install Oracle Database 11.2.0.1 software and use the dbca utility to create a test database.

  1. open_cursors should be greater than or equal to 500
  2. processes should be greater than or equal to 500
  3. Use AL32UTF8 as the database character set
SQL> alter system set processes=500 scope=spfile;
SQL> alter system set open_cursors=800 scope=spfile;
SQL> alter system set session_cached_cursors=500 scope=spfile;
SQL> alter system set session_max_open_files=50 scope=spfile;
SQL> alter system set aq_tm_processes=1 scope=spfile;
SQL> alter system set job_queue_processes=10 scope=spfile;
SQL> shut immediate;
SQL> startup;

Minimum Initialization Parameters for Oracle RAC Databases

Parameter Value
aq_tm_processes 1
dml_locks 200
job_queue_processes 10
open_cursors 800
session_max_open_files 50
sessions 500
processes 500
sga_target 512M
sga_max_size 800M
pga_aggregate_target 100M
session_cached_cursors 500
processes 2500
sga_target 4G
pga_aggregate_target 2G

OAM requires a minimum of 800 open cursors in the database. When OIM and OAM are available, the number of open cursors should be 1500.

Installing IDM schema using RCU

RCU is available only on 32-bit x86 Linux and 32-bit Microsoft Windows operating system platforms. On 64-bit Linux operating systems, you must run the following command before starting RCU:

set linux32 bash

[oracle@mpoojari oracle]$ pwd
/u01/app/oracle
[oracle@mpoojari oracle]$ unzip /u03/media/ofm_rcu_linux_11.1.1.6.0_disk1_1of1.zip
[oracle@mpoojari oracle]$ ls -ltr
total 28
drwxr-xr-x 32 oracle oinstall 4096 Dec 21 19:24 rcuHome
drwxr-xr-x  7 oracle oinstall 4096 Feb 20 19:54 Middleware
[oracle@mpoojari bin]$ pwd
/u01/app/oracle/rcuHome/bin
[oracle@mpoojari bin]$ ls -ltr rcu
-r-xr--r-- 1 oracle oinstall 9220 Aug  2  2011 rcu
[oracle@mpoojari bin] ./rcu

Installing IDM 11gR1

Linux x86-64
Oracle Linux 5 (UL3+)
Red Hat Linux 5 (UL3+) Kernel 2.6.18

binutils-2.17.50.0.6
compat-libstdc++-33-3.2.3
compat-libstdc++-33-3.2.3 (32-bit)
elfutils-libelf-0.125
elfutils-libelf-devel-0.125
gcc-4.1.1
gcc-c++-4.1.1
glibc-2.5-12
glibc-2.5-12 (32-bit)
glibc-common-2.5
glibc-devel-2.5
glibc-devel-2.5-12 (32-bit)
glibc-devel-2.12-1.7.el6.i686.rpm
libaio-0.3.106
libaio-0.3.106 (32-bit)
libaio-devel-0.3.106
ibgcc-4.1.1
libgcc-4.1.1 (32-bit)
libstdc++-4.1.1
libstdc++-4.1.1 (32-bit)
libstdc++-devel 4.1.1
make-3.81 sysstat-7.0.0
openmotif22-2.2.3 (64-bit) (for Oracle Reports Server)
openmotif-2.2.3 (64-bit) (for Oracle Reports Server)
redhat-lsb-3.1-12.3.EL.0.2
  • set hard and soft nofile to 4096 in etc/security/limits.conf
  • unset LD_ASSUME_KERNEL to avoid installation or configuration failure at instance creation.
  • Reboot the server
[oracle@mpoojari bin]$ cd /u02/softwares/
[oracle@mpoojari softwares]$ ls
idm  ofm_idm_linux_11.1.1.6.0_64_disk1_1of1.zip
[oracle@mpoojari softwares]$ cd idm/
[oracle@mpoojari idm]$ ls -ltr
total 36
-rw-r--r-- 1 oracle oinstall 20863 Dec 19 21:44 readme.htm
drwxr-xr-x 6 oracle oinstall  4096 Dec 20 03:01 Disk1
drwxrwxr-x 3 oracle oinstall  4096 Dec 20 03:01 Disk2
drwxrwxr-x 3 oracle oinstall  4096 Dec 20 03:01 Disk3
[oracle@mpoojari idm]$ cd Disk1/
[oracle@mpoojari Disk1]$ ls -ltr
total 36
-rwxrwxr-x  1 oracle oinstall 16429 Oct 27 10:47 runInstaller
drwxrwxrwx  6 oracle oinstall  4096 Dec 20 03:01 doc
drwxrwxrwx  3 oracle oinstall  4096 Dec 20 03:01 utils
drwxr-xr-x 12 oracle oinstall  4096 Dec 20 03:03 stage
drwxrwxrwx  3 oracle oinstall  4096 Dec 20 03:03 install
[oracle@mpoojari Disk1]$
[oracle@mpoojari Disk1]$ ./runInstaller -jreLoc /u01/java/jdk1.6.0_24/jre
Starting Oracle Universal Installer...

run orainventory script as root and click ok

Checking Temp space: must be greater than 400 MB. Actual 4489 MB Passed
Checking swap space: must be greater than 500 MB. Actual 2047 MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2012-02-20_10-38-45PM. Please wait ...

[oracle@mpoojari bin]$ pwd
/u01/app/oracle/Middleware/Oracle_IDM1/bin
[oracle@mpoojari bin]$ ls -ltr config.sh
-rwxr-x--- 1 oracle oinstall 5556 Oct  5 11:37 config.sh

Creating Managed Server instances

Creating managed server instances for OIM and OID yet to be covered. Keep watching this space.

Deinstalling Identity Management

The procedures for deinstalling Oracle Identity Management contains the following sections:

  • Deinstalling the Oracle Identity Management Oracle Home
  • Deinstalling the Oracle Common Home

Deinstall Oracle IDM home

Perform the following steps to deinstall your Oracle Identity Management Oracle Home using the graphical, screen-based deinstaller:

    1. Verify your Oracle Identity Management Oracle Home is not in use by an existing domain.
    2. Stop all processes that use the Oracle Identity Management Oracle Home.
    3. Open a command prompt and move (cd) into the IDM_ORACLE_HOME/oui/bin directory (UNIX) or the IDM_ORACLE_HOME\oui\bin directory (Windows).
    4. Invoke the Deinstaller from command line using the -deinstall option. For example:

On UNIX:

./runInstaller -deinstall

On Windows:

setup.exe -deinstall

The Welcome screen appears.

Deinstalling the Oracle Common Home

Perform the following steps to deinstall the ORACLE_COMMON_HOME directory:

  1. Stop all processes that use the ORACLE_COMMON_HOME directory. To know all the processes that are using ORACLE_COMMON_HOME directory use the following commands:
  2. On UNIX:

    ps-ef grep <oracle_common>

    On Windows:

    Use the Windows Task Manager to identify the processes that use the ORACLE_COMMON_HOME directory.

  3. Deinstall your Oracle Identity Management Oracle Home by performing the steps in Deinstalling the Oracle Identity Management Oracle Home.
  4. Open a command prompt and move (cd) into the ORACLE_COMMON_HOME/oui/bin/ directory (on UNIX) or the ORACLE_COMMON_HOME\oui\bin\ directory (on Windows).
  5. Invoke the Deinstaller from command line using the -deinstall option and the -jreLoc option, which identifies the location where Java Runtime Environment (JRE) is installed. For example:

On UNIX:

./runInstaller -deinstall -jreLoc FULL_PATH_TO_JRE_DIRECTORY

On Windows:

setup.exe -deinstall -jreLoc FULL_PATH_TO_JRE_DIRECTORY

The Welcome screen appears.

Entire documentation is available here

An internal operation has failed: Failed to start the component

Error creating ASComponent oid1.
Cause:
An internal operation has failed: Failed to start the component
Action:
See logs for more details 

While configuring domain for IDM 11.1.1.6.0, I faced an issue during the configuration progress for creating/starting OID or OVD.
Log messages:

[2012-02-26T18:15:18.281+05:30] [as] [NOTIFICATION] [] [oracle.as.provisioning] [tid: 12] [ecid: 0000ItNNVoS2zGYVLqZR8A1DPZ_5000003,0] Start of create component
[2012-02-26T18:15:18.312+05:30] [as] [NOTIFICATION] [] [oracle.as.provisioning] [tid: 12] [ecid: 0000ItNNVoS2zGYVLqZR8A1DPZ_5000003,0] Action for the oid1 is START
[2012-02-26T18:15:18.312+05:30] [as] [NOTIFICATION] [] [oracle.as.provisioning] [tid: 12] [ecid: 0000ItNNVoS2zGYVLqZR8A1DPZ_5000003,0] Trying to start the component oid1
[2012-02-26T18:15:18.687+05:30] [as] [WARNING] [] [oracle.as.config] [tid: 12] [ecid: 0000ItNNVoS2zGYVLqZR8A1DPZ_5000003,0] Failed to start component oid1[[
oracle.as.config.ProvisionException: HTTP status code = 400 : No processes or applications match the specified configuration.

The password for cn=orcladmin remained locked and OID installation cleared failed configuration in file system but not from database repository (ODS schema in database).

Dropped the ODS schema (and ODSSM if exists) using RCU 11.1.1.6.0 32-bit.

set linux 32bash
$RCU_HOME/bin/rcu.sh

I also deleted(or, rename) the AS instance home directory $MW_HOME/asinst_1 and  two more directories, domains and applications under $MW_HOME/user_projects directory for the failed domain.

Reconfigured the IDM domain using $MW_HOME/Oracle_IDM1/bin/config.sh and created schema(ODS and ODSSM) during IDM domain configuration itself.

I had no issues during the configuration phase and the domain was configured without an issue.

Exception in thread “main” java.lang.UnsatisfiedLinkError: /u01/app/oracle/rcuHome/jdk/jre/lib/i386/xawt/libmawt.so: libXtst.so.6: cannot open shared object file: No such file or directory

Error message while invoking Oracle RCU 11.1.1.6.0 32-bit.

Operating System: RHEL 5.5 64-bit

[oracle@mpoojari bin]$ ./rcu
Exception in thread "main" java.lang.UnsatisfiedLinkError: /u01/app/oracle/rcuHome/jdk/jre/lib/i386/xawt/libmawt.so: libXtst.so.6: cannot open shared object file: No such file or directory
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807)
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1703)
        at java.lang.Runtime.load0(Runtime.java:770)
        at java.lang.System.load(System.java:1003)
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807)
        at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1724)
        at java.lang.Runtime.loadLibrary0(Runtime.java:823)
        at java.lang.System.loadLibrary(System.java:1028)
        at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.awt.Toolkit.loadLibraries(Toolkit.java:1605)
        at java.awt.Toolkit.<clinit>(Toolkit.java:1627)
        at com.jgoodies.looks.LookUtils.isLowResolution(LookUtils.java:484)
        at com.jgoodies.looks.LookUtils.<clinit>(LookUtils.java:249)
        at com.jgoodies.looks.plastic.PlasticLookAndFeel.<clinit>(PlasticLookAndFeel.java:135)
        at oracle.sysman.assistants.rcu.ui.InteractiveRCUModel.<init>(InteractiveRCUModel.java:117)
        at oracle.sysman.assistants.rcu.Rcu.execute(Rcu.java:307)
        at oracle.sysman.assistants.rcu.Rcu.main(Rcu.java:363)

Checked RPMs to make sure libXtst.so.6 was installed.

[oracle@mpoojari ~]$ rpm -qa --qf "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" | grep libXtst
libXtst-1.0.1-3.1.x86_64

The error was due to a missing package libXtst-1.0.1-3.1.i386.rpm.

[root@mpoojari cdrom]# find . -name libXtst*
./iso/Server/libXtst-1.0.1-3.1.i386.rpm
./iso/Server/libXtst-1.0.1-3.1.x86_64.rpm
./iso/Server/libXtst-devel-1.0.1-3.1.i386.rpm
./iso/Server/libXtst-devel-1.0.1-3.1.x86_64.rpm
[root@mpoojari cdrom]# rpm -ivh ./iso/Server/libXtst-1.0.1-3.1.i386.rpm
warning: ./iso/Server/libXtst-1.0.1-3.1.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
   1:libXtst                ########################################### [100%]
[root@mpoojari cdrom]# exit
[oracle@mpoojari bin]$ rpm -qa --qf "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" | grep libXtst
libXtst-1.0.1-3.1.i386
libXtst-1.0.1-3.1.x86_64

Now I can invoke RCU without an issue.

 

Starting AdminServer Without Username & Password Prompt in WebLogic Server 10.3

To bypass the username password prompt when starting domain Admin Server or any of its managed ones, you can do the following steps:

1. Navigate to the current Domain Admin server directory that usually should be under the following location:
<FMW_HOME>/user_projects/domains/<Domain_Name>/server/AdminServer/

2. Create the “security” directory under the following location :

$mkdir <FMW_HOME>/user_projects/domains/<Domain_Name>/servers/AdminServer/security
3. Use any text editor to create a file called boot.properties in the security directory recently created in the previous step, and enter the following two lines in this file:
username=weblogic
password=password
After you edit the file, start up the server as soon as possible in order for the entries to be encrypted.
This is applicable to WLS 10.3 to 11.1.1.2 or later versions.

“Error 404–Not Found” While Accessing OSB Console Through URL http://hostname:port/osbconsole

While accessing Oracle Service Bus (OSB) Console through the URL http://<hostname&gt;:<osb-port>/osbconsole as mentioned in the OSB Installation Guide, browser returns “Error 404–Not Found”.

This applies to Oracle Service Bus – Version: 11.1.1.3.0 and later  (any platform)

This is a documentation Bug 9797009. OSB Console can be accessed through URL http://<admin server host>:<admin-port>/sbconsole

How to Delete a Weblogic Server (WLS) Domain

If you want to delete a WLS domain , all you need to do is remove the domain directory FMW_HOME/user_projects/domains/<domainDirectory> or <DomainDirectory>.

There is no special tool or script required to delete a domain. A domain is nothing but a configuration in WebLogic Server, not an installation. So for deleting a domain, uninstall packages are not needed. All the information related to the domain will be maintained within the domain itself. So when you remove the domain root folder, all the details of the domain are completely cleaned up. You can simply comment it.

Also you need edit the “nodemanager.domains” file under WL_HOME/common/nodemanager to remove domain information from that file .

The nodemanager.domains file specifies the domains that a Node Manager instance controls, and  should contain an entry specifying the domain directory for each domain the Node Manager instance controls, in this form:

domain-name=domain-directory

Take backup of the “nodemanager.domains” file before editing it
Delete the entry within domain-registry.xml file that reside under FMW_HOME.

Take backup of the xml file before editing it.