PDF Generator lets you enable multi-threaded file conversions for certain types of files. Multi-threaded file conversion improves the performance of PDF Generator by allowing it to perform multiple conversions at the same time.
By default, PDF Generator can convert only one OpenOffice, Microsoft® Word, or PowerPoint document at a time. If you enable multi-threaded conversions, PDF Generator can convert more than one of the documents concurrently. PDF Generator launches multiple instances of OpenOffice or PDFMaker (used to perform the Word and PowerPoint conversions).
Multi-threaded file conversions are not supported with Microsoft® Word 2003 and PowerPoint 2003. To enable multi-threaded file conversions, upgrade to Microsoft® Word 2007 and PowerPoint 2007 or Microsoft® Word 2010 and PowerPoint 2010.
Multi-threaded file conversions are not supported with Microsoft® Excel, Microsoft® Visio, Microsoft® Project, or Microsoft® Publisher.
Each instance of OpenOffice or PDFMaker is launched using a separate user account. Each user account that you add must be a valid user with administrative privileges on the Forms Server computer. In a clustered environment, the same set of users must be valid for all nodes of the cluster.
On the User Accounts page in the administration console, you can specify which user accounts to use for multi-threaded file conversions. You can add accounts, delete them, or change account passwords. If you are running PDF Generator on Windows Server 2003 or Windows Server 2008, add at least three user accounts that have administrator privileges.
When adding users for OpenOffice, Microsoft® Word, or Microsoft® PowerPoint on Windows Server 2003 or 2008, or for OpenOffice on Linux® or Sun™ Solaris™, dismiss the initial activation dialogs for all users.
On a Windows operating system, the administrator user accounts that are used for PDF conversion (PDFG users) must replace process level token privileges. You can add this right by using the Group Policy Editor:
If you are running OpenOffice, Microsoft® Word, or Microsoft® PowerPoint on Windows Server 2008, disable UAC for each user added.
Add user accounts. (See Add a user account.)
Next, you must change the /etc/sudoers file. The default permission for this file is 440. Change the permission for this file to writable.
Add entries for additional users (other than the administrator who runs the Forms Server) in the /etc/sudoers file. For example, if you are running AEM forms as a user named lcadm and a server named myhost, and you want to impersonate user1 and user2, add the following entries to /etc/sudoers:
lcadm myhost=(user1) NOPASSWD: ALL lcadm myhost=(user2) NOPASSWD: ALL
This configuration enables lcadm to run any command on host ‘myhost’ as ‘user1’ or ‘user2’ without prompting for a password.
Ensure that you have assigned system user and PDFG user roles to ‘user1’ and ‘user2’ . To assign a PDFG role to a user, see Add a user account
Also in the /etc/sudoers file, locate and comment out this line by adding a number sign (#) at the beginning of the line:
This enables you to add Linux® users.
Change the permission for the etc/sudoers file back to 440.
Allow all the users that you added via Add a user account to make connections to the Forms Server. For example, to allow a local user named user1 the permission of making the connection to the Forms Server, use the following command
For more details, see xhost command documentation.
Restart the server.
OpenOffice must be installed in a directory location that all PDFG users can access. You can verify this by logging in as the PDFG user and checking whether you can launch OpenOffice without issues.
In the administration console, click Services > PDF Generator > User Accounts.
Click Add and enter the user name and password of a user who has administrative privileges on the Forms Server. If you are configuring users for OpenOffice, dismiss the initial OpenOffice activation dialogs.
If you are configuring users for OpenOffice, the number of instances of OpenOffice cannot be greater than the number of user accounts specified in this step.
Restart the Forms Server.