Configuring TAL with the Configurator Utility
Servigistics InService provides the Configurator utility to assist you with the process of creating and updating all of the configuration files required for deploying the system. The Configurator provides a TAL entity contains various configuration properties for the TAL process. Note that you must publish any TAL changes made in the Configurator and restart the JBoss server before those changes take effect.
The TAL entity provides the following properties for TAL configuration:
• Enable Content Sharing Mode
In Servigistics InService, 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 unshared mode applies to data sources where the source’s contexts belong to collections that are in different segments.
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, Servigistics InService 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.
|
|
You should decide whether to enable this feature before loading any data into your system. Once data has been loaded in your system, you should never change the setting of this feature. If you do, then you must transform and load all of your data again.
|
• Enable BOM Filtration
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.
• Enable Offline Configuration
You can specify whether data will be loaded for use in offline systems. Refer to the Servigistics InService Offline Systems Guide for more information.
• Organization Names
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”.
• Part Relationships
Servigistics InService supports the following types of relationships between parts:
◦ Supersession
◦ Alternate
◦ Cross Reference
◦ Supplementary
◦ Kit
The Configurator enables you to specify the types of relations ships you want to support.
• IMAN
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.
• Email Notifications
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.
|
|
The transformation process generates notifications with admin as the alias.
|
Refer to Using the Servigistics InService Deployment Configurator Utility in the Servigistics InService Deployment Guide for more information about the Configurator utility.
