Features Overview

Features New to

Back to top

Pre-installation Considerations

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.

Some manual changes are needed to complete the fixes done by this patch. These changes needs to be done after the patch installation. Please refer to section 6, 7 and 8 from the Table of Contents to see what is needed in your environment.

Linux revision of this patch updates the "rpms" using "--repackage" option for the "rpm" command. This option is suppose to keep a copy of original rpms before upgrading to new one and original rpms can be restored from that copy. Linux revision of this patch ships a a script remove which can be used to restore orginal rpms. It is similar to patchrm on solaris. However for now, this script doesn't work if the portal is installed in a non default location because of bugs in rpm utility itself. This script has been tested on RedHat version AS 2.1 with rpm version 4.0.4. Other versions may see different issues when using this script to restore the original rpms. If the script fails with errors and the rpms are not restored, original rpms will have to be manually install. After installing the original rpms "remove" script needs to be executed again to ensure that postbackout changes are complete.

Back to top

Installation Information

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

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

http://www.sun.com/downloads

1. 1. For New customers of Portal Server 6.3.1, patch needs to be applied after completing Portal Server 6.3.1 installation.
2. 2. For existing Portal Server 6.3 customers, who are upgrading to Portal Server 6.3.1, patch must be applied after installing the new packages for PortalServer 6.3.1 but before running the upgrade scripts, upgradePS04Q205Q1 or upgradeSRA-04Q4-05Q1. New packages are installed using different patches for different platforms. Please refer to Portal Server Upgrade Docum ent HERE for more information on installing new packages.

Access Manager upgrade is required before upgrading Portal Server

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.

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
   .//rel_notes.html
   .//SUNWps
   .//SUNWpscfg
   .//SUNWpsdt
   .//SUNWpsgw
   .//SUNWpsma
   .//SUNWpsmas
   .//SUNWpssp
   .//css
   .//images
   

Installing on the Solaris Sparc Platform

STEPS:

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

# unzip

3. 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 ... Postpatch processing complete. Patch packages installed: SUNWps SUNWpscfg SUNWpsdt SUNWpsgw SUNWpsma SUNWpsmas SUNWpssp

4. 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

5. 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.1SP4 B12/16/2004 11:42 info: CORE3016: daemon is running as super-user info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_01] from [Sun Microsystems Inc.] info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/amconsole] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/amserver] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/ampassword] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/amcommon] info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/portletsamples] info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/portal] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/search] info: JAXRPCSERVLET12: JAX-RPC context listener initializing info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[RewriterServlet@24191379]: The servlet "RewriterServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[GatewayConsoleServlet@10436245]: The servlet "GatewayConsoleServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[ProxyletAdminServlet@24742184]: The servlet "ProxyletAdminServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[AMBaseServlet@7974034]: The servlet "AMBaseServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[SMServlet@27525999]: The servlet "SMServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[NetletAdminServlet@19426064]: The servlet "NetletAdminServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[NetFileConsoleServlet@8662644]: The servlet "NetFileConsoleServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[UMServlet@21046486]: The servlet "UMServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: HTTP3072: [LS ls1] http://saleen.red.iplanet.com:80 ready to accept requests startup: server started successfully

6. 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. 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 ... Postpatch processing complete. Patch packages installed: SUNWps SUNWpscfg SUNWpsdt SUNWpsgw SUNWpsma SUNWpsmas SUNWpssp

4. 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

5. 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.1SP4 B12/16/2004 11:42 info: CORE3016: daemon is running as super-user info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_01] from [Sun Microsystems Inc.] info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/amconsole] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/amserver] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/ampassword] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/amcommon] info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/portletsamples] info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/portal] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/search] info: JAXRPCSERVLET12: JAX-RPC context listener initializing info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[RewriterServlet@24191379]: The servlet "RewriterServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[GatewayConsoleServlet@10436245]: The servlet "GatewayConsoleServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[ProxyletAdminServlet@24742184]: The servlet "ProxyletAdminServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[AMBaseServlet@7974034]: The servlet "AMBaseServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[SMServlet@27525999]: The servlet "SMServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[NetletAdminServlet@19426064]: The servlet "NetletAdminServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[NetFileConsoleServlet@8662644]: The servlet "NetFileConsoleServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[UMServlet@21046486]: The servlet "UMServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: HTTP3072: [LS ls1] http://saleen.red.iplanet.com:80 ready to accept requests startup: server started successfully

