Check server dependency

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

The Solution Installer uses the following two methods to check for dependencies:

Dependency checking for PAA files

Edit the assembly level sdd.xml file. Search for the <rootIU> tag. Add the <serverVersionDependency> tag to the <rootIU> tag with the following attributes:

name	Required. Should be set to PortalServer
lowerVersion	Optional. Only one Portal version value is acceptable for this attribute.
higherVersion	Optional. Only one Portal version value is acceptable for this attribute.
versions	Optional. We can add multiple Portal version value for this attribute as a comma-separated list.

For example, we might add the following information to the sdd.xml file:

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

The Solution Installer uses the following rules to determine if a PAA file is compatible with the current 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.

Black list to block deploying PAA file that must not be deployed

The Solution Installer checks the blacklist.txt file located in the /WebSphere/PortalServer/solutioninstaller/wp.si directory. The blacklist.txt file contains a list of PAA file 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 installing a PAA file, theSolution 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 theSolution Installer finds a match in the blacklist.txt file, the PAA file is not installed.

Parent: Develop basic solution applications
Related:
Portal Application Archive (PAA) file creation
Portal Application Archive (PAA) file specification