Scope of Transmitted Data 

Content

Data	Transportable?
Documents	Yes (see Documents section below)
Folders	Yes (see Folders section below)
Links	Links are transmitted, but target items are not. If the target item of a link does not exist in the subscriber’s system, the link does not work.

Documents

The content exchange service is used for distributing large quantities of data. The ICE protocol can transmit content data in any file format.

The content is not only referenced – it is actually downloaded to the subscriber’s repository. The original files are encoded (in Base64) and embedded into an ICE package that is then transmitted to the subscriber. When the exchange process has finished, copies of the physical files are stored in the subscriber’s repository.

To reduce volume, the syndicator can decide not to transmit large files as part of the package.  In such cases, subscribers can download the files from a URL instead. You can restrict the download to a certain time period when you know the server load will be low. The subscriber’s system carries out the download automatically as long as the password for accessing the content is known, or the syndicator has allowed anonymous access.

The syndicator can use filters to restrict which documents are to be transmitted. For example, the syndicator may want only files with certain file name extensions to be transmitted, or only documents created within a certain time frame.

 

Folders

The syndicator can specify one or more folders for an offer. The subscriber receives the specified folder/s with all subfolders and content contained therein. The same folder hierarchy is formed in the target repository as in the source repository.

The syndicator can use a filter to restrict the maximum depth of the transmitted folder hierarchy.

 

Repository Services Data

Data	Transportable?
Ratings	No
Status Management	No
Time-Dependent Publishing	No
Layout Service	No
Access Statistic Service	No
ACL	Yes
Service ACL	No
Versions	Only the current version is transmitted in each transport. For more information, see Versions below.
Discussions	No
Subscriptions	No
Feedback	No
Comments	No
Personal Notes	No

 

Permissions

When permissions are defined for a folder or document, the list of permissions (ACL) is transmitted to the subscriber's system. If the folder referenced in the offer has no ACL, the system transmits an inherited ACL from one of the superordinate folders.

 

Versions

Only the current version is included in an ICE package in the source system and transmitted to the target system.

If versioning is active in the target system, the document from the ICE package is placed into the target repository as the current version. The last available version in the target system is retained as an old version.

The version numbers for syndicator and subscriber are only the same if every version is transmitted.

Example: Versions in Syndicator and Subscriber Systems

The graphic above is an example of versions of a document in the repositories of the syndicator and subscriber. Firstly, version 1 is created in the syndicator’s system and transmitted to the subscriber. Version 2 is then created. However, the next transport does not take place until after the creation of version 3. Version 3 is transmitted in this next transport. The subscriber’s repository now gives the document the next available version number - in this case, 2.

 

Properties

Data	Transportable?
System Properties	Yes (see below for special cases)
·        Created On	Yes, if the following prerequisites are met: The target repository must support the import of this property. This is the case for the CM repositories, for example. If the target repository does not support the import of this property, the system enters the date on which you imported the item into the repository. You must use HTTP transfer. When you import offline packages, the import of this property is not supported.
·        Created By	Yes, if the following prerequisites are met: The target repository must support the import of this property. This is the case for the CM repositories, for example. If the target repository does not support the import of this property, the system enters the name of the user who imported the ICE package into the target system. In the case of HTTP transfer, this is the ICE service user. You must use HTTP transfer. When you import offline packages, the import of this property is not supported. The same users must exist in the target system and the source system.
·        Changed On	No The system enters the time at which you imported the ICE package into the target system.
·        Modified By	No The system enters the user that imported the ICE package into the target system. For HTTP transfer, this is the ICE service user.
Application-Defined Properties (such as Valid From and Valid Until for time-dependent publishing)	No
Predefined Properties (properties that you defined in the configuration of Content Management).	Yes, if the following prerequisites are met: You have saved the properties with every item. You defined the properties identically in both systems. See below for further information.
Metadata of Properties	No
Custom Properties (properties that you can define freely in the Details dialog box).	Yes

 

Predefined Properties

Properties that you defined in the configuration of Content Management are only transported if you save them in the syndicator system with the document in question before creating the ICE package. You normally select property values in the Upload dialog box or in the Details dialog box, and then save them there.

Defining the properties in the configuration is not sufficient. You must save the properties for each document.

The save action is the deciding factor. If you do not assign and save values, the property names are transmitted with empty values.

To be able to work with predefined properties in the subscriber system, you must define them as identical to those in the syndicator system. Make sure that the IDs and values of properties in the subscriber system are exactly the same as those in the syndicator system.

If the subscriber system has a property with the same name but a value that is different to the syndicator system, data inconsistencies may occur.

Only the ID and value are transmitted in the ICE package. The metadata that you defined in the configuration of Content Management is not included. You should therefore ensure that the metadata is identical in both systems.

For example, if you marked a property in the syndicator system as write-protected, but did not do so in the subscriber system, users in the subscriber system will be able to change the value.