Installing Adobe LiveCycle Data Services ES 2.6.1

Contents

Adobe® LiveCycle® Data Services ES runs as a J2EE web application. The installer lets you choose from the following configurations:

  • LiveCycle Data Services ES with integrated Apache Tomcat application server
  • LiveCycle Data Services ES web applications

LiveCycle Data Services ES offers installers for the following platforms:

  • Microsoft® Windows®
  • Linux®
  • Solaris™
  • Java™ (cross-platform installer)

LiveCycle Data Services ES supports the following application 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 (Japanese Version Only)
  • Hitachi Cosminexus 7 (Japanese Version Only)
  • NEC WebOTX (Japanese Version Only)
  • Oracle 10G AS (10.1.3)
  • SAP NetWeaver CE 7.1 SP3
  • Adobe® JRun™ 4 Updater 7

LiveCycle Data Services ES supports the following JDKs:

  • Sun™ JDK 5
  • BEA JRockit 5
  • IBM® JDK 5

Note: You can integrate LiveCycle Data Services ES server with Adobe ColdFusion. For more information, see Integrating LiveCycle Data Services ES with ColdFusion 8.

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

  • lcds.war - The primary LiveCycle Data Services ES WAR file: use this file as a starting point for building your LiveCycle Data Services ES application.
  • lcds-samples.war - Sample LiveCycle Data Services ES applications.
  • ds-console.war - Simple monitoring application for LiveCycle Data Services ES deployments.

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 ES as install_root.

Installing LiveCycle Data Services ES with the integrated Apache Tomcat application server

The LiveCycle Data Services ES 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 ES web application template, used as a starting point for new applications.
lcds-samples.war LiveCycle Data Services ES sample applications.
ds-console.war Simple monitoring application for LiveCycle Data Services ES 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 Contains Flex SDK source code, fully commented configuration files, and directories and files used for security, clustering, Flex Ajax Bridge, and WSRP. Adobe Flash Player installers are in the resources/flex_sdk/flex_sdk_3.zip file.
/sampledb Contains an HSQLDB database used by the sample applications.
/UninstallerData Contains information used to uninstall LiveCycle Data Services ES.

Install LiveCycle Data Services ES in the integrated Tomcat configuration

  1. Read the LiveCycle Data Services ES release notes for known issues and any late-breaking information.
  2. Start the installation program. Do one of the following, depending on your operating system:

    • Windows - Double-click the installer file (lcds261-win.exe).
    • UNIX® or Linux - Set the working directory to the directory that contains the installer file, and then enter the following command that specifies the installer file for your operating system:

      for Linux:
            ./lcds261-lin.bin
      for Solaris:
            ./lcds261-sol.bin
  3. Accept the license agreement.
  4. (Optional) Enter the serial number and follow the prompts. If you don't enter a serial number, LiveCycle Data Services ES 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 ES web application. Then restart the server.

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

    On Microsoft Windows, you can start it by using the following command: Start > Programs > Adobe > LiveCycle Data Services ES 2.6.1 > Start LiveCycle Data Services Server. Or you can 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 run.

Running the sample applications with the integrated Tomcat installation

When you install LiveCycle Data Services ES, 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 ES applications.

  1. The LiveCycle Data Services ES sample applications use an HSQLDB database that is installed in the install_root/sampledb directory. To start the sample database:
    • Open a command prompt and go to the install_root/sampledb directory.
    • Run startdb.bat (Windows) or startdb.sh (Unix-based systems).
    • On Microsoft Windows, you can start it by using the following command: Start > Programs > Adobe > LiveCycle Data Services ES 2.6.1 > Start Samples 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

Installing LiveCycle Data Services ES J2EE web application on a supported application server

The LiveCycle Data Services ES 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 ES web application, used as a starting point for new applications.
lcds-samples.war LiveCycle Data Services ES sample applications.
ds-console.war Simple monitoring application for LiveCycle Data Services ES deployments.
license.txt license information.
/resources Contains Flex SDK source code, fully commented configuration files, as well as directories and files used for security, clustering, Flex Ajax Bridge, and WSRP. Flash Player installers are in the resources/flex_sdk/flex_sdk_3.zip file.
/sampledb Contains an HSQLDB database used by the sample applications.
/UninstallerData Contains information used to uninstall LiveCycle Data Services ES.

Install LiveCycle Data Services ES web applications

  1. Read the LiveCycle Data Services ES release notes for known issues and any late-breaking information.
  2. Start the installation program. Do one of the following, depending on your operating system:

    • Windows - Double-click the installer file (lcds261-win.exe).
    • UNIX or Linux - Set the working directory to the directory that contains the installer file, and then enter the following command that specifies the installer file for your operating system:

      for Linux:
            ./lcds261-lin.bin
      for Solaris:
            ./lcds261-sol.bin
  3. Accept the license agreement.
  4. (Optional) Enter the serial number and follow the prompts. If you don't enter a serial number, LiveCycle Data Services ES 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 ES web application. Then, restart the server.

  5. Specify the directory in which to install LiveCycle Data Services ES or accept the default location.
  6. Select the LiveCycle Data Services J2EE web application option.
  7. Complete the remaining installer steps.
  8. 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 WAR files to the webapps directory and restart the server.
  9. Note: When you deploy the lcds-samples web application, make sure that you specify "lcds-samples" as the context-root.

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

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

  1. Read the LiveCycle Data Services ES release notes for system requirements and any late-breaking information.
  2. Run the installer by opening a command prompt, navigating to the directory that contains the downloaded JAR file (lcds261-install.jar), and executing the following command:
    java_home/bin/java -jar lcds261-install.jar -i console
  3. Continue with steps 3 through 9 of Install LiveCycle Data Services ES as a J2EE web application.

Running the sample applications

When you install LiveCycle Data Services ES, 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 ES applications.

  1. The LiveCycle Data Services ES sample applications use an HSQLDB database that is installed in the install_root/sampledb directory. To start the sample database:
    • Open a command prompt and go to the install_root/sampledb directory.
    • Run startdb.bat (Windows) or startdb.sh (Unix-based systems).
    • On Microsoft Windows, you can start it by using the following command: Start > Programs > Adobe > LiveCycle Data Services ES 2.6.1 > Start Samples 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

You might have to perform additional configuration steps for your application server:

Tomcat

