Features Overview

Features New to

Back to top

Pre-installation Considerations

In addition to the profile and flatfile changes listed in the Template Modifications Required section of the this document, there are also internal changes made that may directly affect how you use, test, or evaluate the product. Most of these behavioral changes tend to be directly related to the rewriter component, but there are other parts of the product that may be affected, as well. As such, it is important that this patch, as with any other, be test thoroughly on a development or QA system prior to being put in to production. Additionally, because of the nature of Portal 6x distribution and the customization requirements for the product, special attention should be given to JSP files that must be modified by the patch installer in order to fix defects, and/or for the product to continue functioning normally.

Back to top

Installation Information

These installation instructions provide steps to install For other document information about Sun Portal Server 6.3 software products, visit:

http://docs.sun.com/db/coll/PortalServer_04q21

http://www.sun.com/downloads

System Requirements

This section describes the system requirements for

System Requirements for Portal

Component Description Operating Environment updates Portal Server 6.3 software, and runs in the Solaris™ 8 and Solaris™ 9, and Red Hat® Advanced Server 2.1 operating environments. Memory Each Portal component should have a minimum of 1GB of main memory. This minimum requirement applies to proof of concepts (POCs), demo/test environments, and production systems alike. Other Patches The Solaris platform requires the 6.3Synch-up patch to be installed prior to installing These patches can be downloaded by logging in to sunsolve.sun.com using a contract ID and specifying the appropriate PatchID bellow using the SunSolve patch portal: Solaris_sparc requires patchID 118195-01 Solaris_x86 requires patchID 118195-01 No other Portal patches are required for the Linux platform.

Installation Overview

Please familiarize yourself completelly with the release notes prior to attempting either installation of, or upgrade to,

The following directories and files are included in :

