Installing Adobe LiveCycle Data Services ES2 Version 3.1

 

 

Contents

Adding LiveCycle Data Services SWC files to the Flex SDK

To compile an application, Flash Builder and mxmlc reference the SWC library files that ship with the Flex SDK in subdirectories of the frameworks directory. In Flash Builder, the frameworks directories for different Flex SDK versions are in the install_root/sdks/sdk_version directory.

LiveCycle Data Services ships the following additional sets of SWC files. Reference the set of SWC files that matches the Flex SDK you compile against.

To add the LiveCycle Data Services SWC files to the Flash Builder or mxmlc library path, copy the subdirectories of the install_root/resources/lcds_swcs/FlexSDK4/frameworks directory or the install_root/resources/lcds_swcs/FlexSDK3/frameworks directory to the corresponding Flex SDK frameworks directory.

Note: Flex 3.5 compatible SWC files are also available in the WEB-INF/flex/libs directory of a LiveCycle Data Services web application. By default, Flash Builder adds these files to the library-path of a project that uses LiveCycle Data Services. However, the Flex 4 compatible versions of these files are not available in that location. Add them manually from the install_root/resources/lcds_swcs/FlexSDK4/frameworks directory.

Installing the application modeling plug-in

The Modeler, also known as the application modeling plug-in, is a tool for creating and editing Adobe application modeling technology models. The Modeler is available on the adobe.com site. It consists of a set of Eclipse plug-ins in the Adobe_Application_Modeling_plugin_v102_eclipse35.zip file that you install into a stand-alone Flash Builder installation or an Eclipse installation that contains the Flash Builder plug-in installation.

You must have an installation of the released version of Flash Builder 4 before installing the Modeler. There are three installation options for Flash Builder:

Stand-alone Flash Builder

  1. Create an Adobe_Modeler_102 directory under the flash_builder_root/dropins directory.
  2. Unzip the Adobe_Application_Modeling_plugin_v102_eclipse35.zip file into the flash_builder_root/dropins/Adobe_Modeler_102/plugins directory. If your unzip program is set up to use folder names, unzip directly to the flash_builder_root/dropins/Adobe_Modeler_102 directory.
  3. Start or restart Flash Builder.

Flash Builder plug-in for separate existing Eclipse

  1. Create an Adobe_Modeler_102 directory under the flash_builder_root/dropins directory.
  2. Unzip the Adobe_Application_Modeling_plugin_v102_eclipse35.zip file to the eclipse_root/dropins/AdobeModeler_102/plugins directory. If your unzip program is set up to use folder names, unzip to the eclipse_root/dropins/AdobeModeler_102 directory.

    Note: If you are using Eclipse 3.4, unzip the Adobe_Application_Modeling_plugin_v102_eclipse34.zip file instead of the Adobe_Application_Modeling_plugin_v102_eclipse35.zip file.
  3. Start or restart Eclipse.

Flash Builder plug-in with bundled Eclipse

  1. Create an Adobe_Modeler_102 directory under the flash_builder_root/dropins directory.
  2. Unzip the Adobe_Application_Modeling_plugin_v102_eclipse35.zip file to the flash_builder_root/eclipse-host-distro/dropins/AdobeModeler_102/plugins directory. If your unzip program is set up to use folder names, unzip directly to the flash_builder_root/eclipse-host-distro directory.

  3. Start or restart Flash Builder.

Configuring and using application modeling

See "Model-driven applications" in Using LiveCycle Data Services for information on configuring and using application modeling. Visit these links to get an overview of model-driven development and its relationship to other features of LiveCycle Data Services and rich Internet application development in general:

Installing the Edge Server

The Edge Server is a standard LiveCycle Data Services server specially configured and deployed in an organization’s demilitarized zone (DMZ), which is the subnetwork that contains and exposes an organization's external services to the Internet. The installation process for the Edge Server is identical to the installation process for a LiveCycle Data Services server in the application tier. The only difference is that the Edge Server is installed in the DMZ and configured to use a gateway service that communicates with a gateway endpoint on the LiveCycle Data Services server in the application tier. For information about configuring and using the Edge Server, see "Edge Server" in Using LiveCycle Data Services.

Installing LiveCycle Data Services