To use LiveCycle Data Services ES 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 path="/lcds-samples" docBase="${catalina.home}/webapps/lcds-samples" privileged="true" antiResourceLocking="false" antiJARLocking="false">
         <Transaction factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60"/>
      </Context>   
      Note: If a context file exists for your web application, add the <Transaction> element under the 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 flex-tomcat-common.jar in tomcat/lib/lcds.
    2. Place flex-tomcat-server.jar in tomcat/lib/lcds.
    3. Edit the tomcat/conf/catalina.properties file to add the following path to the end of the list:
      ${catalina.home}/lib/lcds/*.jar
    4. Add the <Valve className="flex.messaging.security.TomcatValve"/> tag to the Context descriptors. For example, for the LiveCycle Data Services ES samples WAR:
      <Context path="/lcds-samples"
       docBase="${catalina.home}/webapps/lcds-samples" debug="0">
        <Valve className="flex.messaging.security.TomcatValve"/>
      </Context>

      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 ES documentation for more information on custom authentication.

    5. 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 ES WAR file. For Tomcat, ensure that the TomcatLoginCommand is active in the <security> section:
      <security>
      <login-command
       class="flex.messaging.security.TomcatLoginCommand"
       server="Tomcat"/>
      ...
  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 ES. 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 ES 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. <?xml version="1.0" encoding="UTF-8"?>
    <beans>
    	<broker useJmx="true" persistent="false" xmlns="http://activemq.org/config/1.0" brokerName="myBroker">
    
    		<transportConnectors>
    			<transportConnector name="default" uri="tcp://localhost:61716"/>
    		</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 should have the same name as the web application with a .xml extension. For example, if your LiveCycle Data Services ES 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 privileged="true" antiResourceLocking="false" antiJARLocking="false" reloadable="true">
    
        <Resource name="jms/flex/TopicConnectionFactory"
                    type="org.apache.activemq.ActiveMQConnectionFactory"
                    description="JMS Connection Factory"
                    factory="org.apache.activemq.jndi.JNDIReferenceFactory"
                    brokerURL="tcp://localhost:61716"
    
                    brokerName="myBroker"/>
     	<Resource name="jms/topic/flex/simpletopic"
                    type="org.apache.activemq.command.ActiveMQTopic"
                    description="my Topic"
    
                    factory="org.apache.activemq.jndi.JNDIReferenceFactory"
                    physicalName="FlexTopic"/>
    	<Resource name="jms/flex/QueueConnectionFactory"
                    type="org.apache.activemq.ActiveMQConnectionFactory"
    
                    description="JMS Connection Factory"
                    factory="org.apache.activemq.jndi.JNDIReferenceFactory"
                    brokerURL="tcp://localhost:61716"
                    brokerName="myBroker"/>
    
        <Resource name="jms/queue/flex/simplequeue"
                    type="org.apache.activemq.command.ActiveMQQueue"
                    description="my Queue"
                    factory="org.apache.activemq.jndi.JNDIReferenceFactory"
                    physicalName="FlexQueue"/>
        <Valve className="flex.messaging.security.TomcatValve"/>
    
    </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.

WebSphere

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

Configure LiveCycle Data Services ES for use with WebSphere

  1. Expand a LiveCycle Data Services ES 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" class="mx.messaging.channels.RTMPChannel">
       <endpoint url="http://{server.name}:2038/"
        class="flex.messaging.endpoints.RTMPEndpoint"/>
           <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 class="flex.messaging.socketserver.SocketServer" 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 class="flex.messaging.socketserver.SocketServer" 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 enabled

  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

(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 ES custom authentication, see the LiveCycle Data Services ES documentation and information in the install_root/resources/security directory.

  1. Place install_root/resources/security/tomcat/flex-tomcat-common.jar and install_root/resources/security/tomcat/flex-tomcat-server.jar in the jboss_root/server/default/lib folder.
  2. Add <Valve className="flex.messaging.security.TomcatValve"/> tag to the Context descriptors.
  3. Restart JBoss.

OC4J

To run LiveCycle Data Services ES on Oracle Containers for J2EE (OC4J), make the following changes in the oc4j.cmd file:

  • Add the -userThreads argument to the CMDARGS line.
  • Add the –Doc4j.jmx.security.proxy.off=true JVM argument to the JVMARGS line.

The following example shows CMDARGS and JVMARGS lines that use these arguments:

set JVMARGS=%OC4J_JVM_ARGS% -Xmx512m -Doc4j.jmx.security.proxy.off=true  set CMDARGS=-config "%SERVER_XML%" -userThreads

Editing the security policy file when the J2EE Security Manager is enabled

If you enable the J2EE Security Manager on your application server, you must add the following LiveCycle Data Services ES permissions to the security policy file for the application server:

permission javax.management.MBeanServerPermission "createMBeanServer";
permission javax.management.MBeanPermission "*", "registerMBean,unregisterMBean";
permission javax.management.MBeanTrustPermission "register";
permission java.lang.RuntimePermission "modifyThreadGroup";
permission java.lang.RuntimePermission "modifyThread";
permission java.lang.RuntimePermission "getClassLoader";
permission java.net.SocketPermission "*", "accept,connect,listen,resolve";
permission java.util.PropertyPermission "*", "read";

If you are using Hibernate in your LiveCycle Data Services ES application, include the following permissions:

permission java.lang.RuntimePermission "getProtectionDomain";
permission java.lang.RuntimePermission "accessDeclaredMembers";
permission java.lang.reflect.ReflectPermission "suppressAccessChecks"; 

Running LiveCycle Data Services ES from a compressed WAR

  1. Expand the lcds.war file using winzip or the JAR utility.
  2. Create your application, including SWF files, ActionScript files, configuration settings, and HTML wrappers.

    Note: For more information on compiling SWF files and creating HTML wrappers, see the LiveCycle Data Services ES documentation.

  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 do not function within a compressed web application. Therefore, it is advised that you deploy the lcds-samples web application as an uncompressed WAR file. 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.

Upgrading LiveCycle Data Services ES 2.6 to version 2.6.1

LiveCycle Data Services ES 2.6.1 ships with an empty web application called lcds.war. You likely used the lcds.war from version 2.6 as the basis for the web application that you want to upgrade. You are going to use the lcds.war from version 2.6.1 as the basis of your upgraded version 2.6 web application.

The following procedure describes how to upgrade an existing installation of LiveCycle Data Services ES 2.6 to LiveCycle Data Services ES 2.6.1:

  1. Install LiveCycle Data Services 2.6.1.
  2. Create a backup copy of your existing version 2.6 web application. As part of this procedure, you copy assets from the backup copy to the new LiveCycle Data Services 2.6.1 web application.
  3. Uninstall your existing LiveCycle Data Services 2.6 web application from your application server. The steps to do this uninstall are based on your application server. For more information, see the documentation for your application server.
  4. Expand the empty lcds.war file installed with version 2.6.1. If you are starting with a packaged lcds.war, you will need to expand it to a directory and then repackage it when you are finished.
  5. Copy the assets from your existing version 2.6 web application to the empty LiveCycle Data Services 2.6.1 web application. Copy all image, font, SWF, Java, and JAR and other files required by your application.

    Note: Do not copy any configuration files from the WEB-INF/flex directory of your existing version 2.6 web application.

  6. Merge the configuration files from the WEB-INF/flex directory of your existing version 2.6 web application to the configuration files in the WEB-INF/flex directory of the new LiveCycle Data Services 2.6.1 web application. To perform this merge, copy and paste your destination, channel, endpoint, and other definitions from the version 2.6 configuration files to the version 2.6.1 configuration files.

    Note: Because configuration files can contain new configuration properties, or change the default values of existing properties, do not overwrite the version 2.6.1 configuration files with the version 2.6 configuration files. Instead, always merge your custom settings into the version 2.6.1 configuration files.

  7. Adobe recommends that you recompile any MXML files using the SWC files from LiveCycle Data Services 2.6.1 to pick up any client-side bug fixes made in version 2.6.1.
  8. (Optional) If you deploy a compressed or packaged web application, repackage the web application.
  9. Deploy the new web application on your application server.