Overview

Binding & Exporting

Binding

Binding e-Form or Report width data

• OZR or OZD

• Input data, Form parameter, JSON/XML, ODI dataset

Exporting (=Converting)

Exporting e-Form or Report to:

• OZD or

• Documents (PDF, Word, Excel, Image, Text, etc.)

Client-side vs. Server-side Binding

Client-side Binding

1. The Client OZ viewer exports OZR to documents on the local computer or device.

2. Sends exported documents to the application on the server

3. HTML5 viewer is not able to export with font embedding -> Server-side exporting is necessary

Server-side Binding

1. The Client sends input data to OZ Server or Scheduler and

2. OZ Server or Scheduler binds the input data with OZR and

3. Export OZR to documents

4. Exported documents use fonts on the server -> NO font corruption

5. Need to prepare the required fonts on the server.

Server-side Exporting

Scheduler API

• Handle ODM requests for reports and Exporting requests

• Fast performance by parallel task processing

• Effective by scheduled batch processing

• Reduce OZ server task loads

• Simple and easy to add Scheduler server

• Cheaper than scale-up or scale-out

OZ Server binding

• Large data binding and many exporting requests lower the OZ Server performance.

• System scale-up or scale-out is expensive and not that simple and easy