WVS uses publishing rules to control how published output is produced. You must be experienced in writing WVS publishing rules and knowledgeable about the information in WVS Publish Rules.

WVS publishing rules must be set up on Windchill PDMLink so users can choose a publishing rule and WVS can send the associated publish parameters to Arbortext Publishing Engine. Publishing rules must have a clear name and description to distinguish them to the user. When a publishing rule is selected, its contents are transformed into an XML file that WVS sends to Arbortext Publishing Engine. The publishing parameters are put into a pubspec.xml file in the payload. There is a pubspec.xml file in the Service application containing default values for parameters not specified in the file sent from WVS. You can check this file:

For more information on configuring the Service Worker and, refer to Service Worker and Publishing and Service Publishing Rules for WVS.

The Service (or SIS) Worker parameters control the publishing process. Worker parameters are specified in the publishing rule using the following form:

A worker parameter specification is part of a param-set which is passed to WVS when publishing processing begins. For Service Information Manager publishing, you can target a parameter to a specific system or subsystem used by the publishing process.

The Service Worker parameters are documented in Service Worker Parameters.

The option parameter type can specify an ACL debug parameter that reports trace information. For example:

In a publishing rule, the specification could look like the following:

The pe/option:debug parameter runs on Arbortext Publishing Engine. If Arbortext Publishing Engine is configured to save intermediate files in the Transaction Archive, the trace report is listed in the zip archive as the debug option trace file with a content type of text/plain. If the artifactsDirectory is specified, the trace file is stored there, and it has the form trace_timestamp.log. If both are specified, the trace report is placed in both locations.

To register a post-conversion delegate, the publishing rules must use the PostConvertDelegate Java class.

For more information on these Java classes and others, see Advanced Customization of Publishing.

You should set the publishing rules to apply the saved document filters while publishing a service structure from the Representations/Annotations table. To do so, add the following rules for describing, reference and configurable documents respectively to the sampleruleathens.xml file: