TAL Cleanup Prior to Loading a Full Re-Published Bundle
The bundle artifact file PublishInfo.xml tells Servigistics InService how to process the bundle. In particular, the element JobSpecification has three important attributes:
<JobSpecification date="2015-06-10 21:09:59:830" increment="0" incremental="false">
• date – Provides the timestamp of the job.
• increment – Indicates how many times the bundle has been published.
The value of the attribute is zero for a full bundle and incremented thereafter by one for each successive incremental publish. This enables Servigistics InService to detect out-of-sequence bundles (gaps in publishing), a publishing job failure, or a bundle arriving out of sequence in a parallel publishing case.
• incremental – Indicates whether this is a full or incremental publish.
The value of the attribute is either false for a full publish or true when the bundle is an incrementally published bundle.
The combination of timestamp and increment related values enables Servigistics InService to detect gaps and ensures that only the newest version is loaded in the correct order.
Manual Cleanup Prior to Loading a Full Re-Published Bundle
When re-publishing a full bundle that has previously been incrementally published, the data that was previously in the bundle might have been excluded in the new re-published bundle. In this case, the TAL process for the re-published bundle will not fail but it is recommended that you perform some manual clean-up to remove leftover publishing data from the Servigistics InService storage.
Following are some alternative approaches for this manual cleanup:
• The simplest and safest approach is to use the Delete Segment From Sites and Remove Segment Configuration Setting tasks in Task Manager to delete the segment.
However, note that this approach requires that you run TAL process again on all content in the segment so it might not be a viable option.
• You can also use the Clean Environment task in Task Manager.
• Another approach is scripted cleanup. You must be careful to avoid mistakes with this approach.
Follow these steps to perform a selective manual cleanup:
1. Edit the contents of a Px bundle as follows:
a. Identify the objects that are present in earlier versions but now missing in the re-published bundle.
b. Include the missing objects as a part of the excluded objects in the bundle file excludedObjects.xml. Be sure to follow the required structure of the file.
2. Load the manually edited bundle to trigger the deletion of the corresponding objects.