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

Profile Creation, New in 6.1

In 6.0 - To create a profile one can call AppServerPath/bin/ProfileCreator/pctSolaris.bin command or wasprofile.sh command.

Ex.,
./wasprofile.sh -create -profileName bladetcb6profile -profilePath /usr/IBM/WebSphere/AppServer/profiles/bladetcb6profile -templatePath /usr/WebSphere/AppServer -profileTemplates/default -nodeName bladetcb6node -cellName bladetcb6Cell -hostName bladetcb6.rtp.raleigh.ibm.com

Or you can kick this process thru firststeps.

In 6.1, wasprofile.sh command is available too but it is depricated. Instead you have manageprofil.sh command.
ex.,
manageprofiles.sh -create
-profileName shasti
-profilePath /shasti/WebSphere
-templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/dmgr
-cellName cell1
-hostName planetaix
-nodeName dmgr1

64 bit or 32 bit JVM?

How to know your WAS version is 32 bit or 64 bit?
This is a machine which has WAS 64 bit
$ ./java -d64 -version
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_06-erdist-20060404 20060511)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_06-erdist-20060404, mixed mode)
IBM Java ORB build orb50-20060511a (SR2)
XML build XSLT4J Java 2.7.4
XML build IBM JAXP 1.3.5
XML build XML4J 4.4.5

This is a machine which has WAS 32bit
$ ./java -d64 -version
execv(): No such file or directory
Error trying to exec /software/opt/IBM/WebSphere/AppServer/java/jre/bin/sparcv9/java.
Check if file exists and permissions are set correctly.
Failed to start a 64-bit JVM process from a 32-bit JVM.
Verify all necessary J2SE components have been installed.
(Solaris SPARC 64-bit components must be installed after 32-bit components.)

So acid Test is -
goto App Server javahome
/path/to/washome/java/jre/bin
./java -d64 -version

if it is 64 bit, it returns with version info.
otherwise returns with no such file or directory.

Symbolic links

Sometimes, in the process of WebSphere, IHS Administration, it may require you to create symbolic links. This is the procedure.

ln is the command to create symbolic links.
$man ln
User Commands ln

NAME
ln - make hard or symbolic links to files

SYNOPSIS
/usr/bin/ln [-fns] source_file [target]

/usr/bin/ln [-fns] source_file... target

/usr/xpg4/bin/ln [-fs] source_file [target]

/usr/xpg4/bin/ln [-fs] source_file... target

DESCRIPTION
In the first synopsis form, the ln utility creates a new
directory entry (link) for the file specified by
source_file, at the destination path specified by target. If
target is not specified, the link is made in the current
directory. This first synopsis form is assumed when the
final operand does not name an existing directory; if more
than two operands are specified and the final is not an
existing directory, an error will result.

In the second synopsis form, the ln utility creates a new
directory entry for each file specified by a source_file
operand, at a destination path in the existing directory
named by target.
..............................


Example -
Developers wanted to have a look at SystemOut.log and SystemErr.log. They dont have uid on the box. So, I need to create a web link to this through HTTP Server.
I did like this.
I have created a document root called logs.
/logs
I created symbolic links to SystemOut.log and SystemErr.log like this
ln -s source destination
This creates a softlink *from* a file to a *file*
$ln -s /path/to/appserver/profiles/profilename/logs/servername/SystemOut.log SystemOut.log
$ln -s /path/to/appserver/profiles/profilename/logs/servername/SystemErr.log SystemErr.log
This created me two files SystemOut.log and SystemErr.log under /logs
if I ls -ltr on /logs, I get this list
SystemOut.log -> /path/to/appserver/profiles/profilename/logs/servername/SystemOut.log
SystemErr.log -> /path/to/appserver/profiles/profilename/logs/servername/SystemErr.log

Now, I have created a html file, say, index.html with hyperlinks like this -
Server Logs
< A HREF="SystemOut.log">SystemOut< / A>< br />
< A HREF="SystemErr.log">SystemErr< / A>

While using df

Solaris
df -h is the command to display available disk free space in bytes
e.g.,
$df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d84 3.9G 136M 3.8G 4% /var
swap 6.6G 992K 6.6G 1% /tmp
/dev/md/dsk/d101 20G 7.8G 12G 41% /software

Equivalent df in AIX
df -g

Solaris df, du, ls commands

Solaris df command

New df, du, and ls Options

The df, du, and ls commands have a new h option for displaying disk usage and file or file system sizes that are easy to understand.

The default form of the df command displays file system size in blocks (512 bytes). The df output, in kilobytes, follows:

$ df -k / /usr
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 192056 94788 78063 55% /
/dev/dsk/c0t0d0s6 1982988 829966 1093533 44% /usr

The same file system sizes displayed in powers of 1024 follows:

$ df -h / /usr
Filesystem size used avail capacity Mounted on
/dev/dsk/c0t0d0s0 188M 93M 76M 55% /
/dev/dsk/c0t0d0s6 1.9G 811M 1.0G 44% /usr

The default form of the du command displays disk space in blocks (512 bytes). The du output, in blocks, follows:

% du -s k*
100 kadmin
98 kadmin.local
98 kdb5_util
90 keyserv
10 killall

The same disk space displayed in powers of 1024 follows:

% du -h k*
50K kadmin
49K kadmin.local
49K kdb5_util
45K keyserv
5K killall

The default form of the ls -l command displays file size in bytes. Use the ls -lh command to display file size in powers of 1024:

% ls -lh k
-r-xr-xr-x 1 root bin 49K Nov 30 03:32 kadmin
-r-xr-xr-x 1 root bin 49K Nov 30 03:32 kadmin.local
-r-xr-xr-x 1 root bin 49K Nov 30 03:32 kdb5_util
-r-xr-xr-x 1 root sys 44K Nov 25 04:37 keyserv
-r-xr-xr-x 1 root bin 4.3K Nov 25 04:36 killall