adobe forms sizing nw 73

Please make sure that you are always using the most current version of the sizing guideline!

Sizing Guide

Sizing for Adobe DocumentServices

(SAP Netweaver 731 SPS 7 or higherSAP NetWeaver 740 SPS 2 or higher)

Released for SAP Customers and Partners

Document Version 3.0 - July, 2013

Copyright/Trademark

© Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, andVisual Studio are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,System p5, System x, System z, System z10, z10, z/VM, z/OS,OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems,POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale,PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS,HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX,Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet aretrademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the UnitedStates and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader aretrademarks or registered trademarks of Adobe Systems Incorporatedin the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of theOpen Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks orregistered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerryPearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2,BlackBerry PlayBook, and BlackBerry App World are trademarks orregistered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google DataAPI, Google Maps, Google Mobile Ads, Google Mobile Updater,Google Mobile, Google Store, Google Sync, Google Updater, GoogleVoice, Google Mail, Gmail, YouTube, Dalvik and Android aretrademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec TechnologiesCorporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark HoldingsLLC.

Computop is a registered trademark of ComputopWirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAPBusinessObjects Explorer, StreamWork, SAP HANA, and other SAPproducts and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germanyand other countries.

Business Objects and the Business Objects logo, BusinessObjects,Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, andother Business Objects products and services mentioned herein aswell as their respective logos are trademarks or registered trademarksof Business Objects Software Ltd. Business Objects is an SAPcompany.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere,and other Sybase products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks ofSybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services areregistered trademarks of Crossgate AG in Germany and othercountries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks oftheir respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its affiliated companies ("SAP Group")for informational purposes only, without representation or warranty ofany kind, and SAP Group shall not be liable for errors or omissionswith respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

DisclaimerSome components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressly prohibited, as is anydecompilation of these components.

SAP Library document classification: CUSTOMERS & PARTNERS

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:http://service.sap.com/sizing

http://service.sap.com/sizin

__________________________________________________________________________________1 Sizing SAP Interactive Forms by Adobe - SAP Customers and Partners

TABLE OF CONTENTS

1. Introduction ..............................................................................................................................21.1 Functions of SAP Interactive Forms by Adobe .................................................................................21.2 Architecture of SAP Interactive Forms by Adobe ..............................................................................21.3 Factors that influence the performance ............................................................................................31.4 Results from Performance Test........................................................................................................32. Sizing Fundamentals and Terminology ..................................................................................43. Performance Test for print form sizing for Adobe Document Services ................................53.1 Assumptions ....................................................................................................................................53.2 Determining SAPS Rating For Each Document Type .......................................................................53.3 Sizing guideline ...............................................................................................................................64. Batch Print Sizing for Adobe Document Services ..................................................................84.1 Assumptions ....................................................................................................................................84.2 Determining SAPS Rating For Each Document Type .......................................................................84.3 Sizing guideline ...............................................................................................................................95. Interactive Form Sizing for Adobe Document Services ....................................................... 115.1 Assumptions for Sizing .................................................................................................................. 125.2 Determining SAPS Rating For Each Document Type ..................................................................... 125.3 Sizing Guidelines ........................................................................................................................... 145.4 Interactive Form Sizing Example .................................................................................................... 156. Comments and Feedback ...................................................................................................... 16

Sizing SAP Interactive Forms by Adobe - SAP Customers and Partners__________________________________________________________________________________

Copyright/Trademark

22

1. INTRODUCTIONThis document is intended for SAP performance analysts and customers as a general guide todetermining server size requirements for the Adobe document services component in their particularinstallations. This document will provide size guidance based on generic server requirements such assize of documents and data as opposed to end-user business cases.

Adobe document services render PDF, PCL, PostScript, and other output formats from form designscreated using the Adobe LiveCycle Designer. Section 2 of this document is primarily concerned with theproduction of print output (PCL and Postscript) when called in batch or “print” mode. Section 3 isprimarily concerned with the production and modification of interactive PDF when called in singlerequest or “interactive” mode.

This document applies to following releases:

• SAP NetWeaver 731 SP7 and higher, and SAP NetWeaver 740 and higher