6. 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

NOTE:
Installing this patch creates a directory /var/spool/backup/ .
DO NOT REMOVE this directory. It is needed for backingup the patch with original files.
DO NOT REMOVE this directory even after removing the patch if you will be installing this patch version again on the system.

STEPS:

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

# unzip

3. 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

PrePatch Processing .... sun-portal-configurator-6.3-25 Updating sun-portal-configurator-6.3-25.1.i386.rpm .... Preparing... ########################################### [100%] Wrote: /var/spool/backup/118952-01/sun-portal-configurator-6.3-25.i386.rpm 1:sun-portal-configurator########################################### [100%] sun-portal-core-6.3-25 Updating sun-portal-core-6.3-25.1.i386.rpm .... Preparing... ########################################### [100%] Wrote: /var/spool/backup/118952-01/sun-portal-core-6.3-25.i386.rpm 1:sun-portal-core ########################################### [100%] sun-portal-desktop-6.3-25 Updating sun-portal-desktop-6.3-25.1.i386.rpm .... Preparing... ########################################### [100%] Wrote: /var/spool/backup/118952-01/sun-portal-desktop-6.3-25.i386.rpm 1:sun-portal-desktop ########################################### [100%] sun-portal-gateway-6.3-25 Updating sun-portal-gateway-6.3-25.1.i386.rpm .... Preparing... ########################################### [100%] Wrote: /var/spool/backup/118952-01/sun-portal-gateway-6.3-25.1.i386.rpm 1:sun-portal-gateway ########################################### [100%] sun-portal-mobileaccess-6.3-25 Updating sun-portal-mobileaccess-6.3-25.1.i386.rpm .... Preparing... ########################################### [100%] Wrote: /var/spool/backup/118952-01/sun-portal-mobileaccess-6.3-25.i386.rpm 1:sun-portal-mobileaccess########################################### [100%] sun-portal-mobileaccess-6.3-25.1 Updating sun-portal-mobileaccess-config-6.3-25.1.i386.rpm .... Preparing... ########################################### [100%] Wrote: /var/spool/backup/118952-01/sun-portal-mobileaccess-config-6.3-25.i386.rpm 1:sun-portal-mobileaccess########################################### [100%] sun-portal-sample-6.3-25 Updating sun-portal-sample-6.3-25.1.i386.rpm .... Preparing... ########################################### [100%] Wrote: /var/spool/backup/118952-01/sun-portal-sample-6.3-25.i386.rpm 1:sun-portal-sample ########################################### [100%] Making changes for 118952-01...

4. 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

5. 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.1SP4 B12/16/2004 11:42 info: CORE3016: daemon is running as super-user info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_01] from [Sun Microsystems Inc.] info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/amconsole] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/amserver] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/ampassword] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/amcommon] info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/portletsamples] info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/portal] warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding info: WEB0100: Loading web module in virtual server [https-saleen.red.iplanet.com] at [/search] info: JAXRPCSERVLET12: JAX-RPC context listener initializing info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[RewriterServlet@24191379]: The servlet "RewriterServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[GatewayConsoleServlet@10436245]: The servlet "GatewayConsoleServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[ProxyletAdminServlet@24742184]: The servlet "ProxyletAdminServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[AMBaseServlet@7974034]: The servlet "AMBaseServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[SMServlet@27525999]: The servlet "SMServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[NetletAdminServlet@19426064]: The servlet "NetletAdminServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[NetFileConsoleServlet@8662644]: The servlet "NetFileConsoleServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: WEB2798: [/portal] ServletContext.log(): [WARNING] Servlet[UMServlet@21046486]: The servlet "UMServlet" is NOT enforcing strict session timeouts. Be sure to turn on strict session timeout handling or implement the onSessionTimeout() event before putting this application into production. info: HTTP3072: [LS ls1] http://saleen.red.iplanet.com:80 ready to accept requests startup: server started successfully

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

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 consolidatiions 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:

