In PTC Arbortext Content Delivery, the content is split into segments. Each segment is a separate content storage. Content is usually loaded into a single segment based on the collection identifier associated with the input data (bundle). Shared or Non-Shared mode applies to data sources where the source’s contexts belong to collections that are in different segments. The Shared mode is an environment level TAL preference, that must be setup after installation and prior to loading data into the system.

In the case of non-shared mode, a source is loaded only to the collection and segment that is associated with the input’s collection identifier. This is a faster process, since only one segment will be locked and updated. However, this also might result in different versions of the same source document being available for users.

For example, assume a source belongs to collections A, B and C. Collections A and B are in segment X, while collection C is in segment Y. In this case, when an updated source is contained in a bundle that belongs to collection A (or B), then only its instance in segment X will be updated. In this case, a user using a context that applies to collection A or B (that is, to segment X) views the updated version. However, a user using a context that applies to collection C (that is, segment Y) views the old version. Only when the updated source is provided in a bundle for collection C will the segment Y version be updated, and its version will be synchronized with segment X.

In the case of shared mode, the system keeps track of all the instances for each source. Whenever an updated version of the shared source is loaded, PTC Arbortext Content Delivery automatically updates all its instances regardless of the input bundle’s context. This process ensures that all instances of a specific source will always be synchronized. However, this mode takes more time as it requires the loading and locking of multiple segments each time the data is updated.

The decision whether to enable sharing depends on the percentage of the shared content you have, while taking the information above into consideration.

The BOM Filtration builder generates referenced applicability conditions on each of the PartLists. This enables the filtering PartLists based on a PartList and all its ancestors. BOM is also called product instance information.

You can specify whether data will be loaded for use in offline systems. Refer to the PTC Arbortext Content Delivery Offline Systems Guide for more information.

Organization names are used to create persistent IDs for various object types. To improve performance and reduce the memory space required when storing the object IDs in the repository, you should reduce the organization names to a shorter unique string. It is recommended that you provide short notations or abbreviations for any organization name. For example, if organization name is “XYZ Infrastructures Private Limited”, then this can be represented as “XYZ” or “XYZIPL”.

PTC Arbortext Content Delivery supports the following types of relationships between parts:

The Configurator enables you to specify the types of relations ships you want to support.

Identity Management (IMAN) is used to configure the identity attributes and other attributes for a type and source for bundle sources based on SIM data types. Refer to Configuring Identity Management (IMAN) for more information.

You can configure the TAL process to send email notifications regarding the status of the TAL process. For example, you could notify authors if there were data issues in the bundle processing.