1.1 Functions of SAP Interactive Forms by AdobeFor print, Adobe document services will be called in batches to produce PCL and PostScript. The outputis written to a spool file, which is then output to a printer. A batch consists of a form design createdusing LiveCycle Designer and a data file with multiple data records. When Adobe document servicesmerge the form design and the multi-record XML data, documents in PCL or PostScript format thatcontain the results of all the records in the batch are created and returned to the calling application. Theresultant output from Adobe document services is written to a spool file and output to a printer.

In interactive mode, Adobe document services are called (for the scope of this document) to produce asingle interactive PDF. The contents of an interactive request are similar to those of a print requestexcept that the data file contains a single record, thus producing a single output file. Security settingsmay be applied to the generated PDF before it is returned to the calling application. The securitysettings define how the PDF can be modified

1.2 Architecture of SAP Interactive Forms by AdobeThe form processing run time in the ABAP Workbench stack makes use of a PDF object to call Adobedocument services. Adobe document services are passed a form design and data, and then calls theXML form component to merge the form design and multiple data records to produce the PCL orPostScript output. The resultant documents are returned to the form processing run time, which thenpasses the output to the post-processing framework. The post-processing framework writes the outputto the spooler. The spooler then transmits the output to the printer.In interactive mode, the form design is merged with a single data record to produce the PDF, which isthen returned to the calling application in the workflow.


Copyright/Trademark

33

Figure 1: Architecture

1.3 Factors that influence the performanceThe following factors influence performance (more specific factors can be found in sections 3 and 4):

Size and complexity of the form design. The size of the form design is determined by thenumber of elements on the form design. A form design may consist of any number of pages.

In print mode, the amount of scripting that is in the form design. Interactive forms generallycontain little server-side scripting, thus having little affect.

In print mode, the numbers of records in the data file to be merged. This defines the batch sizewhere each data record corresponds to a single piece of output.

Amount of data in each record; that is, the number of pages of generated output.

Number of parallel requests being processed.

Size of the output that the batches generate. Entire output is returned in a memory buffer.

1.4 Results from Performance TestThe result of this document will be a sizing estimate for the target server based on the input provided.For standardization, this measure is expressed in “SAPS”.

SAPS is a hardware independent unit used to describe the CPU-related performance characteristic of agiven hardware configuration. For additional information on SAPS and their equivalent hardwareperformance, see www.sap.com/benchmark -> SAPS.

The performance tests were performed with Adobe document services in SAP Web Application Server731 on a dual CPU Intel Xeon E5520 2.27 GHz Xeon-based server with a rating of approximately 8000SAPS.

Gibson/DSS


Copyright/Trademark

44

The SAP NetWeaver 731 system needs to be sized so that it can handle the worst case load at 66%CPU utilization.

2. SIZING FUNDAMENTALS AND TERMINOLOGYSAP provides general sizing information on the SAP Service Marketplace. For the purpose of this guide,we assume that you are familiar with sizing fundamentals. You can find more information athttp://service.sap.com/sizing Sizing Guidelines General Sizing Procedures.This section explains the most important sizing terms, as these terms are used extensively in thisdocument.

SizingSizing means determining the hardware requirements of an SAP application, such as the networkbandwidth, physical memory, CPU processing power, and I/O capacity. The size of the hardware anddatabase is influenced by both business aspects and technological aspects. This means that thenumber of users using the various application components and the data load they put on the servermust be taken into account.

BenchmarkingSizing information can be determined using SAP Standard Application Benchmarks and scalabilitytests (www.sap.com/benchmark). Released for technology partners, benchmarks provide basic sizingrecommendations to customers by placing a substantial load upon a system during the testing of newhardware, system software components, and relational database management systems (RDBMS). Allperformance data relevant to the system, user, and business applications are monitored during abenchmark run and can be used to compare platforms.