# cat <PS_INSTALL_DIR>/SUNWps/lib/SRAversion.properties
productname=Sun Java(tm) System Portal Server Secure Remote Access
productversion=6.3.1
build=Thu Dec 16 03:30:34 PST 2004
copyright=PROPRIETARY/CONFIDENTIAL. Use of this product is subject to license terms. Copyright 2003 Sun Microsystems, Inc. All rights reserved.
patch= Thu Feb 3 15:14:46 PST 2005

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

# cat <ps_install_dir>/SUNWps/lib/PSversion.properties
productname=Sun Java(tm) System Portal Server
productversion=6.3.1
build=Thu Dec 16 03:30:34 PST 2004
copyright=PROPRIETARY/CONFIDENTIAL. Use of this product is subject to license terms.\nCop yright 2003 Sun Microsystems, Inc. All rights reserved.
patch= Thu Feb 3 15:14:46 PST 2005

Back to top

 

Customizing "amtune" to use "perftune"

For this release, perftune has been changed to use amtune. Unfortunately there are some problems with amtune which require patches from the Access Manager team for amtune to work effectively. The patchids for fixes for amtune for solaris_sparc, solaris_x86 platforms are 119259-01 and 119260-01 respectively. For solaris_sparc this can also be fixed by applying the following workaround to amtune. Please follow the steps below to customize amtune to work properly with perftune after installing the Required Patch.
NOTE:
(In each step substitute your actual base path if you did not choose the default during installation.)

1. Edit /opt/SUNWam/bin/amtune/amtune-as8.
   Find the line:
   $ECHO $ASADMIN_PASSWORD > $ASADMIN_PASSFILE
   and change it to:
   $ECHO "ASADMIN_PASSWORD=$ASADMIN_PASSWORD" > $ASADMIN_PASSFILE
   
2. Edit /opt/SUNWam/bin/amtune/amtune-env.
   Find the line:
   ASADMIN=$CONTAINER_BASE_DIR/bin/asadmin
   and change it to:
   ASADMIN=/opt/SUNWappserver/appserver/bin/asadmin
   

Back to top

 

Completing the Changes Required for Rebranding

This patch adds a new gif file which is required for rebranding of Portal Server. Along with the new gif file, two more changes are required to complete the rebranding, which can be done using amconsole. After installing the patch, Please follow the steps below to complete the process.

1. Change dp-org.xml to have the right background color.
   
   1. Access the amconsole
   2. For default org select the services drop down menu
   3. Select 'Portal Desktop'
   4. In the right panel select 'Edit xml directly'
   5. In the xml file, change the 'brandImage2BgColor' attribute to white (#ffffff) from yellow (#FBE249)
   6. Click on OK and then Save


2. Change dp-providers.xml to have the right version.
   
   1. Access the amconsole
   2. Select Service Configuration tab.
   3. Select Portal Desktop in the left pane.
   4. Click on 'Edit XML Directly' on the right side.
   5. Search for 2004Q2 and replace it with 2005Q1 in all the instances for productName.
   6. Click on 'Identity Management' tab.
   7. Select Portal Desktop in the left pane.
   8. Click on 'Edit XML Directly' on the right side.
   9. Search for 2004Q2 and replace it with 2005Q1 in all the instances for productName.

Back to top

 

Completing the Changes Required for Proxylet Service After Upgrade

This Patch fixes the problem where the proxylet service window on admin console does not show the link to invoke proxylet rules after upgrade. This happens only when portal server is upgraded from portal server 6.3 to portal server 6.3.1. It does not happen on new portal server 6.3.1 install. After the patch has been applied and the upgrade scripts have been executed one more steps needs to be done to have the default values show up in the proxylet service page on admin console. Follow the steps below to complete the fix.

1. Login to admin console .
2. For default org select services from the drop down list called "view" .
3. Delete the Proxylet service from the list of services by selecting the proxylet service from the list of services and click on "delete" button.
4. Add the Proxylet service again by clicking an "Add" button, selecting the proxylet service in right hand frame and clicking okay.

Back to top