Adobe® LiveCycle® Data Services runs as a J2EE web application. You can install LiveCycle Data Services in the secure application tier of your network environment or as an Edge Server in the Demilitarized Zone (DMZ). Installation for LiveCycle Data Services in the secure application tier and installation of the Edge Server are identical. To enable Edge Server functionality, configure the server as described in Using LiveCycle Data Services. LiveCycle Data Services is available on the adobe.com site.

The installer lets you choose from the following configurations:

LiveCycle Data Services offers installers for the following platforms.

See the list of supported platforms for LiveCycle Data Services 3.1 for officially supported operating system versions, application servers, and JDKs.

The installers include the following Web Application Archive (WAR) files:

Each WAR file is a separate, stand-alone web application. If you are using the J2EE web applications configuration, you must have an existing J2EE application server or servlet container available and understand web application deployment. If you do not have an existing J2EE server or are not familiar with WAR file deployment, use the integrated Tomcat configuration to get started.

These installation instructions refer to the root directory where you installed LiveCycle Data Services as install_root.

LiveCycle Data Services with integrated Apache Tomcat application server

The LiveCycle Data Services with integrated Tomcat installation option contains the following files and directories under the installation root:

readme.htm Contains overview information.
lcds.war LiveCycle Data Services web application template, used as a starting point for new applications.
lcds-samples.war LiveCycle Data Services sample applications.
ds-console.war Simple monitoring application for LiveCycle Data Services deployments.
license.txt License information.
/tomcat Contains an installation of Apache Tomcat that includes lcds, lcds-samples, and console web applications expanded and deployed in the default server.
/resources Fully commented configuration files, and directories and files used for security, clustering, Flex Ajax Bridge, and WSRP.
/sampledb Contains an HSQLDB database used by the sample applications.

Install LiveCycle Data Services in the integrated Tomcat configuration

  1. Start the installation program. Do one of the following, depending on your operating system:
  2. Accept the license agreement.
  3. (Optional) Enter the serial number and follow the prompts. If you don't enter a serial number, LiveCycle Data Services runs in developer mode.

    Note: You can upgrade to a fully functioning version by entering a serial number in the fds line of the lcds-webapp-root/WEB-INF/flex/license.properties file for each LiveCycle Data Services web application. Then restart the server.

  4. Specify the directory in which to install LiveCycle Data Services or accept the default location.
  5. Select the LiveCycle Data Services With Tomcat option.
  6. Complete the remaining installer steps.
  7. To start LiveCycle Data Services, open a command window, navigate to install_root/tomcat/bin, and enter the command: catalina run.

    On Microsoft Windows, you can start LiveCycle Data Services from the Start menu, or navigate to the install_root/tomcat/bin in Windows Explorer and double-click the startup.bat icon.

    On UNIX and Linux, enter the command: ./catalina.sh run.

Running the sample applications with the integrated Tomcat installation

When you install LiveCycle Data Services, the installer creates the lcds-samples web application that contains sample applications, including the 30 Minute Test Drive application. The sample applications demonstrate basic capabilities and best practices for developing LiveCycle Data Services applications.

  1. The LiveCycle Data Services sample applications use an HSQLDB database that is installed in the install_root/sampledb directory. To start the sample database:
  2. Start Tomcat (startup.bat or startup.sh in /lcds/tomcat/bin)
  3. Open a browser window.
  4. Access the samples home page by opening the following URL in a browser:
    http://localhost:8400/lcds-samples/
  5. Access the 30 Minute Test Drive application by opening the following URL in a browser:
    http://localhost:8400/lcds-samples/testdrive.htm

LiveCycle Data Services J2EE web applications

The LiveCycle Data Services J2EE web application configuration option installs the following files and directories under the installation root:

readme.htm Contains overview information.
lcds.war LiveCycle Data Services web application, used as a starting point for new applications.
lcds-samples.war LiveCycle Data Services sample applications.
ds-console.war Simple monitoring application for LiveCycle Data Services deployments.
license.txt license information.
/resources Fully commented configuration files, as well as directories and files used for security, clustering, Flex Ajax Bridge, and WSRP.
/sampledb Contains an HSQLDB database that the sample applications use.