SAPSThe SAP Application Performance Standard (SAPS) is a hardware-independent unit that describes theperformance of a system configuration in the SAP environment. It is derived from the Sales andDistribution (SD) Benchmark, where 100 SAPS is defined as the computing power to handle 2,000 fullybusiness processed order line items per hour. (For more information about SAPS, seehttp://www.sap.com/benchmark Measuring in SAPS).

Initial SizingInitial sizing refers to the sizing approach that provides statements about platform-independentrequirements of the hardware resources necessary for representative, standard delivery SAPapplications. The initial sizing guidelines assume optimal system parameter settings, standard businessscenarios, and so on.

Expert SizingThis term refers to a sizing exercise where customer-specific data is being analyzed and used to putmore detail on the sizing result. The main objective is to determine the resource consumption ofcustomized content and applications (not SAP standard delivery) by comprehensive measurements. Formore information, see http://service.sap.com/sizing Sizing Guidelines General Sizing Procedures

Expert Sizing.

Configuration and System LandscapingHardware resource and optimal system configuration greatly depend on the requirements of thecustomer-specific project. This includes the implementation of distribution, security, and high availabilitysolutions by different approaches using various third-party tools. In the case of high availability throughredundant resources, for example, the final resource requirements must be adjusted accordingly.There are some "best practices" which may be valid for a specific combination of operating system anddatabase. To provide guidance, SAP created the NetWeaver configuration guides(http://service.sap.com/instguides SAP NetWeaver).

http://service.sap.com/sizing

http://service.sap.com/sizing

http://service.sap.com/instguides


Copyright/Trademark

55

3. Performance Test for print form sizing for AdobeDocument Services

Print form sizing will depend on the complexity of the form designs that are given to Adobe documentservices to render. It is assumed that a given application will be a mixture of simple, medium, large, andextra-large forms. The flight data form was selected from the SAP performance test samples torepresent each of the four types of complexity. (See Appendix A for a sample of this form.)Performance tests were run to determine the sizing using flight data forms with 1, 10, 100, and 1000pages. The definition was as follows:

Small: equivalent to 1 page of flight data.

Medium: equivalent 10 pages of flight data.

Large: equivalent to 100 pages of flight data.

Extra-large: equivalent to 1000 pages of flight data.

3.1 Assumptions

Adobe document services will be called in small batches that reduce the communication andinvocation overhead. It will be assumed that parallel requests can be made to fully utilize theCPU.

Adobe document services can be called by either passing the request files by way of streams orURI (that is, HTTP URL or local file system). By default, the form design is passed by URl andthe data by way of a stream.

It is assumed that Adobe document services are called in such a way that they can be scaledlinearly, horizontally, and vertically.

It is also assumed that Adobe document services will run proportionally the same speed onvarious platforms based on the CPU rating of the hardware.

The ABAP Workbench stack and Adobe document services exist on the same hardware devicefor optimal configuration.

3.2 Determining SAPS Rating For Each Document TypeThis section describes how a performance test was constructed to determine the SAPS rating for eachAdobe document services print document complexity type. These SAPS ratings can then be reused foreach customer business case.

The criteria for determining the complexity of a form will be the number of form elements, the amount ofscript, and the size of the data. The flight data forms were chosen from SAP samples to represent eachof four form types: small (1-page), medium (10-page), large (100-page), extra-large (1000-page).

The performance test was performed as follows:

Using an optimal size of batches, the maximum throughput of the flight data form in pages per hour wasdetermined.

• Let cpu_saps be the SAPS rating of the CPU performing the performance test.

• Let sph be the number of small print documents that can be generated per hour.

• Let mph be the number of medium print documents that can be generated per hour.

• Let lph be the number of large print documents that can be generated per hour.

• Let eph be the number of extra-large print documents that can be generated per hour.


Copyright/Trademark

66

Example 1: Performance Test Results

cpu_saps = 8000 SAPS (SAPS rating of the computer performing the benchmark)

• sph = 30100.0 (small documents per hour)

• mph = 15030.0 (medium documents per hour)

• lph = 1740.0 (large document per hour)

The system needs to be sized so that it can handle the worst case load at 66% CPU utilization. Theseresults have been scaled to 66% CPU utilization.

The SAPS rating of each print form complexity were determined as follows:

• SAPS(small per hour) = cpu_saps / sph = .2657 SAPS• SAPS(medium per hour) = cpu_saps / mph = .5322 SAPS• SAPS(large per hour) = cpu_saps / lph = 4.5977 SAPS

3.3 Sizing guideline

For a printing application, the SAPS rating is determined based on the number of small, medium, andlarge that the calling application is expected to produce per hour.

The documents that the application produces must be compared with the SAP flight data sample Adobedocument services documents (Appendix A) that have been benchmarked in section 2.2.

With this SAPS rating for each document type, we can estimate the total number of SAPS required foran application with the following formulas.

SmallSAPS = small documents required per hour * SAPS (small per hour)

= small documents required per hour * 0.2657

Medium

SAPS = medium documents required per hour * SAPS (medium per hour)

= medium documents required per hour * 0.5322

Large

SAPS = large documents required per hour * SAPS (large per hour)

= large documents required per hour * 4.5977

The Total SAPS can then be converted to a number of computers by dividing the total SAPS requiredby the SAPS rating of the computer being considered to run the application. (Seewww.sap.com/benchmark to determine the SAPS rating of the computer considered for the application.)

#of computers = Total SAPS / machine_saps

Memory usageThe memory usage will depend on the size of the batch output; however, it is assumed that the batchsizes will be small enough that a simple guideline of allocating 1GB of RAM per Core is sufficient inaddition to other AS Java applications. Note: this 1GB is needed on OS level and it is not meant to bepart of the AS Java Heap Memory. Memory usage depends on the form design. For more information,see SAP Note 1033661.


Copyright/Trademark

77

Example 2:This example uses the SAPS ratings calculated in Example 1 (see section 2.2).The customer requires 10000 small documents per hour, 12500 medium documents per hour and 300large documents per hour.The customer is using a 4-way SMP computer with, according to www.sap.com/benchmark, a SAPSrating of 8000.

SAPS required for small documents = 10000 * 0.2657 = 2657 SAPS

SAPS required for medium documents = 12500 * 0.5322 = 6652 SAPS

SAPS required for large documents = 300 * 4.5977 = 1379 SAPS

This application can be represented in a table (shown below).The total number of SAPS that Adobe document services require can be determined by summing theSAPS ADS Server column.

Category Up to # documents per hour SAPS ADS server

Small 10000 2657

Medium 12500 6652

Large 300 1379

Total SAPS 10688

The customer would require 59302 / 8000 = CPU power equivalent to approximately three 4-way SMPcomputers as described above.

http://www.sap.com/benchmark


Copyright/Trademark

88

4. Batch Print Sizing for Adobe Document ServicesWhen printing individual documents, there is a fixed amount of overhead per document processed.When the documents are small, this overhead can become a disproportionate fraction of the total timetaken for the job. One way to overcome this is to print small jobs in batches. In this way, the fixedoverhead for a job is shared over many jobs, reducing the total processing time. In many cases thisimprovement can be very significant.The server sizing for batch printing will depend on the complexity of the form designs that are given toAdobe document services to render. There are two different types of batch printing: Heterogeneous Batch Printing – Using multiple data sources and multiple templates, multiple

outputs are produced (PDF, PCL, ZPL, PS...).It is assumed that a given application will be a mixture of small, medium, and large forms. The differentforms were selected from the SAP performance test samples to represent each of the three types ofcomplexity. (See Appendix C for a sample of this form.)Tests were run to determine the performance of the different forms, having 1, 2 and 4 pages, inhomogeneous batch printing mode. For the performance test, a form’s size will be defined as follows: Small: equivalent to 1 page of data Medium: equivalent 2 pages of data Large: equivalent to 4 pages of data.

4.1 Assumptions Adobe document services will be called in batches of 50 documents using homogeneous batch

printing. It will be assumed that parallel requests can be made to fully utilize the CPU. Adobe document services can be called either by passing the request files by way of streams or by

URI (that is, HTTP URL or local file system). By default, the form design is passed by URl and thedata by way of a stream.

It is assumed that Adobe document services are called in such a way that they can be scaledlinearly, horizontally, and vertically.

It is also assumed that Adobe document services will run proportionally the same speed on variousplatforms based on the CPU rating of the hardware.

The ABAP Workbench stack and Adobe document services exist on the same hardware device foroptimal configuration.

4.2 Determining SAPS Rating For Each Document TypeThis section describes how a performance test was constructed to determine the SAPS rating for eachAdobe document services print document complexity type when using batch printing. These SAPSratings can then be reused for each customer business case.The criteria for determining the complexity of a form will be the number of form elements, the amount ofscript, and the size of the data. The following forms were chosen to represent each of the three types.

Illness and Injury Report for OSHA – small (1 page).

Check Deposit Status Report - medium (2 page).

Customer Account Statement – large (4 page).


Copyright/Trademark

99

The performance test was performed as follows:Using a batch sizing of 50, the maximum throughput of the forms in pages per hour was determined(number of transactions/sec * 3600 * 50[batch size]).

Let cpu_saps be the SAPS rating of the CPU performing the performance test.

Let sph be the number of small print documents that can be generated per hour.

Let mph be the number of medium print documents that can be generated per hour.

Let lph be the number of large print documents that can be generated per hour.

Example 3: Performance Test Resultscpu_saps = 8000 SAPS (SAPS rating of the computer performing the performance test)

sph = 170000 (small documents per hour)

mph = 102420 (medium documents per hour)

lph = 40500 (large document per hour)

The system needs to be sized so that it can handle the worst-case load at 66% CPU utilization. Theseresults have been scaled to 66% CPU utilization.The SAPS rating of each print form complexity were determined as follows:

SAPS(small per hour) = cpu_saps / sph = 0.0470 SAPS

SAPS(medium per hour) = cpu_saps / mph = 0.0781 SAPS

SAPS(large per hour) = cpu_saps / lph = 0.1975 SAPS

4.3 Sizing guidelineFor a printing application, the SAPS rating is determined based on the number of small, medium, andlarge documents that the calling application is expected to produce, per hour, in batch printing mode.The documents that the application produces must be compared with the different Adobe documentservices documents (Appendix C) that have been benchmarked in section 4.2.With this SAPS rating for each document type, we can estimate the total number of SAPS required foran application with the following formulas.SmallSAPS = small documents required per hour * SAPS (small per hour) = small documents required per hour * 0.0470MediumSAPS = medium documents required per hour * SAPS (medium per hour) = medium documents required per hour* 0.0781LargeSAPS = large documents required per hour * SAPS (large per hour) = large documents required per hour * 0.1975

The total SAPS can then be converted to a number of computers by dividing the total SAPS required bythe SAPS rating of the computer being considered to run the application. (Seewww.sap.com/benchmark to determine the SAPS rating of the computer considered for the application.)

#of computers = Total SAPS / machine_saps

The memory usage will depend on the size of the batch output. However, it is assumed that the batchsize of 50 that was used in the performance test will be enough that a simple guideline of allocating 1GBof RAM per Core is sufficient in addition to other AS Java applications. Note: this 1GB is needed on OSlevel and it is not meant to be part of the AS Java Heap Memory. Memory usage depends on the formdesign. For more information, see SAP Note 1033661.



Copyright/Trademark

1010

Example 4:This example uses the SAPS ratings calculated in Example 3 (see section 3.2).The customer requires 10000 small documents per hour, 12500 medium documents per hour, and 300large documents per hour to be printed using batch printing.The customer is using a 4-way SMP computer with, according to www.sap.com/benchmark, a SAPSrating of 8000.

SAPS required for small documents = 10000 * 0.0470 = 470 SAPS

SAPS required for medium documents = 12500 * 0.0781 = 976 SAPS

SAPS required for large documents = 300 * 0.1975 = 59 SAPS

This application can be represented in a table (shown below).The total number of SAPS that Adobe document services require can be determined by summing theSAPS ADS Server column.

Category Up to # documents per hour SAPS ADS serverSmall 10000 470

Medium 12500 976

Large 300 59

Total SAPS 1505

The customer would require 13858/ 8000 = CPU power equivalent to approximately one 4-way SMPcomputers as described above.



Copyright/Trademark

1111

5. Interactive Form Sizing for Adobe Document ServicesIn a typical application workflow, interactive forms are used to gather specific information and approvalsthroughout an organization. For example, an employee fills out an online requisition for a new monitor.This form is submitted to the SAP server which, after applying business rules to the form, sends it to theemployee’s manager. The manager reviews the form and approves the item for purchase. The form isagain submitted to the SAP server, and the cycle continues until the form has traveled through eachpoint in the workflow.Before the form reaches the employee, it must be rendered by Adobe document services. During formgeneration, Adobe document services produce an interactive PDF and apply security settings before theform is returned to the calling application. Specific security settings are defined in the form generationrequest. They define how the form may be modified (such as fill and sign, modify annotations, and soon), printed (that is, high/low quality or not at all), and whether form content can be extracted.In addition to the security settings, Reader usage rights, that define whether certain Adobe Readerfunctionality is exposed while the form is displayed, are also available. For example, the ability to importand export the form contents in Adobe Reader can be made available or hidden by defining theassociated Reader usage right.Part of the client-side form interaction involves the use of digital signatures. This provides an approvalmechanism to validate a form’s state at a given point in the application workflow. The employee’smanager in the above example would use a digital signature to show that the monitor purchase isapproved. The manager has a credential that identifies that person. A credential consists of two parts: aprivate key used to sign documents and a public key used to verify the signature. The private key isclosely guarded, but the public key is distributed to each entity that needs to verify that manager’ssignature. When a form is signed, a snapshot of the form state is preserved so that it can be retrievedlater.When the server receives a signed form, a list of signatures is typically retrieved and each signature isvalidated to ensure the form is in good standing. When the form’s standing is established, a request issent to Adobe document services to retrieve the form state when a given signature was applied. Theform state includes the values for each form field at the time of signing. The server business logic mayretrieve two or more states to compare certain values as part of the form’s approval process. If themonitor quantity in our example changed between signatures, it could be considered a reason toquestion the form’s approval.Adobe document services form generation offers a PDF caching mechanism when outputting cacheableinteractive PDFs. A version of the form (without data) is stored and later retrieved when subsequentrequests for the same form are received. Data for each of the subsequent requests is merged into thecached PDF and returned to the calling application. If the same Reader usage rights are always appliedto the same interactive form, they can also be cached, thus realizing an additional performance gain.Interactive forms tend to have a static data format (not the actual values) and page count from oneinstance of a form to the next. In contrast, print forms generate output until the entire data file contentsare processed. There is no need to regenerate the base form for each instance of an interactive formwhen only the field values themselves change.In a typical SAP-based application workflow, the following steps are performed:

1. The user logs into an interactive form-based application and requests a specific form.

2. A request is sent to Adobe document services to generate an instance of that form and to applya set of Reader usage rights, and then the form is sent to the user.

3. When completed, XML data is sent to the server for processing.Steps 2 and 3 may repeat several times within the workflow.

4. A final review copy of the form is presented to the user.

5. The system extracts the final form data and validates the digital signatures.Interactive form sizing is more complex than print form sizing due to the nature of interactive forms.Print forms inherently contain repeating data and are sized based on the amount of space required torepresent that data.Interactive forms are generally limited to a small number of pages and therefore require multiple formsto properly determine sizing. Forms with one, two, and four pages are used for the interactive form sizetesting.


Copyright/Trademark

1212

For the performance test, four forms will be used consisting of two one-page forms (simple andcomplex), one two-page form, and one four-page form. Interactive form complexity is based on thenumber of pages, number of interactive form elements (such as drop-down lists and texts fields), andthe number of static form elements (such as text and graphics). Almost all interactive form scripting isperformed on the client and rarely affects the form generation time on the server.

5.1 Assumptions for Sizing Adobe document services will be called as single requests to perform one or more operations per

request. It is assumed that parallel requests can be made to fully utilize the CPU(s). Adobe document services can be called by either passing the request files by way of streams or

URI (that is, HTTP URL or local file system). For interactive sizing tests, the form design andgenerated output were passed using HTTP references. The remaining request files used acombination of streams and the local file system.

It is assumed that Adobe document services are being called in such a way that they can be scaledlinearly, horizontally, and vertically.

It is also assumed that Adobe document services will run proportionally the same speed on variousplatforms based on the CPU rating of the hardware.

The ABAP Workbench stack and Adobe document services exist on the same hardware device foroptimal configuration.

5.2 Determining SAPS Rating For Each Document TypeThis section describes how a performance test was constructed to determine the SAPS rating for eachAdobe document services interactive document complexity type. These SAPS ratings can then bereused for each customer business case.As stated above, the criteria for determining complexity of an interactive form will be the number ofpages, number of interactive form elements, and the number of static form elements. The sampleinteractive forms are sized to represent each of four form types: small simple (1-page), small complex(1-page), medium (2-page) and large (4-page). (See Appendix B for a series of form samples.)Three test sections are defined to represent a typical workflow, form generation, application of securitysettings, and use of digital signatures. Each interactive sample form includes three populated signaturefields:

1. Form Generation

(A) Adobe document services PDF cache disabled and Reader usage rights applied.

(B) Adobe document services PDF cache enabled and Reader usage rights applied

2. Application of Security Settings

(C) Review version of form – no changes or printing permitted

3. Digital Signatures

(D) Extraction of all signatures

(E) Extraction of form data when the second signature was applied


Copyright/Trademark

1313

The performance test was performed as follows:Using an optimal number of parallel requests the maximum throughput of the sample forms in pages perhour was determined.

Let cpu_saps be the SAPS rating of the CPU performing the performance test.

Let ssph be the number of small simple interactive documents that can be generated per hour.

Let scph be the number of small complex interactive documents that can be generated perhour.

Let mph be the number of medium size interactive documents that can be generated per hour.

Let lph be the number of large size interactive documents that can be generated per hour

Example 5: Performance Test Resultscpu_saps = 8000 SAPS (SAPS rating of the computer performing the performance test)

Test SSPH SCPH MPH LPHA 27200 14500 19200 21000B 97110 93600 95940 85800C 23000 21000 22000 20000D 26500 17000 27000 16000E 30000 26000 28000 26500

Table 3.1 All numbers are in documents per hour

The SAPS rating of each interactive form complexity were determined to be as follows:

SS_SAPS(small simple) = cpu_saps / ssph

SC_SAPS(small complex) = cpu_saps / scph

M_SAPS(medium) = cpu_saps / mph

L_SAPS(large) = cpu_saps / lph

Test SS_SAPS SC_SAPS M_SAPS L_SAPSA 0.294 0.551 0.417 0.380B 0.082 0.086 0.083 0.093C 0.347 0.380 0.363 0.400D 0.301 0.470 0.296 0.500E 0.266 0.308 0.286 0.301

Table 3.2 All numbers are in SAPS per document


Copyright/Trademark

1414

5.3 Sizing GuidelinesFor an interactive form-based application, the SAPS rating is determined based on the number of smallsimple, small complex, medium, and large documents that the calling application is expected to produceper hour. It also includes the number of each document type that requires security settings and/or digitalsignature related operations.The documents that the application produces must be compared with the interactive sample Adobedocument services’ documents that have been benchmarked in section 3.2.With the SAPS ratings for each document and operation type combination (Table 3.2), the total numberof SAPS required for an application can be estimated with the following formulas.For each small simple operation:SAPS = small simple documents required per hour * SS_SAPS (sum of SAPS for each operation type)For each small complex operation:SAPS = small complex documents required per hour * SC_SAPS (sum of SAPS for each operation type)For each medium operation:SAPS = medium documents required per hour * M_SAPS (sum of SAPS for each operation type)For each large operation:SAPS = large documents required per hour * L_SAPS (sum of SAPS for each operation type)The Totals SAPS can then be converted to a number of computers by dividing the total SAPS requiredby the SAPS rating of the computer being considered to run the application. (Seewww.sap.com/benchmark to determine the SAPS rating of the computer being considered for theapplication.)

# of computers = Total SAPS / machine_saps



Copyright/Trademark

1515

5.4 Interactive Form Sizing Example

Example 6:This example uses the SAPS ratings calculated in example 5 (see section 4.2).The customer requires 1500 small, simple documents per hour, 1000 small, complex documents perhour, 1400 medium documents per hour, and 700 large documents per hour. Each of these documentsalso requires security settings and that the data be extracted from the document after it has beendigitally signed. If the forms are both interactive and cacheable, performance gains offered by Adobedocument services PDF cache can be realized.The customer is using a 4-way SMP computer with, according to www.sap.com/benchmark, a SAPSrating of 4700.For each document type, the following costs can be combined:

Generate Form(Test B) + Apply Security Settings(Test C) + Extract Data From Form(Test E)

SAPS required for small simple documents = 1500 * (0.082 + 0.347 + 0.266) = 1042 SAPS

SAPS required for small complex documents = 1000 * (0.086 + 0.380 + 0.308) = 774 SAPS

SAPS required for medium documents = 1400 * (0.083 + 0.363 + 0.286) = 1024 SAPS

SAPS required for large documents = 700 * (0.093 + 0.400 + 0.301) = 556 SAPS

This application can be represented in a table (shown below).The total number of SAPS required by Adobe document services can be determined by summing theSAPS ADS Server column below.

Category Up to # documents per hour SAPS ADS serverSmall Simple 1500 1042

Small Complex 1000 774

Medium 1400 1024

Large 700 556

Total SAPS 3396

The customer would require 3396 / 4700 = CPU power equivalent to approximately four 4-way SMPcomputers as described above.



Copyright/Trademark

1616

6. COMMENTS AND FEEDBACKBoth are very welcome; please send them to Peter Barker [email protected]

mailto:[email protected]

adobe forms sizing nw 73

Documents