1. ./
   .//prepatch
   .//postpatch
   .//prebackout
   .//postbackout
   .//README.
   .//.diPatch
   .//patchinfo
   .//SUNWpscp
   .//SUNWpscp/pkgmap
   .//SUNWpscp/pkginfo
   .//SUNWpscp/reloc
   .//SUNWpscp/reloc/SUNWps
   .//SUNWpscp/reloc/SUNWps/web-src
   .//SUNWpscp/reloc/SUNWps/web-src/WEB-INF
   .//SUNWpscp/reloc/SUNWps/web-src/WEB-INF/lib
   .//SUNWpscp/reloc/SUNWps/web-src/WEB-INF/lib/calendarprovider.jar
   .//SUNWpscp/install
   .//SUNWpscp/install/checkinstall
   .//SUNWpscp/install/copyright
   .//SUNWpscp/install/i.none
   .//SUNWpscp/install/patch_checkinstall
   .//SUNWpscp/install/patch_postinstall
   .//SUNWpscp/install/postinstall
   .//SUNWpscp/install/preinstall
   .//SUNWpsgw
   .//SUNWpsgw/pkgmap
   .//SUNWpsgw/pkginfo
   .//SUNWpsgw/reloc
   .//SUNWpsgw/reloc/SUNWps
   .//SUNWpsgw/reloc/SUNWps/lib
   .//SUNWpsgw/reloc/SUNWps/lib/gateway.jar
   .//SUNWpsgw/install
   .//SUNWpsgw/install/checkinstall
   .//SUNWpsgw/install/copyright
   .//SUNWpsgw/install/i.none
   .//SUNWpsgw/install/patch_checkinstall
   .//SUNWpsgw/install/patch_postinstall
   .//SUNWpsgw/install/postinstall
   .//SUNWpsgw/install/preinstall
   .//SUNWpsnl
   .//SUNWpsnl/pkgmap
   .//SUNWpsnl/pkginfo
   .//SUNWpsnl/reloc
   .//SUNWpsnl/reloc/SUNWps
   .//SUNWpsnl/reloc/SUNWps/web-src
   .//SUNWpsnl/reloc/SUNWps/web-src/netlet
   .//SUNWpsnl/reloc/SUNWps/web-src/netlet/netlet.cab
   .//SUNWpsnl/install
   .//SUNWpsnl/install/checkinstall
   .//SUNWpsnl/install/copyright
   .//SUNWpsnl/install/i.none
   .//SUNWpsnl/install/patch_checkinstall
   .//SUNWpsnl/install/patch_postinstall
   .//SUNWpsnl/install/postinstall
   .//SUNWpsnl/install/preinstall
   .//SUNWpsnlp
   .//SUNWpsnlp/pkgmap
   .//SUNWpsnlp/pkginfo
   .//SUNWpsnlp/reloc
   .//SUNWpsnlp/reloc/SUNWps
   .//SUNWpsnlp/reloc/SUNWps/lib
   .//SUNWpsnlp/reloc/SUNWps/lib/netletproxy.jar
   .//SUNWpsnlp/install
   .//SUNWpsnlp/install/checkinstall
   .//SUNWpsnlp/install/copyright
   .//SUNWpsnlp/install/i.none
   .//SUNWpsnlp/install/patch_checkinstall
   .//SUNWpsnlp/install/patch_postinstall
   .//SUNWpsnlp/install/postinstall
   .//SUNWpsnlp/install/preinstall
   .//SUNWpsrwp
   .//SUNWpsrwp/pkgmap
   .//SUNWpsrwp/pkginfo
   .//SUNWpsrwp/reloc
   .//SUNWpsrwp/reloc/SUNWps
   .//SUNWpsrwp/reloc/SUNWps/lib
   .//SUNWpsrwp/reloc/SUNWps/lib/gateway.jar
   .//SUNWpsrwp/install
   .//SUNWpsrwp/install/checkinstall
   .//SUNWpsrwp/install/copyright
   .//SUNWpsrwp/install/i.none
   .//SUNWpsrwp/install/patch_checkinstall
   .//SUNWpsrwp/install/patch_postinstall
   .//SUNWpsrwp/install/postinstall
   .//SUNWpsrwp/install/preinstall
   .//SUNWpssso
   .//SUNWpssso/pkgmap
   .//SUNWpssso/pkginfo
   .//SUNWpssso/reloc
   .//SUNWpssso/reloc/SUNWps
   .//SUNWpssso/reloc/SUNWps/web-src
   .//SUNWpssso/reloc/SUNWps/web-src/WEB-INF
   .//SUNWpssso/reloc/SUNWps/web-src/WEB-INF/lib
   .//SUNWpssso/reloc/SUNWps/web-src/WEB-INF/lib/ssoadapter.jar
   .//SUNWpssso/install
   .//SUNWpssso/install/checkinstall
   .//SUNWpssso/install/copyright
   .//SUNWpssso/install/i.none
   .//SUNWpssso/install/patch_checkinstall
   .//SUNWpssso/install/patch_postinstall
   .//SUNWpssso/install/postinstall
   .//SUNWpssso/install/preinstall
   .//SUNWpsdt
   .//SUNWpsdt/pkgmap
   .//SUNWpsdt/pkginfo
   .//SUNWpsdt/reloc
   .//SUNWpsdt/reloc/SUNWps
   .//SUNWpsdt/reloc/SUNWps/web-src
   .//SUNWpsdt/reloc/SUNWps/web-src/WEB-INF
   .//SUNWpsdt/reloc/SUNWps/web-src/WEB-INF/lib
   .//SUNWpsdt/reloc/SUNWps/web-src/WEB-INF/lib/desktop.jar
   .//SUNWpsdt/install
   .//SUNWpsdt/install/checkinstall
   .//SUNWpsdt/install/copyright
   .//SUNWpsdt/install/i.none
   .//SUNWpsdt/install/patch_checkinstall
   .//SUNWpsdt/install/patch_postinstall
   .//SUNWpsdt/install/postinstall
   .//SUNWpsdt/install/preinstall
   .//SUNWps
   .//SUNWps/pkgmap
   .//SUNWps/pkginfo
   .//SUNWps/reloc
   .//SUNWps/reloc/SUNWps
   .//SUNWps/reloc/SUNWps/sdk
   .//SUNWps/reloc/SUNWps/sdk/desktop
   .//SUNWps/reloc/SUNWps/sdk/desktop/desktopsdk.jar
   .//SUNWps/install
   .//SUNWps/install/checkinstall
   .//SUNWps/install/copyright
   .//SUNWps/install/i.none
   .//SUNWps/install/patch_checkinstall
   .//SUNWps/install/patch_postinstall
   .//SUNWps/install/postinstall
   .//SUNWps/install/preinstall
   .//css
   .//css/default.css
   .//images
   .//images/a.gif
   .//images/ar_lg_red_r_pad.gif
   .//images/ar_lg_yell_d_pad.gif
   .//images/ic_ar_up.gif
   .//images/logo_sun.gif
   .//images/tx_lg_products_services.gif
   .//images/tx_lg_support_training.gif
   .//rel_notes.html
   

