Here are my notes on installing Sun Java System Portal Server 7 2005Q4
I downloaded the software from Sun’s download site using Sun Download Manager, which automatically validated and extracted the software bundle. I uploaded the installable binary to a server that meet the installation requirements and in a clean/ready to install state. The notes below start at the point where I prepare the binary as root:
1. The zip bundle does not preserve the execute permission on the binary. So, I had to tweak them. Here are the commands:
chmod 755 <PS_INSTALL_DIR>/Solaris_x86/installer chmod 755 <PS_INSTALL_DIR>/Solaris_x86/.install/j2se_jre/bin/*
3. Click “Next” on the welcome screen and click “Yes, Accept License >”
4. Select Sun Java(TM) System Portal Server 7 2005Q4
5. Expand Sun Java(TM) System Portal Server Secure Remote Access 7 2005Q4
6. Select Secure Remote Access Core
In case you want to install Gateway, Netlet Proxy, or Rewriter Proxy in the future, you should be able to do so if you already have Secure Remote Access Core installed. If you don’t do this option, you will see a warning message after step 6. Ignore the warning if at that point if you see one.
5. Select Sun Java(Tm) System Web Server 6.1 2005Q4
6. Select Sun Java(TM) System Administration Server 5 2005Q4 and click”Next”
7. Keep the default directory configuration, which are listed below:
Directory Preparation Tool:
8. Click “Next” on “Verify System Requirements” page.
9. Keep “Configure Now” and click “Next”.
10. On “Common Server Settings” page, the installer automatically fills host name, DNS domain name, IP, admin ID, System User, and System Group. If this isn’t the case, enter the appropriate values for these parameters for your environment. Enter a password and click “Next”
11. On “Web Server: Administration (1/2)” page, you should not need to change any of the pre-filled values. Click “Next”. Note what port value Web Server administration port runs on. For me, it was 8888.
12. Again, leave configuration values on default values for “Web Server: Default Web Server instance (2 of 2)” and click “Next”.
13. For “Directory Server: Administration (1 of 5)” page, leave default values and click “Next”.
Note that the installer use the first password you supplied for rest of the configuration, when possible.
14. On “Directory Server: Server Settings (2 of 5)” page, leave default values and click “Next”.
15. Keep “Store configuration data on this server” on “Directory Server: Configuration Directory Server (3/5)” and click “Next”
16. Keep “Store user data and group data on this server” on “Directory Server: Data Storage Location (4/5)” and click “Next”
17. Depending on your preference to have sample organizational structure and data or not, choose the check marks. For my installation, I chose to include sample organizational structure and data. Click “Next”
18. Enter a new password for amldapuser account. Keep install type in Legacy Mode and click “Next”
19. Keep Sun Java System Web Server as the Web Container for Access Manager and click “Next”
20. Keep the default values for “Access Manager: Sun Java System Web Server (3 of 6)” page if you do not want to enable Secure Server Instance Port/SSL. I left the page with default values. Click “Next”.
21. Leave everything as-is and click “Next”
22. Again, leave the default values and click “Next”
23. Since I was creating a new setup, I left the default value “No” for “Is Directory Server provisioned with user data?” question. Click “Next”.
24. Keep Sun Java System Web Server as the Web Container for Portal Server and click “Next”
25. If you dont’ need Secure Server Instance Port (SSL), then leave the default values and click “Next”.
26. Leave the default deployment configuration and click “Next”.
Note that the Deployment URL is /portal on port 80.
27. Leave the default Gateway configuration and click “Next”.
28. On “Administration Server: Server Settings (1 of 2)” page, leave default configuration and click “Next”.
29. Leave the default Directory setting for Administration Server and click “Next”.
30. You should see an installation summary. If everything looks good, click “Next”.
31. Click “Install” to install the software.
Note that you have the option not to open the registration window during installation.
32. If you observe installation failed error, look at the installation log at /var/sadm/install/logs.
33. To start the software for the first time:
/usr/sbin/directoryserver -useversion 5.2 start-admin /usr/sbin/directoryserver -useversion 5.2 start /usr/lib/cacao/bin/cacaoadm start /opt/SUNWwbsvr/https-<SERVER_DOMAIN_NAME>/start
34. Check the following logs for errors:
/var/opt/SUNWportal/logs/config/portal.fabric*.log /var/opt/SUNWportal/logs/admin/portal.0.0.log /opt/SUNWwbsvr/https-<SERVER_DOMAIN_NAME>/logs/errors
Thanks to Sidharth M. for pointing out the locations of the log files and the dependency on cacao.