Hyper.Net 6 SP3 Highlights

Multi-tenant architecture

The new architecture allows organizations to centrally deploy and administer Hyper.Net to simultaneously serve the needs of multiple “customers” that can include, for example, separate applications, business units and/or subsidiaries. The new architecture also enables service providers to offer secure, comprehensive content conversion and publishing services to multiple unrelated businesses or customers at the same time. Specific support for SharePoint server farms is included.

Publication request administration

Transformation requests sent directly to Hyper.Net’s Web Services interface can now be displayed within the Hyper.Net Administration Console along with requests received through Hyper.Net’s traditional document storage connectors (such as the Hyper.Net document storage connector for SharePoint). Large organizations are thus enabled to intuitively filter, delete, re-queue, manage rights and monitor the entire load of transformation requests sent to Hyper.Net, regardless of source.

Customizable administration console

A new, optional Silverlight GUI for the Hyper.Net Administration Console makes it possible to customize specific administration views and tasks. Customizable areas in the SilverLight GUI include Hyper.Net’s configuration profiles, interactive lists, search and filtering functions, navigation and content-sensitive help. The extension supports SilverLight’s plug-in model for 3rd party tools.

Blob manager

Organizations working with very large publications may face relational database-specific performance problems associated with the storage, update and retrieval of the data (PDF files, images, etc.) associated with each publication. To eliminate such bottlenecks, Hyper.Net 6.3’s blob manager enables the XML-based storage of very large publications on file systems and other content stores—including Azure. Only a reference to the blob is stored in the traditional database. The blob itself is retrieved from the designated storage facility on demand by any requesting Web application. The flexible, three-level blob management architecture also makes it possible to use multiple storage facilities (both relational and non-relational) at the same time.

New converters

A completely new, robust converter for InfoPath 2010 enables conversion of InfoPath files into PDF and PDF/A files that can in turn be included in compound PDF and PDF/A publications. Using the new converter, InfoPath forms used to track steps in a workflow process can now be automatically archived along with all the workflow’s associated content. Another new converter enables the conversion and archiving of all email stored in the EML format. EML files can also be published for online use in the HTML and Flash formats. Rounding out the new set of converters is an enhanced TIFF converter that makes it possible to transform single- and multi-page TIFFs into PDF and PDF/A files. The original size and quality of each TIFF page is preserved in the output file. This converter makes migrating from a TIFF-based archive to a PDF/A archive intuitive and transparent.

SharePoint list converter

A new SharePoint list converter allows organizations to recursively convert and publish any content placed on a SharePoint list (including PDF content) into a single PDF or PDF/A file—along with all of each list item’s associated attachments. The layout of the resulting PDF file, which can be printed, compounded and/or archived using traditional approaches, can be flexibly controlled using intuitive, Word-based layout templates. This feature is excellent for implementing “push the button” meeting minutes, proposal generation and other document assembly solutions.

Compound PDF enhancements

Hyper.Net’s compound PDF functions have been extended to create sequential page numbering throughout any compound publication, the creation of a common table of contents based on this numbering and context- and page-sensitive metadata stamping and watermarking. The new power enables the compounding of content from an unlimited number of source files into a single, cohesive, printable PDF publication for end-users or audit-proof PDF/A file for the archive.

Enhanced PDF handling

The process of converting and publishing PDF, PDF/A, compound PDF and compound PDF/A files has been enhanced to allow automatic enablement or disablement of the following properties in the output file: write protection, print protection, copy protection, display annotations, combine documents, hide toolbar and hide menu bar. It is also possible to automatically set passwords to further protect sensitive information and allow conformance with corporate PDF handling policies.