6.1.5.3: Readme for IBM WebSphere Portal 6.1.5 fix pack 3 (6.1.5.3) - cluster

Content

Table of Contents

• What is new with Feature Pack 6.1.5 Fix Pack 3
• Space requirements
• Cluster upgrade planning
• Steps for installing feature pack 6.1.5 Fix Pack 3
• Steps for uninstalling feature pack 6.1.5 Fix Pack 3
• Known issues
• Change History
• Additional information
• Trademarks and service marks

• The instructions in this document allow enablement of the 6.1.5 fix pack 3 on a clustered 6.1.0.6 WebSphere Portal or Web Content Manager or IBM WebSphere Portal Express installation.
• If the 6.1.5 feature pack was enabled on 6.1.0.3, 6.1.0.4, or 6.1.0.5 or you performed a fresh install of 6.1.5, the 6.1.0.6 fix pack upgrades the 6.1.5 features to the 6.1.5.3 level.
• See the WebSphere Portal Version 6.1.5 InfoCenter for additional features that were added.

• Special note: This feature pack and these instructions can also be used for a WebSphere Portal Express - Idle Standby deployment. However, the terminology used in this document is different. WebSphere Portal Express is licensed for use in a single-server configuration and may not be used in either a cloned or a clustered configuration except when you implement Idle Standby for purposes of failover. Implementing the Idle Standby functionality requires purchase of a separate WebSphere Portal Express Idle Standby License Option.
  

• Space requirement for feature pack 6.1.5.3 is 80MB.
• Verify that the free space is available before beginning the installation.
  
  Back to top
  
  

  ---

• For WebSphere Portal 6.1.5.3 enablement, we do not support the 24x7 upgrade in a single cluster. The procedure is to upgrade the cluster while the entire cluster has been taken offline from receiving user traffic. The upgrade is performed on every node in the cluster before the cluster is brought back online to receive user traffic.
• If you must maintain 24x7, you can use a multiple cluster setup. Please see the following document for details: Multiple Cluster Setup with WebSphere Portal.
  
  

1. Perform the following steps before upgrading to Version 6.1.5.3:
1. Verify that the information in the wkplc.properties, wkplc_dbtype.properties, and wkplc_comp.properties files are correct on each node in the cluster:
• Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file.
• Ensure that the DbUser (database name) and DbPassword (database password) parameters are defined correctly for all database domains in the wkplc_comp.properties file.
• Ensure that the value of the XmlAccessPort property in wkplc_comp.properties matches the value of the port used for HTTP connections to the WebSphere Portal server.
2. Ensure nodes are synchronized before starting the upgrade.
   
3. Ensure that automatic synchronization is disabled on all nodes to be upgraded. When the automatic synchronization is enabled, the node agent on each node automatically contacts the deployment manager at startup and then every synchronization interval to attempt to synchronize the node's configuration repository with the master repository managed by the deployment manager.
1. In the administrative console for the deployment manager, select System administration > Node agents in the navigation tree.
2. Click nodeagent for the required node.
3. Click File Synchronization Service.
4. Uncheck the Automatic Synchronization check box on the File Synchronization Service page to disable the automatic synchronization feature and then click OK.
5. Repeat these steps for all other nodes to be upgraded.
6. Click Save to save the configuration changes to the master repository.
7. Select System administration > Nodes in the navigation tree.
8. Select all nodes that are not synchronized, and click on Synchronize
9. Select System administration > Node agents in the navigation tree.
10. For the primary node, select the nodeagent and click Restart.
11. Select the nodeagents of all additional nodes and click Stop.
    
4. Stop user traffic to this cluster and ensure that all user sessions are quiesced before proceeding.
   
5. Perform the following steps to upgrade WebSphere Portal on the primary node:
   
   NOTE: Do not attempt to combine steps 5 and 6 together! The update must be performed first on the primary node then on the additional (also known as secondary) nodes, in accordance with the below instructions.
   
1. Read <PortalServer_root>\license\WebSphere_Portal_V615x.pdf to confirm that you have read and agree to the License Agreement.
2. Perform the following steps to install WebSphere Portal feature pack 6.1.5 fix pack 3 if you accept the license agreement from step 5a:
1. Change to the wp_profile_root/PortalServer/bin directory.
2. Run the appropriate command for your operating system:
• Windows: install615.bat licenseAgree
• Unix/Linux: ./install615.sh licenseAgree
• i5/OS: install615.sh licenseAgree
  
  NOTE: If the installation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination. For i5/OS, download ISA on a system other than i5/OS. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your i5/OS system. Fix what is causing the problem and then rerun the installation task.
  
  NOTE: The following catalog downloads will be removed when you run the install615.bat/sh command:
• WCM Rendering Portlets (JSR 286 version) (catalog)
• WCI (Web Content Integrator, formally an IBM Software Services for Lotus offering)
• WebDAV for Portal (catalog)
  
