Install livecycle Data Services 2.6 beta2. Click production to see the original article. This article is a post after translation. Only the configuration about Tomcat 6 is selected: unzip download installer for Windows (exe, 181 MB) l download installer for Linux (bin, 189 MB) l download installer for Solaris (bin, 192 MB) l download installer for Java (jar, 156 MB) 1. Install livecycle Data Services 2.6 beta22 livecycle Data Services es and Apache Tomcat application server integration 3. Run testdrive 4 livecycle Data Services es on the Integration Platform of livecycle Data Services es and Apache Tomcat Application Server java EE application (if you download a jar package, see, otherwise, skip this step. 5. add specific server configurations (take Tomcat as an example)
1. Install livecycle Data Services 2.6 beta2Adobe livecycle Data Service ES is like a javaee web application, each installation allows you to select * livecycle Data Services es and integrated Apache Tomcat Application Service * livecycle Data Services es web application livecycle Data Services es from the configuration file to provide the installation version for the platform * windows * Linux * Solaris * Java (cross-platform installation) livecycle Data Services es supports the following servers: * Apache Tomcat 6.0.x * JBoss Application Server 4.0.3 SP1 +, 4.2.x * BEA WebLogic 9 and 10 * IBM WebSphere Application Server 6. 1.x * Fujitsu interstage 9 * Hitachi cosminexus 7 * NEC webotx * Oracle 10g as (10.1.3) * SAP NetWeaver ce 7.1 SP3 * Adobe JRun 4 Updater 7 Note: livecycle Data Services es does not include any flex compiler, including the web-layer compiler in previous versions. To set information about your compilation environment, see setting up an SDK, compilers, and flex builder for livecycle services es 2.6. Also note that you integrate standard separate livecycle Data Services es server and ColdFusion. for more information, see integrate livecycle Data Services es and ColdFusion 8. these installations all point to the root path. install_root points to the root path of your livecycle Data Services es installation. These installations include the following web application archive (WAR) file * LCDs. the most important war file, using this file can serve as the starting point for creating your sample livecycle Data Services es application * lcds-samples.war simple sample livecycle Data Services es application * ds-console.war for sample livecycle Data Services es simple listening application per wa R files are isolated and independent applications. If you want to create a Java EE web application configuration, you must have a ready-made Java EE application server or a servlet container that can interpret the web application. If you do not have a ready-made javaee server or are not familiar with war file deployment, you can start by using integrated tomcat configuration.
2. Integration of livecycle Data Services es and Apache Tomcat Application ServerThe livecycle Data Services es and the integrated Apache Tomcat application server the livecycle Data Services es and the integrated tomcat installation options contain the following files and the root directory for installation under the directory: readme.htm contains the overview information LCDs. war livecycle Data Services es Web Application Template, a new starting point for the new application. lcds-samples.war livecycle Data Services es instance application. the ds-console.war is the deployment of a simple listening application for livecycle Data Services es. license/tomcat an installed Apache Tomcat includes LCDs, LCDs-samples, default console for application extension deployment/resources includes flex SDK source code, all annotations Set files for security, clustering, flex Ajax bridge, and wsrp directories and files. Flash Player installation is in the flex_sdk_3.zip file. Install livecycle Data Services es on the integrated tomcat configuration 1. Read the livecycle Data Services es release instructions and the latest consulting 2. Start the installation program. Perform one of the following operations based on your operating system. 1) # Windows version-double-click the installer file (L cds26-W in.exe ). 2) # Unix or Linux-set the working directory to the directory containing the installer file, and then enter the following command and specify the installer file as your operating system; 3) for example: 4 ). /lcds26-lin.bin-I console3. accept license agreement 4. on the serial number page, click "Next" to skip 5. specify the installation directory or accept the default settings. 6. select Tomcat Option 7 for livecycle data services. complete the remaining steps 8. start livecycle data services. Open a command window, browse your install_root/tomcat/bin, enter Catalina, and press Enter. For UNIX and Linux, enter. Catalina. In Windows, you can browse to install_root/tomcat/bin and double-click Catalina. bat. 9. The livecycle Data Services uses the HSQLDB database installed in the install_root/sampledb directory. Start instance Database: 1) Open a command window and go to the install_root/sampledb directory 2) Run startdb. BAT (Windows) or startdb. Sh (UNIX)
3. Run testdrive and integrated tomcat installationHere there is an installed tomcat6.0.14 and LCDs, among which there are many test drivers 1. start Tomcat (startup. BAT or starup. SH) 2. open the browser http: // localhost: 8400/LCDs-Samples
4. javaee web application of livecycle Data Services es
(
If you download jar
Check the package; otherwise, skip it)The following is the directory structure readme.htm LCDs. War lcds-samples.war ds-console.war license.txt/Resources
Install livecycle Data Services es
Web
Applications1. Read the livecycle Data Services es release instructions and the latest consulting 2. Start the installation program. Perform one of the following operations based on your operating system. 1) # Windows version-double-click the installer file (L cds26-W in.exe ). 2) # Unix or Linux-set the working directory to the directory containing the installer file, and then enter the following command and specify the installer file as your operating system; 3) for example: 4 ). /lcds26-lin.bin-I console3. accept license agreement 4. on the serial number page, click "Next" to skip 5. specify the installation directory or accept the default settings. 6. select Tomcat Option 7 for livecycle data services. complete the remaining steps 8. start livecycle data services. Open a command window, browse your install_root/tomcat/bin, enter Catalina, and press Enter. For UNIX and Linux, enter. Catalina. In Windows, you can browse to install_root/tomcat/bin and double-click Catalina. bat. 9. The livecycle Data Services uses the HSQLDB database installed in the install_root/sampledb directory. Start instance Database: 5) open a command window and go to the install_root/sampledb directory 6) Run startdb. BAT (Windows) or startdb. sh (UNIX) 10. run the installation program and open the Command Prompt window, browse to the (lcds26-install.jar) directory, enter java_home/bin/Java-jar lcds26-install.jar-I console9) and complete Step 3-9
5. add specific server configurationsL tomcatl webspherel jbossl oc4jl running_from_a_compressed_war) and the deployed war file you plan to use in the future. These steps are not required for integrated tomcat installation. 1. stop tomcat2. install JTA, I recommend using Java open trasaction Manager (jotm) 1) download jotm from http://jotm.objectweb.org/2) copy the JAR file from jotm-root/lib to [tomcat-root]/common/lib.3) and create a context file. Use the transaction tag to register a jotm file for your web application.
For example:
<Contextdoc base = "$ {Catalina. Home}/webapps/samples"
Privileged = "true" antiresourcelocking = "false"
Antijarlocking = "false"> <transaction
Factory = "org. objectweb. jotm. usertransactionfactory" jotm. Timeout = "60"/> </context> |
Note: If this file already exists, add the <transaction> label under <context>.
4) set the minimum JVM memory to 512 MB. Change the value of java_opts to-xmx 512m3. (Optional) use custom authentication, 4. (Optional) Use JMS middleware such as activemq or openjms 5. restart Tomcat