Installing on the Solaris Sparc Platform

STEPS:

1. In a terminal window, become root.
2. Unzip the downloaded patch binary

# unzip

3. Be sure the server and platform nodes on which you are currently installing are up and running.
   The Following steps show the commands and output for the webcontainer included with the Sun Java™ System Web Server.

# root@ps-server: /var/opt/mps/serverroot/instance_name/start-slapd # root@ps-server: /etc/init.d/amserver start

stopping auth helpers ... done. starting auth helpers ... done.

# root@ps-server: cd <webserver_install_dir>/SUNWwbsvr/https-<instance_names> # root@ps-server: ./stop # root@ps-server: ./start

Sun ONE Web Server 6.1SP2 B04/07/2004 16:09 info: CORE3016: daemon is running as super-user info: HTTP3072: [LS ls1] http://ps-server.int.sun.com:80 ready to accept requests startup: server started successfully done.

4. Use the Solaris™ patchadd command to apply the patch.
   Output shown corresponds to patch application on the primary platform node.



# root@ps-server: patchadd

Checking installed patches... Executing prepatch script... Verifying sufficient filesystem capacity (dry run method)... Installing patch packages... Patch number has been successfully installed. See /var/sadm/patch//log for details Executing postpatch script... Checking for previous patch revisions... Making changes for ... Please Enter Identity Server Super Administrator Password: Again? Modifying the content Page value for IMProvider... Postpatch processing complete. Patch packages installed: SUNWps SUNWpscp SUNWpsdt SUNWpsgw SUNWpsnl SUNWpsnlp SUNWpsrwp SUNWpssso

5. Use the deploy command to deploy the new files.

Deploying to instance "ps-server.int.sun.com"...

# root@ps-server: <PS_INSTALL_DIR>/SUNWps/bin/deploy redeploy

6. Restart all the webcontainer instances.
   The following steps show the commands and output for webcontainer included with Sun Java™ Enterprise System Web Server.



# root@ps-server: cd <webserver_install_dir>/SUNWwbsvr/https-<instance_names> # root@ps-server: ./stop # root@ps-server: ./start

Sun ONE Web Server 6.1SP2 B04/07/2004 16:09 info: CORE3016: daemon is running as super-user info: HTTP3072: [LS ls1] http://ps-server.int.sun.com:80 ready to accept requests startup: server started successfully done.

7. Apply the patch using patchadd to other installed nodes on separate machines including any Portal proxies or Gateway nodes.

Installing on the Solaris Sparc x86 Platform

STEPS:

1. In a terminal window, become root.
2. Unzip the downloaded patch binary

# unzip

3. Be sure the server and platform nodes on which you are currently installing are up and running.
   The Following steps show the commands and output for the webcontainer included with the Sun Java™ System Web Server.

