Bug 488709

Summary:	Problematic check-valid-connection-sql
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Andreas Plesner Jacobsen <apj>
Component:	SOA_ESB_Administration_Guide	Assignee:	soa-docs <soa-docs>
Status:	ASSIGNED ---	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	4.3	CC:	apj
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	All
URL:	http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.GA/html/Administration_Guide/switching_databases.html
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andreas Plesner Jacobsen 2009-03-05 11:45:47 UTC

Description of problem:
If you're using different databases for the different components of the SOA platform, you should also change the check-valid-connection-sql statement of the data source, since these will not contain the jbm_user table.
The manual doesn't mention this.
Steps 2 and 3 should have this information added.

Comment 1 Dana Mison 2009-03-09 01:15:25 UTC

Thank you for your feedback.  We will be incorporating additional details into this guide for a future release.