Adobe Web Output Pak

Version 2.0.7

Readme

March 2009

Edition 1.1

Copyright 2009 Adobe Systems Incorporated. All rights reserved.

This file contains important information that was not available when the product documentation was written. Review this information before installing this version of Adobe Web Output Pak.

What's New

Supported Platform and System Requirements

Known Issues

The Documentation Set

Licenses and Copyrights

What's New

The What's New (WhatsNew.pdf) contains details on the new features added to this release of Web Output Pak.

Back to Contents

Supported Platforms and System Requirements

The following are the supported Microsoft Windows platforms for Web Output Pak 2.0.7:

Supported Platform

Supported Version

Processor

Microsoft Windows 2000

Server Update Rollup #1 for Service Pack 4

x86 or VMware ESX/GSX

Microsoft Windows 2003

Server (32 bit) Service Pack 2 - Standard and Enterprise

x86 or VMware ESX/GSX

Microsoft Windows 2008

Server (32/64 bit) - Standard and Enterprise

x86 or VMware ESX/GSX

Note: Web Output Pak is not supported on a Microsoft Windows 2000 IPv6 environment.

Back to Contents

 

Known Issues

 

 

Posting XML Data to Web Output Pak

 

You can now post XML data via HTTP to the Transaction Processor. Ensure that the application posting the data includes a contentType (also referred to as MimeType or EncodingType) of  "text/xml".

Ensure the XML is well formed, for example:

    <?xml version="1.0"?>

    <data>

        <user>Tony Blue</user>

    </data>

 

Directory Permissions When Using ASPs

 

When using Active Server Pages (ASP) with Web Output Pak on Windows, you may need to modify the security parameters for your temporary directory's access privileges. This directory could be \tmp, \temp or Windows\Temp.

 

IUSR_Computer and IWAN_Computer User Accounts

 

When trying to process the ASP sample with Web Output Pack the following error is returned:

The following error occurred in step 1:
Operation returned exit status 153

The resolve this problem you must ensure that you give the IUSR_Computer and IWAN_Computer administrative privileges.

 

Dynamic Merge Commands

 

Commands other than ^field cannot be passed when using the Transaction Processor with the data DOM. This is as designed. When using the Transaction Processor with the data DOM, only ^field commands can be passed. Any other Dynamic Merge commands, such as ^form or ^global, will be stripped out of the data passed to Print Agent for processing.

If you need to use global fields, you can get that functionality by setting the global attribute for the field. You do this in the template by accessing the Format Field dialog and setting the Global flag on the field.

 

Using Variable Names in an XPR


When using a variable name in the XML code all the levels of the variable name must be used. For example, if the structure of the XPR file states:

Fulfillment
Contact
Firstname

Then the variable call must be Fulfillment.Contact.Firstname. All the levels in the structure must be used.

 

No Asian Language Support


Web Output Pak is not intended for use with Asian languages.

 

Running on Windows Server 2008 Enterprise Edition

 

If you are installing this version of Web Output Pak on Microsoft Windows Server 2008 Enterprise Edition, you must change a number of

configuration settings in order for the software to run properly.

 

Enable CGI Scripts

CGI scripts are prohibited by Microsoft Internet Information Server (IIS) by default. To have the Transaction Processor (jfxp.cgi) function correctly, you must configure IIS to allow CGI scripts by adding jfxp.cgi to the "ISAPI and CGI Restrictions" list at the server level:

1.      Go to IIS Manager > Machine > Feature View > Open "ISAPI and CGI Restrictions", Action pane > Add.

2.      Specify the jfxp.cgi path here, by default the directory /Inetpub/wwwroot/cgi-bin.

3.      Check the "Allow extension path to execute".

4.      Click OK.

5.        

Handler Mapping for CGI Script

To add handler mapping for jfxp.cgi at site/server level:

1.      Go to Site/Server > Feature View > Handler Mappings, Action pane > Add Module Mapping.

2.      Request Path: jfxp.cgi

3.      Module: CgiModule

4.      Name: JF CGI handler

5.      Click OK.

6.        

Enable Active Server Pages

To ensure that Active Server Pages are enabled:

1.      In IIS Manager > Machine > Feature View > Open "ISAPI and CGI Restrictions"

2.      Set Active Server Pages to Allow.

3.        

 Access to Windows Temporary Directory

You must ensure that the Users account has the Full Control permission set on the C:\Windows\Temp directory.

 

Documentation - Web Output Pak version number

Any references to version 2.0.5 in the documentation should be considered applicable for this version of Web Output Pak (2.0.7).

Back to Contents

The Documentation Set

Web Output Pak includes a complete documentation set to assist you in using the software. The documentation resides in the Documentation folder of your Web Output Pak installation. The Web Output Pak DocMap (DocMap.html) provides central access to this documentation set.  To view the documentation, you must have Adobe Reader installed on your computer.  You can download Adobe Reader from the Adobe website at www.adobe.com.

Back to Contents

Licenses and Copyrights

Web Output Pak incorporates "Libwww - The W3C Protocol Library". Ensure that you read and accept all the terms covered by the following copyright notice and the W3C license:

Copyright Notice: http://www.w3.org/Consortium/Legal/libwww-copyright-notice-19980720.html

Full W3C License: http://www.w3.org/Consortium/Legal/copyright-software-19980720

Back to Contents

 

Readme File -- Adobe Web Output Pak, Version 2.0.7 -- 02/20/2009 12:04 PM