+

Search Tips   |   Advanced Search

Check server dependency for PAA files

Before installing a PAA file, verify the file is compatible with the current version of IBM WebSphere Portal.

To define the dependencies for a PAA file, edit the assembly level sdd.xml file in the PAA directory and add the tag...

    <serverVersionDependency>

...to the <rootIU> tag with the following attributes:

    name Set to PortalServer
    lowerVersion Optional. Only one WebSphere Portal version value is acceptable.
    higherVersion Optional. Only one WebSphere Portal version value is acceptable.
    versions Optional. Add multiple version values as a comma-separated list.

For example... 

<serverVersionDependency name="PortalServer" 
           lowerVersion="6.0.0.0" 
           higherVersion="8.5.0.0" 
           versions="7.0.0.1,7.0.0.2" />

To add dependencies for a specific fix level, add the following attributes to the <server> subelement within the <serverVersionDependency> element:

    version Version of WebSphere Portal where to set the level restriction.
    fixlevel Optional. This attribute is compared against the current installation fix level to determine any dependencies. If the attribute is not set, then it is ignored.
    lower Optional. Set to true if the fixlevel is the lowest version for the current server.
    higher Optional. Set to true if the fixlevel is the highest version for the current server.

For example 

    <serverVersionDependency name="PortalServer" 
           lowerVersion="" 
           higherVersion="" 
           versions="" >

     <server version="8.5.0.0" 
             fixlevel="CF02" 
             lower="true"
             higher="false" />

 </serverVersionDependency>

The Solution Installer uses the following rules to determine whether a PAA file is compatible with the current WebSphere Portal version:

  • The Solution Installer assumes the file is compatible in the following situations:

    • If the <serverVersionDependency> tag is not found in the assembly level sdd.xml file
    • If the <serverVersionDependency> tag exists but has no attributes defined

  • The Solution Installer installs the PAA file if the following information is true:

    • The lowerVersion attribute is set and the value is equal to or greater than the current version of WebSphere Portal.
    • The higherVersion attribute is set and the current version of WebSphere Portal is less than or equal to its value.

  • If the versions attribute is set, the Solution Installer installs the PAA file if the current WebSphere Portal matches one of the values.

  • If a <server> element is included, the PAA file is installed if the following information is true:

    • If version and fixlevel are equal to the current server information
    • If lower is true, any fix pack level that is greater than fixlevel
    • If higher is true, any fix pack level that is less than or equal to fixlevel

  • Black list to block deploying PAA files that must not be deployed

    The Solution Installer checks the blacklist.txt file in...

      /WebSphere/PortalServer/solutioninstaller/wp.si

    The blacklist.txt file contains a list of PAA files that WebSphere Portal cannot deploy. The format for the blacklist.txt file is...

      assemblyname: version_number

    Multiple versions are allowed as a semicolon-separated list; for example:

      assemblyname: version_number1;version_number2

    When we install a PAA file, the Solution Installer reads the assembly name and version from the assembly level sdd.xml file. The Solution Installer then looks for the matching information in the blacklist.txt file. If the Solution Installer finds a match in the blacklist.txt file, the PAA file is not installed.


    Parent Develop basic PAA file applications