1) HtmltoPDF (webkit route) does NOT work on AIX for AEM 6.2.
2) HtmltoPDF (webkit route) is deprecated on AIX, AEM 6.2 onwards.
3) HtmltoPDF (webkit route) on Linux and Solaris has a dual dependency on openssl-0.9.x and openssl-1.0.x. This is a known issue that will be addressed by a formal patch but for the moment, it can be made to work with a workaround that requires some additional settings as listed below.

RHEL 6.x and 7.x
We need the following additional 32 bit (i.e. i686) libs on the system:
a. /usr/lib/libcurl.so.3
b. /usr/lib/libssl.so.0.9.6
c. /usr/lib/libcrypto.so.0.9.6
d. /usr/lib/libssl.so.1.0.0
e. /usr/lib/libcrypto.so.1.0.0

Files [a,b,c] are provided by compat-libcurl3, which if installed via yum, pulls in a transitive dependency on openssl-0.9.6
Files [d,e] are provided by openssl-1.0.x. If it does not install these in /usr/lib, create symbolic links with these names pointing to the actual libs.

Ensure 32-bit libs are available (libicudata.so.42) for Webkit based HtmlToPdf conversion and 64-bit libicudata.so.42 libs are available for PhantomJS based HtmlToPdf conversion.

The existence of /usr/lib/X11/fonts is mandatory. In recent RHEL distributions, the directory /usr/lib/X11 has been eliminated therefore we need to manually create it.
  a) Create a symbolic link /usr/lib/X11/fonts -> /usr/share/X11/fonts
  b) Availability of IBM type1 courier fonts. Unzip these to /usr/share/X11/fonts (inside the folder 'font-ibm-type1-1.0.3')
  c) /usr/share/fonts needs to be present
  d) Create a symbolic link /usr/share/fonts/X11_fonts pointing to /usr/share/X11/fonts

Solaris 11
We need the following additional 32 bit (i.e. i686) libs on the system:
a. /usr/lib/libssl.so.0.9.6
b. /usr/lib/libcrypto.so.0.9.6

If these are not present in /usr/lib, create symbolic links with these names pointing to the actual libs viz.
libssl.so.0.9.6 -> libssl.so.1.0.0
libcrypto.so.0.9.6 -> libcrypto.so.1.0.0

Dieses Werk unterliegt den Bedingungen der Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.  Twitter™- und Facebook-Beiträge fallen nicht unter die Bedingungen der Creative Commons-Lizenz.

Rechtliche Hinweise   |   Online-Datenschutzrichtlinie