How to use automation source in FlexBuilder3

September 24, 2009 at 12:18 pm 7 comments

Not able to locate the automation source ?

Do you have a valid professional FB license ? If yes, read further.

As we discussed in the earlier posts, the automation libraries are automation.swc, automation_dmv.swc, automation_flashflexkit.swc

You can find the source for this as follows.

automation.swc  -> C:\Program Files\Adobe\Flex Builder 3\sdks\3.0.0\frameworks\projects\automation

automation_dmv -> C:\Program Files\Adobe\Flex Builder 3\sdks\3.0.0\fbpro\projects\automation_dmv

automation_flashflexkit -> C:\Program Files\Adobe\Flex Builder 3\sdks\3.0.0\fbpro\projects\automation_flashflexkit


Missing fbPro?

If you have a valid professional FlexBuilder license and if you are missing the fbpro location you can get the source in 2 ways.

1. Go to c:/Documents and Settings/All Users/Application Data/Adobe/Flex  ( this is the license-file-location)

2. You will find a file known as . Take a backup copy of this file and delete it

3. restart your FB. Apply the license again (either you may be asked to enter in the start up itself , else using Help -> manage flexLincense)

4. Once the key is accepted and informed as a valid professional key, check for the fbpro folder again.

Still Missing?

FB is supposed to extract the source and 2.0.1 automation libraries, when the key is accepted. But looks like in some cases, it is not. In those case you can get the source as follows

1. go to C:\Program Files\Adobe\Flex Builder 3\sdks\3.2.0\lib

2. Check whether you have DMV-source.jar there

3. You should have it. you can extract the source  from command line as

            java -jar DMV-source.jar {license-file-location} {output-location}

you can find more details on this at

How to use the source for debugging?

If you like to add this source to debug your project.

1. right click on project -> properties

2. Select the Flex Build Path

3. In the source Path tab select the location of the source till src  (e.g C:\Program Files\Adobe\Flex Builder 3\sdks\3.2.0\fbpro\projects\automation_dmv\src)

If your project was including the swc corresponding to this source, now it will compile using the source. So you can edit the source, you can add break point and debug.


Entry filed under: Flex Automation.

Locale libraries for automation Using FileReference.browse or ?

7 Comments Add your own

  • 1. Matthew Zimmer  |  October 31, 2009 at 3:03 am

    I just wanted to send a (possibly premature) word of caution to those attempting to delete the file at least on a Mac (I have not tested on Windows or Linux).

    I noticed while looking at the properties file (“/Library/Application Support/Adobe/Flex/”) that there is a “flexbuilder3=” AND a “flashbuilder4=” section (I have Flash Builder 4 Beta 2 installed now; it should be “flexbuilder4=” but that’s for another day). I suspect this means that, if you happen to be running multiple versions of Flex Builder on the same machine, you will need to enter your license key again for each application version that relies on this file the next time you start them.

  • 2. vish  |  December 8, 2009 at 11:40 pm

    we are compiling these libraries alongwith additional SilkTest library into the flex app.
    How advisable is it to have this on our production environment?
    Is there a security or performance issue?

    • 3. raniskumar  |  December 10, 2009 at 12:46 pm

      It is not advisable to have the automation components in the production code.
      It has impact on performance and size of swf also.

      • 4. mikek  |  February 8, 2011 at 2:23 pm

        could you ellaborate on the performance impact of the statically linked automation libraried?

      • 5. raniskumar  |  April 6, 2011 at 9:46 am

        for every user interaction certain calculation is done to identify the interaction object, its hierarchy, conversion of the interaction details etc. hierarchy information calculation can be expensive if the component is deeply nested.

        However majority these calculation happens, if the application is in the recording mode.

  • 6. ESR  |  March 18, 2011 at 9:33 pm


    We are using runtime loading option for testing Flex application using QTP plugin, we use the automation files in Dev and QA enviroment, However we would like to use these automation files in production to monitor application using test tools,

    What are the security risk in deploying these automation code in Production, Since we use runtime loading this will not impact performance but, I would like to know any security risks.

    The application access is retricted by user name /pwd.

    • 7. raniskumar  |  April 6, 2011 at 9:39 am

      There is no security risk, unless you are sending the recorded data from the users’s machine to some other location. (i.e whatever program knows the automation also knows). e.g password typed , even though it is shown as masked string, the actual entered string is known to the application and hence known to the automation also. But this is not a security risk as long as the tool which captures the data ensures data protection. (i.e in test tool script, one would be able to see the data entered as readable text)


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed


September 2009
« Aug   Oct »

Most Recent Posts

%d bloggers like this: