Bug 1113555

Summary:	Missing and unsupported containers in Development Guide
Product:	[Retired] JBoss BPMS Platform 6	Reporter:	Ivo Bek <ibek>
Component:	Documentation	Assignee:	Vidya <viyengar>
Status:	CLOSED NEXTRELEASE	QA Contact:	Marek Baluch <mbaluch>
Severity:	high	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	high
Version:	6.0.2	CC:	brms-docs, rrajasek
Target Milestone:	CR1
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-04 04:07:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1119701

Description Ivo Bek 2014-06-26 12:18:26 UTC

Description of problem:

I noticed that many parts of Development Guides were not changed from the community documentation and so they contain unsupported containers or in some cases they are missing (e.g. mainly WebSphere is not mentioned).

It might not be all but from the quick look, I found the following:

13.5.1. JMS Queue Setup
"When the Workbench is deployed on the JBoss AS or EAP server," -- I believe we should name the application Business Central and it can be deployed on EAP or WebSphere. (JBoss AS is not supported)

13.6.3. The JMS Remote Java RuntimeEngine Factory
"However, this is only possible when the jBPM console or KIE Workbench instance is running on Wildfly or JBoss AS, or JBoss EAP." -- this part is probably also from the community version. There should be Business Central instead of "jBPM console or KIE Workbench instance" and probably running only on JBoss EAP.

13.10. RemoteJmsRuntimeFactory constructor arguments
serverURL java.net.URL This is the URL of the (JBoss) server instance.. -- it is not just for JBoss EAP server instance but also for WebSphere

Configuration using an InitialContext instance
Important - replace all "JBoss AS 7 or EAP 6" just for "EAP6". In that case the version of the artifact should not vary and a user should know which version to use "Depending on the version of AS 7 or EAP 6 that you use, this version may vary.".

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

Comment 3 Vikram Goyal 2015-03-04 04:07:48 UTC

Since this is an older bug, a lot of these issues have already been addressed. The remaining have been fixed with changes to the sections describer in the bug description.

This can be verified by scanning the Development Guide here [1].

I am closing this bug and marking it for next release.

[1] http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_BPM_Suite/6.1/html-single/Development_Guide/index.html