When using WebSphere, you must perform the following steps:

• Prepare WebSphere install.
• Install Portal Server 7.0 software in Configure Later mode.
• Apply the patch.
• Configure the portal using psconfig utility.
• Perform the post patch installation instructions for 121913-01

Back to top

You must perform the following steps to make 121913-01 effective.

1. Restart the servers (CACAO and web container)
2. Run the doPatchUpdate script that is bundled with the patch.

• cd <PSINSTALLDIR>/SUNWportal/bin
• ./doPatchUpdate

• With Sun ONE Web Server as the web container:
  • cd /opt/SUNWwbsvr/bin/https/bin
  • ./wdeploy delete -u uri_path -i instance -v vs_id [ [-V verboseLevel] | [-q] ] [-n] hard|soft
  • ./wdeploy deploy -u uri_path -i instance -v vs_id [ [-V verboseLevel]| [-q] ] [-n] [-d directory] war_file
• With Sun ONE Application Server as the web container:
  • cd /opt/SUNWappserver/appserver/bin
  • ./asadmin undeploy --user ADMINUSER --host AS81HOST --port AS81PORT --target AS81INSTANCE DEPLOYURI
  • ./asadmin --user ADMINUSER --host AS81HOST --port AS81PORT --contextroot DEPLOY_WARPREFIX --target AS81INSTANCE warfile

• Perform the following steps for file sharing portletapp:
• cp -rf <PSINSTALLDIR>/SUNWportal/portletapps/filesharing/src/* /var/opt/SUNWportal/portals/<PORTALID>/portletapps/filesharing/src/.
• cd /var/opt/SUNWportal/portals/<PORTALID>/portletapps/filesharing
• export JAVA_HOME=/usr/jdk/entsys-j2se
• /usr/sfw/bin/ant customize
• <PSINSTALLDIR>/SUNWportal/bin/psadmin undeploy-portlet -u amadmin -f pwdfile -p <PORTALID> -g filesharing
• <PSINSTALLDIR>/SUNWportal/bin/psadmin deploy-portlet -u amadmin -f pwdfile -p <PORTALID> -g /var/opt/SUNWportal/portals/<PORTALID>/portletapps/filesharing/build/filesharing.war
• Follow the above procedure for the other portlet applications. The location of the various portletapps are listed below:
  • <PSINSTALLDIR>/SUNWportal/portletapps/sharedevents
  • <PSINSTALLDIR>/SUNWportal/portletapps/surveys
  • <PSINSTALLDIR>/SUNWportal/portletapps/sharedtasks
  • <PSINSTALLDIR>/SUNWportal/portletapps/rssportlet
  • <PSINSTALLDIR>/SUNWportal/portletapps/wiki

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.

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

The following section illustrates usage of the doPatchUpdate script:
bash-2.05# cd /space/PS/SUNWportal/bin

bash-2.05# ./doPatchUpdate
Have you restarted all your servers (CACAO, web container)?[y/n]
y
Making changes for 121913-01...

Please Enter Identity Server Super Administrator Password:
Again?

Mon Dec 12 00:26:43 PST 2005 Sun Java(tm) System Portal Server 7.0

Authentication Success ..
Finding the portals in the system ...
Commencing processing for portal portal1..

Redeploying community portlet ..
Please Enter the domain to deploy this portlet {'g' for global or give the exact dn 'o=Dev,dc=india,dc=sun,dc=com'}:
< comment > The value given here depends on domain the portlet is deployed on earlier or you want to deploy it now.
You could determine the level at which a particular portlet is deployed by browsing the DP of an org.
For more information, please read the Portal Server guide. </comment>
g
using -g ..

/space/PS/SUNWportal/bin/psadmin undeploy-portlet -u amadmin -f /space/PS/SUNWportal/bin/pwdfile -p portal1 -g communityportlets
/space/PS/SUNWportal/bin/psadmin deploy-portlet -u amadmin -f /space/PS/SUNWportal/bin/pwdfile -p portal1 -g /space/PS/SUNWportal/portlet/communityportlets.war
Done !

Redeploying wsssoportlet ..
Please Enter the domain to deploy this portlet {'g' for global or give the exact dn 'o=Dev,dc=india,dc=sun,dc=com'}:
< comment > The value given here depends on domain the portlet is deployed on earlier or you want to deploy it now.
You could determine the level at which a particular portlet is deployed by browsing the DP of an org.
For more information, please read the Portal Server guide. </comment>
o=DeveloperSample,dc=india,dc=sun,dc=com
using -d o=DeveloperSample,dc=india,dc=sun,dc=com..

/space/PS/SUNWportal/bin/psadmin undeploy-portlet -u amadmin -f /space/PS/SUNWportal/bin/pwdfile -p portal1 -d o=DeveloperSample,dc=india,dc=sun,dc=com wsssoportlet
/space/PS/SUNWportal/bin/psadmin deploy-portlet -u amadmin -f /space/PS/SUNWportal/bin/pwdfile -p portal1 -d o=DeveloperSample,dc=india,dc=sun,dc=com /space/PS/SUNWportal/portlet/wsssoportlet.war
Done !

Redeploying the portal war ..
/space/PS/SUNWportal/bin/psadmin redeploy -u amadmin -f /space/PS/SUNWportal/bin/pwdfile -p portal1
Done !

Modifying the parallel processing mode property in desktopconfig.properties ...
Done !

Completed processing for portal portal1..

Redeploying Search server search1
Completed patch update
Restart all your servers

Back to top

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

Back to top

The patch 121913-01 has the fix for this issue.
Note: If you have already customized the guessnumber portlet, take necessary precautions to preserve your customizations.

The fix is present in <PSINSTALLDIR>/SUNWportal/portlet/guessnumber.war

• Perform the following steps to redeploy guessnumber portlet :
• <PSINSTALLDIR>/SUNWportal/bin/psadmin undeploy-portlet -u amadmin -f pwdfile {g|-d "o=Dev,dc=sun,dc=com"i} guessnumber
• <PSINSTALLDIR>/SUNWportal/bin/psadmin deploy-portlet -u amadmin -f pwdfile {g|-d "o=Dev,dc=sun,dc=com"i} <PSINSTALLDIR>/SUNWportal/portlet/guessnumber.war

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-01 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-01 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

After patch 121913-01 has been backedout, you need to undo the changes done during your post patch installation.
doPatchUpdate comes with -r option which undoes the changes it performed during post patch installation.

Please do the following:

• cd <PSINSTALLDIR>/SUNWportal/bin
• ./doPatchUpdate -r

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