Connecting Content Items in a Page
Use
To integrate data or functionality between content items in a page, you can define connections between content items. For example, by defining a connection between a list of suppliers and Google Maps, each time the user selects a supplier in the list, Google Maps displays the address of this supplier. This type of integration is also referred to by the term "mashup".
Connections between content items are made via ports and their parameters. For example, the list of suppliers has an out port that transfers the supplier address, and Google Maps has an in port that accepts an address parameter. By connecting between these parameters when creating the page, you enable the integration between the content items at runtime.
The workflow for connecting content items in a page involves the following steps:
-
The administrator and/or developer creates content items that can be connected, as described in the table below.
-
The key user defines and manages connections.
To define connections between content items in a page, use the graphical connection editor. For more information, see Defining Connections Between Content Items .
To manage the connection ports and parameters of a content item, use the Settings editor. For more information, see Managing Connection Ports and Parameters .
The actions required to make a content item connectable depend on the type of the content item. The following table describes the different content item types, whether they can be a source or a target or both, who makes them connectable, and possible actions in the Web Page Composer editing environment:
|
Content Item Type |
Source and/or Target |
Actions Available to Key Users |
Made connectable by: |
How |
|---|---|---|---|---|
|
Deployed application iView A newly created Web Dynpro Java or Portal Application. |
Source and/or target |
Modify or add tags to a parameter |
Developer |
For more information, see Enabling Connections Between Content Items in a Page . |
|
Manually-created Application Integrator iView For example, and iView on top of an ABAP backend application |
Source and/or target |
|
Administrator |
For more information, see Managing Connection Ports and Parameters . |
|
OBN iView |
Source: if the content item has an OBN source link TargetL if the content item is configured as an OBN target |
Only view details |
Developer and Administrator |
The developer implements an OBN source and the administrator defines an OBN target. The OBN metadata, which is used for connections, is resolved automatically. |
|
External Content For example, Google maps. |
Target only. |
|