Publishing a Bundle from an Information Structure
The following lists prerequisites for publishing:
• An information structure for a product must be set up in Windchill.
• A WVS Service Information Manager Worker (also know as a SIS Worker) must be set up in Windchill.
• A Windchill Visualization Services publishing rule must be set up in Windchill.
In the Navigator pane, choose a Windchill Service Information Manager product.
1. Expand the product and open the Information Structure folder.
2. On the Information Structure page, highlight the top level of the information structure.
3. On the toolbar under
Publish, choose
Representation. The
Publish Representation window opens.
4. In the Publish Representation window, provide a Name and Description. Choose a Publishing Rule from the list, and choose whether you want the representation to be the default.
5. Click Submit Publish Job. A confirmation message displays, stating that the job was submitted.
| You can monitor the progress of your job through the WVS Job Monitor. To access the WVS Job Monitor, click the WVS Job Monitor link in the confirmation message. |
Published bundles are not returned to WVS. The bundle output is prepared and staged by
Arbortext Publishing Engine for use by
Servigistics InService. For information on the worker parameters that set the bundle file name and location, see
WVS Service Worker Parameters.
If you have published a bundle for an information structure, and then make additions, changes, or deletions to its groups or content, you can perform an Incremental Publish that contains just the content you changed.
Incremental Publish uses the same publishing rules and configuration specification that were applied to the initial full publishing action, so these must still be configured on the Windchill server.
1. Go to the information structure Representations tab.
2. Choose a previously published bundle representation.
3. On the shortcut menu, choose Incremental Publish.
4. Publishing is performed automatically, and you see a confirmation message.
The incremental bundle is placed on the Arbortext Publishing Engine server where it’s configured to store bundles that have been published.
Choose Refresh from the Actions menu to update the view.
You can apply a version scheme to a bundle to track successive incremental publish operations. For more information, refer to
Bundle Publishing Output.
If the incrementally published bundle representation fails to load to InService, you can perform
Republish Increment to publish that selected incremented representation. For more information, refer to
Republishing an Incremental Bundle Representation.
When publishing bundle representations for big datasets that contain dynamic documents or part list, performance issues may be observed. PTC recommends that you use parallel processing instead of sequential processing for such datasets to reduce the time required to publish the bundle. Configure the following properties in wt.properties file as follows:
• com.ptc.arbortext.windchill.publisher.payload.parallelProcessing—Executes the bundle publishing process in parallel. When set to true, it automatically sets the com.ptc.arbortext.windchill.publisher.payload.numThreads property with the number of CPUs present in the machine and the com.ptc.arbortext.windchill.publisher.payload.batchSize property to 512. The value for thecom.ptc.arbortext.windchill.publisher.payload.numThreads property from automatic detection of cores can be set to a maximum of 10 only. Default value is false.
• com.ptc.arbortext.windchill.publisher.payload.batchSize—Specifies the number of nodes which are processed by one thread at a time. On configuring this property the default value of batch size gets overridden.
• com.ptc.arbortext.windchill.publisher.payload.numThreads—Specifies number of threads to be spawned for parallel publishing. On configuring this property, the default number of threads get overridden.
