WebGrabber Release Notes 8.1.0

Software Requirements

The following software is required to successfully use WebGrabber:

• Windows Server® 2008 R2, 2012 R2, or 2016
• Microsoft® .NET Framework is required to use WebGrabber's .NET component
  (.NET 4.6.2 for the API and for the service — if it is not detected, you can install it.)

Note:

• For WebGrabber installations 2012 R2.1 and higher, ActivePDF recommends Internet Explorer 11 if using the Internet Explorer engine.
• If you are installing an ActivePDF product on a Windows 2012 server, you need to download and install two Microsoft updates for Windows 2012 servers. These updates resolve issues with the Microsoft Visual 2015 C++ Redistributable Runtime Components. For links and step-by-step instructions, see this ActivePDF Knowledge Base article: Installing ActivePDF Products on a Windows 2012 Server.
• Read the following Knowledgebase article if this error occurs when using the Internet Explorer conversion WebGrabber:

  Attempted to run an Internet Explorer conversion with I.E. conversions disabled. Enable I.E. conversions in the Configuration Manager.
  
  

Important! If using Windows Server 2012 or above, and using the Internet Explorer engine for conversions, follow the instructions in the Installation topic of the WebGrabber Quick Start Guide.

Hardware Requirements

The minimum hardware requirements for WebGrabber are:

• 350 MB of RAM

• 175 MB of hard disk space (for application)

New Features

New features for this release include:

• Major upgrade to the Native Engine converter for better fidelity.
• WebGrabber 8.1.0 now supports Windows Server 2016.
• JSON replaces XML in this release. Previously, when upgrading a WebGrabber installation, you could reinstall your custom profiles and settings using the .xml files in the backup folder.
  

  Now, to reinstall your custom profiles and settings, you must convert the .xml files in the backup folder to .json files. Then, you can use those converted files to replace the newly-installed .json files here:

  C:\ProgramData\activePDF\Settings\WebGrabber

  For help converting the existing backup XML settings to JSON settings, contact ActivePDF Support.

• Changes to the API:
  • The WebGrabber COM and .NET ports are now 62625.
• You can now create output files in memory using the updated/new COM API calls:
  • OutputFormat: Updated OutputFormat property, adding File and ByteArray.
  • OutputFileFormat: Added new OutputFileFormat enumerator, which uses 64-byte-encoded characters.
• New .NET API:
  • OutputFormat: Added new OutputFormat property, which uses File and ByteArray.
  • OutputFileFormat: Added new OutputFileFormat enumerator. If OutputFormat is set to ByteArray, it contains the byte array returned from the service.
• WebGrabber supports the let statement in JavaScript.
• In this release, you cannot concatenate files generated in-memory. The Overwrite method has no effect on in-memory generation.