hostname issues

I am still fighting with Portal Express installation. Now, I have changed my strategy and trying to install as silent with responsefile.

-silent
-G licenseAccepted="true"
-W setupTypePanel.selectedSetupTypeId="full"
-W globalInstall.location="/opt/IBM/WebSphere"
-W wasPanel.installChoice="install"

################################################################################
#
# EXISTING WEBSPHERE APPLICATION SERVER INSTALLATION LOCATION
#
# Description: This is the value of the existing WebSphere Application Server
# if you selected to install on an existing instance.
#
# Be sure to follow the convention for specifying path information on your
# platform. For example,
#
# Windows: C:\WebSphere\AppServer
# AIX: /usr/WebSphere/AppServer
# Linux: /opt/WebSphere/AppServer
# Solaris: /opt/WebSphere/AppServer
# iSeries ND: /QIBM/ProdData/WebSphere/AppServer/V7/ND
# iSeries Base: /QIBM/ProdData/WebSphere/AppServer/V7/Base
################################################################################

# -W wasListPanel.existingWasLocation=""

################################################################################
#
# OPTIONAL:
# UNDETECTED WEBSPHERE APPLICATION SERVER INSTALLATION LOCATION (NON-ISERIES)
#
# Description: Sometimes the Portal install program cannot detect an existing
# WebSphere Application Server(WAS). You cannot know this until install runtime
# when the silent install fails because the value of the above parameter
# wasListPanel.existingWasLocation cannot be validated.
#
# When this error occurs, and you are certain that there is a valid WAS at the
# location specified above, uncomment this parameter and enter the same value
# specified above.
#
# Be sure to follow the convention for specifying path information on your
# platform. For example,
#
# Windows: C:\WebSphere\AppServer
# AIX: /usr/WebSphere/AppServer
# Linux: /opt/WebSphere/AppServer
# Solaris: /opt/WebSphere/AppServer
#
################################################################################

# -W was.undetectedWas="/opt/IBM/WebSphere/AppServer"

and so on.
Now, as the responsefile expected, I have installed AppServer. I just wanted run and check, so called startServer.sh server1, to my surprise, it failed.
Stacktrace -
SystemErr R com.ibm.ws.exception.ConfigurationError:javax.naming.ConfigurationException: Cannot get canonical host name for server.

serverindex.xnl has hostname="null".
This is because -
Portal Server expected localhost.localdomain.com as hostname to localhost.localdomain.

I reverted /etc/hosts back to localhost.localdomain
and I have typed in hostname="localhost" in serverindex.xml.
Server started successfully.

Now, to kick start the PortalExpress, I am a kinda stuck, because, portal expects hostname as localhost.localdomain.com.
Portal cannot work with hostname as "localhost.localdomain.com", AppServer cannot run with host name *localhost.localdomain.com*. What a DEADLOCK!!!!!

build failed again

Well!! n-th run, build failed again with same message as posted here - http://javagongura.blogspot.com/2009/11/build-failed-on-line-3121.html

After this step. installation aborts.
Checked the App Server installation log, it was a successful installation.
Though its a failed installation, I tried to start the app server services.
I found some *amazing* things in startServer.log -
[11/25/09 22:31:28:005 EST] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[11/25/09 22:31:28:157 EST] 0000000a AdminTool A ADMU0128I: Starting tool with the wp_profile profile
[11/25/09 22:31:28:159 EST] 0000000a AdminTool A ADMU3100I: Reading configuration for server: WebSphere_Portal
[11/25/09 22:31:32:605 EST] 0000000a WsServerLaunc E ADMU3002E: Exception attempting to process server WebSphere_Portal
[11/25/09 22:31:32:607 EST] 0000000a WsServerLaunc E ADMU3007E: Exception com.ibm.ws.process.exception.InvalidExecutableException: PROC0004E: Executable: [/opt/XYZWEBSPHEREXYZ/AppServer/java/bin/java] does not appear to be a valid executable. Process could not be created.
at com.ibm.ws.process.UnixProcessImpl.create(UnixProcessImpl.java:159)
at com.ibm.ws.process.ProcessFactory.create(ProcessFactory.java:69)
at com.ibm.ws.management.launcher.ProcessLauncher.launch(ProcessLauncher.java:70)
at com.ibm.ws.management.launcher.LaunchCommand.launchProcess(LaunchCommand.java:246)
at com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.java:309)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:264)
at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:120)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:263)

