The other day, I was trying to finish up an install for someone, and ran into a problem. I couldn’t get psadmin to create a new PIA domain. Finally, thanks to OTN, I found that I had to have JRockit JDK set as the Java environment for WebLogic. Note that this was to create the domain not just start the domain.
Logs
If there was one thing I could change about this whole thing, it would the logs. I spent so long on this issue just because I had no clues. We have got to have more logs to look at for clues! If am missing something, please comment below and point it out. If not, Oracle, please add some logging — at least maybe print out what JVM it is using.
This is the first log file that I found: <PS_CFG_HOME>/webserv/piainstall_<domain name>.log
Install Action : CREATE_NEW_DOMAIN Creating Domain... Deploying Web Applications... Deploying WebLogic Extension files... Deploying PeopleSoft Site files... Deploying PeopleSoft Site Doc files... Completed. PS_CFG_HOME: /psoft/pscfgs/fnprd PIA_INSTALL_FAIL
This is the second log: /tmp/piaInatallLog_<timestamp>
Install Action : CREATE_NEW_DOMAIN Creating Domain... Deploying Web Applications... Deploying WebLogic Extension files... Deploying PeopleSoft Site files... Deploying PeopleSoft Site Doc files... Completed.
Also, in <PS_CFG_HOME>, I found the wlspiainstall.properties which included all of the settings that it was using to create the domain.
Avoiding the Error
The best way to avoid this error is to make sure that you set the JAVA_HOME to your JRockit installation before installing WebLogic. So, assuming that you have JRockit installed at /opt/jdk, you can run something like this:
export JAVA_HOME=/opt/jdk export PATH=$JAVA_HOME/bin:$PATH which java java -version
Your output should look something like this:
$export JAVA_HOME=/opt/jdk $export PATH=$JAVA_HOME/bin:$PATH $which java /opt/jdk/bin/java $java -version java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Oracle JRockit(R) (build R28.1.0-123-138454-1.6.0_20-20101014-1350-linux-x86_64, compiled mode)
If it looks like this, you have something wrong. This is open source OpenJDK JVM:
$which java /usr/bin/java $java -version java version "1.7.0_03" OpenJDK Runtime Environment (IcedTea7 2.1.1pre) (7~u3-2.1.1~pre1-1ubuntu3) OpenJDK 64-Bit Server VM (build 22.0-b10, mixed mode)
Or, this is the Sun JDK, which caused me problems:
$java -version java version "1.5.0_30" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_30-b03) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_30-b03, mixed mode)
Now, once you have that correct, you should run the Weblogic install from that command-line session.
Fixing the Problem
Now, my problem was that Weblogic had already been installed. Apparently, it was using the Sun JDK instead of the JRockit JDK. Normally, I would look in the <PS_CFG_HOME>/webserv/<domain>/bin/setcmd…. file to change the setting. But, I don’t even have the domain installed at this point.
I found that I could set the JAVA_HOME and JAVA_VENDOR variables in the <weblogic home>/wlserver_10.3/common/bin/commEnv.sh file. Note that the JAVA_VENDOR was required. If it is not set, some of the logic later on in the script overwrites the JAVA_HOME.
So, I added these two lines near the top between the comments:
# #***************************************************************************** JAVA_HOME=/opt/jdk JAVA_VENDOR=Oracle #***************************************************************************** # sub functions #*****************************************************************************
After that, my PIA built with no problem.
ULOG{date}.log – BEATuxedoLog
Weblogic.log – PS_HOMEwebservdomainlogs