You must perform the following steps to complete the installation of patch 121913-03.

1. Restart the servers (CACAO and web container)
2. Run the psupdate utility.
   • cd <PSINSTALLDIR>/SUNWportal/bin
   • ./psupdate -a
     • Note: "psupdate -a" may perform all, some, or none of the update actions shipped with the patch, depending upon the exact details and patch history of the installation being updated.
     • See "psupdate" Utility for more information.
3. Restart all the servers (CACAO and web container)

Steps to restart the servers:

• Restart the CACAO Server :
  • /opt/SUNWcacao/bin/cacaoadm stop
  • /opt/SUNWcacao/bin/cacaoadm start
• Restart the web container:
  
  Sun ONE Web Server:
  • /opt/SUNWwbsvr/https-INSTANCE/stop
  • /opt/SUNWwbsvr/https-INSTANCE/start
  Sun ONE Application Server:
  • /opt/SUNWappserver/sbin/asadmin stop-domain --domain DOMAINNAME
  • /opt/SUNWappserver/sbin/asadmin start-domain --user admin

WebSphere Related Special Instructions

• Remove the jvm option java.util.logging.manager=com.sun.identity.log.LogManager from server.xml
• Increase the minimum and maximum heap size to 512M
• Need to restart WAS after above changes.

Back to top

You must perform the following steps to complete removal of patch 121913-03

1. Restart the servers (CACAO and web container)
2. Run the psupdate utility.
   • cd <PSINSTALLDIR>/SUNWportal/bin
   • ./psupdate -r
     • Note: "psupdate -r" may perform all, some, or none of the downgrade actions shipped with the patch, depending upon the exact details and patch history of the installation being downgraded.
     • Note: Following successful completion of all update actions related to the patch downgrade, the psupdate utility will either be removed, or changed to reference the most recent version remaining on the system, that was shipped with a previous Portal Server maintenance patch.
     • See "psupdate" Utility for more information.
3. Restart all the servers (CACAO and web container)

Back to top

Installations of Portal Server 7.0 using WebSphere must be performed in the following manner:

• Perform an appropriate WebSphere installation.
• Install Portal Server 7.0 software in Configure Later mode.
• Apply patch 121913-03.
• Configure the portal using the "psconfig" utility.
• Perform the post patch installation instructions for 121913-03.

Back to top

Add the following entry to /var/opt/SUNWportal/portals/<PORTALID>/desktop/classes/JSPTableContainerProviderJSP.properties
logout=Logout

Back to top