# root@ps-server: /var/opt/mps/serverroot/instance_name/start-slapd # root@ps-server: /etc/init.d/amserver start

stopping auth helpers ... done. starting auth helpers ... done.

# root@ps-server: cd <webserver_install_dir>/SUNWwbsvr/https-<instance_names> # root@ps-server: ./stop # root@ps-server: ./start

Sun ONE Web Server 6.1SP2 B04/07/2004 16:09 info: CORE3016: daemon is running as super-user info: HTTP3072: [LS ls1] http://ps-server.int.sun.com:80 ready to accept requests startup: server started successfully done.

4. Use the Solaris™ patchadd command to apply the patch.
   Output shown corresponds to patch application on the primary platform node.



# root@ps-server: patchadd

Checking installed patches... Executing prepatch script... Verifying sufficient filesystem capacity (dry run method)... Installing patch packages... Patch number has been successfully installed. See /var/sadm/patch//log for details Executing postpatch script... Checking for previous patch revisions... Making changes for ... Please Enter Identity Server Super Administrator Password: Again? Modifying the content Page value for IMProvider... Postpatch processing complete. Patch packages installed: SUNWps SUNWpscp SUNWpsdt SUNWpsgw SUNWpsnl SUNWpsnlp SUNWpsrwp SUNWpssso

5. Use the deploy command to deploy the new files.

Deploying to instance "ps-server.int.sun.com"...

# root@ps-server: <PS_INSTALL_DIR>/SUNWps/bin/deploy redeploy

6. Restart all the webcontainer instances.
   The following steps show the commands and output for webcontainer included with Sun Java™ Enterprise System Web Server.



# root@ps-server: cd <webserver_install_dir>/SUNWwbsvr/https-<instance_names> # root@ps-server: ./stop # root@ps-server: ./start

Sun ONE Web Server 6.1SP2 B04/07/2004 16:09 info: CORE3016: daemon is running as super-user info: HTTP3072: [LS ls1] http://ps-server.int.sun.com:80 ready to accept requests startup: server started successfully done.

7. Apply the patch using patchadd to other installed nodes on separate machines including any Portal proxies or Gateway nodes.

Installing on the Linux x86 Platform

STEPS:

1. In a terminal window, become root.
2. Unzip the downloaded patch binary

# unzip

3. Be sure the server and platform nodes on which you are currently installing are up and running.
   The Following steps show the commands and output for the webcontainer included with the Sun Java™ System Web Server.

# root@ps-server: /var/opt/mps/serverroot/instance_name/start-slapd # root@ps-server: /etc/init.d/amserver start

stopping auth helpers ... done. starting auth helpers ... done.

# root@ps-server: cd <webserver_install_dir>/SUNWwbsvr/https-<instances_names> # root@ps-server: ./stop # root@ps-server: ./start

Sun ONE Web Server 6.1SP2 B04/07/2004 16:09 info: CORE3016: daemon is running as super-user info: HTTP3072: [LS ls1] http://ps-server.int.sun.com:80 ready to accept requests startup: server started successfully done.

4. Use the update command included in the patch contents to freshen the installed Portal RPMs.
   Output shown corresponds to the update being run on the primary platform node.



# root@ps-server: ./update

Freshening sun-portal-calendarapi-6.3-7.1.i386.rpm... ########################################### [100%] ########################################### [100%] Freshening sun-portal-desktop-6.3-7.1.i386.rpm... ########################################### [100%] ########################################### [100%] Freshening sun-portal-gateway-6.3-7.1.i386.rpm... ########################################### [100%] ########################################### [100%] Freshening sun-portal-netlet-6.3-7.1.i386.rpm... ########################################### [100%] ########################################### [100%] Freshening sun-portal-netletproxy-6.3-7.1.i386.rpm... Freshening sun-portal-rewriterproxy-6.3-7.1.i386.rpm... Freshening sun-portal-sdk-6.3-7.1.i386.rpm... ########################################### [100%] ########################################### [100%] Freshening sun-portal-ssoadapter-6.3-7.1.i386.rpm... ########################################### [100%] ########################################### [100%]

