Install a Portal Application Archive (PAA) file

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

1. Review and readme files include with the PAA

2. Install the PAA
   cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh install-paa -DPAALocation=paa_file_location -DWasPassword=foo -DPortalAdminPwd=foo

   To control the behavior of the installed IBM WCM libraries, we can add the following optional parameter to the install-paa command:

   -Dwcmdetect=true

   If you include this parameter, a properties file is created in the paa/ComponentName directory. The name of the properties file matches the PAA file name.

3. After the task successfully completes, verify the following subdirectory exists:
   WP_PROFILE/paa/paa_filename

4. From the PAA file subdirectory, open the components.properties file.

   To check for and resolve conflicts with previously installed components:

   1. Search for the component parameters.

      Parameters set to true are not already installed. Parameters set to false are already installed.

   2. To update existing components, change their value in the components.properties file to true.

   3. Save the changes to the components.properties file.

5. To use the Web application bridge integration feature included the -Dwcmdetect=true parameter:

   1. Open the properties file in the paa/ComponentName directory.

   2. Set the value of all the Web Content Manager libraries to update to true.

   3. Set the value of all the Web Content Manager libraries to keep the old version to false.

   4. Save the changes.

6. If you changed values in the components.properties file, update the registration of the existing components with those of the new assembly.
   ./ConfigEngine.sh update-paa-components -DappName=assemblyName -DWasPassword=foo -DPortalAdminPwd=foo

7. If we are using SPNEGO for single sign-on, log on to the WAS admin console, and uncheck...

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

8. Deploy the PAA content to WebSphere Portal:
   ./ConfigEngine.sh deploy-paa -DappName=assemblyName -DWasPassword=foo -DPortalAdminPwd=foo

   If we are deploying to a virtual portal, include the context root and host name parameters for the virtual portal. Add the -DVirtualPortalHostName and -DVirtualPortalContext parameters to the deploy-paa task.

   By default, only components set to true in the components.properties file are deployed. To deploy all components, add the -DforceDeploy=true parameter to the deploy-paa task.

9. Optional: To enable SPNEGO:

   1. Log on to WAS admin console.

   2. Go to Security > Global security > Web and SIP security > SPNEGO Web authentication.

   3. Check the Enable SPNEGO checkbox.

   4. Save the changes.

Parent: Use the Solution Installer