I am currently researching the various PTC tools (ArborText Editor, Publishing Engine) for API information. What I am looking for is a way to publish a document in the various supported format. In essence, mimick the GUI behaviour but from a script. Based on searching the threads and some of the reference documentation, I have a couple of questions.
- Is the ACL reference shared amongst the tools (PE and Editor)?
- Is it possible to run a script (Java, Perl etc.) OUTSIDE of ArborText Editor (the Programmer's Guide seems to indicate that this is not possible) and publish a document? Or should one access the PE in Windchill to publish a document?
There are many ways to use the publishing functionality.
There is loads of ACL code that ships with the application. This implements a lot of the GUI functionality, so you can reuse those functions in your own code, e.g. to publish. Just do a bit of fossicking through the *.acl files.
Thank you. I wanted to do a sanity check becasue I thought wach Arbortext product has its own API.
I would like to futher my check based on your responses...
There is a considerable amount I wish to cover with this research and I am learning the tool as we go. There is a picture within the Programmer's Guide that shows Editor and PE can be accessed with a Java application/script. But we want to be able to publish and not have to launch the GUI. If this is not possible and the only way to accomplish this is to use the folder structure to store our scripts, then I would like to demo such functions.
This looks promising...
Will update with newer questions.
Batch mode (batch processing): https://en.wikipedia.org/wiki/Batch_processing
Yes you can publish without using the GUI, no problem at all. You make HTTP or SOAP requests to PE and it will do the necessary. You can pass files "over the wire" or by placing them on a file share accessible to the PE machine and pointing PE to those files. You do need to ensure your doctypes (custom folder) is up to date on the PE machine and registered with PE. The custom folder is what will contain your DTD/Schema and stylesheets.
I have looked into the WVS portion for publishing an XML to PDF and I see that WVS is used more with/for the Creo View. The documentation indicates that one would need to install WVS and configure WVS to use the PE for publishing. Would this suffice for an XML to PDF conversion?
Also, if WVS leverages PE, what really is the difference between WVS versus PE?
WVS (Windchill Visualization Services) is the connector between the Windchill repository and the Publishing Engine service. It is an integration tool, nothing more.