The Arbortext Publishing Engine Query Structure
HTTP requests contain instructions for returning some kind of file or message to the HTTP client making the request. This query is constructed from a function and its parameters, and it's designed to convert documents or deliver other files or messages to the HTTP client. Arbortext Publishing Engine Test Utility provides a user interface for creating HTTP requests to test your custom Java, JavaScript, or ACL applications.
|
|
The basic sample Arbortext Publishing Engine applications that retrieve information about the Arbortext Publishing Engine environment are included in the PE_HOME/e3/samples subdirectories. There is one each for ACL, Java, JavaScript, and VBScript.
|
The query must include a name=value statement specifying one of the unique Arbortext Publishing Engine function names. Arbortext Publishing Engine Test Utility generates these name=value pairs based on information you specify in the appropriate test editor.
• f=java
This function specifies a custom Java application whose name is specified in the accompanying class=class-name statement.
• f=javascript
This function specifies a custom JavaScript application whose name is specified in the accompanying function=function-name statement.
• f=acl
This function specifies a custom ACL application whose name is specified in the accompanying function=function-name statement. (The old style p0=function-name is still supported in this release, but you should migrate to the function form of the query.)
• f=convert
A built-in Arbortext Publishing Engine function for handling document conversion. It takes a set of parameters that control a variety of document manipulations.
Refer to the Programmer's Reference for more information on creating Arbortext Publishing Engine HTTP requests.