3. Optional: The 6.1.5.3 upgrade does not add the mashup integration. If you want to take advantage of this feature, you will need to perform the following steps:
1. Change to the wp_profile_root/ConfigEngine/ directory.
2. Run the following ConfigEngine command to enable mashup:
• Windows: ConfigEngine.bat deploy-portal-mashup-ui -DWasPassword=password -DPortalAdminPwd=password.
• Unix/Linux: ./ConfigEngine.sh deploy-portal-mashup-ui -DWasPassword=password -DPortalAdminPwd=password.
• i5/OS: ConfigEngine.sh deploy-portal-mashup-ui -DWasPassword=password -DPortalAdminPwd=password.
  
3. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
4. To remove passwords from wkplc*.properties files, run the following task from the wp_profile_root/ConfigEngine/ directory to delete the passwords:
• Windows: ConfigEngine.bat delete-passwords
• Unix/Linux: ./ConfigEngine.sh delete-passwords
• i5/OS: ConfigEngine.sh delete-passwords
  
6. Perform the following steps to upgrade WebSphere Portal on each additional node after completing the upgrade on the primary node:
   
   NOTE: Do not attempt to upgrade additional nodes until after completing the Step 5 (Primary Node)! The update for the primary must be performed and completed first then upgrade any additional nodes. Additional nodes upgrades can be performed sequentially or in parallel. Update the additional nodes in accordance with the below instructions.
   
1. Perform the following steps to install WebSphere Portal feature pack 6.1.5 fix pack 3:
1. Start the node agent on the node.
2. Change to the wp_profile_root/PortalServer/bin directory.
3. Run the appropriate command for your operating system:
• Windows: install615.bat licenseAgree
• Unix/Linux: ./install615.sh licenseAgree
• i5/OS: install615.sh licenseAgree
  
  NOTE: If the installation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination. For i5/OS, download ISA on a system other than i5/OS. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your i5/OS system. Fix what is causing the problem and then rerun the installation task.
  
  NOTE: The following catalog downloads will be removed when you run the install615.bat/sh command:
• WCM Rendering Portlets (JSR 286 version) (catalog)
• WCI (Web Content Integrator, formally an IBM Software Services for Lotus offering)
• WebDAV for Portal (catalog)
  
2. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
3. To remove passwords from wkplc*.properties files, run the following task from the wp_profile_root/ConfigEngine/ directory to delete the passwords:
• Windows: ConfigEngine.bat delete-passwords
• Unix/Linux: ./ConfigEngine.sh delete-passwords
• i5/OS: ConfigEngine.sh delete-passwords
  
7. Perform the following post-cluster installation upgrade steps:
1. Re-enable automatic synchronization on all nodes in the cluster if you disabled it earlier.
1. In the administrative console for the deployment manager, select System administration > Node agents in the navigation tree.
2. Click nodeagent for the required node.
3. Click File Synchronization Service.
4. Check the Automatic Synchronization check box on the File Synchronization Service page to enable the automatic synchronization feature and then click OK.
5. Repeat these steps for all remaining nodes.
6. Click Save to save the configuration changes to the master repository.
7. Select System administration > Nodes in the navigation tree.
8. Select all nodes that are not synchronized, and click on Synchronize.
9. Select System administration > Node agents in the navigation tree.
10. Select all node agents where automatic synchronization has been re-enabled and click Restart.
    
2. Install any APARs that need to be applied. See the Recommended fixes and updates for WebSphere Portal and Web Content Manager page.
3. If you are running an external Web server such as IBM HTTP server and you are using the WebSphere Application Server automatic generation and propagation of the plugin, then just restart the Web server. If you are not using the automatic generation and propagation, then perform the following steps:
1. Regenerate the Web server plugin.
2. Copy the plugin-cfg.xml file to the Plugin directory.
3. Restart the Web server.
   
4. Optional: The 6.1.5.3 upgrade does not modify the theme that you have assigned as default theme. If you want to take advantage of the page sharing capabilities, you will either need to do the following steps or adjust your theme:
1. Log on to WebSphere Portal.
2. Navigate to Administration -> Portal User Interface -> Manage Themes and Skins.
3. Select Tab Menu - Page Builder from the Themes list.
4. Click Set as default portal theme.
5. Log off of WebSphere Portal and then log back in to see the changes.
   

1. Perform the following steps before you uninstall the Version 6.1.5.3:
   
   NOTE: The steps listed in this point need to be performed on all nodes.
   
1. Ensure that you have enough free space allocated for your operating system in the appropriate directories.
2. Verify that the information in the wkplc.properties, wkplc_dbtype.properties, and wkplc_comp.properties files are correct on each node in the cluster.
• Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file.
• Ensure that the DbUser (database name) and DbPassword (database_password) properties are defined correctly for all database domains in the wkplc_comp.properties file.
• The WebSphere Portal Update Installer removes plain text passwords from the wkplc*.properties files.
• Ensure that the value of the XmlAccessPort property in wkplc_comp.properties matches the value of the port used for HTTP connections to the WebSphere Portal server.
3. Uninstalling feature pack 6.1.5 fix pack 3 will remove all introduced changes; therefore, you must make sure that you do not use any of the 6.1.5.3 features before uninstalling the 6.1.5 fix pack 3. For example, if you assigned one of the new themes, you must unassign it or if you created a mashup artifact, you must remove them from the pages.
2. Ensure nodes are synchronized before starting uninstall.
   
