Bug 838950

Summary:	JBoss Data Grid 6 Administration & Configuration Guide 3.1 - Missing critical information
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Johnathan Ingram <jingram>
Component:	Documentation	Assignee:	Misha H. Ali <mhusnain>
Status:	CLOSED DUPLICATE	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	jdg-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Instance Name: Not Defined Build: CSProcessor Builder Version 1.4 Build Filter: null Build Name: Build Date: 15-06-2012 10:17:05
Last Closed:	2012-07-12 04:50:47 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:

Description Johnathan Ingram 2012-07-10 13:42:29 UTC

Description of problem:

Section 3.1 for distribution mode of the cache contains no information on how to configure the cache in distributed mode.

The section needs to contain example configuration and detail for the configuration items. (There is no examples on 

Infinispan has a different configuration to EDG and hence the community configuration examples cannot be used as an example of configuring EDG

As the documentation stands, its impossible for us to be able to configure EDG outside of having to ask internal Red-Hat resources for basic information such as how does the 


Expected results

The documentation needs to allow partners to configure the product (The basics)
The documentation is not product ready in order for partners to be able to test, provide proof of concepts or even production install EDG without having to log bugs to obtain basic configuration information.

Comment 1 Misha H. Ali 2012-07-12 04:50:47 UTC

Johnathan,

I believe this is addressed by another bug that requests the same information. Please view the following bug and if the problem is not completely addressed, feel free to reopen this bug with a comment outlining what else you would require.

https://bugzilla.redhat.com/show_bug.cgi?id=837957

*** This bug has been marked as a duplicate of bug 837957 ***