The generic XML Digital Data Connector plug-in

Use the IBM Digital Data Connector for WebSphere Portal plug-in directly to integrate remote XML data without coding. We can integrate arbitrary XML document formats using list-rendering profiles, which describe the transformation between a specific XML document format, and the generic bean list data structure generated by the DDC plug-in. We identify the generic XML DDC plug-in using...

[Plugin:ListRenderingContext extension-id="ibm.portal.ddc.xml"]

The generic XML DDC plug-in supports the attributes shown in the following list. We specify these attributes when setting up the list-rendering context using the ListRenderingContext tag provided by WCM.

source

URI that serves the XML data. Must be accessible through the portal resource addressability framework. Supported URI schemes include http, https, and dav. If we access external XML data using http or https URLs, adjust the outbound HTTP connection to allow outbound access to these URLs.

[Plugin:ListRenderingContext action="set" 
 extension-id="ibm.portal.ddc.xml"
 profile="ibm.portal.atom"
 attribute="source=https://www.ibm.com/connections/communities/service/atom/catalog/public"
 compute="always"

sortCriteria

Sort the content of a bean list based on a specific attribute. This sorting attribute must be defined in the list-rendering profile the current list-rendering context uses. This built-in sorting capability sorts only the data contained in the current bean list. Do not use this attribute if the bean list represents only a fragment of a larger result set. Instead, provide the sorting process by the backend service. If not specified, the bean list maintains the sequence of items as served by the external data source. To specify the sort order, use the sortOrder attribute.

sortOrder

Use this attribute in combination with the sortCriteria attribute to specify the sort order. Supported values are asc and desc for sorting in ascending or descending order. Example:

[Plugin:ListRenderingContext action="set" 
 extension-id="ibm.portal.ddc.xml"
 profile="ibm.portal.atom"
 attribute="source=https://www.ibm.com/connections/communities/service/atom/catalog/public"
 attribute="sortCriteria=title" 
 attribute="sortOrder=asc"]

cacheScope

cache scope for bean lists resulting from a specific list-rendering context. Supported values:

public

Default. If set to public, the cached bean list values are shared across users.

private

If set to private, individual bean list objects are cached per user. Specify private if the bean lists contain user-specific information.

Example:

[Plugin:ListRenderingContext action="set" 
 extension-id="ibm.portal.ddc.xml"
 profile="ibm.portal.atom"
 attribute="source=https://www.ibm.com/connections/communities/service/atom/catalog/my"
 attribute="cacheScope=private" 
 compute="always"]

cacheType

Cache type to be used for bean lists resulting from a specific list-rendering context. Supported values:

invalidateOnLogin

If we use this setting, cached bean list objects are invalidated if the user for whom the bean list was computed logs in to portal. Use this value only in combination with the setting cacheScope=private.

default

If we use this setting, resulting cached bean lists are not invalidated during user login.

invalidateCache

Invalidate the bean list. If set to "always", the bean list is always invalidated before the new list-rendering context is set up. In other words, the bean list is recomputed for each rendering. To achieve a conditional invalidation, we can set the attribute to a different value. In this case, the cache is invalidated only if a portlet session attribute or a request attribute with the specified value is available in the current execution context.

clearCache

Clear the bean list cache. If set "always", the cache is always cleared before the new list-rendering context is set up. To achieve a conditional clearing action, we can set the attribute to a different value. In this case, the cache is cleared only if a portlet session attribute or a request attribute with the specified value is available in the current execution context.

Parent Integrate remote XML data

Related concepts:

Outbound HTTP connection