Wiring cooperative portlets

For portal projects, you can configure wires between same-API portlets within the same portal page. This capability is only available for WebSphere® Portal 5.1 portal projects.

Portal Designer provides Page properties in the Properties view that enable you to configure wires. The Wires Properties page lists configured wires and provides possible candidates for source portlets, output properties, target portlets and actions that are required to create a wire. This page allows you to add or remove wiring information. Wiring options are based on cooperative capabilities that have already been configured for specific portlet projects used in the portal page.
Note: There is no way to edit a configured wire. If you want to change wiring properties, you have to remove the existing wire and create a new one with the appropriate properties.
Some wiring capabilities require the related portlet projects to be in your workspace to retrieve portlet information. However, all portlet projects of portlets in the selected page do not always exist in the workspace, for example, if you work with the portal project that you imported from WebSphere Portal. The following table shows which functions are supported when a portlet project does not exist in the workspace. (All are supported when the portlet project exists in the workspace.)
Function Available without a portlet project in your workspace
Add a wire No
Remove a wire Yes
Note: Be careful when removing wires from portlets whose portlet projects do not exist in the workspace, because you cannot re-add those wires if the portlet projects are not in the workspace.
Display configured wires Yes

The Outline view does not display wire elements.

Deploying wires between IBM® portlet API portlets to WebSphere Portal 5.1.0.0 (prerequisite)

To deploy new wires between IBM portlet API portlets defined using Portal Designer to a remote server, you must perform the following steps first:
  1. Locate the ConfigService.properties file in the wp51_installdir/PortalServer/shared/app/config/services directory.
  2. Open the ConfigService.properties file, and set the host.name and host.port.http properties to the hostname and HTTP port of the target portal server used for the import.
  3. Save the file.
  4. Restart WebSphere Portal.
Note: These steps are not required for using the WebSphere Portal 5.1 Test Environment. They are required only for deploying to a WebSphere Portal 5.1.0.0 remote server.
Related concepts
Developing cooperative portlets
Related tasks
Adding wires
Enabling existing portlets for cooperation
Enabling cooperative sources
Enabling cooperative targets
Inserting Click-to-Action encodeProperty
Inserting Click-to-Action encodeProperties
Editing Click-to-Action encodeProperty
Editing Click-to-Action encodeProperties

(C) Copyright IBM Corporation 2002, 2005. All Rights Reserved.