• Searching for a discussion throws desktop error on WebSphere. (# 6375526)

  • With WebSphere as the web container, searching for a discussion in the community sample throws a desktop error.
    121913-03 fixes this issue.

    For the fix to take effect, do the following:
    cp <PSINSTALLDIR>/SUNWportal/par-src/community_sample/pbfiles/templateBaseDir/community_sample/JSPDynamicSingleContainer/dynamicSingle.jsp /var/opt/SUNWportal/portals/<PORTALID>/desktop/community_sample/JSPDynamicSingleContainer/dynamicSingle.jsp
    

• Portal not accessible after redeployment on WebSphere. (# 6378407)

  • With WebSphere as web container, the portal webapp is not accessible after executing the "psadmin redeploy" command.
    To overcome this issue,

    • Goto the Websphere admin console
    • start the portal webapp

• Monitoring not working with Websphere version 5.1.1.5. (# 6376117)

  • The patch includes the fix for this issue. But if you have a portal instance created before applying the patch, perform the following workaround:

    • cd /var/opt/SUNWportal/portals/<PORTALID>/config/<INSTANCEID>
    • set the following properties in monitoring.properties files
      • com.sun.portal.monitoring.ConnectorContext.sasl.disable=true
      • com.sun.portal.monitoring.ConnectorContext.ssl.disable=true

• Logging on WebSphere 5.1 not functional. (# 6301159)

  • The logging functionality is not working for Portal Server hosted on WebSphere 5.1.
    Workaround:

    • Remove the following JVM options from the server configuration file:
      • -Djava.util.logging.manager=com.sun.identity.log.LogManager
      • -Djava.util.logging.config.class=com.sun.identity.log.s1is.LogConfigReader
    • Add the following JVM options as the *first two jvm entries* to the server configuration file:
      • -DLOG_COMPATMODE=Off
      • -Ds1is.java.util.logging.config.class=com.sun.identity.log.s1is.LogConfigReader

• Not able to configure producer on PS7.0 when WebSphere is the web container. (#6362385)
  Add the following jars to classpath in server configuration file:
  • /opt/SUNWportal/lib/endorsed/xalan.jar
  • /opt/SUNWportal/lib/endorsed/jaxp-api.jar
  • /opt/SUNWportal/lib/endorsed/sax.jar

Back to top

• The psadmin redeploy on Weblogic managed server throws exception in logs. (# 6374906)
  Workaround:
  • Login to admin console and undeploy the <portal_URI>.war
  • deploy the war file manually from the Weblogic admin console from
    /var/opt/SUNWportal/portals/<PORTALID>/war/<portal_URI>.war


• Deploying portlets on admin server requires deployment from admin console. (# 6338787)
  If psadmin deploy-portlet is executed, the portlet is not displayed on the desktop.
  Workaround:
  • The portlet war file has to be manually deployed from the admin console from the location
    /var/opt/SUNWportal/portals/<PORTALID>/war/<portlet_name>.war


• The command psadmin delete-portal does not clean up the startManagedWeblogic.sh script properly. (# 6376297)
  Workaround:
  • Clean the startManagedWeblogic.sh and startWeblogic.sh scripts manually.
• Not able to configure producer on PS7.0 when Weblogic is the web container. (# 6362963)
  Workaround:
  Add the following jars to classpath in the web container configuration file related to each portal in your system:
  • /opt/SUNWportal/lib/endorsed/xalan.jar
  • /opt/SUNWportal/lib/endorsed/jaxp-api.jar
  • /opt/SUNWportal/lib/endorsed/sax.jar

Back to top

Search data is not migrated from JES3 to PS7.0. In order to fix this issue, do the following:

• cd <PSINSTALLDIR>upgrade-resource
• ./update_search.sh <PS6.3.1 Portal instance directory> /var/opt/SUNWportal/searchservers/UpgradedSearch

Back to top

This patch 121913-03 introduces functionality to register/unregister portlets present in a EAR file.

Registration is the process by which Display Profile entries can be created for all portlet applications packaged in a EAR file, after the EAR file is deployed to the underlying Application Server. Unregistration is the process of removing Display Profile entries for all portlet applications packaged in a EAR file.

This feature will work only with ear files generated by JCAPS tools since the EAR files need to have Sun Portal proprietary artifacts inserted into them. For the end-to-end use case involving usage of this functionality, please refer to the JCAPS product documentation including the JCAPS Release Notes.

Description
Registers all all portlet applications packaged in a EAR file. This feature will work only with ear files generated by Java CAPS tools since the EAR files need to have Sun Portal proprietary artifacts inserted into them.

Syntax
Long Format
psadmin register-portlet --adminuser uid --passwordfile password-filename --dn dn | --global [--rolesfile roles-file] [--userinfofile user-info-file] --portal portal-ID portletearfile
Short Format
psadmin register-portlet -u uid -f passwordfile -d [-r roles-file] [-n user-info-file] -p portal-ID portletearfile

Options:
The following options are required:

• [--adminuser | -u] uid
  Specifies the administrator's distinguished name.
• [--dn | -d] dn
  Specifies the distinguished name in the LDAP node to access the display profile document. The -d or -g option is required.
• [--passwordfile | -f] password-filename
  Specifies the administrator's password in the password file.
• [--portal | -p] portal-ID
  Specifies the portal ID.

• [--global | -g]
  Specifies the global level node in LDAP to access the display profile document. The -d or -g option is required.
• [--rolesfile | -r] roles-file
  Specifies the file containing the Access Manager software and portlet application role mapping information.
• [--userinfofile | -n] user-info-file
  Specifies the file containing the user information mapping information.

• portletearfile
  Specifies the path to the EAR file.

Usage

psadmin register-portlet -u amadmin -f pfile -p portal1 -g /tmp/helloworld.ear

In the above example, all portlet applications in helloworld.ear are registered at the global level.

psadmin register-portlet -u amadmin -f pfile -p portal1 -d o=DeveloperSample,dc=sun,dc=com ?r /role.props /export/home/myejbapp.ear

In the above example, all portlet applications in myejbapp.ear are registered at the DeveloperSample node. A role mapping file is also specified.

Description
Unregisters all portlet applications packaged in a EAR file. This feature will work only for EAR files that have been already registered using the register-portlet command.

Syntax
Long Format
psadmin unregister-portlet --adminuser uid --passwordfile password-filename --dn dn | --global --portal portal-ID portletearapp
Short Format
psadmin register-portlet -u uid -f passwordfile -d -p portal-ID portletearapp

Options
The following options are required:

• [--adminuser | -u] uid
  Specifies the administrator's distinguished name.
• [--dn | -d] dn
  Specifies the distinguished name in the LDAP node to access the display profile document. The -d or -g option is required.
• [--passwordfile | -f] password-filename
  Specifies the administrator's password in the password file.
• [--portal | -p] portal-ID
  Specifies the portal ID.

• [--global | -g]
  Specifies the global level node in LDAP to access the display profile document. The -d or -g option is required.

• portletearapp
  Name of the EAR application that needs to be unregistered

Usage

psadmin unregister-portlet -u amadmin -f pfile -p portal1 -g helloworld

In the above example, all portlet applications that were packaged as a part of the helloworld.ear application are unregistered from the global level.

psadmin unregister-portlet -u amadmin -f pfile -p portal1 -d o=DeveloperSample,dc=sun,dc=com myejbapp

In the above example, all portlet applications that were packaged as a part of the myejbapp application are unregistered from the DeveloperSample node.

Back to top

You will need to adapt the following instructions to your particular installation if you have customized and deployed any of the following portlet applications:

• filesharing
• sharedevents
• surveys
• sharedtasks
• rssportlet
• wiki

These instructions are to be used only as a guideline. Depending upon which files you have customized, you may need to manually merge your customizations with the changes delivered by this patch.

These instructions use the "filesharing" portlet application as an example. Adjust to your particular situation.

To incorporate the fixes delivered by this patch into a customized portlet application, one would generally perform the following steps:

1. Copy the updated portlet application war file to the directory in which the portlet application is built. For example:
   • cp /opt/SUNWportal/portletapps/filesharing/src/filesharing.war.tokenized /var/opt/SUNWportal/portals/portal1/portletapps/filesharing/src/.
2. Copy/merge any remaining changes to the portlet application build directory, being careful to not destroy the "tokens.properties" file in the build directory.
3. Rebuild and redeploy the portlet application. For example:
   • cd /var/opt/SUNWportal/portals/portal1/portletapps/filesharing
   • export JAVA_HOME=/usr/jdk/entsys-j2se
   • /usr/sfw/bin/ant customize
   • /opt/SUNWportal/bin/psadmin undeploy-portlet -u amadmin -f pwdfile -p portal1 -g filesharing
   • /opt/SUNWportal/bin/psadmin deploy-portlet -u amadmin -f pwdfile -p portal1 -g build/filesharing.war

Back to top

• Online help is broken for NetFile. (# 6375496)
  Unable to access help files for NetFile when portal is deployed on Weblogic.
  


• Discussion appears as created by anonymous user when created in Weblogic and WebSphere. (# 6363127)
  When a discussion is created by a user whose "common name" is empty, then the discussion gets displayed as created by anonymous user


• The command patchadd on Solaris 10 gives some errors
  When you do a patchadd of the patch on Solaris 10, it displays some error messages related to pkginfo files. This is very specific to Solaris 10. Ignore these messages.
  Sample error messages:
  Cannot open pkginfo file /tmp/patch/121913-01/images/pkginfo
  Cannot open pkginfo file /tmp/patch/121913-01/css/pkginfo

Back to top

Description
The "psupdate" utility is used to complete changes related to the application or removal of Portal Server maintenance patches. The utility, with the appropriate options, must be run whenever a Portal Server maintenance patch is either applied or removed.

When the Portal Server maintenance patch is applied, a patch version specific copy of various update scripts, including psupdate, are copied into the Portal's "/var" directory. The following symlink:

<PSINSTALLDIR>/SUNWportal/bin/psupdate

is created and points at the current patch's version of "psupdate".

Syntax
psupdate -a | -r [-n] [-v] [-i] [-N]

Options:
One of the following must be specified:

• -a: Must be used whenever a Portal Server maintenance patch has been applied to a Portal installation. When invoked with this option, the utility will query the user for any information needed to complete the update, e.g., passwords, and will then apply only those update completion steps determined to be required by the present installation.
• -r: Must be used whenever a Portal Server maintenance patch has been removed from a Portal installation. When invoked with this option, the utility will query the user for any information needed to complete the update, e.g., passwords, and will then apply only those update completion steps determined to be required to remove the changes applied by the most recent invocation of "psupdate -a".
  • When "psupdate" in "remove mode" finishes its task, and if all downgrade operations competed successfully, the utility removes the symlink in the Portal's "bin" directory, and creates a symlink pointing to the "psupdate" utility belonging to the most recent version of a Portal Server maintenance patch remaining on the system (if any). In addition, the "/var" directory entry belonging to the maintenance patch that was just removed, is also deleted.

• -n: This option will cause the utility to display all operations determined to be required by invocation of either the "-a" or "-r" option, but will not actually perform the operations.
• -v: This option will cause the utility to display all operations as they are being performed.
• -i: Ordinarily, the psupdate utility will only complete a particular upgrade operation once. Once the upgrade of a particular component has completed successfully, successive invocations of the psupdate utility will not cause the upgrade for that component to be repeated. The "-i" option indicates that the utility should ignore the fact that update of a component may have completed successfully, and should repeat the update operation anyway.
• -N: The psupdate utility uses various temporary files to perform its tasks. Ordinarily, the utility removes these files upon exit. This option indicates that the utility should not delete these files upon exit.
  • WARNING: These temporary files may contain sensitive information, such as passwords. Use this option with care.

Back to top

This section illustrates the use of Rewriter Proxy on HTTP mode. By default, the Rewrtier Proxy runs on HTTPS mode.

Configuration change to run Rewriter Proxy on HTTP mode is listed below. If a node A runs Rewriter Proxy, then to set Rewriter Proxy on this node to HTTP, do the following :-

Log in to psconsole Navigate to Secure Remote Access -> Profile (select the desired profile(s) -> Deployment -> Rewriter proxy List Enter Rewriter Proxy host as http://A:10443 In Rewriter Proxy node's platform.conf.[instance-name] , please enter the following ... rewriterproxy.protocol=http Please repeat the above steps for all Gateway profiles and platfor.conf.[instance-name]s as needed. Restart the Rewriter Proxy and the Gateway.

Back to top