test

Sun Java System Portal Server 7.1 Update 1 Release Notes

Upgrade

For upgrade issues, refer to the Upgrade Issues in Sun Java Enterprise System 5 Release Notes for UNIX and Sun Java Enterprise System 5 Upgrade Guide for UNIX.


When you upgrade Portal Server 7.0 to Portal Server 7.1 Update 1, jdbc/WikiDB fails. So that Wiki portlets do not function. (#6536212)

Solution:

Do the following:

  1. Log in to administration console of the web container.

  2. Click on the Resources link.

  3. Click on the JDBC link.

  4. Create a connection pool for Wiki, for example, WikiDBPool.


     --Datasource Classname--org.apache.derby.jdbc.ClientDataSource
--Resources Type--javax.sql.ConnectionPoolDataSource
--serverName--Name of the server where derby is running
--portNumber---1527
--Password--portal
--user---portal
--databaseName---wikidb_portal1

  5. Create a JDBC resource, jdbc/WikiDB, for this connection pool.


Filesharing does not work after you upgrade Portal Server 7.0 to Portal Server 7.1 Update 1. (#6550408)

Solution:

Do the following:

  1. Change the directory to the Filesharing portlet location.

    /var/opt/SUNWportal/portals/portal1/portletapps/filesharing/

  2. Create an XML file, for example, update.xml.

  3. Copy and paste the following to the XML file.


    <project name="File Sharing Database Update for 7.0 to 7.1 " 
							default="update" basedir=".">
<target name="update">
      	<property file="build/conf/common.dbadmin"/>
      	<!-- Performs the Sql Tasks -->
      	<sql
            onerror="continue"        
	    delimiter="${sql.delimiter}"
	    delimitertype="${sql.delimiter.type}"
      	    driver="${db.driver}"
      	    url="${db.url}"
      	    userid="${db.user}"
      	    password="${db.password}"
      	    classpath="${db.driver.classpath}">
	    <transaction>
	    create table newfilesystem(
  repositoryId varchar(255) not null,
  directory varchar(255) not null,
  name varchar(255) not null,
  isDir smallint not null,
  creator varchar(255) not null,
  created bigint not null,
  modified bigint not null,
  datasize int not null,
  data blob(5000000),
  primary key(repositoryId,directory,name)
);

	    </transaction>
	    <transaction>
	    rename table filesystem to oldfilesystem;

	    </transaction>
	    <transaction>
	    rename table newfilesystem to filesystem;

	    </transaction>
	    <transaction>
	    insert into filesystem (repositoryId,directory,name,isDir,creator, 
				created,modified,datasize,data)
select repositoryId,directory,name,isDir,creator,created,modified,
				size as datasize,data from oldfilesystem;
	    </transaction>
       </sql>
   </target>

</project>

  4. Run the following ant script.

    ant -f update.xml


After upgrading Portal Server 7.1 to Portal Server 7.1 Update 1, the Search Provider and the Discussion Provider JSPs are not updated automatically. (#6534282)

Solution:

Do the following:

  1. Copy the Discussion provider JSP templates.

    cp PortalServer-base/par-src/default-portal/pbfiles/templateBaseDir/default /DiscussionProvider/*.jsp /var/opt/SUNWportal/portals/portal1/desktop/default/DiscussionProvider

  2. Copy the Search provider JSP templates.

    PortalServer-base/par-src/default-portal/pbfiles/templateBaseDir/default /SearchProvider/*.jsp /var/opt/SUNWportal/portals/portal1/desktop/default/SearchProvider


When you upgrade Java ES 4 to Java ES 5, the search migration fails. (#6440906)

Solution:

Do the following:

  1. Before running the psugrade script, open the Java ES 4 search.conf file.

    The search.conf file is located in the /var/opt/SUNWps/https-server/portal/config directory.

  2. In the search.conf file, change libdir="/opt/SUNWps/lib" to libdir="/opt/SUNWps.bak/lib:/opt/SUNWps/lib".

    where /opt/SUNWps is the Java ES 4 installation directory.

  3. Run the psupgrade script.

After the upgrade, some of the customization made to the search server configuration are not migrated to the UpgradeSearch. For the migration that is not handled by psugrade, manual carry over from upgraded Portal Server 6.3.1 is needed. These operations should be performed after stopping all search related processes, such as search webapp, robot, rdregister, autoclassify, and profiler.

  1. Copy the following files to the upgraded search server directory:


    cp $SRC/config/taxonomy.rdm $DEST/config
cp $SRC/config/filterrules.conf $DEST/config
cp $SRC/config/import.conf $DEST/config
cp $SRC/config/classification.conf $DEST/config
cp $SRC/config/schema.rdm $DEST/config

    where SRC is the path to the old search server directory and DEST is the path to the new upgraded search server directory.

  2. Depending on what was customized in Portal Server 6.3x, do the following:

    • For Robot, use the Portal Server 7.1 administration console's robot/properties to reconfigure the robot.conf's parameter such as proxy and authentication. Use the Portal Server 7.1 administration console's robot/filter to update the robot filter properties with the customization done on Portal Server 6.3.1's /var/opt/SUNWps.bak/server/portal/config/filter.conf file.

    • For federated search databases, refer to the Portal Server 7.1 configuration guide for more information on how to set up Federated Search.

  3. Restart the search server web container and search related processes.