Additional Windchill Capabilities > Service Information Management > Configuring Windchill Service Information Manager and Service Parts > Service Publishing Setup > Bundle Publishing Output
  
Bundle Publishing Output
A bundle is a type of output that is used as input to InService. The file sent from WVS is called a payload, which contains the content and metadata to be processed by Arbortext Publishing Engine. The bundle is then produced in a format for use by InService based on either XHTML or XML.
A bundle requires that the output type and parameters to be applied during publishing are specified in a publishing rule selected by the user. For more information, see Creating Service Publish Rules and Service Worker Parameters.
The XML bundle is specified in a publishing rule as output="xmlbundle". The XML bundle publishing process produces content in XML.
* 
Information on how Servigistics InService uses bundles is provided in its documentation.
The bundle file can contain a variety of files and a manifest. For information about the content of payloads, refer to Payload and Manifest.
Setting the Service Effectivity Data Format
By default for bundles version 2.2 and earlier, service effectivity data is stored in the payload in manifest.xml as several properties of the target’s Object element. For example:
<Object uri=...">
...
<Metadata id="ServiceEffectivity_183695" source="...">
<Property token="thePersistInfo.updateStamp">
<Value>2016-06-121 18:12:44.0</Value>
</Property>
<Property token="beginDateRange">
<Value>2016-06-21 00:00:00.0</Value>
</Property>
<Property token="thePersistInfo.modifyStamp">
<Value>2016-06-21 18:12:44.0</Value>
</Property>
<Property token="effTarget">
<Value>EPMDocument_183639</Value>
</Property>
<Property token="effectivityType">
<Value>date</Value>
</Property>
<Property token="effContextReference">
<Value ref="x-wc://3f81b557fbc1da98:wt.part.WTPartMaster:0000000003"/>
</Property>
</Metadata>
...
</Object>
Alternately, you can choose to store service effectivity data in APEX format. To do so, set the useApexServiceEffectivity property to “true” in the Windchill site.xconf file as follows:
<Property name="com.ptc.arbortext.windchill.publisher.toggle.
useApexServiceEffectivity" overridable="true" default="true" />
Setting the useApexServiceEffectivity property to “true” stores the effectivity data in APEX format in the first Metadata element of the target’s Object element. For example:
<Object uri=...">
<Metadata id="EPMDocument_183639" source="...">
...
<Property token="ServiceEffectivity">
<Value>(AND (PRODUCT 'x-wc://3f81b557fbc1da98:wt.part.WTPartMaster:0000000003')
(DATE_RANGE '2015-12-01 00:00:00.0' ''))</Value>
</Property>
...
</Metadata>
...
</Object>
Be aware that the following properties will not appear in the APEX format:
• thePersistInfo.updateStamp
• thePersistInfo.modifyStamp
• effTarget
The value of the effTarget property is the same as the id attribute of the Metadata element where the APEX Service effectivity data resides. The thePersistInfo.updateStamp and the thePersistInfo.modifyStamp properties do not appear in the payload.
To use APEX-formatted effectivity data with bundle version 2.2, you must set useApexServiceEffectivity to “true”. For bundle versions later than 2.2, APEX-formatted effectivity data is the default. For those versions, set useApexServiceEffectivity to “false” to avoid using APEX formatted effectivity data.