Bug 779341 (SOA-1730) - Rework documentation related to jBPM/ESB integration options
Summary: Rework documentation related to jBPM/ESB integration options
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: SOA-1730
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation
Version: 5.0.0 ER5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.3.0 GA
Assignee: David Le Sage
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-17 08:07 UTC by Jiri Pechanec
Modified: 2014-01-31 05:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-31 05:20:40 UTC
Type: Task


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 780416 0 high CLOSED Example to illustrate how to restore the jBPM native services job executor? 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1730 0 Blocker Closed Rework documentation related to jBPM/ESB integration options 2014-01-31 05:19:15 UTC

Internal Links: 780416

Description Jiri Pechanec 2009-12-17 08:07:16 UTC
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Date of First Response: 2009-12-17 11:29:03
project_key: SOA

It was agreed that JMS/JCA inflow based configuration of jBPM/ESB integration is the default configuration and the signle one supported with one exception. We thus need to modify the documentation to
1) Describe JMS/JCA inflow based configuration of jBPM/ESB integration as the single supported way in SOA-P configurations with ESB deployed
2) Document the limitation that jbpm.esb supports only JBoss Messaging JMS provider - pleae ask Kevin if we put this limitation to jbpm.esb as the whole or only on those one or two queues that really uses JBM specific features.
3) Remove text about JMS/JCA inflow/quartz scheduler based jBPM/ESB integration
4) Document that jBPM JobExecutor is supported only for configurations that does not have ESB deployed (the executor is typically started by servlet in WAR file)

Comment 1 Julian Coleman 2009-12-17 16:29:03 UTC
As per SOA-1728 and SOA-1729:
  the default integration is now the JMS/JCA inflow one.
  the previous default (JobExecutor) integration is now available in the
    server/<profile>/jbpm.esb/config/jobexecutor directory.
  the Quartz based integration is no longer available in the platform.


Comment 2 Dana Mison 2009-12-21 01:59:29 UTC
Hi, we need more specifics on what sections of what document this applies to.

Comment 5 Len DiMaggio 2010-01-05 21:00:36 UTC
Section 7.2.5 of the Programmers' Guide describes the ESB's use of a Quartz Scheduler - is this the same JMS/JCA inflow/quartz scheduler?



Comment 6 Dana Mison 2010-02-04 01:04:45 UTC
Replaced content of "jBPM Message and Scheduler Service" section with:

The supported jBPM/ESB integration in the JBoss Enterprise SOA Platform has the following limitations:

1 - JMS/JCA inflow is the only supported configuration of jBPM/ESB integration for server configurations with ESB deployments.

2 - jbpm.esb only supports the JBoss Messaging JMS provider.

3 - The jBPM JobExecutor is supported only for configurations that do not have the ESB deployed. The executor needs to be started by a servlet in a WAR file.

4 - Integration using the Quartz scheduler is not longer available.

Comment 7 Jiri Pechanec 2010-02-12 10:28:09 UTC
The documentation is incorrect as JCA-inflow integration is now the default one. So the XML configuration should contain values specific for JCA-inflow and the instructions that follows has to be modified to see how to enable back jBPM native services (from jobexecutor dir) for the standalone deployments.

Comment 8 Dana Mison 2010-02-15 08:03:11 UTC
Sorry Jiri, I don't know why this document never updated on the doc-stage site with the content as per my comment on the 3rd of February.

I've just rebuilt it now, hopefully it will show up in a few hours.

If for some reason it doesn't (don't know why), there is another copy here: http://downtown.englab.bne.redhat.com/drafts/JBoss_Enterprise_SOA_Platform/5.0.0/Administration_Guide/html/message_and_scheduler_service.html

Can you please supply what additional content is required.

Comment 9 Dana Mison 2010-02-15 21:45:19 UTC
Didn't reassigned issue.  See previous comment.

Comment 12 Anne-Louise Tangring 2010-09-21 18:44:46 UTC
This is a candidate for SOA 5.1.0

Comment 14 Dana Mison 2011-01-05 00:12:11 UTC
Writer: Added: Darrin


Comment 15 Dana Mison 2011-01-27 06:43:22 UTC
Link: Added: This issue related SOA-2847


Comment 16 Dana Mison 2011-01-27 07:33:55 UTC
Re your comment above: 
https://issues.jboss.org/browse/SOA-1730?focusedCommentId=12514180&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12514180

Does that mean that the originally requested content is now wrong ?  If so can you please supply updated content for this JIRA ?

(I misread that comment originally, feel kind of stupid now)

Comment 17 David Le Sage 2011-07-22 04:22:02 UTC
Release Notes Docs Status: Added: Not Required
Writer: Removed: Darrin Added: dlesage



Note You need to log in before you can comment on or make changes to this bug.