]
Ramesh Reddy commented on TEIID-2262:
-------------------------------------
I do not believe this is an issue with Teiid 8.2.x
Add ability to move VDB to ACTIVE/UP state from Admin Console
-------------------------------------------------------------
Key: TEIID-2262
URL:
https://issues.jboss.org/browse/TEIID-2262
Project: Teiid
Issue Type: Feature Request
Components: Jopr Plugin
Reporter: Marc Shirley
Assignee: Ken Johnson
Currently, a VDB that is deployed to a server, but does not deploy successfully (for
instance, because a datasource referenced by the VDB is not active) must be redeployed to
the server to fix the inactive status. In the case of an incorrect JNDI name being used
within the VDB, the JNDI name can be corrected through the Admin Console, but there is no
way to redeploy or move the VDB to an active state from the Admin Console. This causes
confusion due to being able to make changes to the configuration, but not being able to
effect those changes on a currently INACTIVE/DOWN status VDB.
There was expectation to be able to administer the VDB from Admin Console due to the
ability to alter the configuration properties in the UI. However, if the initial
deployment fails and results in the VDB being marked as DOWN/INACTIVE, then they are
unable to rectify this without fully redeploying the VDB.
Would like the ability to update the JNDI names and effect those changes on the currently
deployed VDB to move it from an INACTIVE to an ACTIVE state.
This can be tested with the below steps:
1) Configure a VDB with an incorrect JNDI name
2) Deploy the VDB to an EDS server
3) Log into the Admin Console
4) Navigate to the VDB
5) Confirm the VDB is listed in an INACTIVE state
5) Modify the incorrect JNDI name to point to a valid datasource
6) Confirm that the VDB has moved to an ACTIVE state
--
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: