For Windchill 12.1.1.0 and higher, the Arbortext Publishing Engine Worker can pass the document and graphic content that Arbortext Publishing Engine needs for publishing in a payload. This way Arbortext Publishing Engine does not need to call back into Windchill to fetch the compound document components that are being published. Whenever the com.ptc.arbortext.wvs/ PreferAdapter setting in the publishing rule is set to no or never, the payload method will be used. When the payload method is used, any two-way or to-xml metadata rules need to be included in a separate CopyMetadataConfig.xml file for the xml content to reflect the correct metadata values during publishing.

Configuring two-way metadata allows to synchronize changes in values that appear in document object metadata as well as inside the document object xml.

You can configure two-way metadata to synchronize changes made to metadata in Windchill into documents published using Arbortext Publishing Engine. You must create a CopyMetadataConfig.xml file to configure this option.

The configuration file uses three elements:

CopyMetadataConfig—The root element

Boundary— Constrains the copy behavior to doctypes with an optional specific root node

Copy— Defines the metadata source, the condition, and the target location

For example,

In this case, at the time of publishing the topic, the content of the title element is taken from IBA2 attribute in Windchill.

The following example shows different ways the target element can be specified::

The XML document must be of the given doctype and start with the root element rootname (if given and not *). In order, these four sample rules copy in the metadata metaname:

The match condition is that the element must have an attribute by the name matchattrname whose value is matchattrvalue.

This file is looked for in (local to the Arbortext Publishing Engine server):

Note that for IBAs (reusable attributes), .bcf files must include the internal name of the IBA whereas in case of CopyMetadataConfig.xml file, you must use the logical identifier of the IBA.

For example, the same twowaymetadatarule added in a .bcf file to set up twowaymetadata in Arbortext Editor is given below:

In Windchill, you must set the value false for the worker parameter com.ptc.arbortext.wvs/disableMetadataReplacer added to your publishing rules for the Arbortext authoring application. See the SamplePublishingRules.xml file located at Windchill-path\codebase\com\ptc\arbortext\windchill\worker for an example. This ensures that any changes made to applicable Windchill metadata are reflected in the published document.

The metadata attributes that are used for two-way-metadata must be included in the payload that is sent from Windchill to Arbortext Publishing Engine. To do this, you need to edit the file manifest_attset.xml and include the attributes. For more information on the manifest_attset.xml file.

The following PTC Server System Attributes are supported values for the source attribute.

If you want to use the above attributes in CopyMetadataConfig.xml file, then you must ensure that their Windchill attributes are included in the manifest_attset.xml file for the DynamicDocument type in Windchill.

For example:

The other PTC Server System Attributes apart from the ones listed above are not supported for two-way-metadata.

See Windchill Help topic Defining Attribute Sets.

For more information about twowaymetadata rule, see the Assigning PTC Server Properties topic.