6.1.5.1: Readme for IBM WebSphere Portal for z/OS 6.1.5 fix pack 1 (6.1.5.1) - cluster

Content

Table of Contents

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

• The instructions in this document allow enablement of the 6.1.5 fix pack 1 on a clustered 6.1.0.4 WebSphere Portal or Web Content Manager installation on z/OS.
• If the 6.1.5 feature pack was enabled on 6.1.0.3, the 6.1.0.4 fix pack upgrades the 6.1.5 features to the 6.1.5.1 level.
• See the WebSphere Portal for z/OS Version 6.1.5 InfoCenter for additional features that were added.

• Space requirement for feature pack 6.1.5.1 is 80MB.
• Verify that the free space is available before beginning the installation.
  

• For WebSphere Portal 6.1.5.1 enablement, we do not support the 24*7 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 24*7, 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.1:
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. Perform the following steps to run the installation program:
1. Check the status of all active application servers and stop any active application servers.
2. Start the WebSphere Portal Customization Dialog.
3. In the Portal configuration panel, select Basic configuration tasks.
4. Select Configure WebSphere Portal version 6.1.5 Feature Pack.
   
   NOTE: If you receive a 'Selection Error' message, verify that the dialog has defined variables under option 2, Configure base portal into a federated WebSphere Application. You can load the variables from the SAVECFG files from the previous full installation of the same portal server and update the variables under the 'Configure base portal into primary node' option, as appropriate.
   
5. Select Define variables.
   
   Reminder: Press F1 to display the help panel if you need assistance defining the variables.
   
6. Generate the customization jobs.
7. Follow the Customization Dialog instructions for submitting the customization jobs.
   
   NOTE: If the installation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination.
   
   NOTE: The following catalog downloads will be removed when you run the customization jobs:
• WCM Rendering Portlets (JSR 286 version) (catalog)
• WCI (Web Content Integrator, formally an IBM Software Services for Lotus offering)
• WebDAV for Portal (catalog)
  
2. After the feature pack is installed, check the status of the node you are upgrading in the Deployment Manager administrative console. Perform the following steps:
1. In the Deployment Manager administrative console, click System Administration>Nodes.
2. If the primary node has a status of Not Synchronized or Unknown, ensure that the node agent is running on the node, then click Synchronize and wait for the synchronization to complete. The end of synchronization is indicated by the message "BBOO0222I: ADMS0003I: The configuration synchronization completed" in the system log.
3. Wait at least 20 minutes before performing the next step to ensure that the node agent EAR expansion process completes.
4. Restart the WebSphere_Portal server on the primary node.
3. Run the following task to activate the portlets:
• ./ConfigEngine.sh activate-portlets -DPortalAdminPwd=password -DWasPassword=password
4. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
5. If you are not using automatic generation and propagation for the Web server plug-in, manually generate and/or propagate the plugin-cfg.xml file to the Web servers.
   
   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.
6. Perform the following steps to upgrade WebSphere Portal on each additional node after completing the upgrade on the primary node:
1. Perform the following steps to run the installation program:
1. Check the status of all active application servers and stop any active application servers.
2. Start the node agent on the node.
3. Start the WebSphere Portal Customization Dialog.
4. In the Portal configuration panel, select Basic configuration tasks.
5. Select Configure WebSphere Portal version 6.1.5 Feature Pack.
   
   NOTE: If you receive a 'Selection Error' message, verify that the dialog has defined variables under option 2, Configure base portal into a federated WebSphere Application. You can load the variables from the SAVECFG files from the previous full installation of the same portal server and update the variables under the 'Configure base portal into secondary node' option, as appropriate.
   
6. Select Define variables.
   
   Reminder: Press F1 to display the help panel if you need assistance defining the variables.
   
7. Generate the customization jobs.
8. Follow the Customization Dialog instructions for submitting the customization jobs.
   
   NOTE: If the installation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination.
   
   NOTE: The following catalog downloads will be removed when you run the customization jobs:
