ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzamm_5.4.0.1/rzammportletcooperative.htm

81 lines
5.3 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Cooperative portlets" />
<meta name="abstract" content="The term cooperative portlets refers to the capability of portlets on a page to interact with each other by sharing information." />
<meta name="description" content="The term cooperative portlets refers to the capability of portlets on a page to interact with each other by sharing information." />
<meta name="DC.Relation" scheme="URI" content="rzammportletconcept.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammportalprint.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammdatabaseportlets.htm" />
<meta name="DC.Relation" scheme="URI" content="pfiles.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammportalprint.htm" />
<meta name="DC.Relation" scheme="URI" content="rzammdatabaseportlets.htm" />
<meta name="DC.Relation" scheme="URI" content="pfiles.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2003, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2003, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzammportletcooperative.dita" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Cooperative portlets</title>
</head>
<body id="rzammportletcooperative.dita"><a name="rzammportletcooperative.dita"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Cooperative portlets</h1>
<div><p>The term cooperative portlets refers to the capability of portlets
on a page to interact with each other by sharing information. </p>
<p>One or more cooperative portlets on a portal page can automatically react
to changes from a source portlet triggered by an action or event in the source
portlet. A source portlet is the sender of information that will be consumed
and processed by a target or receiving portlet. Portlets that are targets
or receivers of the piece of information can process the information and react
by displaying the appropriate information in their portlet content area. Cooperation
between source and target portlets is facilitated by a WebSphere<sup>®</sup> Portal runtime entity called
the property broker.</p>
<p>Portlets on a page can cooperate in this way even if they were developed
independently and are part of different applications. The only requirement
for this to work is both the sender portlet and the receiver portlet of a
piece of information need to be on the same portal page, and be set up to
handle the same type of information. By default a manual action is required
for source portlet information to be sent to a target portlet. This manual
action is called Click To Action (C2A). If an automatic sending of the information
is desired, the portlets can be "wired" together. An administrator can do
the wiring by using the IBM<sup>®</sup> Wiring portlet. In this scenario, the piece of information
will automatically flow to the correct receiving portlet when an action is
taken in the source portlet. End users or administrators can also wire two
portlets together by holding down the CTRL key while clicking on the Action
icon on the source portlet. This source-target relationship will be honored
until a user holds down the CTRL key and clicks on the Action icon a second
time.</p>
<p>iSeries™ Access
for Web's portal functionality includes multiple cooperative portlets. The
functional areas containing cooperative portlets include: Database, File,
and Print. See the detailed information in these sections to determine which
portlets work together to provide a more advanced set of functionality.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzammportletconcept.htm" title="Learn about portlets, cooperative portlets, and issues pertaining to WebSphere Portal's Cross Site Scripting (CSS) security protection configuration.">Portal concepts</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzammportalprint.htm">Print</a></div>
<div><a href="rzammdatabaseportlets.htm">Database</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="pfiles.htm" title="The iSeries Access portlets provide support for accessing files on i5/OS.">Files</a></div>
</div>
</div>
</body>
</html>