+

Search Tips   |   Advanced Search

Unsupported and deprecated features for V8.5

After a migration, unsupported supported and deprecated features can result in unpredictable behavior. Remove them before starting the migration. If migrating from version 7.0, review the unsupported and deprecated page for version 8.0. too.


Unsupported features and themes in v8.5

    Web Clipper
    Use the Virtual Web Application Manager portlet instead.

    IBM themes from a previous version
    The following themes are no longer supported:

    • Portal
    • PortalWeb2
    • Tab Menu - Page Builder

    These themes are migrated as is to WebSphere Portal v8.5. However, they no longer work and are no longer supported. Manually update those themes. Merge their function into a clean copy of a Portal 8.5 theme on the target server.

    The PageBuilder2 and 7.0.0.2 themes are supported if migrated to v8.5.

    Composite applications
    Composite applications are no longer supported. If we have a composite application in the system and we are migrating to v8.5, the migration fails. Ensure that all composite applications are deleted before starting the migration. When we delete a composite application, we must also run the resource cleaner, otherwise pages can still exist in the database.

    CAI/TAI portlets
    When we are migrating from one version to another, the script can contain references to the CAI/TAI portlets. These portlets are no longer available and any reference to these portlets will cause your script to fail.


Deprecated features

    Shared pages
    Shared pages are deprecated.

    Enabler Component
    The Enabler component is deprecated.

    Full and Base installation options
    Before WebSphere Portal v8.5, a customer chose either a full deployment with all the same pages and artifacts or a base deployment to customize their portal. Starting with v8.5, the Configuration Wizard installs the full deployment. Customers can then remove pages to customize their portal. Then, they can package their customizations as a Portal Application Archive (PAA) file. Finally, customers can install their production server, run the empty-portal task, and install the customization PAA file.

    LikeMinds and Feedback
    The LikeMinds and Feedback database domains are deprecated.

    Stand-alone LDAP user registry
    The stand-alone LDAP user registry configuration is deprecated. Instead, configure the federated LDAP user registry. If we upgraded from WebSphere Portal v7.0 or 8.0 with a stand-alone LDAP user registry, we can continue to use the stand-alone LDAP user registry. However, run the wp-modify-federated-security to change to a federated LDAP user registry.

    Active Credentials
    Active credentials are deprecated from the Credential Vault portlet. Passive credentials are still available.

    Parallel Portlet rendering
    The Parallel Portlet rendering feature is deprecated.

    Mashups Enabler API
    The Mashups Enabler API is deprecated.

    Add a category from an outside component.
    We can no longer add a category from an outside component. Use the site toolbar instead.

    LTPA version 1 token support
    The LTPA version 1 token is deprecated. WebSphere Application Server v8.5.5. disables the LTPA version 1 token by default. If we are integrating with third-party applications that rely on LTPA version 1, update the application to support LTPA version 2. If we cannot update the application, manually re-enable LTPA version 1 support after after completing the migration. For information on updating the application to support LTPA version 2, see the documentation for the application.

    Tagging and rating dialog and inline widgets
    In tagging and rating, the tag and rating widgets of previous portal versions are deprecated. This affects both pairs of the old widgets, the dialog widgets of the default user interface and the inline widgets of the alternative user interface. They are replaced by a new pair of interactive inline widgets. The new widgets combine the functions of the separate widgets of earlier portal versions.

    URL mappings
    URL mappings are deprecated. If we upgrade from v8.0 to v8.5, we can continue to use the existing URL mappings, but creating new URL mappings is no longer supported. Use vanity or friendly URLs.

    IBM Portlet API Web Content Viewer portlet
    The Web Content Viewer portlet based on the IBM Portlet API has been removed and is no longer supported. If we use the IBM Portlet API Web Content Viewer, and you migrate to v8.5, then we must replace the portlet and its clones with the JSR 286 Web Content Viewer portlet as a post-migration step.

    IBM Portlet API Remote Web Content Viewer portlet
    The Remote Web Content Viewer portlet based on the IBM Portlet API has been removed and is no longer supported. If we use the IBM Portlet API Remote Web Content Viewer, and you migrate to v8.5, then we must replace the portlet and its clones with the JSR 286 Web Content Viewer portlet as a post-migration step.


Deprecated integration portlets

The following integration portlets were removed in WebSphere Portal v8.5:


Deprecated Business portlets

The following Business portlets were removed in WebSphere Portal v8.5:

    Remote Rendering Portlet
    The remote rendering portlet is now deprecated. Use the Web Content Viewer (JSR 286) portlet and WSRP instead.

    Web2Bookmarks portlet
    The Web2Bookmarks portlet is no longer available for immediate use. Instead, download the portlet from the IBM WebSphere Portal Business Solutions Catalog.


Deprecated theme

The WebSphere Portal Page Builder 7.x theme was deprecated.


Parent New

Related concepts:
Configure authentication filters
Configure the federated LDAP user registry
Solutions Catalog: WebSphere Portal
WebSphere Portal V8.0: Unsupported and deprecated features
WebSphere Application Server Network Deployment 8.5.5: Deprecated features