+

Search Tips   |   Advanced Search

Update an existing PAA file

Overview

When a new version is available, we can update an existing Portal Application Archive (PAA) file using the install-paa-update task.

PAA file developer note: Make all updates in the custom code. No code generation is available for an upgrade through the regular install-paa task.

The install-paa-update command creates a backup of the current PAA file in...

    WP_PROFILE/paa/backup

The command then completes the following actions:

  • Uninstalls the PAA file from IBM WebSphere Portal
  • Deletes the content from the expanded PAA file
  • Installs the new version of the PAA file

After running install-paa-update, deploy the changes to the system.


Update existing PAA file

Cluster note: Complete these steps on the primary node and then on all additional nodes.

  1. Run...

      cd WP_PROFILE/ConfigEngine
      ./ConfigEngine.sh install-paa-update -DappName=assemblyName -DWasPassword=foo -DPortalAdminPwd=foo

    ...which creates file...

      WP_PROFILE/paa/paa_filename/component.properties

    To control the behavior of the installed WCM libraries set parameter

      -Dwcmdetect=true

  2. Edit...

      WP_PROFILE/paa/paa_filename/component.properties

    Check for and resolve conflicts with previously installed components...

    1. Parameters set to true are not already installed. Parameters set to false are already installed.
    2. To update existing components, change their value in components.properties to true.
    3. Save the changes to components.properties.

  3. If set -Dwcmdetect=true

    1. Open the properties file in...

        paa/ComponentName

    2. Set the value of all the WCM libraries to update to true.

    3. Set the value of all the WCM libraries to keep the old version to false.

    4. Save the changes.

  4. If we changed values in components.properties, update the registration of the existing components with the new assembly...

      ./ConfigEngine.sh update-paa-components -DappName=assemblyName -DWasPassword=foo -DPortalAdminPwd=foo

  5. If we use SPNEGO for single sign-on, disable SPNEGO:

    Log on to WAS console, go to...

      Security | Global security | Web and SIP security | SPNEGO Web authentication

    ...and clear the check box...

      Enable SPNEGO

  6. Deploy the updated PAA content to WebSphere Portal:

      ./ConfigEngine.sh deploy-paa -DappName=assemblyName -DWasPassword=foo -DPortalAdminPwd=foo

    If deploying to a clustered environment, and the PAA file contains xmlaccess.sh script files, add parameters...

    • -DmaxTimeToWait
    • -DmaxAppTimeToWait

    These values define the time the wplc-wait-for-sync-to-complete task waits to synchronize the nodes. Default values are...

    • -DmaxTimeToWait=30
    • -DmaxAppTimeToWait=5

    The values are in minutes.

    If deploying to a virtual portal, include the context root and host name parameters for the virtual portal. Add paramters...

    By default, only components set to true in components.properties are deployed. To deploy all components, add parameter...

      -DforceDeploy=true

  7. Re-enable SPNEGO:

    Go to...

      Security | Global security | Web and SIP security | SPNEGO Web authentication

    ...and check box...

      Enable SPNEGO


Parent Manage the existing Portal Application Archive (PAA) file