Installing the PDF Generator ES2 Network Printer client

PDF Generator ES2 includes an executable file to install the PDF Generator ES2 network printer on a client computer. After the installation is complete, a PDF Generator ES2 printer is added to the list of existing printers on the client computer. This printer can then be used to send documents for conversion to PDF.

Note:The PDF Generator ES2 Network Printer Client (wizard) is supported on 32-bit Windows platforms only.

If the PDFG Network Printer fails to install on Windows, use the operating system’s native Add Printer utility and configure it as described in “To configure PDFG Network Printer on Windows using the native Add Printer wizard:” on page 64.

➤ To install the PDF Generator ES2 Network Printer Client:

1. Ensure that you successfully installed PDF Generator ES2 on your server.

2. From a Windows client computer, enter the following URL in your web browser, where [server] is the name of the server where you installed PDF Generator ES2 and [port] is the application server port used:

Adobe LiveCycle ES2 Post-Deployment Activities

Installing and Deploying LiveCycle ES2 Using Turnkey Installing the PDF Generator ES2 Network Printer client 64

http://[server]:[port]/pdfg-ipp/install

3. On the Configure Internet Port screen, select Use the specified user account and provide the credentials of a LiveCycle user who has the PDFG Administrator/User role. This user must also have an email address that can be used to receive the converted files. To have this security setting apply to all users on the client computer, select Use the same security options for all users, and then click OK. Upon successful installation, a dialog box appears, indicating that “The Printer Adobe LiveCycle PDF Generator ES2 has been successfully installed.”

4. Click OK. You will now have a printer named Adobe LiveCycle PDF Generator ES2 in your list of available printers.

➤ To configure PDFG Network Printer on Windows using the native Add Printer wizard: 1. Click Start > Printers and Faxes and double-click Add Printer.

2. Click Next, select A network printer, or a printer attached to another computer, and then click

Next.

3. Select Connect to a printer on the internet or on a home or office network and type the following URL for the PDFG printer, where [server] is the server name and [port] is the port number where the server is running:

http://[server]:[port]/pdfg-ipp/printer

4. On the Configure Internet Port screen, select Use the specified user account and provide valid User Management credentials.

5. In the Printer Driver Select box, choose any standard PostScript-based printer driver (for example, HP Color LaserJet PS).

6. Complete the installation by choosing appropriate options (for example, setting this printer as default).

Note:The user credentials used while adding the printer must have a valid email ID configured in User Management to receive the response.

7. Configure the email service’s sendmail service. Provide a valid SMTP server and authentication information in the service’s configuration options.

➤ To install and configure the PDF Generator ES2 Network Printer Client using Proxy server port forwarding

1. Configure port forwarding on the CC Proxy server on a particular port to the LiveCycle ES2 server, and disable the authentication at proxy server level (since LiveCycle ES2 uses its own authentication). If a client connects to this Proxy server on the forwarded port, then all the requests will be forwarded to the LiveCycle ES2 server.

2. Install PDFG Network Printer using the following URL:

http://[proxy server]:[forwarded port]/pdfg-ipp/install. 3. Provide the necessary credentials for authentication of the PDFG Network Printer.

4. The PDFG Network Printer will be installed on the client machine which you can use for PDF conversion using the firewall protected LiveCycle ES2 server.

Adobe LiveCycle ES2 Post-Deployment Activities

Installing and Deploying LiveCycle ES2 Using Turnkey Installing the PDF Generator ES2 Network Printer client 65

If you installed the Connector for IBM FileNet service as part of your LiveCycle ES2 solution, you must configure the service to connect to the FileNet object store.

➤ To configure the connector using FileNet 4.x or FileNet 5.0 and CEWS transport: 1. Open the application server run file in a text editor. The run file is as follows:

● (Windows) [appserver root]/bin/run.bat ● (UNIX) [appserver root]/bin/run.sh

2. Add the location of the FileNet Configuration files as a Java option to the application server start command, and then save the file.

Note: If JBoss is running as a service, add the Java option in the registry where other JVM arguments are defined.

-Dwasp.location= <configuration files location>

For example, using a default FileNet Application Engine installation on a Windows operating system, add this Java option:

-Dwasp.location=C:/Progra~1/FileNet/AE/CE_API/wsi 3. If your deployment uses the Process Engine Connector service, copy the file

[appserver root]\client\logkit.jar to the following directory: ● (Manually-configured JBoss) [appserver root]/server/all/lib

