TAL Customization
This section describes various Transform Aggregate Load (TAL) customization use cases and the steps to follow when handling specific issues. Customization primarily involves modifying various TAL artifacts on the Publisher server.
TAL tasks process the bundle input into a XML representation understood by PTC Arbortext Content Delivery repository through transformations for different types. For viewing in the user interface, data gets extracted from the repository through view stylesheets and gets displayed through JSON attributes. Similarly indexing and filtering information is provided by type definitions for the different types.
By default, TAL allows the transformation of limited content into PTC Arbortext Content Delivery Repository. If you want to extract more information or want to optimize the search, indexing, or filtering strategy, then you must do customization. In general, TAL customizations are done in the following ways:
• Updates to the transformation to add, update, or remove additional attributes.
• Updates to the Type Definition to add, update, or delete the following types:
◦ Search fields
◦ Document links
◦ Filtering information
• Updates to the view stylesheet to add, update, or remove additional information.
|
|
A customization hook is an intercept point where you make it possible to modify the usual behavior of the TAL process, so both performance and security issues (such as tampering with the data, unintended side effects, and so forth) should be a concern. All custom approaches must be thoroughly examined for these issues.
Note that you can seriously affect TAL performance through customization, depending on how it is implemented.
|
