[
https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin...
]
Paul Richardson commented on TEIID-2650:
----------------------------------------
Brian,
Many thanks for that helpful information. It raises an interesting question though. In
order to get teiid up and running, I use the
[
teiid-domain-mode-install.cli|https://docs.jboss.org/author/display/teiid...]
script to install the teiid resources on the domain master. Thus, I think that would
constitute domain-wide would it not?
Certainly, my domain member server inherits the teiid configuration from the domain
master. It would seem that teiid is not merely a single application that is only deployed
on member servers and in that sense 1 teiid configuration per domain?
A jboss server in domain mode does not advertise its teiid
runtime-version
--------------------------------------------------------------------------
Key: TEIID-2650
URL:
https://issues.jboss.org/browse/TEIID-2650
Project: Teiid
Issue Type: Bug
Components: Server
Affects Versions: 8.4
Reporter: Paul Richardson
Assignee: Ramesh Reddy
Priority: Blocker
Fix For: 8.4.1, 8.5
A standalone jboss server installed with teiid advertises its teiid runtime version at
the path /subsystem=teiid/runtime-version.
Likewise, a domain jboss server installed with teiid in the 'ha' profile should
advertise its runtime version at the path /profile=ha/subsystem=teiid/runtime-version.
However, whereas the standalone returns the correct value for this attribute, the domain
mode server fails, only returning 'undefined'.
This attribute is essential to designer in determining what version is the teiid
instance. This in turns determines the functionality of the modelling that is available
and which teiid client should be used for connection.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira