What I do is:
1. Download the log4jdbc4-1.2alpha2.jar, and put into $PE_HOME/jars
2. Download from SL4J the compress file: slf4j-1.5.8.tar.gz. Extract slf4j-api-1.5.8.jar and slf4j-simple-1.5.8.jar from the compress file, and put into $PE_HOME/jars
3. Modify $PE_HOME/conf/pe_dic.props, remark the old value and change the line:

#pe_dic.Url=jdbc:oracle:thin:@myoraclemachine:1521:PHDIC
pe_dic.Url=jdbc:log4jdbc:oracle:thin:@myoraclemachine:1521:PHDIC
#pe_dic.Driver=oracle.jdbc.driver.OracleDriver
pe_dic.Driver=net.sf.log4jdbc.DriverSpy

You’ll need to check your $PE_HOME/logs/pe_dic-server.log, to see the additional jdbc log messages.
Below is the snippet of the log file:

.........
11824 [main] INFO jdbc.audit - 1. Connection.isClosed() returned false
11824 [main] INFO jdbc.audit - 1. Statement.new Statement returned 
11824 [main] INFO jdbc.audit - 1. Connection.createStatement() returned net.sf.log4jdbc.StatementSpy@2e67cd84
11824 [main] INFO jdbc.sqlonly - SELECT upper(d.DATASTORE_NAME),c.DATABASE_S,c.DATABASE_NAME,c.TYPE,c.DRIVER,c.URL,c.TWO_TASK,c.SEQ_NAME,c.CLASS_NAME,c.PRIVATE 
FROM SLG_DATABASE c, SLG_DATASTORE d WHERE c.DATASTORE_S=d.DATASTORE_S ORDER BY d.DATASTORE_NAME,c.DATABASE_NAME 

11833 [main] INFO jdbc.sqltiming - SELECT upper(d.DATASTORE_NAME),c.DATABASE_S,c.DATABASE_NAME,c.TYPE,c.DRIVER,c.URL,c.TWO_TASK,c.SEQ_NAME,c.CLASS_NAME,c.PRIVATE 
FROM SLG_DATABASE c, SLG_DATASTORE d WHERE c.DATASTORE_S=d.DATASTORE_S ORDER BY d.DATASTORE_NAME,c.DATABASE_NAME 
 {executed in 9 msec}
11833 [main] INFO jdbc.resultset - 1. ResultSet.new ResultSet returned 
11833 [main] INFO jdbc.audit - 1. Statement.executeQuery(SELECT upper(d.DATASTORE_NAME),c.DATABASE_S,c.DATABASE_NAME,c.TYPE,c.DRIVER,c.URL,c.TWO_TASK,c.SEQ_NAME,c.CLASS_NAME,c.PRIVATE FROM SLG_DATABASE c, SLG_DATASTORE d WHERE c.DATASTORE_S=d.DATASTORE_S ORDER BY d.DATASTORE_NAME,c.DATABASE_NAME) returned net.sf.log4jdbc.ResultSetSpy@20e5ace9
11833 [main] INFO jdbc.resultset - 1. ResultSet.next() returned true
11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(1) returned AOI_SHAPEFILE
11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(2) returned 1263
11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(3) returned AOI_SHAPEFILE
11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(4) returned shapefile
11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(5) returned dummy
11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(6) returned dummy
11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(7) returned dummy
11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(8) returned seq
11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(9) returned null
11833 [main] INFO jdbc.resultset - 1. ResultSet.getString(10) returned N
11833 [main] INFO jdbc.resultset - 1. ResultSet.next() returned true
.............

export OW_DEFAULT_DISTRICT=OWSIDEAST

2. OW_ADMIN_UTILS_PW
You will need to set the value of this environment variable, if you change the password of OW_ADMIN_UTILS.

export OW_ADMIN_UTILS_PW=owadminutilspassword

The problem happen when we try to install as a user which its home directory is not mounted. We tried to set the HOME to other directory by setting up HOME environment variable. But, we got:
No module find error

