[
https://jira.jboss.org/jira/browse/TEIID-193?page=com.atlassian.jira.plug...
]
Larry O'Leary commented on TEIID-193:
-------------------------------------
Can we not expose each membership domain as a separate service in the service list?
Basically all components that are derived (marked) as membership service could be
displayed as a separate service with its own service status in the service state panel of
the Console.
So, if I had a file membership domain defined called file01.dom and an LDAP membership
domain defined called ldap01.dom then I would see in the service panel:
PlatformStandard
|
+--MembershipService: file01.dom -- Running
+--MembershipService: ldap01.dom -- Failed Initialization
MembershipService does not show failure in Console when unable to
connect to LDAP database
------------------------------------------------------------------------------------------
Key: TEIID-193
URL:
https://jira.jboss.org/jira/browse/TEIID-193
Project: Teiid
Issue Type: Feature Request
Components: Console
Affects Versions: 6.x
Reporter: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
Defect Tracker #2865 : Set up MembershipService to have MetaMatrix and LDAP users.
Server PC was unable to communicate with Unix box hosting LDAP database. Server started
and MembershipService showed Running even though it had failed to read LDAP users. There
is an exception in MetaMatrixVM log but need a visual clue in Console.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira