Configuring Publishing for Arbortext Authored Dynamic Documents
This section describes the configuration process for publishing Dynamic Documents that were created using Arbortext Editor.
The WVS framework allows the publishing of Dynamic Documents authored using Arbortext Editor. To configure publishing of these documents, you must configure the WVS Publisher for the Arbortext Editor using wvs.properties. You can then define and load rules for publishing the documents. These are called publish rules.
Windchill Visualization Services (WVS) provides a framework that allows the publishing of EPMDocuments to create a Representation for visualization. This publishing is accomplished using a worker, and is managed by the Worker Agent. Dynamic Documents are a soft type of EPMDocument, so the framework supports them in the same manner.
WVS sends a request to the Arbortext Publishing Engine based on specified publish rules. These rules specify when the Representation is created, such as upon check-in, and the desired Representation format, such as PDF and HTML. Once the Representations are created, WTDocuments can be created and linked to each Representation of the Dynamic Document with a PublishedContent link. The new WTDocument can be used as part of a downstream business process.
Configuring the WVS Publisher for the Arbortext Editor
In order for the Arbortext Publishing Engine to download input files from Windchill and subsequently upload the output file, an authentication file is needed. This file is typically called auth.properties.
|
|
The wvs.properties file, located in the <Windchill>\codebase\WEB-INF\conf directory, contains the following property setting, which defines the location of the auth.properties file. If you change the location of this file, you must edit this property accordingly.
publish.cadconvert.ARBORTEXT=com.ptc.wvs.server.publish.CadConvertARBORTEXT,
useworkerdownload=$(wt.home)$(wvs.dir.sep)auth.properties,
types=PDF HTML WEB POSTSCRIPT HTMLHELP SGML XML RTF DMP 3D,
defaulttype=PDF
|
To configure the auth.properties file, follow these steps:
1. Create the auth.properties file in your <Windchill> root directory (also known as %WT_HOME%) using a text editor
2. Add an authentication variable that includes a user name and an optional password value. This is the only entry in this file. The syntax would be either of the following:
auth=username
auth=<username>:<password>
To use auth=<username>:<password>, set the value com.arbortext.e3.allowAuthenticationWithoutTrustedHost in e3config.xml to true on the Arbortext Publishing Engine server.
|
|
PTC recommends the use of auth=<username>:<password> in demo or test servers only.
|
3. Replace <username> and <password> with valid values. The user must have enough privileges to read and download all Dynamic Document structures stored in Windchill that need to be published.
4. Save your changes and close the auth.properties file.
5. In the publish.cadconvert.ARBORTEXT property described previously, a default location of $(wt.home)$(wvs.dir.sep)auth.properties is provided for the auth.properties file. If you use a different location for this file, be sure to edit this property value to reflect the updated path. You must use the xconfmanager utility to make this change:
xconfmanager -s
"publish.cadconvert.ARBORTEXT=com.ptc.wvs.server.publish.CadConvertARBORTEXT,
useworkerdownload=$(wt.home)$(wvs.dir.sep)auth.properties,
types=PDF HTML WEB POSTSCRIPT HTMLHELP SGML XML RTF DMP 3D,
defaulttype=PDF" -t <Windchill>\wvs.properties
-p
6. Restart the Windchill servers.
|
|
The wvs.properties file contains a setting (called publish.usesPublishRules=ARBORTEXT). If this property is deleted or ARBORTEXT is removed, WVS does not use Publish Rules for Arbortext-authored Dynamic Documents. This is not recommended.
|
|
|
WVS supports Trusted Host Authentication. This feature allows workers to authenticate without a password, which enables the ability to use the "real user" for authentication during publishing operations.
|
Publishing Arbortext-Authored Dynamic Documents
Publishing of Dynamic Documents is controlled by Publish Rules. See
About Publish Rules for details.
