Bug 779028 (SOA-1440)

Summary:	Admin Guide: standalone server instructions inadequate for product
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Dana Mison <dmison>
Component:	Documentation	Assignee:	David Le Sage <dlesage>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2 CP04, 4.3 CP02
Target Milestone:	---
Target Release:	FUTURE
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1440
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-05 18:44:21 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dana Mison 2009-08-14 04:23:05 UTC

Affects: Documentation (Ref Guide, User Guide, etc.)
Complexity: Low
project_key: SOA

The standalone server section of the configuration chapter in the administration guide basically just points the user to a jboss.org wiki page.  Not good enough :-)

this section needs to be fleshed out with specific details rather than just directing the user to the wiki page

Needs to dicuss:
 - multi-homed machines
 - using the service binding manager to handle port numbers

This content would be equally useful for the ESB community docs & should go upstream in some form.

Comment 1 Dana Mison 2011-02-25 00:50:58 UTC

This is really an application server level issue - not specific to the ESB - and material that briefly covers this has been introduced into the GSG in 5.1.0  

Suggest removing that section from the product ESB Admin Guide.  Content from the 5.1.0 GSG can be moved over.  Engineering will need to review that content and provide updates.

Comment 2 David Le Sage 2011-07-14 04:52:15 UTC

Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage

Comment 3 David Le Sage 2011-07-14 04:52:49 UTC

This was fixed as part of the 4.3.CP05 release.  If there is ever another 4.2 series release, we can reopen this JIRA.