Adobe LiveCycle : Release for business managers BUSINESS WHITE PAPER TABLE OF CONTENTS 1 Purpose of the document 1 Background 1 Why migration is recommended 1 Migration strategy 2 Overview of 8 Available migration paths 8 Migration guidelines Purpose of the document This document summarizes the capabilities and benefits of Designer 7.0, Reader Extensions 7.0, Forms 6.0, and Adobe LiveCycle Form Manager 6.0 software. In addition, you will find guidelines for migrating from previous Adobe products to these versions. While actual migration strategies and procedures will depend on your particular applications and technology, these guidelines will help you prepare for the migration effort. Background As organizations continue to make major investments in ERP, CRM, and other solutions, it is critically important that they can exchange data among these systems as well as connect people and processes with essential business data. As a result, open standards for technology have evolved to facilitate greater information sharing. As part of our continuing commitment to help organizations more fully integrate the use of Intelligent Documents with existing business processes and infrastructure, Adobe has built the products on J2EE, the industry-leading common server technology. The J2EE architecture offers organizations an unparalleled opportunity to integrate document-based processes with the existing technology infrastructure. Why migration is recommended software offers a long-term solution to increase the use of Intelligent Documents in business processes so that organizations can enrich the quality of communications inside and outside the organization, reduce processing and communication costs, and meet governmental regulations for protecting the privacy and integrity of information. Migrating to LiveCycle products will enable you to extend the value of existing core enterprise systems and integrate with other enterprise servers and design tools in a J2EE environment. By migrating, you gain the benefits of J2EE s flexible and open architecture to eliminate software and platform compatibility issues and streamline the exchange and capture of data. As a result, you can rapidly and cost-effectively generate Intelligent Documents and integrate them into current processes as well as take advantage of future technologies and solutions. Migration strategy A transition plan will help to simplify and streamline the migration process. For customers who want assistance, Adobe Professional Services and its partners will help you conduct a complete review of your existing Adobe applications and develop a road map for achieving a cost-effective, strategic, and thorough migration. Our three-step approach helps to ensure a systematic assessment of your migration requirements, resulting in a migration plan that is tailored to meet your business objectives.
1. Current-state analysis Adobe Professional Services will help you complete an initial determination of the size, complexity, and business requirements of the application(s) to be migrated and determine the optimal timing and scope of the on-site migration assessment visit. 2. Migration assessment Adobe will work with your team to conduct an on-site migration assessment that covers transition issues, dependencies, use of existing Adobe server modules, and current form-rendering clients and requirements. The assessment will include a review of the desired infrastructure, knowledge, and skill sets around the new technologies. 3. Migration plan development Based on the migration assessment, Adobe will help you develop a migration plan. This plan will provide a business case for the migration and expected benefits, an assessment of impact on infrastructure, and an upgrade road map, including a recommended timetable for implementation. Contact your Adobe sales representative or solutions partner to discuss how to begin the migration process. Adobe Premium Maintenance and Support customers can contact the Customer Center at 866-766-2256 or their account manager. Overview of The products addressed in this paper are a new generation of server software and design tools. software delivers Adobe Document Services, the underlying technologies that create and integrate Intelligent Documents with enterprise applications and business processes. Adobe Document Services are an ideal solution to help enterprises overcome the problems of disconnected systems, people, and processes. These services replace manual workarounds and isolated processes with efficient document-centric processes that automate and streamline the generation, use, and management of Intelligent Documents. With the standards-based architecture, software enables organizations to easily generate high-quality documents, integrate data into documents, quickly adapt processes to meet changing business needs, and more safely share information outside the firewall. The common server architecture delivers the following major capabilities: ML support for document integration with core business systems to bring business processes fully online. Organizations can connect documents directly to core systems so that they can be prepopulated with data automatically, and so that data added by recipients can be captured into back-end systems without manual intervention. software provides this level of integration through support for third-party ML schemas, which enables users to communicate with anyone on any type of system for interactive round-trip forms functionality. Quick generation of high-quality Intelligent Documents to reduce document development costs and maintain process familiarity. Organizations can rapidly generate complex Intelligent Documents to replace paper-based processes with efficient online processes that maintain the familiar look and functionality of paper. Offline or online document use for process flexibility. With documents managed through Adobe Document Services, recipients can view and work with Intelligent Documents online or offline. Persistent document security to more effectively safeguard electronically shared information. Encryption, user permissions, digital signatures, and document certification can be applied to Intelligent Documents. The security assigned to a document is persistent, traveling with the document at all times so that access to a document and changes to its content can be controlled and tracked even after the document is delivered and used offline. Products discussed in this document include: Designer 7.0 A graphical form design tool for designers and developers to create intelligent ML form designs that may be deployed as Adobe PDF and HTML forms. Reader Extensions 7.0 A server product that enables organizations to extend the functionality of Adobe Reader at no cost to the end user. 2
Forms 6.0 A server product that enables organizations to extend data capture processes beyond the firewall with secure Intelligent Documents and forms deployed in Adobe PDF and HTML. Form Manager 6.0 A server product that provides a central repository for administrators to manage form publication and end users to access enterprise forms. The following sections provide a brief summary of the value of the J2EE architecture and each product s capabilities and benefits. The J2EE platform Adobe has chosen to migrate its enterprise products to the J2EE environment because it is better suited to the rigors of enterprise-level Internet computing, especially at a time when business users conduct transactions on a wide range of server platforms and consumer devices. J2EE offers complete cross-platform portability and support for open standards, makes it easy to leverage the work of other developers, and enables organizations to build enterprise applications that are more secure, scalable, easy to maintain, and stable. J2EE provides the following advantages: Faster application time to market. J2EE handles many middleware tasks so that developers can focus on the business problem, rather than middleware development. As a result, applications can be developed more quickly, resulting in a faster time to market. Greater utilization of existing IT assets. Because J2EE layers on top of existing systems, organizations can leverage past investments. Customers can remain with their existing middleware vendors and use existing applications, operating systems, hardware and developer skill sets. This reduces IT deployment costs and risk levels. Greater protection of future IT assets and a faster response to change. J2EE provides a high degree of adaptability, enabling a well-designed J2EE application to be deployed in a heterogeneous environment of middleware, hardware, or operating system products with minimal modifications. Choice of proven, scalable, and reliable platforms. J2EE customers can choose from a wide array of operating systems and hardware that can scale to a large number of processors with a proven history of high availability. As a result, customers can increase the scalability levels of the underlying platform quickly and easily with lower risk. Adobe products in this release require a J2EE application server for the Java-based applications. Most version 7.0 products may be deployed on IBM WebSphere, BEA WebLogic, or JBoss application servers. Form Manager runs on WebSphere only; Forms runs on WebSphere and JBoss application servers. The IBM and BEA application servers have been selected because of their commanding presence in the application server market and the long-term working relationships Adobe has developed with both vendors. JBoss, a free, open-source application server, has been selected because of its prevalence in the application development community and growing use in production environments. Designer 7.0 Designer 7.0 is the premier development tool for rapidly creating Intelligent Documents that can be rendered as Adobe PDF and HTML. For organizations that want to automate form data capture and processing, Designer offers an outstanding solution to create forms that combine high-fidelity presentation with ML-data handling. Form authors can quickly design complex documents that include business logic, the ability to import and export data from back-end systems, and higher levels of document security. The graphical design environment lets nontechnical users design sophisticated, intelligent forms without custom programming, which reduces costs and time to market for forms-based services, while built-in intelligence for data collection increases the accuracy and speed of processing. Support for third-party ML provides point-and-click binding to any ML schema or data, database, or Web service to integrate electronic forms with enterprise systems. This easy method for passing data into and out of forms reduces the costs for automating form processing and extends the value and use of current systems. 3
An ML form template can be rendered as Adobe PDF and HTML to support a variety of uses and reduce costs for deploying forms in multiple formats. Forms can dynamically adjust to data and events while in use. Customization is cost-efficient because authors do not have to create multiple form designs to provide individually customized forms. ( Forms 6.0 is required to enable this functionality on the server side.) Existing documents from a variety of sources including Adobe Acrobat, Microsoft InfoPath, Word, and more can be imported and modified to reduce form design time and costs. Forms can be encrypted, protected with passwords, and include digital signatures from leading security vendors so that organizations can meet regulatory requirements for electronically sharing information. Forms designed with Designer 7.0 may be viewed in Adobe Acrobat or Adobe Reader. Forms can also be rendered as HTML and viewed in a Web browser using LiveCycle Forms so that users even people with disabilities can participate in form-based processes without being required to purchase or install additional software. This chart shows the enhanced capabilities of Designer 7.0 compared with earlier versions of the product and Adobe Acrobat Professional 6.0. Please note that Adobe LiveCycle Designer 7.0 is included in Adobe Acrobat Professional 7.0. FE AT U R E S AC R O B AT PRO FES- S I O N A L 6. 0 F O R M 5. 6. 0 L I V E C YC L E 7. 0 Support for Adobe s dynamic barcode technology Support for client-side dynamic forms Interactive image field authoring that allows users to populate a form field by selecting an image from the file system Support for encryption, password protection, and digital signatures from leading security vendors. Integration with other Adobe LiveCycle modules Support for J2EE common server architecture Ability to design forms for Acrobat 7.0 Support for third-party arbitrary ML that can be published in multiple formats Support for DP file format Point-and-click form design tool Drag-and-drop field level data binding for ML schemas or databases 4
FE AT U R E S AC R O B AT PRO FES- S I O N A L 6. 0 F O R M 5. 6. 0 L I V E C YC L E 7. 0 Ability to design dynamic subforms for Adobe PDF and HTML Point-and-click Web service binding Ability to import existing form designs from applications including Adobe Acrobat, Microsoft InfoPath, and Microsoft Word Ability to design forms for Forms Ability to design forms for Adobe Form Client Ability to preview forms as Adobe PDF in real time Support for JavaScript Support for FormCalc script Support for VBScript Encryption/decryption of forms with PKI passwords Support for offline form creation with Reader Extensions Creation of accessible forms (for Section 508 requirements) Support for FT file format Support for FDF file format Reader Extensions 7.0 For organizations looking to streamline the process of serving customers, working with external partners, and gathering data from virtually any third party, Reader Extensions 7.0 provides a powerful solution for extending processes outside the network and offline. Intelligent Adobe PDF documents that contain usage rights, built-in logic for data validation, back-end system updates, and so forth can be rights-enabled by Reader Extensions 7.0 so that Adobe Reader users can work with and complete the forms at no cost. Adobe Reader users gain access to additional functionality to review and mark up documents and forms, annotate them, work online or offline, save local copies, and more. Users can easily share forms with others to increase collaboration and be fully integrated into automated processes. Users on Windows, Macintosh, and Linux can work with dynamic, intelligent Adobe PDF documents without additional desktop applications, which eliminates software and platform compatibility issues. Adobe Reader users can interact with complex documents that include data prepopulation and data capture from multiple applications to reduce processing costs and increase accuracy. Adobe Reader users can digitally sign and validate Adobe PDF documents before returning them. With greater assurances of electronic document integrity and authenticity, organizations can bring more mission-critical processes online and more successfully comply with regulations for electronically distributed information. 5
This chart shows the enhanced features in Reader Extensions 7.0 compared to previous versions. FE AT U R E S D O C U M E N T S E R V E R F O R R E A D E R E T E N S I O N S 6. 0 R E A D E R E T E N S I O N S S E R V E R 6.1 L I V E C YC L E R E A D E R E T E N S I O N S 7. 0 Support for Acrobat 7.0 and Adobe PDF 1.6 Compatible with Adobe Reader 5.1 * Ability to add rights to Adobe Designer 6.0 files Support for Sun Solaris UNI Support for Microsoft Windows Support for Linux Integration with IBM WebSphere Integration with BEA WebLogic Integrate access control to server with IS Lightweight Directory Access Protocol (LDAP) infrastructure Compatible with Adobe Reader 6.x Support for Barcoded Forms Support for the J2EE-based platform Web-based UI Web service access for scripting (sample code) (sample code) Rights controlled by digital certificate * Note: Requires Patch #30. Forms 6.0 With Forms 6.0, organizations can extend data capture beyond the firewall with electronic forms deployed in Adobe PDF and HTML. Forms 6.0 executes the built-in processing logic that form designs created in Designer 6.0 can include. As a result, organizations can fully automate business transactions to increase transaction volumes without increasing resources, eliminate paper-based form costs, and accelerate transaction cycles. Forms 6.0 includes the following capabilities: Dynamically render an ML-based form template as Adobe PDF or HTML to reduce deployment costs and speed up user adoption by presenting forms in ways best suited to the user and platform. Import, export, and link third-party ML schemas and data and extract captured data in HTML and Adobe PDF forms as ML to eliminate manual data entry and reduce error rates. Execute all business logic contained in an Designer form design to improve accuracy and processing speed. Digitally sign, validate, encrypt, and decrypt Adobe PDF forms on the server, in coordination with Reader Extensions, for greater assurances of a document s authenticity and integrity. Manage and track document use inside and outside the firewall more effectively (in coordination with Policy Server). Provide close integration with other Adobe enterprise solutions, including Designer 6.0, Form Manager 6.0, and Reader Extensions 7.0. Organizations gain a complete solution for all types of form processing from simple print-and-fill forms to complete processes requiring multiple participants, review cycles, and data integration. 6
Forms 6.0, formerly Adobe Form Server, offers these enhanced features: FE AT U R E S Windows server support only J2EE architecture common server architecture F O R M S E R V E R 5. L I V E C YC L E F O R M S 6. 0 Dynamic HTML forms rendering Dynamic Adobe PDF forms rendering Dynamic subforms in Adobe PDF and HTML Point-and-click form design using Adobe LiveCycle Designer Support for DP file format Support for third-party arbitrary ML Offline form support using Reader Extensions Web-based user interface Accessibility Multi-server support Compatibility with Acrobat 7.0 and Adobe PDF 1.6 Form Manager 6.0 Form Manager 6.0 provides a centralized repository for managing forms. Using Form Manager, organizations can reduce forms management time and costs as well as more securely expand the use of electronic forms outside the firewall. In addition, Form Manager helps organizations increase productivity by tightly integrating forms management into online business processes. Form Manager can be combined with other Adobe products for a complete electronic forms solution to manage complex forms processing. Form Manager 6.0 will be required for applications that plan to use Adobe Workflow Server 6.2 in conjunction with Forms 6.0. With the centralized repository for storing and managing blank forms of any file type, forms created in a variety of applications can be stored in native formats for a flexible solution to migrate from a paper-based or fill-and-print forms environment to fully automated electronic forms processing. Administrators can assign permissions to restrict user access to forms. Form Manager uses the authentication credentials stored in an existing LDAP directory to determine access so that organizations can leverage existing LDAP user and group structures to assign access rights via an application server. Automatic version control covers all aspects of a form, including the form design and any referenced objects, such as corporate logos or referenced script files. Automated version control reduces costs, as administrators do not waste time determining the most current version of a form. Processing costs and errors decrease because version control automatically ensures use of the most current form. The interface is designed for ease of use. Forms are presented in categories via a familiar folders-style directory. Users can search for forms based on a variety of criteria, such as by title, content, or use in a particular workflow. Additionally, users can search for previously filled out forms using a full text search. They can specify any data that was contained within the form as search criteria to locate a specific form instance. Since nontechnical administrators can manage the repository, form maintenence costs are lower. Form managers using Form Manager can designate forms fields to be automatically prepopulated with data. Each user can create a profile of data that is used automatically on all forms where fields for prepopulation have been designated. Data prepopulation reduces error rates and form completion time to increase user productivity. 7
Available migration paths The recommended migration path for Adobe products is as follows: P R E V I O U S P R O D U C T U P G R A D E P R O D U C T Adobe Form Designer 5.0 and 5.1 and Adobe Designer 7.0 Designer 6.0 Adobe Form Server 5.x Forms 6.0 Adobe Document Server for Reader Reader Extensions 7.0 Extensions 5.x/6.x Adobe Document Server 5.x/6.0 and Adobe Reader Extensions Server 5.x/6.0 Forms 6.0 and Reader Extensions 7.0* *Note, this migration path is available only to customers previously using Adobe Document Server for forms generation and data extraction. These customers will have the opportunity to migrate to Forms. In addition, for organizations that want to take advantage of the new capabilities offered by Adobe products released on the J2EE architecture, the following migration paths are available: P R E V I O U S P R O D U C T Adobe Form Client 4.x/5.x JetForm Filler Delrina FormFlow O P T I O N A L U P G R A D E Forms 6.0 and Reader Extensions 7.0 Forms 6.0 and Reader Extensions 7.0 Designer 7.0, Forms 6.0, or Reader Extensions 7.0 Note: Users of Adobe Output Designer may also want to consider migrating to Adobe LiveCycle Designer 7.0. Migration guidelines This section provides an overview of the migration process. While each migration effort will be unique, these guidelines will help you understand the scope of the effort involved and particular issues that you may encounter. In general, the migration steps are as follows: Migrate portions of Web applications that call Adobe technology to the J2EE application server. If you are to move to a.net environment rather than J2EE, you can leverage the SOAP API provided with Forms 6.0 to integrate your applications into.net environments. You will still need a J2EE environment to run Forms 6.0. Convert existing form designs into either PDF or the DP file format for forms that will be used with Forms 6.0. Adobe provides a set of import tools to simplify this process. The DP file format separates ML data from the form design, providing several advantages. For example, it enables users to see different data in a form or different parts of the form, making it easy to customize and personalize forms without having to maintain a separate form design for each user. Data can be transmitted separately from the form design to reduce network traffic. For more information about DP, see the Designer area on the developer pages of Adobe.com: www.adobe.com/enterprise/developer. Replace any VBScript used in form designs since VBScript is not fully supported across all Web browsers and platforms. JavaScript is the recommended scripting language to replace VBScript and business logic that is not available through the Designer 7.0 point-andclick environment. Map object references to the new ML Forms Architecture (FA) data model. The Adobe LiveCycle products use a common data model. FA is an open, public standard for an ML grammar used to specify how a form appears and acts as well as how it interacts with application-defined ML documents. Form developers may need to become familiar with the new data model so that they can map references to objects in forms to be migrated to objects in the new data model. 8
Rewrite existing applications and solutions to be compatible with the J2EE environment and the new data model, when necessary. Developers will need to be familiar with Web application development, including Web services and J2EE programming equivalents such as JSP, servlets, Java, JavaBeans, EJBs, and JDBC. General guidelines for converting existing forms Form designs created in previous versions of Adobe Form Designer, Adobe Acrobat, or Delrina FormFlow must be converted to the DP file format before they can be used with Adobe LiveCycle Forms 6.0. In general, the following process applies to migrating form designs from any of the applications listed. Migrate existing form designs using Designer 7.0 import tools, which perform the ML conversion and store the form designs in the DP file format or as Adobe PDF. Rebuild JavaScript logic. Replace any VBScript. All VBScript in form designs will be commented out in the imported form. Conversion will be simpler if VBScript is converted to JavaScript before importing the form into Designer 7.0. Consider redesigning the form to take advantage of the additional capabilities of Adobe LiveCycle Designer 7.0, such as support for dynamic forms on either the server or the client side. Map object references to the new data model. Save the form design as an DP file or Adobe PDF. Migrating to the new client applications This section identifies product-specific issues when migrating to Designer 7.0 and Reader Extensions 7.0. M I G R AT I O N FR O M Adobe Acrobat Adobe Form Client JetForm Filler and Delrina FormFlow TO Designer 7.0 Designer 7.0 Reader Extensions 7.0 Forms 6.0 Reader Extensions 7.0 Designer 7.0 P O T E N T I A L I SSUES Not all of the forms-related capabilities of Adobe Acrobat are available in Designer7.0. Importing Adobe Form Client FT forms will be limited to objects, events, and scripting languages supported in Designer 7.0. Additional scripting work may be required. Because Adobe Form Client uses Active technology, not all of the capabilities delivered through Active components are available in Designer 7.0. Most functionality that has been designed to execute at the user s client machine will have to be revised to execute on the server. In some cases, an application using standalone forms will have to be replaced with a Web-based application. The MDF file cannot be directly imported into Designer 7.0. Use the source (IFD) file, which can be imported directly into Designer 7.0. Because JetForm Filler and Delrina FormFlow are thick clients, the existing code for applications using these two products cannot be migrated. Applications will need to be restructured as Web applications. 9
Migrating to the new servers This section identifies issues you may need to address when migrating to Forms 6.0 and Reader Extensions 7.0 from Adobe Form Server 5.0 and Adobe Reader Extensions Server 5.x/6.x. It also discusses the new Form Manager 6.0 and its use in applications that combine the use of Forms 6.0 with Adobe Workflow Server 6.2. M I G R AT I O N FR O M Adobe Form Server 5.0 Adobe Document Server for Reader Extensions 5.x/6.x Adobe Document Server 5.x/6.0 and Adobe Reader Extensions Server 5.x/6.0 Adobe Workflow Server 6.2 and Adobe Form Server 5.x TO Forms 6.0 Adobe LiveCycle Reader Extensions 7.0 Forms 6.0 Forms 6.0 P O T E N T I A L I SSUES In general, you have three options for migrating existing applications for use with Forms 6.0 as follows: Use your current Adobe Form Server 5.0 applications with Forms 6.0 by updating your SOAP client. You will need to change the application server for Forms 6.0 to J2EE. Migrate to a J2EE environment, which will require changing your applications to be J2EE compatible. Migrate to a.net environment and use the.net SOAP interface provided with Forms 6.0. Entrust TruePass thin-client signatures are not supported. Digital signatures can be used with Adobe PDF. Offline HTML (or CHTML, WML, APPLET, HTML32, or custom HTML) are not supported. Can be replaced with offline Adobe PDF documents that are rightsenabled using Reader Extensions 7.0. There are no issues of backward compatibility when migrating to Reader Extensions 7.0. Forms that were rights-enabled with previous versions can be used with the new version. Adobe Premium Support and Maintenance customers who have both Adobe Document Server 5.x/6.0 and Adobe Reader Extensions Server 5.x/6.0 will be entitled to migrate from Adobe Document Server to Forms 6.0. This will be a one-time decision for these customers, who can choose to stay on Adobe Document Server or migrate. The decision will remain in effect for all future migrations. Because Forms 6.0 includes data extraction and data prepopulation capabilities, Reader Extensions 7.0 can now be used with Forms 6.0 when data extraction and data prepopulation are required. Adobe Premium Support and Maintenance customers who have both Adobe Workflow Server 6.x and Adobe Form Server 5.x and who choose to migrate to Forms 6.0 must have Adobe LiveCycle Form Manager 6.0. Adobe will provide a single free CPU of Adobe LiveCycle Form Manager 6.0, regardless of how many CPUs of Adobe Workflow Server or Forms 6.0 will be in use. Customers can purchase additional CPUs of Form Manager 6.0. 10
FOR MORE INFORMATION To learn more about the family of products, please call 800-861-9428 (in North America) or visit www.adobe.com/ products/server/. Developer resources are available at www.adobe.com/enterprise/developer. Enterprise server technical support and the knowledge base are available at http://www.adobe.com/support/products/ enterprise/main.html Learn more about Adobe Professional Services by visiting http://www.adobe.com/support/profservices/ main.html Solution migration examples The issues encountered during solution migration will be a combination of the migration guidelines explained in the previous sections. This section provides a series of sample use cases and issues that are likely to be encountered during migration. Data capture using Adobe Form Client and Adobe Workflow Server for routing A typical solution consists of forms presented using Adobe Form Client and routed using Adobe Workflow Server. Often, this type of application will have custom components, such as ASP and custom business object for database communication. A typical configuration consists of a Web farm of IIS servers, Adobe Workflow Server in a cluster environment, and a single database server. To migrate this type of solution: Forms must be converted to DP file format, the code modified to match the FA object model, and the VBScript rewritten in JavaScript. All custom components will need to be rewritten in J2EE-compatible technologies. Certain Adobe Form Client data capture functionality is not available in Adobe LiveCycle Forms 6.0 and will require workarounds. For example, Adobe Form Client form-in-form technology must be replaced with an HTML form used for data capture. The form can only be presented in HTML, not as Adobe PDF, in order to maintain equivalent functionality. In general, simple modifications, such as changing the Web interface stylesheet for fonts and colors, to the standard configuration of Form Manager are straightforward. However, for more extensive customization, Adobe recommends that customers contact Adobe Professional Services for assistance. Form Manager 6.0 will be the Web-based user interface to Adobe Workflow Server. Application performance will need to be tested. Data capture and print preview using Adobe Form Server 5.0 In this solution, a series of HTML pages are used to capture data followed by presentation of a static Adobe PDF form for print previewing. Adobe Form Server 5.0 serves either HTML or Adobe PDF forms from the FT file format. This application may include custom components to assemble the Adobe PDF files before presenting them to the end user. To migrate this type of solution: Forms must be converted to the DP file format and the code modified to match the FA object model. All VBScript will need to be rewritten in JavaScript. All custom components will need to be rewritten in J2EE-compatible technologies. Your IT organization may wish to maintain a hybrid environment for this type of application, as the Web and application server can remain on Microsoft IIS. If you choose to migrate fully to a J2EE environment, all custom components will need to be rewritten in J2EE-compatible technologies. Data capture using Adobe Form Server 5.0 with Adobe Workflow Server for routing A typical solution consists of a series of HTML pages used for data capture, which are then routed using Adobe Workflow Server. The issues with this type of solution will be the same as those described in the two previous examples for data capture using Adobe Form Client and data capture/print preview using Adobe Form Server 5.0. Adobe helps people create, manage, and deliver the highest quality digital content in the world. Better by Adobe. Adobe Systems Incorporated 345 Park Avenue, San Jose, CA 95110-2704 USA www.adobe.com Adobe, the Adobe logo, Acrobat,, Reader, and Better by Adobe are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Linux is a registered trademark of Linus Torvalds. Active, Microsoft, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Sun and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UNI is a registered trademark of The Open Group. All other trademarks are the property of their respective owners. Standalone JetForm Filler or Delrina FormFlow solution In this type of application, JetForm Filler or Delrina FormFlow is used to fill and print data. To migrate this type of solution: Because of the requirement for Web-based applications used with Forms 6.0, the existing applications will have to be rebuilt using J2EE-compatible technologies. Locally saved data in DAT format or in dbase files is no longer supported. One possible solution is to merge the DAT files with MDF forms to create static Adobe PDF files for archiving. 2004 Adobe Systems Incorporated. All rights reserved. Printed in the USA. 95004494 12/04