Bug 1227857

Summary: [GSS](6.4.z) Add all resource adapter configuration options to console
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Carl <carlton.zachary>
Component: Web ConsoleAssignee: Enrique Gonzalez Martinez <egonzale>
Status: CLOSED WONTFIX QA Contact: Pavel Jelinek <pjelinek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: bbaranow, bmaxwell, brian.stansberry, cdewolf, egonzale, hbraun, hpehl, jkudrnac, jolee, pjelinek, rpelisse, tcowhey
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-11 08:50:50 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 Carl 2015-06-03 16:12:05 UTC 
Description of problem:


When configuring a .rar resource adatper via the admin console I noticed there are some configuration options that are not available via the console, but are available via the CLI, such as the connection-definition options:

timeouts
recovery
capacity
...
etc.

All should be configuration via admin console for resource adapters.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Romain Pelisse 2015-06-04 07:36:34 UTC 
Hi,

Can you contact your support unit, using the Red Hat Customer Portal[1], as issues against EAP needs to be processed first by our support unit (and will take care of creating this BZ, but also the one(s) required against upstream (Wildfly).

In the meantime, I close this entry with "INSUFFICIENT_DATA", for clarity purpose.

Thanks !

[1] https://access.redhat.com/
Comment 2 JBoss JIRA Server 2015-09-17 13:38:43 UTC 
Heiko Braun <ike.braun> updated the status of jira HAL-684 to Resolved