Bug 1172615 - Unify JMS setup across supported containers
Summary: Unify JMS setup across supported containers
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Marco Rietveld
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-10 13:17 UTC by Radovan Synek
Modified: 2016-09-20 05:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-08 16:33:46 UTC
Type: Enhancement
Embargoed:

Attachments (Terms of Use)

Description Radovan Synek 2014-12-10 13:17:34 UTC 
BPMS supports JMS on WebSphere, WebLogic and EAP containers. However, on each of these containers different configuration is needed. For example, for EAP there is a single connection factory, for WebSphere two CFs are needed (KIE.RESPONSE.ALL and KIE.INPUT), for WebLogic 4 CFs - there is a CF for each queue. Also default JNDI queue names are diffent - e.g. jms/KIE.SESSION vs. jms/queue/KIE.SESSION. Please see more details in a readme for corresponding containers [1], [2].

Is it possible to unify the JMS setup for supported containers in following ways? 
- number and default naming of connection factories
- default naming of queues

[1] WAS : https://github.com/droolsjbpm/kie-wb-distributions/tree/6.0.x/kie-wb/kie-wb-distribution-wars/src/main/was8

[2] WLS : https://github.com/droolsjbpm/kie-wb-distributions/tree/master/kie-wb/kie-wb-distribution-wars/src/main/assembly/weblogic12
Note You need to log in before you can comment on or make changes to this bug.