User manual MACROMEDIA LIVE CYCLE 7.2 INSTALLING AND CONFIGURING LIVECYCLE FOR JBOSS

[. . . ] bc Installing and Configuring LiveCycle for JBoss Adobe® LiveCycleTM October 2006 Version 7. 2 © 2006 Adobe Systems Incorporated. Adobe® LiveCycleTM 7. 2 Installing and Configuring LiveCycle for JBoss® for Microsoft® Windows® and Linux® Edition 1. 1, October 2006 If this guide is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected under copyright law even if it is not distributed with software that includes an end user license agreement. [. . . ] On the Application Configuration and Assembly Summary screen, review the configuration details, and then click Next. On the Configure and Assemble Products Summary screen, click Next. On the Tasks Completed screen, click Next (if you selected another task for Configuration Manager to perform) or click Finish to close Configuration Manager. Next step You must now configure your application server. (See "Manually Configuring JBoss" on page 53. ) 7 Manually Configuring JBoss This chapter describes how to manually configure the JBoss Application Server to prepare for the manual deployment of LiveCycle products. You can also automatically configure your application server, as part of the turnkey installation. (See "Installing LiveCycle Products Using the Turnkey Installation" on page 20. ) You need to perform the following tasks: Modify various JBoss configuration files on the instance of JBoss that hosts LiveCycle products. (See "Modifying the JBoss configuration files" on page 54. ) Copy the appropriate Watched Folder file to JBoss. (See "Configuring JBoss for Watched Folder" on page 58. ) Create the data source so that LiveCycle products can connect to the database. (See "Connecting JBoss for LiveCycle products to the LiveCycle database" on page 58. ) Note: If you have installed LiveCycle PDF Generator in addition to other previously installed LiveCycle products, you need to change the credentials of the login user account to those of the account used to install Microsoft Office on the machine where LiveCycle is installed. The procedures in this chapter are for configuring the application server for all LiveCycle products. If a product requires a different process, the steps are highlighted. If you previously configured your application server for deploying other LiveCycle products, you do not need to perform the procedures in this chapter again. This chapter assumes that you have configured your database and created a database user account. If you have not done this, see "Preparing Your Environment" on page 42. Starting and stopping JBoss Several procedures in this chapter require you to stop and start the instance of JBoss where you want to deploy LiveCycle products. To start JBoss: 1. From a command prompt, navigate to [appserver root]/bin. Start the server by entering the following command: (Windows) run. bat -c all (Linux) . /run. sh -c all To stop JBoss: 1. From a command prompt, navigate to [appserver root]/bin. Stop the server by entering the following command: (Windows) shutdown. bat -S (Linux) . /shutdown. sh -S 53 Adobe LiveCycle Installing and Configuring LiveCycle for JBoss Manually Configuring JBoss Modifying the JBoss configuration files 54 Modifying the JBoss configuration files You need to modify the following areas on the instance of JBoss that hosts LiveCycle products: endorsed directory run. bat file (Windows) or run. sh file (Linux) JMS jacorb. properties file EAR file class-loading isolation maximum threads settings dom4j. jar file cluster-service. xml Note: If you are running JBoss on Red Hat Enterprise Linux Advanced Server 3. 0, you must set the LD_ASSUME_KERNEL environment variable to 2. 4. 19 using the export LD_ASSUME_KERNEL=2. 4. 19 command. You must then run JBoss from the same shell in which you set the environment variable. To create an endorsed directory: 1. Navigate to the [appserver root]/server/all/lib directory and create a new directory called endorsed. Copy the following files from the [LiveCycle root]/components/um/endorsed directory to the endorsed directory you just created: dom3-xercesImpl-2. 4. 0. jar dom3-xml-apis-2. 4. 0. jar xalan-2. 4. 1. jar To modify the run. bat or run. sh file: 1. Navigate to the [appserver root]/bin directory and open the following file in a text editor: (Windows) run. bat (Linux) run. sh Tip: Turn off word wrapping while editing to ensure that there are no hard returns in these command lines. [. . . ] You must then restart the database and application server. Adobe LiveCycle Installing and Configuring LiveCycle for JBoss Enhancing Server Performance Improving Windows Server Performance with LDAP 119 Improving Windows Server Performance with LDAP Using connection pooling on the search connection can decrease the number of ports need by as much as 50%, since that connection always uses the same credentials for a given domain, and the context and related objects are closed explicitly. To configure your Windows Server for connection pooling: 1. Start the registry editor by clicking Start > Run and in the Open box type regedit and click OK. Navigate to the registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters 3. In the right pane of the registry editor, look for the TcpTimedWaitDelay value name. [. . . ]