In this example, log=1 turns debugging on (log=0 turns it off) and logdir is the directory where the log file is created. The log file is named arswww.log.
9.3.2 Using the AFP2PDF transform with ARSLOAD In the previous example, we discussed a transform that occurred on the retrieval side. Xenos can also perform the transform during ARSLOAD, before the print file gets loaded to OnDemand. In addition to transforming the data, Xenos can also provide indexing and resource collection capabilities as well as print file segmentation into logical documents or statements. To enable the Xenos transforms on the load side, you must specify the indexer to be Xenos in the OnDemand application. When ARSLOAD sees an indexer of Xenos, it calls the Xenos transform with the parameter and script files that are specified in the application. Xenos creates three files to be sent back to ARSLOAD, the index file, the output file, and a resource file. ARSLOAD uses these files to update the database and object server. When using Xenos to parse the input printstream file, it is possible to allow the transform to pull indexes from the file and to split the file into logical documents. When doing this, it is important to define the same database fields in both Xenos and OnDemand. Xenos provides an .ind file that contains each field and the value. If OnDemand receives too many indexes or not enough indexes, or if the indexes are a different data type, the load fails. This example discusses the conversion of an AFP document to an Adobe PDF format before loading it into OnDemand. This PDF format can be viewed through the OnDemand client and the ODWEK client with the Adobe Acrobat software. We first used Xenos Developer Studio to select field locations from the document and define document splitting rules. We also created a script file (Example 9-22 on page 302) and parameter file (Example 9-23 on page 306). The parameter file defines the parser and generator that we use. It also contains the locations of the AFP resources to be used to convert the file, and the rules for creating the PDF file. Finally, the script defines the data to be used as the index for the document. In this example, we only define one index field, Name. We created an application and application group called xenos-pdf. We are loading AFP data, but because Xenos converts it to PDF before it is loaded, we define the View Information data type to be PDF. In the Indexer Information page, the indexer is defined as Xenos; this directs OnDemand to call the Xenos transforms. When you use Xenos as the indexer, there are only four parameters in the indexing details: Xenos parameter file, Xenos script file, Xenos License file, and warning level. See our application as set up in Figure 9-13.
300
Content Manager OnDemand Guide