3. Ensure that automatic synchronization is disabled on all nodes to be downgraded.
1. In the administrative console for the deployment manager, select System administration > Node agents in the navigation tree.
2. Click nodeagent for the required node.
3. Click File Synchronization Service.
4. Uncheck the Automatic Synchronization check box on the File Synchronization Service page to disable the automatic synchronization feature and then click OK.
5. Repeat these steps for all other nodes to be downgraded.
6. Click Save to save the configuration changes to the master repository.
7. Select System administration > Nodes in the navigation tree.
8. Select all nodes that are not synchronized, and click on Synchronize
9. Select System administration > Node agents in the navigation tree.
10. For the primary node, select the nodeagent and click Restart.
11. Select the nodeagents of all additional nodes and click Stop.
    
4. Stop user traffic to this cluster and ensure that all user sessions are quiesced before proceeding.
   
   NOTE: Do not attempt to combine steps 5 and 6 together! The update must be performed first on the primary node then on the additional nodes, in accordance with the below instructions.
   
5. Perform the following steps to uninstall the feature pack on the primary node:
1. Perform the following steps to remove the WebSphere Portal feature pack 6.1.5 fix pack 3:
1. Change to the wp_profile_root/PortalServer/bin directory.
2. Run the appropriate command for your operating system:
• Windows: uninstall615.bat
• Unix/Linux: ./uninstall615.sh
• i5/OS: uninstall615.sh
  
  NOTE: If the uninstallation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination. For i5/OS, download ISA on a system other than i5/OS. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your i5/OS system. Fix what is causing the problem and then rerun the installation task.
  
2. If you previously customized any configuration files in the portal_server_root/config directory, check to see if uninstalling the feature pack affected those files by restoring a version of the files that was saved when the feature pack was originally installed. If it did affect the files, you will need to perform the same customization on the restored version of each file.
3. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
   
   
6. Perform the following steps to uninstall the feature pack on each additional node;
   
   NOTE: Do not attempt to uninstall additional nodes until after completing the Step 5 (Primary Node)! The uninstall of the primary must be performed and completed first then uninstall any additional nodes. Uninstalling additional nodes can be performed sequentially or in parallel. Uninstall the additional nodes in accordance with the below instructions.
   
1. Perform the following steps to remove the WebSphere Portal feature pack 6.1.5 fix pack 3:
1. Start the node agent on the node.
2. Change to the wp_profile_root/PortalServer/bin directory.
3. Run the appropriate command for your operating system:
• Windows: uninstall615.bat
• Unix/Linux: ./uninstall615.sh
• i5/OS: uninstall615.sh
  
  NOTE: If the uninstallation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination. For i5/OS, download ISA on a system other than i5/OS. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your i5/OS system. Fix what is causing the problem and then rerun the installation task.
  
2. If you previously customized any configuration files in the portal_server_root/config directory, check to see if uninstalling the feature pack affected those files by restoring a version of the files that was saved when the fix pack was originally installed. If it did affect the files, you will need to perform the same customization on the restored version of each file.
   
3. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
4. To remove passwords from wkplc*.properties files, run the following task from the wp_profile_root/ConfigEngine/ directory to delete the passwords:
• Windows: ConfigEngine.bat delete-passwords
• Unix/Linux: ./ConfigEngine.sh delete-passwords
• i5/OS: ConfigEngine.sh delete-passwords
7. Perform the following post-uninstallation step:
1. Re-enable automatic synchronization on all nodes in the cluster if you disabled it earlier.
1. In the administrative console for the deployment manager, select System administration > Node agents in the navigation tree.
2. Click nodeagent for the required node.
3. Click File Synchronization Service.
4. Check the Automatic Synchronization check box on the File Synchronization Service page to enable the automatic synchronization feature and then click OK.
5. Repeat these steps for all remaining nodes.
6. Click Save to save the configuration changes to the master repository.
7. Select System administration > Nodes in the navigation tree.
8. Select all nodes that are not synchronized, and click on Synchronize.
9. Select System administration > Node agents in the navigation tree.
10. Select all node agents where automatic synchronization has been re-enabled and click Restart.
2. If you are running an external Web server such as IBM HTTP server and you are using the WebSphere Application Server automatic generation and propagation of the plugin, then just restart the Web server. If you are not using the automatic generation and propagation, then perform the following steps:
1. Regenerate the Web server plugin.
2. Copy the plugin-cfg.xml file to the Plugin directory.
3. Restart the Web server.