Working with Remote Delta Link Content 

Applicable to: remote delta link mode

Whether you have created remote delta links on your consumer portal as local unit objects or have added them directly to local content, you manage the remote delta link content on your portal as you would with other locally created delta link content.

Certain restrictions and limitations apply, as discussed in this topic.

Common Administrative Tasks

Some of the common administrative tasks you perform with remote delta link content on the consumer portal include the following:

·        Assigning remote-based iViews and pages to local pages.

·        Assigning remote-based pages (and iViews) to local worksets and roles.

·        Assigning remote-based worksets to local roles.

·        Assigning remote-based roles to local users and groups.

Creating a remote delta link to a remote role does not include the user assignments made to the source role on the producer.

●      Editing copied objects.

Remote delta link pages on a consumer portal: A content administrator using the Page Editor can only hide existing content in the page, edit object properties, and switch layouts already assigned to the page. The administrator cannot add or remove content and layouts from a remote delta link page.

●      Preparing properties in remote-based iViews and page for end-user personalization.

General portal administration tasks are described in Content Administration.

For information about using business objects in a federated portal network scenario, see Using Object-Based Navigation.

See also Assigning End-User Permission to Producer Objects and Content.

Synchronizing Content Updates

Standard delta link behavior applies to remote delta link content, whereby the source object resides on the producer portal and the target object resides on the consumer portal. For example:

●      If a property is modified in an object on the producer, the modification is applied to the same property in the corresponding remote delta link object on the consumer.

●      However, if a property is modified in remote delta link object on the consumer, the inheritance is broken. Any subsequent modifications to the same property in its source object on the producer are no longer updated in the target object on the consumer; unless the delta link between the objects has been restored (see Resetting Properties).

At set intervals, modifications made by content administrators to source objects on the producer portal are transferred to their corresponding target delta link objects on the consumer portal. A system administrator on the consumer portal can also initiate on-demand updates. For more information about performing a manual content update and setting automated updates, see Configuring the Federated Portal Cache and Clearing and Synchronizing the Federated Portal Cache.

Limitations

In addition to the issues described in this topic, other limitations and restrictions apply when using remote delta link content on a consumer portal. For more information, see the technical aspects described in 'Remote Delta Link' Mode.