5.3 System requirements

On supported Windows and UNIX -like environments, LiveCycle supports Intel and AMD64 compatible chipsets running either 32-bit or 64-bit supported operating systems.

For a small production environment:

Intel environments: Pentium 4, 2.8 GHz or greater. Using a dual core processor will further enhance performance.

Sun SPARC environments: UltraSPARC V or later.

IBM AIX environments: Power4 or later

Memory requirements: 4 GB of RAM.

If you are installing Content Services for use with a DB2 database, you must have a minimum of 2 GB of RAM on the computer hosting the DB2 database.

When installing LiveCycle on AIX, Linux, or Solaris operating systems, you must install and configure the US English version of UTF-8 locale if it is not already installed. You will need the install media (CDs or DVDs) for the operating system to perform this task.

On Linux operating systems, ensure the following:

• All Linux distributions: Ensure that X Window libraries are installed on your operating system. This is required for PDF Generator and Forms. See documentation for your operating system for more information.

• SUSE Linux: You must install the glibc-locale-32bit library that ships with SUSE Linux Enterprise Server; otherwise, LiveCycle will not generate PDF files. This library file is not installed by default, you must use YaST to install it. (See the SUSE Linux Enterprise Server documentation for details.)

  If you plan to install LiveCycle on SUSE Linux 11, you must also install the libstdc++- libc6.2-2.so.3 libraries. SUSE Linux 11 does not include these libraries by default. For more information, see this Novell Web page. These libraries are required for running Adobe Central Pro Output Server

To avoid StuckThread issues on a Solaris or Linux environment, add or increase the rlim values in the /etc/system file.

1. (Linux) Locate and open the /etc/security/limits.conf file.

   (Solaris) Locate and open the /etc/system file.

2. (Linux) Add the following lines to the /etc/security/limits.conf file:

   <app_group> soft nofile 8192 
   <app_group> hard nofile 8192

   Replace <app_group> with the user group who will run the application server. You may also replace <app_group> with an asterisk (*) to match all users and user groups.

   (Solaris) Locate and modify the rlim values in the /etc/system file as follows:

   set rlim_fd_cur: The initial (soft) maximum number of file descriptors per process. Set this value to 8192 or more.

   set rlim_fd_max: The hard maximum number of file descriptors per process. Set this value to 8192 or more. (This modification is required only if the default value is lower than 8192). You must have super user privileges to change this value.

   Note: The rlim_fd_max value must be equal to or greater than the rlim_fd_cur value.

3. Save and close the file.

4. Restart your computer.

1. To access the System Configuration Utility, go to Start > Run and then enter MSCONFIG.

2. Click the Tools tab and scroll down and select Disable UAC.

3. Click Launch to run the command in a new window.

4. When finished, close the command window and close the System Configuration window.

5. Restart your computer.

To enable the UAC again, repeat the steps above and select Enable UAC before clicking Launch.

1. To access the System Configuration Utility, go to Start > Run and then enter MSCONFIG.

2. Click the Tools tab and scroll down and select Change UAC Settings.

3. Click Launch to run the command in a new window.

4. Adjust the slider to the Never notify level.

5. When finished, close the command window and close the System Configuration window.

6. Restart your computer.

To enable the UAC again, repeat the steps above and adjust the slider to a desired level before restarting your computer.

You must use a user account with administrator privileges for the following tasks:

• Installing Microsoft Office

• Installing PDF Generator

• Installing Acrobat for PDF Generator

• Running the application server process

If you are using a 64-bit application server on a system with PDF Generator, ensure that a 32-bit Java 6 JDK is installed in addition to the 64-bit one the application server uses. Set the environment variable JAVA_HOME_32. This variable is required to point to a 32-bit JDK on systems where a 64-bit application server is in use. The specific path varies based on the installation directory you specified and the operating system you are installing on.

Before you install PDF Generator, install the software that supports the file formats for which PDF conversion support is required and manually activate the licenses for the software using the user account that is used for running the application server process.

Refer to the individual licensing agreement for each native application that your LiveCycle deployment will support, and ensure that your LiveCycle deployment meets the licensing requirements specified. Typically, each LiveCycle user who will use native application support must also have an activated license on their own computer for the native application.

PDF Generator can be extended to convert these additional file types to PDF files by using the following applications:

• Microsoft Office 2007, 2010 (DOC,DOCX XLS,XLSX PPT,PPTX, RTF, TXT, Microsoft Office open XML Formats)

• Microsoft Office Visio 2007, 2010 (VSD)

• Microsoft Publisher 2007, 2010 (PUB)

• Microsoft Project 2007, 2010 (MPP)

• AutoCAD 2008 and 2009 (DWG, DWF)

• Corel WordPerfect 12, X4 (WPD)

• Adobe Photoshop® CS3

• Adobe FrameMaker® 7.2, 8.0 (FM)

• Adobe PageMaker® 7.0 (PMD, PM6, P65, PM)