5. Use the deploy command to deploy the new files.

Deploying to instance "ps-server.int.sun.com"...

# root@ps-server: <PS_INSTALL_DIR>/bin/deploy redeploy

6. Restart all the webcontainer instances.
   The following steps show the commands and output for webcontainer included with Sun Java™ Enterprise System Web Server.



# root@ps-server: cd <webserver_install_dir>/https-<instance_names> # root@ps-server: ./stop # root@ps-server: ./start

Sun ONE Web Server 6.1SP2 B04/07/2004 16:09 info: CORE3016: daemon is running as super-user info: HTTP3072: [LS ls1] http://ps-server.int.sun.com:80 ready to accept requests startup: server started successfully done.

7. Apply the patch using update command to other installed nodes on separate machines including any Portal proxies or Gateway nodes.

Back to top

 

Template Modifications Required

Every attempt is made by the patch installer to both preserve customized template information and automate the update of that information. However, since the contents of the files cannot be accurately predetermined, any modified template files are backed up in the same directory as their updated counterparts with the patch name postfixed to the template name. For example, when a patch is installed on the Solaris platform: /etc/opt/SUNWps/desktop/default/MyFrontPageTabPanelContainer \ /Netlet/display.template might be backed up to /etc/opt/SUNWps/desktop/default/MyFrontPageTabPanelContainer/ \ /Netlet/display.template.pre . The backup files are also copied back to their original location upon patch removal. To help avoid potential content-related customization problems, refer to the Tips for Customizing Templates section of this document. The following template files, .properties files, jsps, xml files, and platform files are modified by this patch consolidation:

Template and Flatfile Modifications Made by
Name	Component	Change
Solaris: /etc/opt/SUNWps/desktop/default/IMProvider/IMContent.jsp Linux: /etc/opt/sun/portal/desktop/default/IMProvider/IMContent.jsp	IMProvider	Modified the file because to set the current value of variable "src" from the "src_url" parameter
Template and Flatfile Modifications Made by Previous releases:
Name	Component	Change
N / A

Back to top

 

Tips for Customizing Templates

Because the Portal Server itself is so customizable, you should follow some precautions to insure that any customizations made to the Portal Server are preserved after a product upgrade. First, set up a customized template directory if you have not already done so. While this directory could be an entire subset of the default template directory, it is advisable to only copy over those template files that you will be customizing. This particular scheme would then use the default directory as a 'base' for all templates and would help insure that customized templates are not accidentally overwritten when the default templates are modified.

NOTE: Files in the default template directory should should never be customized.

To create a customized template directory:

Create a directory at the same level as the /etc/opt/SUNWps/desktop/default/ on Solaris, or /etc/opt/sun/portal/desktop/default on Linux, with a new name such as mytemplates. In that directory, only copy the templates you need to modify in their proper directories. The other templates will be retrieved as needed from the default directory using Portal's own filelookup mechanism. Edit the templates in the mytemplates directory according to your own preference. Log into the administration console. Select the appropriate services configuration screen. Fox example, select View: Services to administrate the desktop service globally. Alternately, select an organization, and then View: Services to administrate the desktop service for that organization only. Expand the link next to Desktop under the Portal Server Configuration subheading on the left view pane Modify the Desktop Type field located on the right view pane from default to mytemplates. Select Save

As a general rule of thumb, avoid modifying templates that have only a functional purpose rather than a look and feel purpose. One example of a template that should not need modifications is the NetletProvider/display.template . This template contains only JavaScript necessary for the launching of the Netlet. The contents of the Netlet Pop-up window should instead be customized by modifying the associated .properties file. The reason for this is that there could be a functional change in the product that would overwrite a customization done specifically to that particular template file. This example also exhibits why it is important to only keep customized files in the customized template directory.