Then we try to debug the installation by:
sh -x setup.bin
It come back with a lot of debug messages, and at the end we will see a line with:
CLASSPATH=/tmp/install.829388/jar/...
exec /tmp/install.829388/jre/bin/java ....

What we did is to manipulate the user home by
$export CLASSPATH=/tmp/install.829388/jar/...
/tmp/install.829388/jre/bin/java -Duser.home=/tmp/tmpdir ...
This way, we will force the installer to use different HOME directory

As a reminder to myself, the LD_ASSUME_KERNEL should be set as:
# Set the LD_ASSUME_KERNEL environment variable only for Red Hat 9,
# RHEL AS 3, and RHEL AS 4 !!
# Use the "Linuxthreads with floating stacks" implementation instead of NPTL:
export LD_ASSUME_KERNEL=2.4.1 # for RH 9 and RHEL AS 3
export LD_ASSUME_KERNEL=export LD_ASSUME_KERNEL=2.4.19 # for RHEL AS 4
Honestly, I don’t know why we have to set differently between RH9 & RHEL AS 3 vs RHEL AS 4. I’ll do it anyway.

As I read from the Red Hat Release Notes, it says:
export LD_ASSUME_KERNEL=2.4.19 — Linuxthreads with floating stacks
export LD_ASSUME_KERNEL=2.2.5 — Linuxthreads without floating stacks

Once we set the environment, we can check which thread library that active, we can use ‘getconf GNU_LIBPTHREAD_VERSION’ command as follow:
bash-3.00$ unset LD_ASSUME_KERNEL
bash-3.00$ getconf GNU_LIBPTHREAD_VERSION
NPTL 2.3.4
bash-3.00$ export LD_ASSUME_KERNEL=2.4.1
bash-3.00$ getconf GNU_LIBPTHREAD_VERSION
linuxthreads-0.10
bash-3.00$ export LD_ASSUME_KERNEL=2.4.19
bash-3.00$ getconf GNU_LIBPTHREAD_VERSION
linuxthreads-0.10
bash-3.00$ export LD_ASSUME_KERNEL=2.5.2
bash-3.00$ getconf GNU_LIBPTHREAD_VERSION
NPTL 2.3.4
bash-3.00$ unset LD_ASSUME_KERNEL
bash-3.00$ getconf GNU_LIBPTHREAD_VERSION
NPTL 2.3.4

Information about NPTL can be found in wikipedia.

The work around is to set IATEMPDIR environment to location that has sufficient space
$ export IATEMPDIR=/glb/apps/3rdparty_test/tmp

Before you run the script, you have to make sure that the following environment variable is populated correctly:
OWHOME
OWSYSSID
ORACLE_HOME
OW_HOME_DIR

From your linux shell, please run the following:
Bash$ ${OWHOME}/jre/bin/java \
-classpath ${OWHOME}/jar/com_lgc_ow_devkit.jar \
com.lgc.ow.credentials.OracleWallet \
${OWSYSSID} ${ORACLE_HOME} ${OW_HOME_DIR}

If it’s not exist, it will create ${HOME}/wallet directory with user and password entry. The password created by the script has to be equal as the user. If you have different password value, you’ll need to use the default OpenWorks user dialog.

Strange vs Normal interface

You can fix this strange interface by unset the environment:
unset GNOME_DESKTOP_SESSION_ID
then call your PowerExplorer startup script, and you will have your normal PowerExplorer interface.

Now, I’m trying to setup the RHEL 4.0 64-bit guest on top of it. There’s no issue when I install VMWare Server. But when I try to startup 64-bit guest, I encounter error message:

This CPU is VT-capable, but VT is not enabled (check your BIOS settings).
You have configured this virtual machine as a 64-bit guest operating system. However, this host’s CPU is not capable of running 64-bit virtual machines or this virtual machine has 64-bit support disabled.
For more detailed information, see http://www.vmware.com/info?id=152

I went to BIOS and enable the VT:
System Configuration > Device Configuration > Virtualization Technology = Enable
Then I rebooted the laptop, and the same error still come up.

Until, I found this website, then I power-off my laptop make sure everything is off. After couple of minutes, I started up the laptop, and the RHEL 64-bit can be started up!