|
| |
| Sun Java System Portal Server 6 2004Q2 Migration Guide | |
Chapter 14
Upgrading Sun™ ONE Portal Server Software from Version 6.0 to Version 6.2This chapter provides an overview and discussion on how to upgrade your Sun™ ONE Portal Server system from the 6.0 software release to the 6.2 software release.
This chapter contains the following sections:
The Upgrade ProcessThe Sun ONE Portal Server 6.0 to 6.2 upgrade process involves the following high-level steps:
Installing Sun ONE Portal Server 6.2 SoftwareInstall the Sun ONE Portal Server 6.2 software using the Sun Java™ Enterprise System installer program located on the Sun Java™ Enterprise System media. For example, the Solaris SPARC version of the installer is located in /orion/s9orion/orion1of2_sparc.s9_orion/latest/Solaris_sparc directory.
- If you have not already done so, log in to the machine and become superuser.
You will need root access to install the Sun ONE Portal Server.
- Change directories to where the installer is located. For example,
cd /orion/s9orion/orion1of2_sparc.s9_orion/latest/Solaris_sparc
- If you used the su command to become root on your system, use the xhost command to grant access to your display. For example, use the following command to grant access to all users:
xhost +
- Type the following command to launch the installer:
./installer
- At the Welcome screen, click Next.
- Review the Software License Agreement and click Yes, Accept License to accept.
- Specify the appropriate language support for the system and click Next.
- On the Select Components tab, uncheck any previously checked boxes and check only the Sun ONE Portal Server 6.2 checkbox.
- A warning message displays indicating that the Sun ONE Portal Server requires the Sun ONE Application Server or Sun ONE Web Server be installed or that Sun ONE Portal Server be configured to an existing Web Container. Click Continue.
- On the Shared Component Upgrades Required panel, review the list of shared components that must be upgraded and click Next.
- Verify the target installation directories and click Next.
- If the Checking System Requirements panel indicates that any patches are needed, cancel the install and add any required patches. Otherwise, click Next to continue.
- On the Configuration Type Panel, select Minimal Configuration and click Next.
Note
You must install using the Minimal Configuration option to be able to restore the previous Portal Server configuration.
- On the Ready to Install panel, click Next.
- On the Installation Complete panel, select the appropriate button to view the Summary or the Install Log and click Close.
Restoring the Customized FilesThe Sun ONE Portal Server 6.2 software includes a script (postupgrade) that restores user modified templates from the Sun ONE Portal Server 6.0 installation. This script is located on the Sun Java™ Enterprise System media. For example, the Solaris SPARC version of this script is located in /orion/pointproducts/Solaris_sparc/Product/portal_svr/Tools directory. In addition to the running the postupgrade script, you must also verify some deployment information, deploy the Portal WAR file, and configure some security, login, and authentication information.
Perform the following steps to complete the upgrade process.
- Open the /etc/opt/SUNWps/PSConfig.properties file with a text editor and verify that it contains correct values for the following variables:
DEPLOY_DIR=
DEPLOY_DOCROOT=
DEPLOY_DOMAIN=For example, on systems deployed in the default directory of a Sun ONE Web Server installation, the settings for DEPLOY_DIR, and DEPLOY_DOCROOT would be
DEPLOY_DIR=/opt/SUNWwbsrvr
DEPLOY_DOCROOT=/opt/SUNWwbsrvr/docs- Type the following command to deploy the Portal WAR file
- Change directories to where the postupgrade script is located. For example,
cd /orion/pointproducts/Solaris_sparc/Product/portal_svr/Tools
- Type:
./postupgrade
- Update the Web Container’s classpath in web-container-install-root/instance-name/config/server.xml to include the portlet jar files: "/opt/SUNWps/lib/jdom.jar:/opt/SUNWps/lib/portlettl.jar:/opt/SUNWps/lib/portlet.jar:/opt/SUNWps/lib/portletcontainercommon.jar:/opt/SUNWps/lib/portletcommon.jar"
By updating the web container’s classpath to include the portlet jar files, you can avoid the following exception when restarting the web container.
- Run the restoremodfiles script to restore the 6.0 customized files that were backed up. For example, from the /orion/pointproducts/Solaris_sparc/Product/portal_svr/Tools directory, type:
./restoremodfiles
- When prompted, enter the Sun ONE Identity Server administration password.
- When prompted, enter the LDAP User password.
- Restart the web container.
For example, to start the web container on a Sun ONE Portal Server system using a Sun ONE Web Server on server sesta, do the following:
- Change directories to the directory containing the web server start and stop scripts.
cd /opt/SUNWwbsrvr/https-sesta
- Type the following commands to stop and start the web server.
./stop
./startTo start the web container on a Sun ONE Portal Server system using an application server as its web container, use the appropriate application server start command.
- Log in to the Sun ONE Identity Server Administration console.
- Select the Service Configuration tab.
- Select Core and then Organization Authentication Modules.
- Click Add Membership and then Save.
- From the Service Configuration tab, select Membership and specify amldapuser in the Password for Root User Bind.
- From the Service Configuration tab, select Authentication Configuration and specify the Default Success URL.
- Restart the web container.
You have now completed the upgrade process. Your Sun ONE Portal Server 6.2 system should be up and running with all of the previous existing data and customizations. You should access your Portal Desktop to verify that all the files have been upgraded successfully.
Localizing Online Help
After a successful upgrade, the channel help URLs will not have the locale in the URL. For example, the URLs will be similar to:
http://host/portal/docs/online_help/...
To localize the online help, update the display profile documents and provide the correct <ConditionalProperties> definition. For example, for the locale en_US use the <ConditionalProperties> definition to define the helpURL as:
<ConditionalProperties condition="locale" value="en">
<ConditionalProperties condition="locale" value="US">
<String name="helpURL"
value="online_help/user_help/desktop/desktopTOC.html"
advanced="true"/></ConditionalProperties>
</ConditionalProperties>
After defining the helpURL, the Desktop Channel Help URL will be similar to:
http://host/portal/docs/en_US/online_help/...
Upgrading Sun ONE Portal Server: Secure Remote Access PackTo complete the upgrade process for Sun ONE Portal Server: Secure Remote Access Pack installations, you need to do the following:
- Add a new key, gateway.logging.password in each of the /etc/opt/SUNWps/platform.conf. files with the value amService-srapGateway logging user’s password.
- Change the value of gateway.notification.url from /notification to notification.
- Add the netletproxy.port and rewriterproxy.port properties and set to the appropriate values specified for netletproxy and rewriterproxy.
- The following entries in the platform.conf file are backward compatible; however, they will default to the 6.0 behavior if not modified:
- gateway.favicon—Accepts the URL path to to which the Gateway will redirect requests for the favicon.ico file. Default is null.
- gateway.enable.customurl—Indicates that there is a reverse proxy in front of the gateway. Default is false.
- gateway.enable.accelerator—Indicates that there is SSL accelerator support on the gateway. Default is false.
- gateway.httpurl—Specifies the custom http URL to be used as the gatewayURL by the rewriter when gateway.enable.customurl is enabled.
- gateway.httpsurl—Specifies the custom https URL to be used as the gatewayURL by the rewriter when gateway.enable.customurl is enabled.
You have now completed the upgrade process. Your Sun ONE Portal Server: Secure Remote Access Pack 6.2 system should be up and running with all of the previous existing data and customizations.