LiveCycle Data Services ES Installation

Adobe LiveCycle Data Services ES is a J2EE web application that you can install by using one of the following options:

LiveCycle Data Services ES includes installers for the following platforms:

  • Windows
  • Solaris
  • Linux
  • Java (cross-platform installer)

The default installation directory is C:\lcds on Windows and /opt/lcds on UNIX and Linux. These installation instructions refer to this location as install_root.

Tip: The installer prompts for a serial number. If you omit the serial number, the installer installs LiveCycle Data Services Express. You can upgrade from express mode 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) and restarting the server.

LiveCycle Data Services ES includes the following Web Application Archive (WAR) files:

  • flex.war - The primary Flex WAR file: use this as a starting point for building your LiveCycle Data Services application.
  • samples.war - Sample Flex applications.
  • flex-admin.war - Simple administration and monitoring application.

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

Updating to LiveCycle Data Services ES : There is no installer support for automatic upgrade from Flex Data Services 2 to LiveCycle Data Services ES. It is a complete install with updated files and you must install it into a new directory. To upgrade to LiveCycle Data Services ES, perform the following steps:

  1. Install LiveCycle Data Services into a new directory.
  2. Copy existing applications and settings to the new structure. Be sure to include the following:
    • MXML and ActionScript files.
    • Application assets, such as images and sound files.
    • Java source code and compiled classes for assemblers, data access objects, and data objects.
    • Destination definitions and other settings specified in the WEB-INF/flex/*.xml configuration files
    • Compiler options specified in the WEB-INF/flex/flex-config.xml file.
    • Custom component libraries (SWC files)

This page also includes installation instructions for Flex Automated Testing.

LiveCycle Data Services with integrated JRun

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

readme.htm Contains an overview of important information.
flex.war Flex web application, used as a starting point for new applications.
samples.war LiveCycle Data Services sample applications.
flex-admin.war Flex Administrator application.
license.txt license information.
/jrun4 Contains a custom installation of JRun 4 u6, including flex, samples, and flex-admin web applications expanded and deployed in the default server.
/resources Contains Flex SDK source code, fully commented configuration files, as well as directories and files used for security, clustering, Hibernate, Flex-Ajax Bridge, WSRP, and manually creating HTML wrappers. Flash Player installers are in the Flex SDK ZIP file.
/UninstallerData Contains the uninstaller.

To install LiveCycle Data Services ES in the integrated JRun 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 (lcds25-win.exe).
    • UNIX or Linux - Set the working directory to the directory that contains the installer file, and then enter the following command specifying the installer file for your operating system; for example:
                  ./lcds25-lin.bin -i console
  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 runs in express mode.
    Note: You can upgrade from express mode 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) and restarting the server.
  5. Select the LiveCycle Data Services With Integrated JRun option.
  6. When the installation finishes, view the Readme file for late-breaking information.
  7. (optional) Install the debugger version of Flash Player from the player/debug directory of the install_root/resources/flex_sdk/flex_sdk_2.zip file.
  8. (UNIX and Linux only) On UNIX headless servers, open the lcds-webapp/WEB-INF/flex/flex-config.xml file in a text editor and set the <headless-server> element to true.
  9. To start LiveCycle Data Services ES, select Start > Programs > Adobe > LiveCycle Data Services ES2.5 > Start Integrated LiveCycle Data Services Server or open a command window, navigate to install_root/jrun4/bin, and enter the jrun start default command. On UNIX and Linux, enter ./jrun start default.

LiveCycle Data Services J2EE web application

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

readme.htm Contains an overview of important information.
flex.war Flex web application, used as a starting point for new applications.
samples.war LiveCycle Data Services sample applications.
flex-admin.war Flex Administrator application.
license.txt license information.
/resources Contains Flex SDK source code, fully commented configuration files, as well as directories and files used for security, clustering, Hibernate, Flex-Ajax Bridge, WSRP, and manually creating HTML wrappers. Flash Player installers are in the Flex SDK ZIP file.
/UninstallerData Contains the uninstaller.

LiveCycle Data Services includes installers for Windows, Linux, and Solaris. It also includes a Java installer to deploy LiveCycle Data Services on other supported platforms.

To install LiveCycle Data Services ES as a J2EE web application:

  1. Read the LiveCycle Data Services ES RC 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 (lcds25-win.exe).
    • UNIX or Linux - Set the working directory to the directory that contains the installer file, and then enter the following command specifying the installer file for your operating system; for example:
      ./lcds25-lin.bin -i console
  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 runs in express mode.
    Note: You can upgrade from express mode 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) and restarting the server.
  5. Select the LiveCycle Data Services J2EE Web Application option.
  6. When the installation finishes, view the Readme file for late-breaking information.
  7. (optional) Install the debugger version of Flash Player from the player/debug directory of the install_root/resources/flex_sdk/flex_sdk_2.zip file.
  8. Deploy the flex, samples, and flex-admin web applications by using your application-server-specific deployment method.
    For example, for JRun 4 u6, expand the flex.war, samples.war, and flex-admin.war files to directories named flex, samples, and flex-admin, respectively. Then copy these directories to the root of your JRun server instance. For Tomcat, copy the WAR files to the webapps directory and restart the server.
  9. Perform additional application-server specific configuration, as described in Additional server-specific configuration.
  10. (UNIX and Linux headless servers only) Open the lcds-webapp/WEB-INF/flex/flex-config.xml file in a text editor and set the <headless-server> element to true.

To install LiveCycle Data Services ES as 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, and executing the following command:
    java_home/bin/java -jar downloaded_file_name.jar -i console

    For example, set the working directory to the directory that contains the lcds25-install.jar file. Enter the following command, replacing java_home with the path to the bin directory for your JRE installation:
    java_home /java -jar lcds25-install.jar -i console
  3. Continue with steps 3 through 10 of To install LiveCycle Data Services ES as a J2EE web application.

Additional server-specific configuration

You may need to perform additional configuration steps for the following application servers:

Tomcat

To use LiveCycle Data Services ES with Tomcat 5.5, you must install support for the Java Transaction API (JTA) and may also need 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:

  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, e.g. for the samples WAR create a [tomcat-root]/conf/Catalina/localhost/samples.xml file and add the following lines:
      <Context docBase="${catalina.home}/webapps/samples" privileged="true"
         antiResourceLocking="false" antiJARLocking="false">
         <Transaction factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60"/>
      </Context>
      
      Note: If a context file already exists for your web application, simply add the <Transaction> element under the element.
  3. Increase the maximum memory to at least 512MB. For Tomcat, this is achieved 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. Depending on the version of Tomcat, follow one of these sets of instructions:
      For Tomcat 5.5:
      • Put flex-tomcat-common.jar in common/lib
      • Place flex-tomcat-server.jar in server/lib (NOT shared/lib)
      • Copy context.xml in your web application under the META-INF directory (or adjust an existing context.xml to add the <Valve>)

      For Tomcat 5.0:
      • Put flex-tomcat-common.jar in common/lib
      • Place flex-tomcat-server-4150.jar in server/lib (NOT shared/lib)
      • Add a <Context> entry for your flex application that includes the security Valve (or edit an existing Context to add the <Valve>). For example, for the samples WAR:
        <Context path="/samples" docBase="${catalina.home}/webapps/samples" debug="0">
         <Valve className="flex.messaging.security.TomcatValve4150"/>
        </Context>
        

      You will now be authenticated against the current Tomcat realm. Usually, the default for this authentication stores user information in conf/tomcat-users.xml. See the Tomcat documentation for more information on realms. See the documentation for more information on LiveCycle Data Services custom authentication.
    2. You may also need to update the active 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 class="flex.messaging.security.TomcatLoginCommand" server="Tomcat" />
      ...
      
  5. (Optional) To use the JMSAdapter with the Message Service, you must install and configure a JMS provider (such as activeMQ or openJMS) for use with Tomcat.
  6. (JDK 1.4.x Only) If you are using Tomcat 5.5 with JDK 1.4.x, LiveCycle Data Services ES requires an implementation of Java Management Extensions (JMX), which is not provided with JDK 1.4.x. You can download JMX from the Sun web site or use an open-source implementation, such as MX4J.
  7. Restart Tomcat.

WebSphere

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

Note (WebSphere 5.1.x): To use the RTMP channel in a dataservice destination that uses transactions, you must install the WebSphere Business Integration Server version, which includes WorkManager.

To configure LiveCycle Data Services ES for use with WebSphere:

  1. Expand the flex WAR file to a temporary folder:
    jar -xvf flex.war 
  2. Uncomment the resource-ref element for WorkManager in web.xml. This 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 web.xml 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>

    To configure dataservice destinations that do not use transactions with RTMP based channels, set <use-transactions>false</use-transactions> for the dataservice destination in /WEB-INF/flex/data-management-config.xml.

  4. Create a WAR file from the expanded directory structure. For example:
    jar -cvf flex.war *
  5. 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.
  6. 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).
  7. (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.

JBoss

To use custom authentication with LiveCycle Data Services on JBoss, you must perform the following configuration steps:

  1. Put 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. Copy install_root/resources/security/tomcat/context.xml to your web application under the WEB-INF directory or adjust an existing context.xml to add the <Valve>.
  3. Restart JBoss.

You will now be authenticated against the current JBoss realm. Usually, the default 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 ES documentation and information in the install_root/resources/security directory..

XPath Issues with JBoss 4.0.3 SP1

There is a conflict with using the JDK5 XPathFactory with the current xerces 2.7.1/xalan 2.6.2 combo that manifests as a "No XPathFctory implementation found for..." error. The xalan JAR file needs to be updated to the 2.7.0 version to correct this. XalanJ Download. For more information, see http://wiki.jboss.org/wiki/Wiki.jsp?page=403UpgradeIssues.

OC4J

To run LiveCycle Data Services ES on Oracle Containers for J2EE (OC4J), you must pass 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 

SAP NetWeaver

SAP NetWeaver requires that LiveCycle Data Services ES be deployed in an Enterprise Application Archive (EAR) file. To deploy LiveCycle Data Services ES on SAP NetWeaver, perform the following steps:

  1. Create an EAR file that contains the flex.war file, along with the files required by SAP in the ear-root/META-INF folder.
  2. Update the NeverCompressed property of the HTTP Provider Service, to include *.swf, application/x-shockwave-flash, application/xml and application/x-amf.
  3. Deploy the EAR file.

Running from a compressed WAR

On some J2EE application servers (such as IBM WebSphere and Tomcat), the deployment process expands the WAR file into a working directory and, from that point forward, the expanded directory is considered to be the application. On other application servers (such as BEA WebLogic), the deployment process does not expand the WAR file into a temporary directory and the application server considers the compressed EAR or WAR file to be the application. When running LiveCycle Data Services ES on application servers that only support the compressed EAR or WAR format, such as WebLogic, some features, such as clustering and the web tier compiler, are not available.

LiveCycle Data Services supports the compressed WAR file deployment model, although you must pre-compile your application, since the web-tier compiler does not run from a compressed WAR file.

To run LiveCycle Data Services ES from a compressed WAR file, perform the following steps:

  1. Expand the flex.war file using winzip or the JAR utility.
  2. Create your application, including MXML files, ActionScript files, configuration settings and HTML wrappers.
    Note: When running from a compressed WAR, you must run compiled SWF files from within HTML wrappers; you cannot run MXML files directly. For more information on compiling SWF files and creating HTML wrappers, see Building and Deploying Flex 2 Applications.
  3. Open the WEB-INF/web.xml file in a text editor.
  4. Remove the servlet and servlet-mapping elements for the following:
    • FlexMxmlServlet
    • FlexSwfServlet
    • FlexForbiddenServlet
    • FlexInternalServlet
  5. Locate the servlet definition for MessageBrokerServlet, and update the flex.write.path init-param element to specify an existing, writeable, directory path:
    <init-param>    
    <param-name>flex.write.path</param-name> <param-value>C:/bea/flex</param-value>
    </init-param>
  6. Create a compressed WAR file from the expanded web application structure.
  7. Deploy the compressed WAR file.

Installing and configuring Flex Automated Testing

The Flex Automation Package installer comes with two installation preferences: With the QTP plugin and without the QTP plugin. If you install it with the QTP plug-in, the following files and directories are created:

  • QTP_Plugin_Demo — Contains an Adobe Captivate movie that describes the basics. Be sure to enable audio on your computer.
  • Flex 2 Plug-in for Mercury QuickTest Pro — Contains the QTP plug-in files.
  • frameworks — Libraries required to make flex applications automation aware.
  • resources — Contains the files required to use Run time loading feature.
  • Uninstall Flex Automation — Uninstaller.
  • license_automation.htm — License information.
  • readme_automation.htm — Readme file.

If you choose to install only the Automation Package, the QTP plug-in will not be installed. However the QTP plug-in installer will be saved for future installation. The Flex 2 Plug-in folder and QTP_plugin_Demo folder will not be created, but the other files and folders will remain unchanged. The following installer executable will be added:

  • QTP_Plugin_Installer.exe — The installer used to install the Flex plug-in for Mercury QTP.

To test applications with the Flex Automation Package and the QTP agent, you must install the following:

  • Mercury QuickTest Professional 9.1 or later (no support for Smart Identification)
  • Mercury QuickTest Professional 9.2 and patch 1701 if u want Smart Identification support
  • Adobe Flex 2 Plug-in for Mercury QuickTest Pro
  • Microsoft Internet Explorer, version 6 or later
  • Flash Player ActiveX control, version 9.0.28.0 or higher

Another way is to build your own custom agent. An example can be found at Custom Agents. Those who are planning to build a custom agent need not install the QTP plug-in.

Installing Flex Automated Testing files

Follow the steps below to install Flex Automated Testing files:

  1. Download the platform-specific Flex Automated Testing installer from the Adobe website:
    • Windows - Executable file (.exe extension).
    • Macintosh OS X - ZIP file that contains the installer application.
    • UNIX and Linux - Executable JAR file. Run with the java -jar command.
  2. Run the Flex Automated Testing installer.
  3. Accept the license agreement, specify a Flex Data Services license key, and follow the prompts.
  4. (Developers) Configure your Flex environment by following the steps outlined in Configuring automated testing support in Flex. (This step is optional if Run time loading feature is used)
  5. Test run-time loading by performing the following steps:
    • Compile the Flex applications that you want to test using standard compiler options. You do not need to include the automation SWC files when you use run-time loading.
    • Copy the runtimeloading.swf and RunTimeLoading.html files to your application SWF folder and deploy your compiled applications to the web server.
    • In Internet Explorer, request the RunTimeLoading.html file and pass the SWF name of the application you want to test as the value of the automationswfurl parameter; for example:
			http://localhost:8700/flex/RunTimeLoading.html?automationswfurl=myapp.swf
  1. (QC testing professionals only) Configure QTP by following the steps outlined in Configuring the QTP testing environment.

Configuring automated testing support in Flex

If you are using run-time loading, which Adobe recommends, you are not required to compile your application files with the automation libraries. You can ignore this section if you are using run-time loading feature.


Before you can pass a Flex application's SWF file to the QC professional, you must recompile it with the Flex automation libraries. For this, you must add automation.swc, automation_agent.swc, and qtp.swc files to the compiler's included libraries before compiling your application. If your applications use charts, you also add the automation_charts.swc file to the included libraries. This section describes how to do this with Flex Builder, the command-line compiler, and web-tier compiler.
Testing Flex applications with QTP requires the following SWC files:

  • automation.swc, automation_agent.swc, and qtp.swc - You deploy these SWC files to the same directory as your other SWC files (typically, the frameworks/libs directory). You must add these SWC files to your include-libraries compiler option.
  • automation_charts.swc - Add this SWC file to your include-libraries compiler option if your application uses charts.
  • automation_rb.swc and automation_agent_rb.swc - You deploy this SWC file to the /locale/en_US directory. This SWC file provides English-language resource bundles for the automated testing messages.

The automation.swc, automation_charts.swc and automation_rb.swc files are already installed with the Flex Data Services or Flex Builder installation. The qtp.swc and automation_agent.swc files are in the flex_automation_installer/frameworks/libs directory after you run the Flex Automation Installer. The automation_agent_rb.swc file is in the flex_automation_installer/frameworks/locale/en_US directory.
For all the SWC files except the automation_agent_rb.swc file, you extract them to the frameworks/libs directory (see the instructions below). If you use compile-time loading, compile with these libraries for every application you want to test.
Flex Builder: To set up Flex Builder to support Flex Automation with QTP:

  1. Copy the qtp.swc and automation_agent.swc files from the flex_automation_installer/frameworks/libs directory to flex_builder_dir/Flex SDK 2/frameworks/libs.
  2. Copy the automation_agent_rb.swc file from the flex_automation_installer/frameworks/locale/en_US directory to flex_builder_dir/Flex SDK 2/frameworks/locale/en_US.
  3. Start Flex Builder.
  4. Create a new Flex Project.
  5. Select your new Flex project in the Navigator.
  6. Select Project > Properties > Flex Compiler.
  7. In the "Additional compiler arguments" field, enter the following:
-include-libraries "flex_builder_dir\Flex SDK 2\frameworks\libs\automation.swc" "flex_builder_dir\Flex SDK 2\frameworks\libs\automation_agent.swc"    
  "flex_builder_dir\Flex SDK 2\frameworks\libs\qtp.swc" "flex_builder_dir\Flex SDK 2\frameworks\libs\automation_charts.swc"

The include-libraries compiler option is relative to the Flex Builder installation directory; the default on Windows is "C:\Program Files\Adobe\Flex Builder 2\".

  1. Click the OK button to save your changes and OK to close the project Properties dialog box.
  2. Compile your Flex application.

Command-line compiler: To set up the command-line compiler to support Flex Automation with QTP:

  1. Copy the qtp.swc and automation_agent.swc files from the flex_automation_installer/frameworks/libs directory to flex_sdk_dir/frameworks/libs.
  2. Copy the automation_agent_rb.swc file from the flex_automation_installer/frameworks/locale/en_US directory to flex_builder_dir/Flex SDK 2/frameworks/locale/en_US.
  3. Add the automation.swc, qtp.swc, automation_agent.swc, and automation_charts.swc files to the application's library by using the include-libraries compiler option. When you do this, be sure to use the += operator so that your entry is appended to the list of libraries and does not replace it. For example:
mxmlc -include-libraries+=../frameworks/libs/automation.swc;../frameworks/libs/qtp.swc;../frameworks/libs/automation_agent.swc;../frameworks/libs/automation_charts.swc MyApp.mxml

The exact paths depend on the location of the Flex application file relative to the mxmlc command-line compiler and the libs directory.

  1. Create an HTML wrapper file using the instructions in the Flex 2 Building and Deploying Flex Applications book.
  2. Compile your Flex application.

Web-tier compiler: To set up the web-tier compiler with Flex Data Services (FDS) to support Flex Automation with QTP:

  1. Copy the qtp.swc and automation_agent.swc files from the flex_automation_installer/frameworks/libs directory to flex_webapp_dir/WEB-INF/flex/libs.
  2. Copy the automation_agent_rb.swc file from the flex_automation_installer/frameworks/libs directory to flex_webapp_dir/WEB-INF/flex/locale/en_US.
  3. Open the flex_webapp_dir/WEB-INF/flex/flex-config.xml file.
  4. Add the automation_agent.swc, automation_charts.swc, automation.swc and qtp.swc files to the <include-libraries> entry, as the following example shows:
<include-libraries>
		<library>libs/automation.swc</library>
		<library>libs/automation_agent.swc</library>
     <library>libs/automation_charts.swc</library>
     <library>libs/qtp.swc</library>
</include-libraries>
  1. Restart your FDS server.
  2. Compile your Flex application.

After you compile the Flex application with the automation testing libraries, you pass the application and the wrapper to the QC professional so that they can run the application with QTP. Typically, you deploy these files to a web server that the QC professional has access to.

Configuring the QTP testing environment

This section describes the steps necessary for a QC testing professional to configure QTP to work with Flex applications.
To configure QTP for use with Flex:

  1. Install Flash Player 9 ActiveX control (9.0.28.0 or higher) for Microsoft Internet Explorer. This is currently the only supported player.
  2. Install QTP 9.1 or later. You must get QTP 9.1 from Mercury.
  3. Restart your computer.
  4. If you have selected “With QTP plugin” as your installation preference, you can skip this step. If you have selected “Only Automation” as your installation preference, the Adobe Flex 2 Plug-in for Mercury QuickTest Pro with the QTP_Plugin_Installer.exe is available in the Flex Automation installation directory. This step requires that you have JRE 1.4.2 or later installed.
  5. Start QTP.
  6. Close QTP.
  7. Copy the compiled SWF file and wrapper files to your web server. If you run the SWF file without a wrapper file from the file system rather than from a web server, you must make sure that the file is in the local-trusted sandbox.
  8. Start QTP again. The Add-in Manager lists the Flex plug-in.
  9. Select the Flex plug-in in the Add-in Manager..
  10. Select New > Test and click the Record button.

NOTE: Flex application testing with QTP currently supports only Microsoft Internet Explorer with the ActiveX Flash Player.
For more information on these tasks and using QTP to test Flex applications, see Testing with QTP.

Uninstalling

Uninstalling LiveCycle Data Services ES on Windows:

  1. Select Start > Settings > Control Panel.
  2. Select Add or Remove Programs.
  3. Click Adobe LiveCycle Data Services ES 2.5.
  4. Click the Uninstall button in the uninstaller dialog box.
  5. Click Done.

Note: On Windows, LiveCycle Data Services ES can also be uninstalled using Start > All Programs > Adobe > LiveCycle Data Services ES 2.5 > LiveCycle Data Services Uninstaller.

Unix

Run the following shell script to uninstall LiveCycle Data Services ES:

      ./lcds_root/UninstallerData/Uninstall Adobe_LiveCycle_Data_Services_ES

Java

If you installed LiveCycle Data Services ES with the Java installer, use the following command to uninstall:

      java -jar /lcds_root/UninstallerData/uninstaller.jar -i console

 


Take a survey