Install LiveCycle Data Services web applications

  1. Start the installation program. Do one of the following, depending on your operating system:
  2. Accept the license agreement.
  3. (Optional) Enter the serial number and follow the prompts. If you don't enter a serial number, LiveCycle Data Services runs in single CPU mode.

    Note: You can upgrade to a fully functioning version by entering a serial number in the fds line of the lcds-webapp-root/WEB-INF/flex/license.properties file for each LiveCycle Data Services web application. Then restart the server.

  4. Specify the directory in which to install LiveCycle Data Services or accept the default location.
  5. Select the LiveCycle Data Services J2EE web application option.
  6. Complete the remaining installer steps.
  7. Deploy the lcds.war, lcds-samples.war, and ds-console.war web applications by using your application-server-specific deployment method. For example, for Tomcat, copy the web application to the webapps directory and restart the server.

    Notes: To use the model-driven development features, you must deploy the web applications as expanded directories rather than WAR files. For production, you can package web applications in compressed WAR files.

    Many samples applications in lcds-samples web application require that you deploy the web application as an expanded directory structure. When you deploy the lcds-samples web application, make sure that you specify "lcds-samples" as the context-root.

  8. Perform additional application-server specific configuration, as described in Additional server-specific configuration.

Install LiveCycle Data Services as a J2EE web application by using the Java installer (any platform)

  1. Run the installer by opening a command prompt, navigating to the directory that contains the downloaded JAR file (lcds3-install.jar), and executing the following command:
    [java_home]/bin/java -jar lcds3-install.jar -i console
  2. Continue with steps 3 through 9 of Install LiveCycle Data Services as a J2EE web application.

Running the sample applications

When you install LiveCycle Data Services, the installer creates the lcds-samples web application that contains sample applications, including the 30 Minute Test Drive application. The sample applications demonstrate basic capabilities and best practices for developing LiveCycle Data Services applications.

  1. The LiveCycle Data Services sample applications use an HSQLDB database that is installed in the install_root/sampledb directory. To start the sample database:
  2. Start the web application server on which you deployed lcds-samples.war. The host name and port number of the deployed lcds-samples.war file depend on the configuration of your web application.
  3. Open a browser window.
  4. Access the samples home page by opening the following URL in a browser:
    http://hostName:portNumber/lcds-samples/
  5. Access the 30 Minute Test Drive application by opening the following URL in a browser:
    http://hostName:portNumber/lcds-samples/testdrive.htm

Additional server-specific configuration

There are additional configuration steps for the following application servers:

Tomcat

To use LiveCycle Data Services with Tomcat when not using the integrated Tomcat configuration, install support for the Java Transaction API (JTA). You might also have to install several other libraries depending on the features that you plan to use. Follow these steps after deploying the LiveCycle Data Services WAR files. These steps are not necessary for the integrated Tomcat installation.

  1. Stop Tomcat.
  2. To install support for JTA, a recommended implementation is the Java Open Transaction Manager (JOTM), which is a fully functional open source stand-alone transaction manager.
    1. Download JOTM from http://jotm.objectweb.org.
    2. Copy the JAR files from jotm-root/lib to [tomcat-root]/common/lib.
    3. Create a context file for your web application and register JOTM using the Transaction element. For example, for the samples WAR create a tomcat-root/conf/Catalina/localhost/lcds-samples.xml file and add the following lines:
      <CONTEXT antijarlocking="false" antiresourcelocking="false"   docbase="${catalina.home}/webapps/lcds-samples" path="/lcds-samples"   privileged="true">  <TRANSACTION factory="org.objectweb.jotm.UserTransactionFactory"   jotm.timeout="60"></TRANSACTION></CONTEXT>  
      Note: If a context file exists for your web application, add the <TRANSACTION> element under the <CONTEXT> element.
  3. Increase the maximum memory to at least 512 MB by specifying the maximum heap size for the JVM in the JAVA_OPTS variable: -Xmx512m
  4. (Optional) To enable custom authentication, locate the Tomcat security resource libraries under install_root/resources/security/tomcat.
    1. Place the flex-tomcat-common.jar and flex-tomcat-server.jar files in the tomcat/lib folder.
    2. Add the following line to the context descriptor file for your web application:

      <VALVE classname="flex.messaging.security.TomcatValve"></VALVE>

      You can now perform authentication against the current Tomcat realm. Usually, the default configuration for authentication stores user information in conf/tomcat-users.xml. See the Tomcat documentation for more information on realms. See the LiveCycle Data Services documentation for more information on custom authentication.

    3. You might also have to update the active <LOGIN-COMMAND> in /WEB-INF/flex/services-config.xml in each deployment of a LiveCycle Data Services WAR file. For Tomcat, ensure that the TomcatLoginCommand is active in the <SECURITY>section:
      <SECURITY><LOGIN-COMMAND server="Tomcat"></LOGIN-COMMAND>...</SECURITY>
  5. (Optional) To use the JMSAdapter with the Message Service, install and configure a JMS provider (such as ActiveMQ or openJMS) for use with Tomcat.
  6. Restart Tomcat.

