Flash player release or debug ?


LiveCycle Correspondence Management Solution has a Flex based user interface which works with Flash Player version of 10.2 or above.


Though Flash Player is installed almost on every internet connected PC , often some Correspondence Management solution users have following questions in their minds

1) What is the version of Flash Player plug-in installed in my browserr?

2) Is the Flash Player plug-in that is installed in my browser a release version or a debug version?

When users log on to Correspondence Management Solution http://hostname:port/cm/manageassets.html , Correspondence Management Asset Manager UI is loaded only if FlashPlayer 10.2 or higher is installed if not users are prompted with a URL in their browser to get a latest version of Flash from Adobe’s website.


latest version of Flash Player can be downloaded from http://get.adobe.com/flashplayer/

If FlashPlayer is already installed it’s easy to check which version of it is installed

1) If you are connected to internet just click here to check what version of Flash Player you currently have and what is the latest version available

2) If you are not connected to internet , Once you log on to CM solution , Right Click anywhere on Manage Assets UI , If the FlashPlayer is of debug version you would see a menu item ‘Debugger’ in context sensitive menu , If not it means the Flash Player that is installed is a release version. Version number of Flash Player is also displayed on the context sensitive menu (see the below image)


Connection Error


Developers who are working with Correspondence Management solution would have encountered these errors when working with author and publish instances (see the screen grab of error below).



These errors will be seen when Author and Publish instances of Correspondence Management solution are run on same machine and if one tries to work with both author and publish instances in two different tabs of same browser. This is quite common on a development system but not on production systems.

These errors can be avoided in different ways

1) Instead of accessing author and publish with same name or IP in browser’s address bar , One can use an IP address for one instance and FQDN for another instance i.e

http://fqdn:author-port/cm/manageassets.html (for author)

http://ipaddress:publish-port/cm/manageassets.html (for publish)

2) One can use two different browsers , one for accessing author instance and another for publish instance

3) Make two entries in hosts file with same IP address but different names , i.e if one’s client machine’s IP address is xx.xx.xxx.xxx one can add following entries in the hosts file of client machine from where the author and publish CM instances are accessed via browser and access the author and publish instances with their names provided in hosts file

e.g entries in hosts file (If the system is Win XP the hosts file will be under %SystemRoot%\system32\drivers\etc\ folder )

xx.xx.xxx.xxx    author

xx.xx.xxx.xxx    publish

Once the above entries are made in hosts file one can access the author and publish instances as below