• OpenOffice 3.3 (ODT, ODP, ODS, ODG, ODF, SXW, SXI, SXC, SXD, SXM)

You do not need to install a native software application to convert the following native file formats:

• Print files (PS, PRN, EPS)

• Web files (HTML)

• Image files (JPEG, GIF, BMP, TIFF, PNG)

However, if LiveCycle is installed and Acrobat X is not installed, install Acrobat X and then run the Acrobat_for_PDFG_Configuration.bat script, located in the folder [LiveCycle root]\pdfg_config. Otherwise, PDF conversions may fail.

The Configuration Manager sets the Acrobat_PATH (case-sensitive) environment variable automatically. You can also choose to set it manually, see 5.3.7.7 Setting environment variables. Restart your application server after setting the environment variable.

1. Open Acrobat.

2. Select Edit > Configurations.

3. Select Convert to PDF > Autodesk AutoCAD.

4. Click Edit Settings.

5. Click Configuration Preferences.

6. Click Browse next to the SHX Font File Search Path and specify the path to the SHX font file.

7. Click OK on each opened dialog.

PDF Generator requires that QuickTime 7 (Player or Pro) be installed if you want to convert video embedded in files, such as PowerPoint presentations to PDF multimedia files. This application is available from the Apple Downloads site.

You must set the environment variables in Windows if you plan to create PDF documents from applications such as FrameMaker, Photoshop, PageMaker, and WordPerfect.

The names of these environment variables are listed here:

• FrameMaker_PATH

• Notepad_PATH (This should be left blank)

• OpenOffice_PATH

• PageMaker_PATH

• Photoshop_PATH

• WordPerfect_PATH

• Acrobat_PATH

These environment variables are optional and need to be set only if you plan to use the corresponding application to convert PDF files through PDF Generator. The value of the environment variable should contain the absolute path of the executable that is used to start the corresponding application.

For example, the variable FrameMaker_PATH may contain the value C:\Program Files\Adobe\ FrameMaker7.2\FrameMaker.exe. However, OpenOffice_PATH is different from others. This variable must be set to the OpenOffice installation folder (instead of the path to the executable). A typical value of OpenOffice_PATH on Windows would be C:\Program Files (x86)\OpenOffice.org 3\.

Paths for Microsoft Office applications such as Word, PowerPoint, Excel, Visio, and Project or for AutoCAD are not required. The Generate PDF service starts these applications automatically if they are installed on the server.

Before you complete an automatic installation of PDF Generator on Windows, ensure that the Service Control Manager command line tool, sc.exe, is installed in the Windows environment. Some Windows servers do not have this software preinstalled. By default, the sc.exe file is installed in the C:\Windows\system32 directory. Most OS installations have this tool installed. If you do not have the tool installed, it is available in the Windows Resource Kit for your specific version of Windows. To confirm that the tool is installed on your server, type sc.exe from a command prompt. The tools usage is returned.

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 by launching multiple instances of OpenOffice or PDFMaker (which is used to perform the Word and PowerPoint conversions).

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 LiveCycle Server computer. On 64-bit Windows, disable Windows UAC. For more information, see 5.3.5 Configuring Windows installation

After your LiveCycle Server is configured, add LiveCycle user accounts in Administration Console. See the User accounts for multi-threaded file conversions section in the LiveCycle installation guide for your application server. To enable multiuser support for native files and OpenOffice files on a Windows environment, add a minimum of three users with the following permissions.

When you add users for PDF Generator native conversions, grant the user running the application server with the Replace a process level token privilege.For more information, see 5.3.7.12 Granting the Replace a process level token privilege (Windows only)

To enable multi-user support for native files and OpenOffice files on a Windows environment, a minimum of three users with the following permissions must be added. On a AIX, Linux, or Solaris platform, create at least one user.

When you add users for PDF Generator native conversions, you must grant the user running the application server with the Replace a process level token privilege. See 5.3.7.12 Granting the Replace a process level token privilege (Windows only).

User accounts that are used to start the application server from a command prompt and not as a Windows service requires the Replace a process level token privilege. This setting is required for PDF Generator.

1. Click Start > Run, and then type gpedit.msc.

2. On the Group Policy dialog box, select Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment, and double click Replace a process level token.

3. Click Add User or Group, add the Windows user account that is used to open the command prompt from which the application server is started.

4. Restart Windows, and then start the application server.

1. Start the DB2 Configuration Assistant.

2. Click Selected > Add Database Using Wizard.

3. Select Manually Configure a Connection to a Database and click Next.

4. Select TCP/IP and click Next.

5. Specify the following TCP/IP communication options and then click Next:

   • In the Host Name box, type the host name of the server hosting DB2 Content Manager.

   • Leave the Service Name box empty.

   • In the Port Number box, type the port number. The default DB2 Content Manager port number is 50000.

6. In the Database Name box, type the IBM Content Manager datastore name and, in the Database Alias box, type the alias name for the datastore and then click Next.

