LiveCycle ES2 removes JMS and uses Workmanager API… Yay!!

April 25th, 2010

Until LiveCycle ES2, the JMS was used in LiveCycle to manage processes and tasks. This has led to some of the odd and painful incidents..

LiveCycle ES2 uses Workmanager API (JSR-237) which will definitely make the LiveCycle community happier..

The Livecycle server can also have the java parameters to control the workmanager throttling options.
Here are the option that you can tweak as java parameters:

  • adobe.work-manager.queue-refill-interval
  • adobe.workmanager.debug-mode-enabled
  • adobe.workmanager.memory-control.enabled
  • adobe.workmanager.memory-control.high-limit
  • adobe.workmanager.memory-control.low-limit

More details at – http://kb2.adobe.com/cps/825/cpsid_82568/attachments/WorkManagerThrottle.pdf

Filed under: Uncategorized

Tags: , ,

Leave a Comment

(required)

(required), (hidden)

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

TrackBack URL  |  RSS feed for comments on this post.


Categories

Recent Tweets

    Recent Posts

    Blogroll

    Tags

    add-ons dataDoc Form Guide Forms pre-population Innovation JSR-237 LC keywords LiveCycle Designer LiveCycle ES LiveCycle ES2 LiveCycle Forms LiveCycle operators LiveCycle testing Logical Operators Max 2009 Orchestration Render Service Richtext in Textfield Route conditions Styling Task Instructions Upgrade Workbench Workmanager API Workspace XPath and or XPath expression XPath keyword

    The fine print!!

    The views on this blog are my own and don’t necessarily represent my employer's views, strategies or opinions.