Back to top

 

Checking the Current Product Install Level

and subsequent patch consolidations make changes to both the gateway, and version scripts necessary to print additional information about the current install level. In previous versions of Portal, this information had to be gathered from a variety of sources including the package versions, patchadd -p output, or from a flatfile that was not updated by patches themselves. Portal patches will now update the version files when they are installed and again when they are backed out.

To get the version information for the Gateway node, from node itself as root, type:

# /etc/init.d/gateway version
Fri May 7 18:45:51 PDT 2004
Mon Apr 26 14:38:05 PST 2004

To get the version information for the Portal Server node, from the node itself as root, type:

# <install_dir>/SUNWps/bin/version
Fri May 7 18:45:51 PDT 2004 Sun Java(tm) System Portal Server 6.3
Mon Apr 26 14:30:18 PST 2004

To get the version information for the Identity Server node, from the node itself as root, type:

# /etc/init.d/amserver version
Sun Java System Identity Server version 2004Q2

An RFE has been filed to modify the Identity Server version information to match that which is available in Portal Server. The First line of the version output contains the major version information that may also include the product build date. Each remaining line of output represents a patch that has been applied to the major version. The comma separated list in order includes the actual patchID (currently a Solaris patch ID), the patch name, and the patch install date. All of this information is important for supportability purposes and to help Portal administrators in product maintainance.

Back to top

 

Configuring the Network Socket Timeout Between the Gateway and the Netlet Proxy

This patch includes a new option to configure a fixed timeout for the network socket that is opened between the Gateway and Netlet Proxy if the Netlet Proxy is in use. This option was included to reduce socket depletion resulting from sockets on the Netlet Proxy node remaining indefinitely in an ESTABLISHED state.

For example, prior to this fix, if a Telnet session was opened via the Netlet and there was no activity for 2-4 minutes, the Telnet session would timeout as a result of the idle timout being reached. However, the socket opened between Gateway and Netlet Proxy would remain in an ESTABLISHED state. The same behavior would result from a user explicitly exiting the Telnet session as well.

The new option included with this patch gives portal administrators the ability to explicitly set a timeout for how long the abandoned socket should remain open. The default value of this timeout is 10 minutes. So, if there is no activity between the Gateway and Netlet Proxy socket for 10 minutes, the socket will be closed. If this value needs to be changed, an entry for gateway.netletproxy.socket.timeout can be added to the platform.conf file on the Gateway with the new value specifi ed in milliseconds.

Example:
To change the value to five minutes, the following step should be performed on the Gateway instance(s) which require modification.

1. Change directory to /etc/opt/SUNWps on a Solaris machine, or /etc/opt/sun on a Linux machine
2. Backup the platform.conf.<gateway_instance> file; where gateway_instance is the instance you want to configure this option for.
3. Edit the platform.conf.<gateway_instance> file and add the following entry:
   
   gateway.netletproxy.socket.timeout=300000
   
   
4. Restart the gateway Instance

NOTE: If the socket timeout is set too high, the socket depletion could be significant enough to cause Netlet connections to hang.

Back to top

 

Configuring Portal Server to Work with a Load Balancer that Performs SSL Termination

Some links on the Portal Server Desktop are generated using the configured port/host/protocol values. If a load balancer sitting in front of the Portal Server has been configured to perform SSL termination, there will be a protocol mismatch, and some links created on the desktop will be broken. To resolve this problem, an additional entry, called lbProtocol needs to be added to the desktopconfig.properties file located at /etc/opt/SUNWps/desktop/desktopconfig.properties on a Solaris machine and at /etc/opt/sun/portal/desktop/desktopconfig.properties on Linux.

Example:
If the load balancer is performing SSL termination, it's protocol will be https so the new property entry will look like:

lbProtocol=https

Back to top