7. Click Next to accept the default data source settings.

8. In the Operating System list, select the operating system you are using and then click Next.

9. Specify the following system options and then click Next:

   • In the System Name box, type the server name hosting DB2. If you click Discover, DB2 Content Manager searches for the system name you specified and, if the system is not found, all of the DB2 instances are listed.

   • In the Host Name box, type the name of the host, or click View Details to show the domain and IP address of the system you named in the previous step.

   • In the Operating System list, select the operating system (Windows, Linux, or AIX) on which you deployed DB2 Content Manager.

10. (Optional) To specify Security options, select Use Authentication Value in Server’s DBM Configuration and click Finish.

11. In the Test Connection dialog box, test the connection as required.

1. Configure the initial connection by following the steps in 5.3.9.1 Configure the connection for a single IBM Content Manager datastore.

2. Add additional database connections by modifying the cmbicmsrvs.ini file (the file that stores the datastore information) as follows:

   • From a command prompt window, change the directory to [II4C home]/bin (for example, C:\Program Files\db2cmv8\ on Windows or /opt/IBM/db2cmv8 on AIX, Linux, or Solaris).

   • Run the cmbenv81.bat (Windows) or cmbenv81.sh (AIX, Linux, or Solaris) file to set the environment and the classpath for the Java Utilities of II4C.

   • Change the directory to [II4C working directory]/cmgmt/connectors where [II4C working directory] is one of the following paths:

     (Windows) C:/Program Files/db2cmv8

     (Linux, AIX) /home/ibmcmadm

     (Solaris) /export/home/ibmcmadm

   • Run the command

     java com.ibm.mm.sdk.util.cmbsrvsicm -a add -s <library server database name> -sm <database schema name>

     where <library server database name> is the same as Database Alias configured in step 6 above.

   Note: The following procedure allows users without DB2 rights to share the connection credentials through the cmbicmenv.ini file.

1. From a command prompt window, change the directory to [II4C home]/bin (for example, C:\Program Files\db2cmv8\ on Windows or /opt/IBM/db2cmv8 on AIX, Linux, or Solaris).

2. Run the cmbenv81.bat (Windows) or cmbenv81.sh (AIX, Linux, or Solaris) file to set the environment and the classpath for the Java Utilities of II4C.

3. Change the directory to [II4C working directory]/cmgmt/connectors, where [II4C working directory] is one of the following paths:

   (Windows) C:/Program Files/db2cmv8

   (Linux, AIX) /home/ibmcmadm

   (Solaris) /export/home/ibmcmadm

4. Run the command

   java com.ibm.mm.sdk.util.cmbenvicm -a add -s <library server database name> -u <database user ID> -p <database password>

   where <library server database name> is the same as Database alias configured in step 6 above.

1. In a text editor, copy the following script:

   Note: The following text contains formatting characters for line breaks. If you copy this text to a location outside this document, remove the formatting characters when you paste it to the new location.

   For DB2 9.1

   connect to dbname; 
   CREATE BUFFERPOOL BP32K SIZE 4000 PAGESIZE 32768 NOT EXTENDED STORAGE; 
   CREATE TEMPORARY TABLESPACE dbname_TEMP_32K IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 32768 MANAGED BY SYSTEM USING ('DB2_root\dbname32k_TEMP') EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL BP32K; 
   CREATE REGULAR TABLESPACE dbname_DATA_32K IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 32768 MANAGED BY DATABASE USING (FILE'DB2_root\dbname32k_DATA'9000) EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL BP32K; 
   commit work; 
   deactivate database dbname; 
   activate database dbname; 

   For DB2 9.5

   connect to dbname; 
   CREATE BUFFERPOOL BP32K SIZE 500 PAGESIZE 32768; 
   CREATE TEMPORARY TABLESPACE dbname_TEMP_32K IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 32768 MANAGED BY SYSTEM USING 'DB2_root\dbname32k_TEMP') EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL 
   BP32K; 
   CREATE REGULAR TABLESPACE dbname_DATA_32K IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 32768 MANAGED BY DATABASE USING (FILE'DB2_root\dbname32k_DATA'9000) EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL BP32K; 
   commit work; 
   deactivate database dbname; 
   activate database dbname;

2. Make the following changes to the script:

   • Replace the instances of dbname with the name of your LiveCycle database.

   • Replace DB2_root with the path to the root directory where DB2 is installed.

   • Ensure that no commands include line breaks and each command is terminated by a semicolon (;).

   • Change 9000 in the following line based on your database size:

   FILE'DB2_root\dbname32k_DATA'9000

   This number specifies the minimum number of pages that is required to initialize the database. You can also change this number by using the DB2 administration tools after you initialize the database.

3. Save the text file in a location that DB2 Command Line Processor can access.

4. Open a DB2 command prompt and type the following command to run the script:

db2 -tf <path_to_script_file>/<script_file_name>