• WCM Rendering Portlets (JSR 286 version) (catalog)
• WCI (Web Content Integrator, formally an IBM Software Services for Lotus offering)
• WebDAV for Portal (catalog)
  
2. After the feature pack is installed, check the status of the current node in the Deployment Manager administrative console. Perform the following steps:
1. In the Deployment Manager administrative console, click System Administration>Nodes.
2. If the current node has a status of Not Synchronized or Unknown, ensure that the node agent is running on the node, then click Synchronize and wait for the synchronization to complete. The end of synchronization is indicated by the message "BBOO0222I: ADMS0003I: The configuration synchronization completed" in the system log.
3. Wait at least 20 minutes before performing the next step to ensure that the node agent EAR expansion process completes.
4. Restart the WebSphere_Portal server on the additional node.
3. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
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. Optional: The 6.1.5.1 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 and perform.
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.1:
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) properties 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. Uninstalling the feature pack 6.1.5 fix pack 1 will remove all introduced changes; therefore, you must make sure that you undo any of the 6.1.5.1 features before uninstalling the 6.1.5 fix pack 1. 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 downgrade 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 run the uninstallation program:
1. Check the status of all active application servers and stop any active application servers.
2. Start the WebSphere Portal Customization Dialog.
3. In the Portal configuration panel, select Basic configuration tasks.
4. Select Configure WebSphere Portal version 6.1.5 Feature Pack.
   Select Define variables.
   
   Reminder: Press F1 to display the help panel if you need assistance defining the variables.
   
5. Generate the customization jobs.
   
   NOTE: If you saved the customization jobs from the previous installation of Feature pack 6.1.5.1 and the portal environment has not been changed, you can reuse the uninstall Jobs and do not need to regenerate the jobs.
   
6. Follow the Customization Dialog instructions for submitting the uninstall customization jobs.
   
   NOTE: If the uninstallation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination.
2. After the feature pack is uninstalled, check the status of the node you are uninstalling on in the Deployment Manager administrative console. Perform the following steps:
1. In the Deployment Manager administrative console, click System Administration>Nodes.
2. If the primary node has a status of Not Synchronized or Unknown, ensure that the node agent is running on the node, then click Synchronize and wait for the synchronization to complete. The end of synchronization is indicated by the message "BBOO0222I: ADMS0003I: The configuration synchronization completed" in the system log.
3. Wait at least 20 minutes before performing the next step to ensure that the node agent EAR expansion process completes.
4. Restart the WebSphere_Portal server on the primary node.
3. Run the following task to activate the portlets from the previous release:
• ./ConfigEngine.sh activate-portlets -DPortalAdminPwd=password -DWasPassword=password
4. 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 the 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 run the uninstallation program:
1. Check the status of all active application servers and stop any active application servers.
2. Start the node agent on the node.
3. Start the WebSphere Portal Customization Dialog.
4. In the Portal configuration panel, select Basic configuration tasks.
5. Select Configure WebSphere Portal version 6.1.5 Feature Pack.
6. Select Define variables.
   
   Reminder: Press F1 to display the help panel if you need assistance defining the variables.
   
7. Generate the customization jobs.
   
   NOTE: If you saved the customization jobs from the previous installation of Feature pack 6.1.5.1 and the portal environment has not been changed, you can reuse the uninstall Jobs and do not need to regenerate the jobs.
   
8. Follow the Customization Dialog instructions for submitting the uninstall customization jobs.
   
   NOTE: If the uninstallation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination.
2. After the feature pack is uninstalled, check the status of the node you are uninstalling on in the Deployment Manager administrative console. Perform the following steps:
1. In the Deployment Manager administrative console, click System Administration>Nodes.
2. If the current node has a status of Not Synchronized or Unknown, ensure that the node agent is running on the node, then click Synchronize and wait for the synchronization to complete. The end of synchronization is indicated by the message "BBOO0222I: ADMS0003I: The configuration synchronization completed" in the system log.
3. Wait at least 20 minutes before performing the next step to ensure that the node agent EAR expansion process completes.
4. Restart the WebSphere_Portal server on the additional node.
3. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
7. Perform the following post-cluster uninstall 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.