Sun and OracleChannel SunHow to BuyLog InEspañol

Sun Java System Portal Server 7 Installation Guide
  Buscar sólo este libro
Buscar Ayuda
Contained Within
Find More Documentation
Featured Support Resources
 Descargar este libro en PDF (531 KB)

Chapter 7 Upgrading to Sun Java System Portal Server 7

This chapter contains the following:

Pre-Upgrade Requirements

This section includes the following:

Hardware and Operating System Requirements

The following hardware and software are required to upgrade from Portal Server 6 2005Q1 software on Solaris to this release.

Table 7–1 Hardware and Operating System Requirements for Upgrade

Component 

Platform Requirements 

Supported Platforms  

Sun UltraTM 60, or Sun Blade, or better workstation or server

Operating System 

Solaris 8 or Solaris 9 U6 or Solaris 10 on SPARC Solaris 9 or Solaris 10 on x86 Red Hat Enterprise Linux 2.1 or 3.0 Updated 3 on x86 

RAM 

1024 Mbytes of RAM for evaluation install 

1.2 Gbytes of RAM for regular deployment on Sun Java System Web Server 

2.0 Gbytes of RAM for regular deployment on Sun Java System Application ServerSun Java system Application Server 

Disk space 

1 Gbyte of disk space for Portal Server software and associated applications 

Swap Space 

The swap space of the machine should be twice the amount of physical memory. For example, if the machine has 2.0 Gbytes of RAM, the swap space should be 4.0 Gbytes. 

Software Requirements

Note –

The stack components must be upgraded to their respective Java Enterprise System 4 versions prior to executing the psupgrade script.

The Portal Server software requires the following stack components:

  • Sun Java System Directory Server 5.2 P4

  • Sun Java System Access Manager 7 installed in legacy mode.

    Note –

    Apply the Access Manger 7.0 Patch 1 before or after the Portal Server Installation. Apply this patch for all web containers including BEA WebLogic, or IBM WebSphere. The patch number depends on the operating system.

    • For Sparc, use patch 120954-01

    • For Linux, use 120956-01

    • For x86, use 120955-01

  • Sun Java System Web Server 6.1 SP5 or Sun Java System Application Server 8.1 (including the patches).

The sun-soarsdk rpm (registry server SDK rpm) is not re-locatable; so, do not choose non-default locations for registry on Linux.

Note –

Sun Java System Portal Server 7 software does not support Sun Java System Access Manager 7 installed in realm mode. Access Manager must be installed in legacy mode before installing Portal Server 7 software.

Web Containers

Portal Server 7 software supports the following web containers:

Java Enterprise System Application Server 8.1 

Java Enterprise System Web Server 6.1 

BEA Weblogic Server 8.1 sp2 

BEA Weblogic Server 8.1 sp4 

IBM Websphere Server 5.1 

Sun Java System Access Manager Software

Portal Server software can be upgraded on machines with:

Access Manager software previously installed and configured on the same physical machine using Java Enterprise System 3. 

Access Manager software previously installed and configured on a separate machine using Java Enterprise System 3. The Java Enterprise System 3 Access Manager software SDK must be installed on the Portal Server software host. 

Java Enterprise System 3 Access Manager software SDK installed on the machine were Portal Server Gateway is previously installed. 

Before You Begin

Before upgrading to Portal Server 7 software on the Solaris platform, perform the following pre-upgrade steps:

  1. Verify that the web container and web container Admin Server are running.

  2. Verify that the following values are set:

    • ANT_HOME is set to a valid Ant installation path.

    • JAVA_HOME is set to a Java Development Kit (JDK) v1.4.2 or higher.

    • AM and AM SDK are at the Java Enterprise System Release 4 level.

  3. On Solaris, after Access Manager upgrade to Java Enterprise System 4, verify that the revision of SUNWamsdkconfig is 7.0 by issuing the command pkginfo -x SUNWamsdkconfig. If value is not set to 7.0, edit file /var/sadm/pkg/SUNWamsdkconfig/pkginfo file. Set the version as 7.0 (VERSION=7.0,...). Reset to the original value after upgrade.

  4. If you upgrade the gateway, the Netlet Proxy, or the Rewriter Proxy, verify that these components are stopped before starting the upgrade.

  5. On a node on which Portal Server is not installed—that is, the gateway, Netlet Proxy, or Rewriter Proxy only node—edit PortalServer6.3.1-base/lib/SRAversion.properties. Change the line with productversion= to with version=. Reset to the original value after the upgrade.

  6. See to perform an upgrade on a gateway-only node.

Instructions to Upgrade and Verify Upgrade

This section contains the following:

