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.
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.
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.
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.
Verified with BRMS/BPMS-6.0.2.ER2