● (Adobe-preconfigured JBoss)[appserver root]/server/lc_<db-name>/lib

4. Locate the adobe-component-ext.properties file in the [appserver root]/binfolder (if the file does not exist, create it).

5. Add a new system property that provides the location of these FileNet Application Engine JAR files: ● javaapi.jar

● soap.jar ● wasp.jar

● builtin_serialization.jar (FileNet 4.0 only) ● wsdl_api.jar ● jaxm.jar ● jaxrpc.jar ● saaj.jar ● jetty.jar ● runner.jar ● p8cjares.jar ● Jace.jar ● (optional) pe.jar

Note: Add the pe.jar file only if your deployment uses the IBMFileNetProcessEngineConnector service. The new system property should reflect this structure:

Adobe LiveCycle ES2 Post-Deployment Activities

Installing and Deploying LiveCycle ES2 Using Turnkey Installing the PDF Generator ES2 Network Printer client 66

[component id].ext=[JAR files and/or folders]

For example, using a default FileNet Application Engine installation on a Windows operating system, add the following system property on a new line with no line breaks and end the line with a carriage return:

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

Note: For FileNet 4.x, add following .jar files

com.adobe.livecycle.ConnectorforIBMFileNet.ext= C:/Program Files/FileNet/AE/CE_API/lib2/javaapi.jar, C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/soap.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/wasp.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/builtin_serialization.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/wsdl_api.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/jaxm.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/jaxrpc.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/saaj.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/jetty.jar, C:/Program Files/FileNet/AE/CE_API/wsi/lib/runner.jar, C:/Program Files/FileNet/AE/CE_API/lib2/p8cjares.jar, C:/Program Files/FileNet/AE/CE_API/lib/Jace.jar, C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar

Note: Add C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar only if your

deployment uses the IBMFileNetProcessEngineConnector service.

Note: For FileNet 4.5, remove the line C:/Program

Files/FileNet/AE/CE_API/wsi/lib/builtin_serialization.jar,

Note: For FileNet 5.0, add following .jar files

C:/Program Files/FileNet/AE/CE_API/lib/Jace.jar, C:/Program Files/FileNet/AE/CE_API/lib2/javaapi.jar, C:/Program Files/FileNet/AE/CE_API/lib2/log4j.jar, C:/Program Files/FileNet/AE/Router/lib/mailapi.jar, C:/Program Files/FileNet/AE/Workplace/WEB-INF/lib/pe.jar C:/Program Files/FileNet/AE/CE_API/lib/stax-api.jar, C:/Program Files/FileNet/AE/CE_API/lib/xlxpScanner.jar C:/Program Files/FileNet/AE/CE_API/lib/xlxpScannerUtils.jar C:/Program Files/FileNet/AE/Router/java/jre/lib/xml.jar

6. (FileNet Process Engine Connector only) Configure the connection properties for the process engine as follows:

● Using a text editor, create a file with the following content as a single line and end the line with a carriage return:

RemoteServerUrl = cemp:http://[contentserver_IP]:[contentengine_port]/ wsi/FNCEWS40DIME/

Adobe LiveCycle ES2 Post-Deployment Activities

Installing and Deploying LiveCycle ES2 Using Turnkey Installing the PDF Generator ES2 Network Printer client 67

● Save the file as WcmApiConfig.properties in a separate folder, and add the location of the folder that contains the WcmApiConfig.properties file to the adobe-component-ext.properties file.

For example, if you save the file as c:/pe_config/WcmApiConfig.properties, add the path c:/pe_config to the adobe-component-ext.properties file.

Note: The filename is case-sensitive.

7. Locate the login-config.xml file in thefollowing folder and add the following application policy as a child of the <policy> node:

● (Manually-configured JBoss)[appserver root]/server/all/conf

● (Adobe-preconfigured JBoss)[appserver root]/server/lc_<db-name>/conf <application-policy name = "FileNetP8WSI">

<authentication>

<login-module code = "com.filenet.api.util.WSILoginModule" flag = "required" />

</authentication> </application-policy>

8. (FileNet Process Engine Connector only) If your deployment uses the process engine, add the following node to the login-config file:

<application-policy name = "FileNetP8"> <authentication>

<login-module code = "com.filenet.api.util.WSILoginModule" flag = "required" />

</authentication> </application-policy>

9. If the application server is not currently running, start the server. Otherwise, stop and then restart the server.