ProcedimientoTo Upgrade to Portal Server 7 Software on Solaris

  1. Go to the directory where you have downloaded the software and unzip the Portal Server zip file.

  2. Go to Product/portal_svr/Tools/upgrade/bin directory and type ./psupgrade.

    The upgrade script requires you to provide the following:

    • Access Manager server administrator's password.

    • Access Manager ldapuser password

    • Directory Server Directory Manager password.

    • Web container administrator's password.

    • Web container Master Password in case of Application Server 8.1 for Portal Server software installation.

    • Secure remote access certificate database password if Secure Remote Access was previously installed on this machine.

    • Secure Remote Access log user password if Secure Remote Access or its constituents were previously installed on this machine.

    When you upgrade, the upgraded Portal Server installation is located at PortalServer6.3.1-base/SUNWportal directory, where PortalServer6.3.1-base is the name of the directory in which the Java Enterprise System 3 Portal Server was installed.

  3. Restart the Portal Server web container and Gateway (if Gateway was installed and upgraded).

  4. If you performed an upgrade on Application Server 8.1, do the following:

    • Remove any line breaks in the server classpath value.

    • Remove the classpath entry corresponding to jss3.jar.

  5. If you performed an upgrade on Web Server 6.1, do the following after Access Manager upgrade and before starting Portal Server upgrade:

    • Edit Web Server's server.xml file.

    • Modify classpathsuffix entry jss3.jar to jss4.jar.

    • Add PortalServer6.3.1-base/lib/ to serverclasspath.

    • Add PortalServer6.3.1-base/lib/ to nativelibraryprefix.

ProcedimientoTo Upgrade to Portal Server 7 Software on Linux

  1. Go to the directory where you have downloaded the software and unzip the software file.

  2. Go to Product/portal_svr/Tools/upgrade/bin directory and type ./psupgrade.

    The upgrade script requires you to provide the following:

    • Access Manager server administrator's password.

    • Access Manager ldapuser password

    • Directory Server Directory Manager password.

    • Web container administrator's password.

    • Web container Master Password in case of Application Server 8.1 for Portal Server software installation.

    • Secure Remote Access certificate database password if Secure Remote Access was previously installed on this machine.

    • Secure Remote Access log user password if Secure Remote Access or its constituents were previously installed on this machine.

  3. Restart the Portal Server web container and Gateway (if you installed and upgraded the gateway).

  4. If you performed an upgrade on Application Server 8.1, do the following:

    • Remove any line breaks in the server classpath value.

    • Remove the classpath entry corresponding to jss3.jar.

  5. If you performed an upgrade on Web Server 6.1, do the following after Access Manager upgrade and before starting Portal Server upgrade:

    • Edit Web Server's server.xml file.

    • Modify classpathsuffix entry jss3.jar to jss4.jar.

    • Add PortalServer6.3.1-base/lib/ to serverclasspath.

    • Add PortalServer6.3.1-base/lib/ to nativelibraryprefix.

  6. Install sun-mobileaccess rpms from the installer after the upgrade if they are missing. Use the following command to see if the sun-mobileaccess rpms are missing:

    rpm -qa | grep sun-mobileaccess

ProcedimientoTo Upgrade A Gateway-Only Node

  1. Install Directory server from the Java Enterprise System stack.

  2. Perform the following:

    1. cd to Product/portal_svr/Tools/upgrade/resource/jes3

    2. Issue the following command:

      /usr/jdk/entsys-j2se/bin/jar --xf upgraderesource.jar upgrade.xml

    3. Edit the upgrade.xml file.

      After the line:

      <replace file="${PS_70_PRODUCT_DIR}/lib/ServiceLDIFMap.properties" 
token="psWSRPConsumer2.ldif" value=""/>

      Include the following two lines in the upgrade.xml file. 

      <replace file="${PS_70_PRODUCT_DIR}/template/PortalDomainConfig.properties"  
token="domain.data.host=" value="GATEWAY_HOST_NAME"/>
      <replace file="${PS_70_PRODUCT_DIR}/template/PortalDomainConfig.properties"  
token="domain.data.port=" value="LOCAL_DIRECTORY_SERVER_PORT"/>

    4. Modify the following lines:

      Change <target name="fetchGlobalDP" > to <target name="fetchGlobalDP" if="PORTAL_INSTALLED">

      Change <target name="fetchOrgDP" > to <target name="fetchOrgDP" if="PORTAL_INSTALLED">

      Change <target name="uploadGlobalDP" > to <target name="uploadGlobalDP" if="PORTAL_INSTALLED">

      Change <target name="uploadOrgDP" > to <target name="uploadOrgDP" if="PORTAL_INSTALLED">

    5. Issue the following command:

      /usr/jdk/entsys-j2se/bin/jar -uf upgraderesource.jar upgrade.xml

  3. Copy the security folder from /etc/opt/SUNWcacao/security from the Portal Server machine to the Gateway machine.

  4. Start Directory Server.

  5. Start the cacao server.

  6. Run the command ./psupgrade.

    A failure occurs. You can ignore.

  7. Copy the psconfig file from /var/tmp/pconfigupgradeXXXXXxml to /tmp/psconfig.xml.

  8. Replace the following unreplaced tokens in the psconfig.xml file:

    • JAVA_BASE_DIR. For example, use /usr/jdk/entsys-j2se.

    • HOSTNAME.DOMAIN:PORTNO

    • mydomain.com with the gateway domain

  9. Run the command /opt/SUNWportal/bin/psconfig --config /tmp/psconfig.xml

  10. Restart the web container.

ProcedimientoTo Ensure Upgrade to Portal Server 7 was Successful

  1. Access the Access Manager software administration console from your browser. To access, type http://hostname/amconsole.

  2. Access the Portal Server Desktop. To access, type protocol://fully-qualified-hostname:port/portal-URI.

    If the sample Portal desktop displays without any exception, then your upgrade was successful. Try logging in as a user to ensure that the sample Portal desktop displays without errors.

  3. Access the Portal Server software administration console. To access, type protocol://fully-qualified-hostname:port/psconsole.

    Verify that it displays information about Portal Server7 software. Ensure that a Portal with portal-id Upgraded is created.