Bug 1073637 - Create BRMS/BPMS product distribution for Websphere
Summary: Create BRMS/BPMS product distribution for Websphere
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Build and Assembly
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER1
: 6.0.2
Assignee: Ryan Zhang
QA Contact: Radovan Synek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-06 20:47 UTC by Rajesh Rajasekaran
Modified: 2014-08-06 19:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 19:49:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rajesh Rajasekaran 2014-03-06 20:47:03 UTC
Description of problem:
It was brought to attention that the current generic deployable distribution intended for non-EAP containers does not work with Websphere due to 
- conflicts in classpath
- additional libraries required to support websphere
- configuration being different from what is required for Tomcat in the generic distribution today. 

Create a deployable distribution that supports BRMS and BPMS on Websphere. 
Package naming - TBD

This might also affect the naming of the current generic deployable as it is no longer generic.

Comment 1 Ryan Zhang 2014-04-10 10:13:47 UTC
It makes sense to me to rename the deployable-deployable-generic since  the generic is mean to be only JBoss Web Server and WeSphere as certified container.

(In reply to Rajesh Rajasekaran from comment #0)
> Description of problem:
> It was brought to attention that the current generic deployable distribution
> intended for non-EAP containers does not work with Websphere due to 
> - conflicts in classpath
> - additional libraries required to support websphere
> - configuration being different from what is required for Tomcat in the
> generic distribution today. 
> 
> Create a deployable distribution that supports BRMS and BPMS on Websphere. 
> Package naming - TBD
> 
> This might also affect the naming of the current generic deployable as it is
> no longer generic.

Comment 2 Ryan Zhang 2014-04-14 10:09:24 UTC
After discussed in PM maillist, we are going to add jboss-bpms-${version}-deployable-websphere.zip and keep the jboss-bpms-${version}-deployable-generic.zip since the generic also contains others bits for engines.

Comment 3 Ryan Zhang 2014-04-14 10:28:37 UTC
It makes more sense to use "jboss-bpms-${version}-deployable-was8.zip" instead of "jboss-bpms-${version}-depolyable-websphere.zip".

(In reply to Ryan Zhang from comment #2)
> After discussed in PM maillist, we are going to add
> jboss-bpms-${version}-deployable-websphere.zip and keep the
> jboss-bpms-${version}-deployable-generic.zip since the generic also contains
> others bits for engines.

Comment 4 Radovan Synek 2014-04-28 15:23:12 UTC
Verified with BRMS/BPMS-6.0.2.ER2


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