This line in the above stack trace *Executable: [/opt/XYZWEBSPHEREXYZ/AppServer/java/bin/java] does not appear to be a valid executable. Process could not be created.* amazed me.
Why startServer is trying to look for java in /opt/XYZWEBSPHEREXYZ/AppServer/java/bin/java?

So, I have created folder structure like /opt/XYZWEBSPHEREXYZ/AppServer/java/bin/ and created a softlink to original appserver/java/bin/java.
But, its looking for remaining binaries in the same location.
So, need to create softlink for the entiar installation under /opt/XYZWEBSPHEREXYZ/AppServer/

Lets see...
BTW - Found a technote on this -
http://www-01.ibm.com/support/docview.wss?uid=swg21202564
The technote mentions that, because its a broken installation, you get such an error.

unzip

On linux (RHEL),
to unzip a zip file,
unzip file.zip
To unzip to a specific folder -
unzip file.zip -d /path-to-destination

BUILD FAILED on line 3121

(Nov 23, 2009 1:56:17 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: BUILD FAILED
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/PortalServer/exp_inst/wp.config/config/includes/wp.config_cfg.xml:46: The following error occurred while executing this line:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/AppServer/profiles/wp_profile/ConfigEngine/config/actions/db_cfg_mgr.xml:277: The following error occurred while executing this line:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/PortalServer/base/wp.db.impl/config/includes/wp.db.impl_cfg.xml:95: The following error occurred while executing this line:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/PortalServer/base/wp.db.impl/config/includes/wp.db.impl_cfg.xml:337: ERROR: Error during the execution of the sql files.
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: Total time: 38 seconds
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut:
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction, msg2, Return code = 1
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction, msg2, Executing command: completed
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction, msg2, Completed install step: Please wait while the WebSphere Portal Express database is initialized.
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ScanFileAction, msg1, fileName=/software/IBM/WebSphere/PortalExpress/AppServer/profiles/wp_profile/ConfigEngine/log/ConfigTrace.log
(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ScanFileAction, msg1, Found text BUILD FAILED on line 3121
(Nov 23, 2009 1:57:06 PM), PortalExpress.install, com.ibm.wps.install.SwingPopUp, err, Logged message: EJPIC0017E: Portal installation failed. The Portal configuration step completed with errors. Please refer to the log file /software/IBM/WebSphere/PortalExpress/PortalServer/log/wpinstalllog.txt for additional information. The installer will now exit.
(Nov 23, 2009 1:57:06 PM), PortalExpress.install, com.ibm.wps.install.SwingPopUp, msg2, Exiting installer.
What to do?


Follow Up - http://www-01.ibm.com/support/docview.wss?uid=swg21291586

EJPIC0229E

My DB2Express installation on Linux is failing with the above error - EJPIC0229E: The DB2 Express installation step failed.

Just above to this log entry -
error while loading shared libraries: libstdc++.so.5: cannot pen shared object file: No such file or directory.


Follow up -
Found this technote http://www-01.ibm.com/support/docview.wss?rcss=faqtt_1Q09&uid=swg21297575


Follow up -
As mentioned in the above technote, I have downloaded and installed compat-libstdc++-33-3.2.3-61.i386.rpm. I got this from http://rpm.pbone.net/index.php3/stat/4/idpl/3416184/com/compat-libstdc++-33-3.2.3-61.i386.rpm.html_.
DB2Express successfully installed.

Now!! PortalExpress process get past Db2 hickup and installing WAS. Lets see what happens.

EJPIC0067E

I am installing PortalExpress v 6.1.0.0 on RHEL 5.2 on my laptop.

Some tips -
Run install.sh -console

You may encounter EJPIC0067E error.
EJPIC0067E: {0} requires a fully-qualified host name that is recognized by the DNS server. Short host names, loopback addresses, IP addresses and illegal characters such as blanks are not allowed. Enter the host name again.
Explanation: This installation requires a fully-qualified host name. Short host names, loopback addresses, and IP addresses are not allowed.
User Response: Enter the host name again.

To resolve this -
Just check the complete name of your box
uname -a
for me it is
localhost.localdomain
Now -
vi /etc/hosts as root
edit localhost.localdomain to localhost.localdomain.com