Training and Knowledge Center › Knowledge Base and Forums › Knowledge Base › Arbortext › Publishing and Stylesheets › Getting the RDS for a Publication Structure in Windchill
Tagged: Publishing Structure, RDS, windchill
- This topic is empty.
-
AuthorPosts
-
-
June 13, 2024 at 10:04 am #2496Elizabeth FraleyKeymaster
These are the instructions for getting the RDS (resolved document for styler) out of the publishing structure. The general idea is that if you have the Payload, you can open the document from the payload in Editor and then create the RDS. Here is the outline of the process:
- Do a publish from Windchill using PE
- Go to the Transaction archive and download the Payload (instructions at the bottom)
- Unzip the Payload
- Open the Publication structure document in Styler and do File->Publish to PDF (The Pub Structure document will have a name like
0000000241.xml
) - Notice that a techinfomap xml document was created alongside the .pdf
- Open the techinfomap document in Styler
- Do Edit->Edit Resolved Document->For Styling
In addition, you just the e3config.xml setting that will keep the transaction archive for successful jobs. Normally it only keeps the archive for failing jobs.
<Parameter name="com.arbortext.e3.transactionArchive.selector" value="all" />
How to get the Payload
The Transaction Archive is on the PE home page
Since you want to get a transaction archive for a successful job, you will need to change an e3config.xml setting:
<!-- This parameter specifies which kinds of transactions are stored in the --> <!-- transaction archive after completion. Legal values are "none" --> <!-- (archive no transactions), "error" (archive transactions that fail), --> <!-- "log" (archive transactions that fail and transactions --> <!-- that have associated application log entries or intermediate files) --> <!-- and "all". --> <Parameter name="com.arbortext.e3.transactionArchive.selector" value="all" />
This will cause all jobs to be saved. Then you can open the Transaction Archive and download the request payload:
You will get a file called
rqbody.dat
. Just change it to berqbody.zip
and you can open it like a .zip file.There is an alternative method for getting the payload on the Windchill side. Use the payloadCache publishing parameter to have the payload stored on a folder on the Windchill server. https://support.ptc.com/help/windchill/r13.0.1.0/en/#page/Windchill_Help_Center/sim_installconfig/sis7009.html
How to find the RDS inside the Payload
Prerequisite:
Make sure you have the service application installed in your Editor/Styler installation.
Inside the payload, you’ll find an
SM****.xml
file. That’s the Publishing Structure in XML.Steps:
- Unzip the Payload (
rqbody_XXX.dat
) - Open the Publication structure document in Styler and do File->Publish to PDF (The Pub Structure document will have a name
SMXXXXXXXX.xml
)- If you see a stylesheet association error, Fix the Stylesheet Association Error (below) before going to step 3.
- While the Publish dialog is visible, open the windows folder where the .xml file was.
- Notice that a techinfomap xml document was created alongside the .xml In this case it is called
SMXXXXXXXX-techinfomap.xml
- Copy this file because it will get cleaned up by Styler
- Cancel out of the Publish dialog
- Open the copied techinfomap document in Styler
- Do Edit->Edit Resolved Document->For Styling
Where to install the Service Application
This is a prerequisite for working with payload-created, publication structures in Arbortext Styler. You need the DTD for the service application. It comes with PE. You can find it in
application/com.ptc.arbortext.service
Put this entire folder in the application folder in the Arbortext Editor install tree:
How to Fix the Stylesheet Association Error in the Publication Structure document
If you see the following error window, you will need to edit the pubspec.xml to comment out the stylesheet association parameter:
Steps to fix:
- Open the
pubspec.xml
- Comment out the Parameter token=”stylesheet” markup
Now you should be able to continue and publish the
SM****.xml
file.
-
-
AuthorPosts
- You must be logged in to reply to this topic.