Configuring ActiveMQ 4.1.1 with Tomcat 6.0.x

These instructions create a configuration that matches what is distributed with LiveCycle Data Services. You can integrate Apache ActiveMQ 4.1.1 with earlier versions of Tomcat. You can integrate newer versions of ActiveMQ with Tomcat 6.0.x, but none of these configurations have been tested. These instructions require that you have a valid Apache Ant installation.

  1. Download ActiveMQ 4.1.1 from http://activemq.apache.org.
  2. Download and install the ActiveMQ distribution following the instructions provided on the ActiveMQ website.
  3. ActiveMQ ships with an example that contains the JAR files and configuration settings that work with a web application deployment. Build the example by opening a command prompt, changing to the activemq_root/example directory and running the following command to build the example:
  4. ant war
  5. In the tomcat_root/lib directory, create a directory called activemq4.1.1. Copy the contents of the activemq_root/example/target/activemq-web/WEB-INF/lib directory to this new directory.
  6. Open the catalina.properties file from the tomcat_install/conf directory in a text editor. Modify the common.loader property by adding the following to the list of comma-separated paths:
    ${catalina.home}/lib/activemq4.1.1/*.jar
  7. Modify your LiveCycle Data Services web application to start an ActiveMQ message broker when the web application starts. To do so, open the WEB-INF/web.xml file for your web application in a text editor. Add the following context-param and listener elements. Make sure that you place them in the correct location within the web.xml. The order of these parameters and elements must match the web-app DTD.
  8. <CONTEXT-PARAM>
      <PARAM-NAME>brokerURI</PARAM-NAME>
      <PARAM-VALUE>/WEB-INF/activemq.xml</PARAM-VALUE>
    </CONTEXT-PARAM>
    <LISTENER>
      <LISTENER-CLASS>org.apache.activemq.web.SpringBrokerContextListener</LISTENER-CLASS>
    </LISTENER>
  9. In the WEB-INF directory of your web application, create a file called activemq.xml. Open the file in a text editor and add the following text:
  10. <BEANS>
    <BROKER brokername="myBroker" persistent="false" usejmx="true"
    xmlns="http://activemq.org/config/1.0">
    <TRANSPORTCONNECTORS>
    <TRANSPORTCONNECTOR name="default" uri="tcp://localhost:61716">
    </TRANSPORTCONNECTOR>
    </TRANSPORTCONNECTORS></BROKER>
    </BEANS>  

    This configuration starts an ActiveMQ message broker with a broker name of myBroker listening for requests on the localhost network interface at port 61716.

  11. Add the ActiveMQ connection factories and any JMS Topics and Queues to JNDI. In Tomcat 6.0.x, create a context file for your web application in the tomcat_install/conf/Catalina/localhost directory. If the Catalina/localhost directory does not exist, create it now. The file that you create must have the same name as the web application with a .xml extension. For example, if your LiveCycle Data Services web application is named samples, name the Tomcat context file samples.xml. For more information on context files, see your Tomcat documentation. After you create the file, open it in a text editor. Add the following contents to the file, replacing the example topic and queue shown here with your own topics and queues:
  12. <CONTEXT antijarlocking="false" antiresourcelocking="false"
    privileged="true" reloadable="true">
    <RESOURCE brokername="myBroker" brokerurl="tcp://localhost:61716"
    description="JMS Connection Factory"
    factory="org.apache.activemq.jndi.JNDIReferenceFactory"
    name="jms/flex/TopicConnectionFactory"
    type="org.apache.activemq.ActiveMQConnectionFactory">
    </RESOURCE>
    <RESOURCE description="my Topic" factory="org.apache.activemq.jndi.JNDIReferenceFactory"
    name="jms/topic /flex/simpletopic"
    physicalname="FlexTopic" 
    type="org.apache.activemq.command.ActiveMQTopic">
    </RESOURCE>
    <RESOURCE brokername="myBroker"
    brokerurl="tcp://localhost:61716"
    description="JMS Connection Factory"
    factory="org.apache.activemq.jndi.JNDIReferenceFactory"
    name="jms/flex/QueueConnectionFactory" 
    type="org.apache.activemq.ActiveMQConnectionFactory">
    </RESOURCE>
    <RESOURCE description="my Queue" 
    factory="org.apache.activemq.jndi.JNDIReferenceFactory"
    name="jms/queue/flex/simplequeue" physicalname="FlexQueue" 
    type="org.apache.activemq.command.ActiveMQQueue">
    </RESOURCE>
    <VALVE classname="flex.messaging.security.TomcatValve"></VALVE>
    </CONTEXT>  
  13. Start your Tomcat server. The ActiveMQ message broker starts listening for messages on port 61716. You can send messages to and receive messages from the JMS topics and queues that you configured. For more information about configuring and using ActiveMQ, see the ActiveMQ documentation available on http://activemq.apache.org.

WebLogic

There is a known Hibernate 3 integration issue for most WebLogic versions. The LiveCycle Data Services model-driven development and Hibernate assembler features use Hibernate. The easiest solution is to put the antlr JAR file shipped with LiveCycle Data Services in the WebLogic bootstrap class path. The antlr JAR file is in the WEB-INF/lib directory of the LiveCycle Data Services web applications.

WebSphere

LiveCycle Data Services includes a WebSphere-specific implementation of the RTMP server. This version uses threads created by WebSphere.

Configure LiveCycle Data Services for use with WebSphere

  1. Expand a LiveCycle Data Services WAR file to a temporary folder:
    jar -xvf  [lcds].war
  2. Uncomment the resource-ref element for WorkManager in the web.xml file. This setting makes the resource available in java:comp/env/ at res-ref-name (java:comp/env/wm/MessagingWorkManager):
    <RESOURCE-REF>
    <DESCRIPTION>Flex Messaging WorkManager</DESCRIPTION>
    <RES-REF-NAME>wm/MessagingWorkManager</RES-REF-NAME>
    <RES-TYPE>com.ibm.websphere.asynchbeans.WorkManager</RES-TYPE>
    <RES-AUTH>Container</RES-AUTH>
    <RES-SHARING-SCOPE>Shareable</RES-SHARING-SCOPE>
    </RESOURCE-REF>
  3. Map the WorkManager resource-ref in the web.xml file to the RTMPEndpoint in [lcds-webapp-root]/WEB-INF/flex/services-config.xml. The websphere-workmanager-jndi-name maps to the res-ref-name available in java:comp/env in step 2. For example:
    <CHANNEL-DEFINITION id="my-rtmp"><ENDPOINT url="http://{server.name}:2038/">
    </ENDPOINT>
    <PROPERTIES>
    ...
    <WEBSPHERE-WORKMANAGER-JNDI-NAME>
    java:comp/env/wm/MessagingWorkManager
    </WEBSPHERE-WORKMANAGER-JNDI-NAME>
    ...
    </PROPERTIES>
    </CHANNEL-DEFINITION>
  4. To configure data service destinations that do not use transactions with RTMP based channels, set <USE-TRANSACTIONS>false</USE-TRANSACTIONS> for the data service destination in the /WEB-INF/flex/data-management-config.xml file.
  5. To integrate the new NIO HTTP server, update the services-config.xml to include the websphere-workmanager-jndi-name declaration in the <SERVERS> section:
    <SERVERS>
    <SERVER id="data-nio-server">
    <PROPERTIES>
    <BIND-PORT>12080</BIND-PORT>
    <WEBSPHERE-WORKMANAGER-JNDI-NAME>
    java:comp/env/wm/MessagingWorkManager
    </WEBSPHERE-WORKMANAGER-JNDI-NAME>
    </PROPERTIES>
    </SERVER>
    <SERVER id="data-nio-secure-server">
    <PROPERTIES>
    <BIND-PORT>2051</BIND-PORT>
    <WEBSPHERE-WORKMANAGER-JNDI-NAME>
    java:comp/env/wm/MessagingWorkManager
    </WEBSPHERE-WORKMANAGER-JNDI-NAME>
    <KEYSTORE-PASSWORD>changeit</KEYSTORE-PASSWORD>
    </PROPERTIES>
    </SERVER>
    </SERVERS>
  6. Create a WAR file from the expanded directory structure. For example:
  7. jar -cvf [lcds].war *
  8. From the WebSphere Administrator, define a WorkManager for use by your application. From the admin, choose Resources > Asynchronous Beans > Work managers. By default, the DefaultWorkManager is available at the wm/default jndi-name. Also, you can add a separate WorkManager for your application.
  9. Deploy the WAR file. During deployment, map the WorkManager resource-ref to an actual JNDI name for your WorkManager. For the DefaultWorkManager, wm/MessagingWorkManager (name used by your web.xml) maps to wm/default (the JNDI name of the actual server resource).
  10. (Optional) To enable custom authentication, open the WebSphere Administrator and configure a custom user registry using the files under [install_root]resources/security/websphere/ as usersFile and groupsFile custom properties.

Running the monitoring application, ds-console.war, on WebSphere with administrative security

  1. Uncomment the <SECURITY> section under the RuntimeManagement destination in the services-config.xml file for the ds-console web application. The file contains comments instructing users to do this when running on WebSphere with administrative security enabled.
  2. Uncomment the <SECURITY-CONSTRAINT> section under <SECURITY> in the services-config.xml file for the ds-console web application. The file has comments instructing users to do this when running on WebSphere with administrative security enabled.
  3. Make sure that you use the WebSphereLoginCommand.
  4. Create a WAS User Group called console_administrator and add any users who are allowed to use this application to this group. These users must also have at least one role that allows them to access MBeans under WebSphere security.

JBoss

JBoss web application deployment

JBoss 4 authentication

(Optional) This configuration provides custom authentication against the current JBoss realm. Usually, the default location for this authentication stores user information in jboss_root/server/default/conf/users.properties and roles information in jboss_root/server/default/conf/roles.properties. For more information on realms, see the JBoss documentation. For more information on LiveCycle Data Services custom authentication, see the LiveCycle Data Services documentation and information in the install_root/resources/security directory.

  1. Copy the flex-tomcat-common.jar and flex-tomcat-server.jar files from the install_root/resources/security/tomcat folder to the jboss_root/server/default/lib folder.
  2. Add the TomcatValve to the context.xml in the jboss_root/server/default\deploy/jboss-web.deployer folder:
    <VALVE classname="flex.messaging.security.TomcatValve"></VALVE>
  3. Add users and roles to the users.properties and roles.properties files in jboss under jboss_root/server/default/conf folder.
  4. Restart JBoss.

You will now be authenticated against the current JBoss realm.

JBoss 5 authentication

This configuration provides custom authentication against the current JBoss realm:

  1. Copy the flex-tomcat-common.jar and flex-tomcat-server.jar files from the install_root/resources/security/tomcat folder to the jboss_root/server/default/lib folder.
  2. Add the TomcatValve to the context.xml under \server\default\deploy\jboss-web.sar:
    <VALVE classname="flex.messaging.security.TomcatValve"></VALVE>
  3. Create a tomcat-users.xml file in the jboss_root/server/default/conf directory. The following example shows a basic tomcat-users.xml file:
  4. <xml version='1.0' encoding='utf-8'?>
    <tomcat-users>
    <role rolename="tomcat"/>
    <role rolename="role1"/>
    <user username="tomcat" password="tomcat" roles="tomcat"/>
    <user username="both" password="tomcat" roles="tomcat,role1"/>
    <user username="role1" password="tomcat" roles="role1"/>
    </tomcat-users>

  5. Replace the current security realm in the server.xml file under \server\default\deploy\jboss-web.sar with the following:

    <Realm className="org.apache.catalina.realm.MemoryRealm" pathname="../server/default/conf/tomcat-users.xml"/>

  6. Restart JBoss.


Running LiveCycle Data Services from a compressed WAR

  1. Expand a LiveCycle Data Services WAR file using winzip or the JAR utility.
  2. Create your application, including SWF files, ActionScript files, configuration settings, and HTML files.
  3. Create a compressed WAR file from the expanded web application structure.
  4. Deploy the compressed WAR file.

    Note: Many samples applications in lcds-samples.war file do not function within a compressed web application. Therefore, it is advised that you deploy the lcds-samples web application as an expanded directory structure. If you uncompress a WAR file into a subdirectory that you create, that subdirectory must match the name of the prefix of the WAR file. That directory is also the context root of the web application. To use the model-driven development features, you must deploy the web applications as expanded directories rather than WAR files; For production, you can package web applications in compressed WAR files.

Building applications

Once you have installed LiveCycle Data Services, see "Getting Started with LiveCycle Data Services" in Using LiveCycle Data Services for a quick introduction to features and practical information about building and deploying applications.