Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Deprecated features

This topic summarizes features that were available in previous versions of IBM^® WebSphere^® Portal Express but are no longer available in this version.

As they become available, links to additional information will be provided to help you migrate away from deprecated features.

IBM Portlet API

The IBM Portlet API is being deprecated for this version but is still supported. No new functionality will be added and it is recommended that you use the Standard Portlet API.

Exchange, Domino, and POP3 are no longer supported protocols in the Common PIM Portlets.

If you had been using CPP with Exchange, you can now use the Exchange portlets

If you had been using CPP with Domino, you can now use the Domino Web Access portlet.

The calendar portlet is no longer being shipped.

If you had been using CPP with Exchange, you can now use the Exchange portlets

If you had been using CPP with Domino, you can now use the Domino Web Access portlet.

Collaborative Portlets

The following collaboration portlets are deprecated:

• Team Workplaces (launch portlet)
• Lotus Instant Messaging Connect (launch portlet)

Instead of using these launch portlets, you can add universal resource locaters (URLs) to your site's Bookmarks portlet to open an IBM Lotus^® QuickPlace^® or the Lotus Sametime Center, if you have Lotus QuickPlace and Lotus Sametime servers in your environment.

Use a URL like this for Sametime:

http://your_sametime_server_name.your_domain_name.com/stcenter.nsf

Use a URL like this for Lotus QuickPlace:

http://www.your_site.com/home.nsf/welcome/quickplace

The collaboration file deppwelcome.war is also deprecated. The information from this file is now included in an information portlet.

Domino and POP3 are no longer supported for CPP portlets.

Special Member Manager attribute for the People Finder portlet

The attribute ibm-personAwarenessIdentity is deprecated from the Member Manager schema. This attribute's purpose was to resolve problems with people awareness in a portal site with a different LDAP service configured for Lotus Sametime or Lotus QuickPlace (for example, Lotus Domino LDAP) than for People Finder, which uses the LDAP directory configured for WebSphere Portal Express. A person's DistinguishedName (dn) may be different in the different directories, causing person links that appear in Lotus Sametime or Lotus QuickPlace portlets to be unable to open the Profile and Organization View of the found person.

Instead of using the attribute, you can use either of the following methods to resolve problems with multiple LDAPs:

• You can use an identical schema in the different directories, and ensure that each person's DistinguishedName (dn) is the same in the two directories.
• If use different LDAP directories with different schemas, then you may create alias mappings between users in the People Finder LDAP directory and the same users in the other LDAP directory or directories. Consult your LDAP documentation for information on creating alias mappings.

IBM Lotus Web Content Management™

• DreamWeaver plugins to enable users to create links to Web Content Management items have been removed. Users should now use the linking feature in a rich text element.
• The Web Content Management search feature is no longer supported. WebSphere Portal Express search should be used instead.
• The use of "connect tags" to aggregate data from databases or aggregate content from Web pages is no longer supported. Alternate methods to aggregate data and Web content are documented in the information center.