These documents provide guidance and important information regarding changes in Adobe Reader 9 that may affect enterprise workflows. We recommend you start with the Adobe Reader 9.0 Compatibility Overview document, and then review any of the other documents that are likely to affect your specific organizational workflows.
There are numerous features in Adobe Reader 9.0 that may be of interest to you as you engage in efforts to install and use Adobe Reader in the enterprise. These features include improvements in the experiences of installing, document viewing, performance, security, accessibility, and real-time collaboration. There are also changes in Adobe Reader 9.0 of which you should be aware. These changes, which occurred since Adobe Reader 8.0, may affect workflows used in your company.
PDF was originally a format used for final form representation for viewing, printing, and document interchange. With the addition of interactive form features, multimedia, and scripting, PDF files continue to become more capable with each release. To proactively address potential security issues, Acrobat 9 and Adobe Reader 9 feature an Enhanced Security mode designed to provide advanced control over cross-domain data access and how FDF files are handled. Because the Enhanced Security restrictions may affect some legacy PDF workflows, Reader 9 also provides ways to increase privileges for documents and servers that can be fully trusted.
The Acrobat 9 family of products and Adobe Reader 9 (collectively called Acrobat 9) offer better support for digital signatures in forms created in Acrobat and LiveCycle Designer ES. This support improves the usability and validity of digital signatures. These changes should be of interest to business process developers and PKI owners.
This document describes two changes on how PDF documents are rendered in a browser with Acrobat 9 and Adobe Reader 9: In some cases, the browser HTTP stack, including cookies and session information, will be used for HTTP requests instead of using Acrobat or Adobe Reader's HTTP stack. In-process DLLs will be used to render PDF documents in the browser.