1 Introduction

1.4.2.1 Restrictions on Specific Browsers

1.4.2.2 Process to Install and Configure WebCenter With 32-bit JDK on Supported 64-Bit Platform

For WebCenter 11g Release 1, the following platform has been verified with 32-bit JDK:

Solaris Sparc:

32-bit Sun JDK 1.6.0_11+

To install and configure WebLogic Server with 32-bit JDK perform the following steps:

1. Install the supported 32-bit JDK

2. Export the 32-bit JDK environment. For example:

   export JAVA_HOME=/scratch/aime/jdk1.6.0_11
   export PATH=/scratch/aime/jdk1.6.0_11/bin:$PATH
   

3. Run the WebLogic Server generic installer to install WebLogic Server with 32-bit JDK:

   java -jar  wls1031_generic.jar
   

4. Install WebCenter with the required 64-bit JDK. Unzip the shiphome and go to Disk1, then invoke runInstaller command with -jreLoc pointing to the 64-bit JDK. For example:

   ./runInstaller -jreLoc /scratch/aime/jdk1.6.0_11/jre
   

5. Run the configuration script to create the WebCenter Domain:

   $ORACLE_HOME/common/bin/config.sh
   

6. Provide the 32-bit JDK location while running the configuration script. After the domain is configured with 32-bit JDK, no further updates are required.

1.4.2.3 Process to Install and Configure SOA With 32-bit JDK on 64-bit Solaris Sparc

For SOA 11g Release 1, the following platform has been verified with 32-bit JDK:

Solaris Sparc:

JDK: 32-bit Sun JDK 1.6.0_11+

To install and configure WebLogic Server with 32-bit JDK and SOA with 64-bit JDK on 64-bit Solaris Sparc perform the following steps:

1. Install the supported 32-bit JDK

2. Export the 32-bit JDK environment. For example:

   export JAVA_HOME=/scratch/aime/jdk1.6.0_11
   export PATH=/scratch/aime/jdk1.6.0_11/bin:$PATH
   

3. Run the WebLogic Server generic installer to install WebLogic Server with 32-bit JDK:

   java -jar  wls1031_generic.jar
   

4. Install SOA with the required 64-bit JDK. Unzip the shiphome and go to Disk1, then invoke runInstaller command with -jreLoc pointing to the 64-bit JDK. For example:

   ./runInstaller -jreLoc /scratch/aime/jdk1.6.0_11/jre
   

5. Replace the 64-bit X-Engine libraries installed by Oracle Universal Installaer (OUI) ($MWHOME/soainstalldir/soa/thirdparty/edifecs) with the 32-bit X-Engine library, XEngine_solaris_sparc.tar.gz, which can be downloaded as Patch 8693816 from MyOracleSupport.

6. After the domain is configured with 32-bit JDK, the setSOADomainEnv.sh script needs to be updated to remove the -d64 option, with details below:

   before:
   #-----------------------------------------------------
   # Sun OS
   #-----------------------------------------------------
   SunOS)
   USER_MEM_ARGS="-d64 ${PORT_MEM_ARGS}"
   export USER_MEM_ARGS
   

   after:
   #-----------------------------------------------------
   # Sun OS
   #-----------------------------------------------------
   SunOS)
   USER_MEM_ARGS="${PORT_MEM_ARGS}"
   export USER_MEM_ARGS
   

Cloning

Cloning is the process of copying an existing entity to a different location while preserving its state. Cloning operation starts with creating the archive containing Middleware Home or Oracle Home of the original installation. Once the archive is prepared, we can execute command applyclone.

java -jar $ORACLE_HOME/jlib/cloningclient.jar ac -al $ARCHIVE_STORE_LOC/mw.jar -tl 
$CLONE_MW_HOME -invloc $ORAINST_LOC/oraInst.loc -so all -ldl /tmp

Where the $ARCHIVE_STORE_LOC is the location to pick up the cloning archive, $CLONE_MW_HOME is the location to create the cloned middleware home and $ORAINST_LOC is the location to pickup the oraInst.loc file.

On 64-bit Solaris Sparc, applyclone needs to be executed with 64-bit Sun JDK; otherwise, a java.lang.UnsatisfiedLinkError will be thrown.