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. [. . . ] 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. (Windows) In the run. bat file, locate the following line: "%JAVA%" %JAVA_OPTS% -classpath "%JBOSS_CLASSPATH%" org. jboss. Main %* Replace the line with the following text: "%JAVA%" %JAVA_OPTS% -classpath "%JBOSS_CLASSPATH%" -Xms128m -Xmx512m -Dorg. apache. lucene. writeLockTimeout=10000 -Djava. endorsed. dirs=%JBOSS_HOME%/server/all/lib/endorsed org. jboss. Main -c all %* Adobe LiveCycle Installing and Configuring LiveCycle for JBoss Manually Configuring JBoss Modifying the JBoss configuration files 55 3. (Linux) In the run. sh file, locate the following text: # Execute the JVM "$JAVA" $JAVA_OPTS \ -classpath "$JBOSS_CLASSPATH" \ org. jboss. Main "$@" Replace the text with the following text: # Execute the JVM "$JAVA" $JAVA_OPTS -Xms128m -Xmx512m \ -classpath "$JBOSS_CLASSPATH" \ -Dorg. apache. lucene. writeLockTimeout=10000\ -Djava. endorsed. dirs=$JBOSS_HOME/server/all/lib/endorsed \ org. jboss. Main -c all "$@" 4. (SQL Server) Add the following argument to the text you modified in step 2 or 3: -Dadobe. workflow. scheduler. jdbc. delegate=org. quartz. impl. jdbcjobstore . MSSQLDelegate \ Note: This command should immediately follow the appropriate -Djava command above. Navigate to the [appserver root]/server/all/deploy/jms directory and open the hajndi-jms-ds. xml file in a text editor. Add the following text after the Jms XA Resource adapter section: <tx-connection-factory> <track-connection-by-tx>true</track-connection-by-tx> <jndi-name>adobe_JmsQueueXA</jndi-name> <xa-transaction/> <adapter-display-name>JMS Adapter</adapter-display-name> <config-property type="java. lang. String" name="SessionDefaultType">javax. jms. Topic</config-property> <security-domain-and-application>JmsXARealm </security-domain-and-application> <config-property type="java. lang. String" name="JmsProviderAdapterJNDI">java:/DefaultJMSProvider </config-property> </tx-connection-factory> <tx-connection-factory> <track-connection-by-tx>true</track-connection-by-tx> <jndi-name>adobe_JmsTopicXA</jndi-name> <xa-transaction/> <adapter-display-name>JMS Adapter</adapter-display-name> <config-property type="java. lang. String" name="SessionDefaultType">javax. jms. Topic </config-property> <security-domain-and-application>JmsXARealm </security-domain-and-application> Adobe LiveCycle Installing and Configuring LiveCycle for JBoss Manually Configuring JBoss Modifying the JBoss configuration files 56 <config-property type="java. lang. String" name="JmsProviderAdapterJNDI">java:/DefaultJMSProvider </config-property> </tx-connection-factory> 3. (LiveCycle PDF Generator, LiveCycle Assembler) Navigate to the [appserver root]/server/all/deploy/jms directory and unpackage the jms-ra. rar file. (LiveCycle PDF Generator, LiveCycle Assembler) Navigate to the [appserver root]/server/all/deploy/jms/META-INF directory and open the ra. xml file in a text editor. (LiveCycle PDF Generator, LiveCycle Assembler) In the ra. xml file, locate the following lines: <config-property-name>Strict</config-property-name> <config-property-type>java. lang. Boolean</config-property-type> <config-property-value>true</config-property-value> Change the value for <config-property-value> from true to false and save your changes to the file. Repackage the jms-ra. rar file. To modify the jacorb. properties file: 1. Navigate to the [appserver root]/server/all/conf directory and open the jacorb. properties file in a text editor. Locate the jacorb. poa. thread_pool_max property and change the property value to 16. To modify the maximum threads settings: 1. Navigate to the [appserver root]/server/all/deploy/jbossweb-tomcat50. sar/ directory and open the server. xml file in a text editor. In the <connector> element for port 8080, set maxThreads to 75, minSpareThreads to 25, and maxSpareThreads to 50, as shown in the following example: <!-- A HTTP/1. 1 Connector on port 8080 --> <Connector port="8080" address="${jboss. bind. address}" maxThreads="75" minSpareThreads="25" maxSpareThreads="50" enableLookups="false" redirectPort="8443" acceptCount="250" connectionTimeout="20000" disableUploadTimeout="true"/> 3. Save and close the file. To set EAR file class-loading to isolation mode: 1. Navigate to the [appserver root]/server/all/deploy/jbossweb-tomcat50. sar/META-INF directory and open the jboss-service. xml file in a text editor. Locate and set the following attribute: <attribute name="UseJBossWebLoader">false</attribute> 3. [. . . ] To account for heap fragmentation, the inline document size must not be set higher than 0. 1% of the total heap size. For example, a JVM maximum heap size of 512 MB can support a maximum inline size of 512 MB x 0. 001 = 0. 512 MB, or 512 KB. Cleaning up temporary files in the Global storage directory When a workflow process is executed, temporary files are placed in the Global storage directory, but are not deleted when the process is complete. These files are placed under subdirectories with the name, Session[NNNN], where NNNN is the workflow process ID. To prevent running out of disk space, you must regularly remove the Session directories associated with fully completed processes. [. . . ]