Portal installation bug?
Hello,
We have installed the Portal server (JES 4) on a single host for evaluation; we used the graphical installer and selected the Portal Server (without the SRA), Directory Server, Administration Server and Application Server all in one session.
We chose to "configure now" and accepted all the defaults. The requirements check was OK, the instalation went OK and all the products in the post-installation review were "Installed".
However, when we tried to start the application server we couldn't; we found out that the domain directory in /var/opt/SUNWappserver/domains/domain1/ was not complete, and asadmin refused to start the domain.
The Directory and Administration servers run ok and the access manager DIT was created.
After this we uninstalled everything (there were problems because the uninstaller couldn't connect to the appserver) and installed the Application Server in one installer session, started it, and installed the rest in another session. Everything works ok now.
We haven't found this bug (?) in the release notes or the installation doc... Is this a known issue?
Our setup:
System Configuration: Sun Microsystems sun4u
Memory size: 2048 Megabytes
SUNW,Ultra-250
# uname -a
SunOS g-sie 5.9 Generic sun4u sparc SUNW,Ultra-250
# df -k
Filesystemkbytesusedavail capacity Mounted on
/dev/dsk/c0t8d0s032944868 7099494 2551592622%/
/proc 0000%/proc
mnttab 0000%/etc/mnttab
fd 0000%/dev/fd
swap236536840 23653281%/var/run
swap23674882160 23653281%/tmp
Thanks