10. If JBoss runs as as service, start (or restart) the JBoss for Adobe LiveCycle ES2 service. 11. Open a web browser and enter this URL:

http://[host]:[port]/adminui

12. Log in using the default user name and password:

User name: administrator

Password: password

13. Click Services > LiveCycle ES2Connector for IBM FileNet.

14. Provide all of the required FileNet repository information and, under Repository Service Provider Information, select IBM FileNet Repository Provider.

If your deployment uses the optional process engine service, under Process Engine Settings, select Use Process Engine Connector Service and specify the process engine settings. For more information, click the Help link in the upper-right corner of the page.

Note: The credentials that you provide in this step are validated later when you start the IBM FileNet repository services. If the credentials are not valid, an error is thrown and the services will not start.

Adobe LiveCycle ES2 Post-Deployment Activities

Installing and Deploying LiveCycle ES2 Using Turnkey Installing the PDF Generator ES2 Network Printer client 68

16. Select the check box next to each of these services and then click Start: ● IBMFileNetAuthProviderService

● IBMFileNetContentRepositoryConnector ● IBMFileNetRepositoryProvider

● IBMFileNetProcessEngineConnector (if configured)

If any of the services do not start correctly, verify the settings entered in step 14. 17. Do one of the following tasks:

● To use the FileNet Authorization service (IBMFileNetAuthProviderService) to display content from a FileNet object store in the Resources view of Workbench ES2, continue with this procedure. Using the FileNet Authorization service overrides the default LiveCycle ES2 authorization and must be configured to log in to Workbench ES2 by using FileNet credentials.

● To use the LiveCycle ES2 repository, log in to Workbench ES2 by using the LiveCycle ES2 super administrator credentials (by default, Administrator and password). The credentials provided in step 14 use the default LiveCycle ES2 authorization service for accessing the default repository in this case.

18. Restart your application server.

19. Log in to LiveCycle Administration Console and click Settings > User Management > Domain Management.

20. Click New Enterprise Domain and then type a domain ID and name. The domain ID is the unique identifier for the domain. The name is a descriptive name for the domain.

Note: When using MySQL for your LiveCycle ES2 database, use only single-byte (ASCII) characters for the ID. (See “Adding enterprise domains” in LiveCycle ES2 Administration Help.)

21. Add a custom authentication provider: ● Click Add Authentication.

● In the Authentication Provider list, select Custom. ● Select IBMFileNetAuthProviderService and then click OK. 22. Add an LDAP authentication provider:

● Click Add Authentication.

● In the Authentication Provider list, select LDAP and then click OK. 23. Add an LDAP directory:

● Click Add Directory and, in the Profile Name box, type a unique name, and then click Next. ● Specify values for the Server, Port, SSL, Binding, and Populate page with options. If you select

User for the Binding option, you must also specify values for the Name and Password fields. ● (Optional) Select Retrieve Base DN to retrieve base domain names, as required. When finished,

click Next.

● Configure the user settings, click Next, configure group settings as required, and then click Next. For details about the settings, click Help linkin the upper-right corner of the page.

Adobe LiveCycle ES2 Post-Deployment Activities

Installing and Deploying LiveCycle ES2 Using Turnkey Configuring SharePoint client access 69

25. Select the new enterprise domain and click Sync Now. Depending on the number of users and groups in your LDAP network and the speed on your connection, the synchronization process may take several minutes.

(Optional) To verify the status of the synchronization, click Refresh and view the status in the Current Sync State column.

26. Navigate to Settings > User Management > Users and Groups.

27. Search for users that were synchronized from LDAP and perform these tasks: ● Select one or more users and click Assign Role.

● Select one or more LiveCycle ES2 roles and click OK. ● Click OK a second time to confirm the role assignment.

Repeat this step for all users you want to assign roles to. For more information, click the Help link in the upper-right corner of the page.

28. Start Workbench ES2 and log in using the following credentials for the IBM FileNet repository:

User name:[username]@[repository_name]

Password: [password]

The FileNet object store should now be visible in the Resources view within Workbench ES2. If you do not log in using the username@repository name, Workbench ES2 attempts to log in to the default repository specified in step 14.

29. (Optional) If you intend to install the LiveCycle ES2 Samples for Connector for IBM FileNet, create a FileNet object store named Samples and install the samples in that object store.

After you configure your Connector for IBM FileNet service, it is recommended that you see LiveCycle ES2 Administration Help. for information about configuring Workbench ES2 functions properly with your FileNet repository.