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

Product readme


Abstract

IBM WebSphere Portal for z/OS feature pack stand-alone installation instructions for all editions

Content

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


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

Table of Contents





What is new with Feature Pack 6.1.5
Fix Pack 1
  • The instructions in this document allow enablement of the 6.1.5 fix pack 1 on a stand-alone 6.1.0.4 WebSphere Portal or Web Content Manager installation for 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.

Back to top




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

    Back to top



Steps for installing
Feature Pack 6.1.5 Fix Pack 1

Before you begin:

Familiarize yourself with the Portal Upgrade Best Practices available from IBM Remote Technical Support for WebSphere Portal.

  • Portal Upgrades: Best Practices

    1. Perform the following steps before upgrading to Version 6.1.5.1:
      1. If you are running an external Web server such as HTTP server, stop the Web server.
      2. Verify that the information in the wkplc.properties, wkplc_comp.properties and wkplc_dbtype.properties files are correct.
        • Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file.
        • In the wkplc_comp.properties file, set the passwords for the database entries.
        • 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.
        • If using a database other than the default, grant permissions to databases within the framework by setting the DbUser (database name) and DbPassword (database password) parameters in the wkplc_comp.properties file.
      3. Perform the following steps to change the HTTP connection timeout value for the WebSphere_Portal server:
        1. Click Servers --> Application Servers --> WebSphere_Portal>Web container settings --> Web container transport chains. When using WAS 7.x (for the editions that support WAS 7.x see the hardware&software requirements doc) use the following path click Servers --> Server Type --> WebSphere Application Servers --> WebSphere_Portal>Web container settings --> Web container transport chains.
        2. Increase the timeout values for each entry listed in the web container transport chain section. Click HTTP Inbound Channel. Change the Read timeout value to 180 and change the Write timeout value to 180.
        3. Save your changes.
    2. Perform the following steps to install the WebSphere Portal 6.1.5 fix pack 1:
      1. Start the WebSphere Portal Customization Dialog.
      2. In the Portal configuration panel, select Basic configuration tasks.
      3. 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.
      4. Select Define variables.

        Reminder: Press F1 to display the help panel if you need assistance defining the variables.
      5. Generate the customization jobs.
      6. 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)
    3. Perform the following post installation steps:
      1. 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.
      2. 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.
        2. Navigate to Administration > Portal User Interface > Manage Themes and Skins.
        3. Select Tab Menu - Page Builder from the Themes list.
        4. Select Set as default portal theme.
        5. Log off of WebSphere Portal and then log back in to see the changes.
      3. Install any APARs that need to be applied. See the Recommended fixes and updates for WebSphere Portal and Web Content Manager page.




    Back to top




    Steps for uninstalling
    Feature Pack 6.1.5 Fix Pack 1
    Perform the following steps to uninstall Version 6.1.5.1:

    NOTE: Changing the server context root after upgrading is an unsupported uninstall path. To uninstall after changing the context root, you must first change the server context root back to the values of the previous version.

    IMPORTANT: Uninstalling the 6.1.5.1 feature might result in an unsupported configuration. If uninstalling because of a failed upgrade, fix what is causing the problem and rerun the installation task.
    1. Perform the following steps before you uninstall the Version 6.1.5.1:
      1. Ensure that you have enough free space allocated for your operating system in the appropriate directories. See supported hardware and software requirements for information.
      2. If you are running an external Web server such as HTTP server, stop the Web server.
      3. Verify that the information in the wkplc.properties, wkplc_comp.properties, wkplc_dbtype.properties, and wkplc_sourceDB.properties files are correct.
        • Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.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.
        • If using a database other than the default, grant permissions to databases within the framework by setting the DbUser (database name) and DbPassword (database password) parameters in the wkplc_comp.properties file.
      4. 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. Perform the following steps to remove the WebSphere Portal for z/OS 6.1.5 fix pack 1:
        1. Start the WebSphere Portal Customization Dialog.
        2. In the Portal configuration panel, select Basic configuration tasks.
        3. Select Configure WebSphere Portal version 6.1.5 Feature Pack.
        4. 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.
    3. Start the Portal server.
    4. 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.
    5. If you previously customized any configuration files in the PortalServer_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 must perform the same customization on the restored version of each file.


    Back to top




    Known issues

    Back to top


    Change History
    Initial Release

    Back to top



    Additional information

    You can find additional information on the WebSphere Portal support page.

    Back to top



    Trademarks and service marks

    For trademark attribution, visit the IBM Terms of Use Web site.

    Back to top


    Rate this page:

    (0 users)Average rating

    Document information


    More support for:

    WebSphere Portal
    Installation

    Software version:

    6.1.0.4, 6.1.5.1

    Operating system(s):

    z/OS

    Software edition:

    Enable, Extend, Server

    Reference #:

    7017958

    Modified date:

    2010-06-21

    Translate my page

    Machine Translation

    Content navigation