Details
-
Type:
Improvement Request
-
Status:
New
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 3.1
-
Fix Version/s: None
-
Component/s: Installation/Deployment
-
Security Level: Public
-
- Description:
-
Hide
Today, an artefact can be to the UNKNOWN state into the, for 2 main reasons:
1->an error occurs during the general recovery
2->an error occurs during the nominal installation/deployment/uninstalltion/undeployment//stop/start/shutdownOn the second case (and maybe on the first case, i don't know), if the component is developed on a great way (implied message
), we can start it again after the correction. For examples, do the good rights to the user for the bc filetransfer, or create the MySQL user for the se kpi: that's the 2 points tested today through ant tasks. So we can simply "save" our installation, without do a complete reinstall. Moreover, if we can't restart the artefact, we can at least do a forced uninstall/undeploy...and keep safe the others non impacted artefacts.The Web Consolle seems to be able to show the atefacts under UNKNOWN state. We "just" have to put them into the lists provided by the Petals ESB.
ShowToday, an artefact can be to the UNKNOWN state into the, for 2 main reasons: 1->an error occurs during the general recovery 2->an error occurs during the nominal installation/deployment/uninstalltion/undeployment//stop/start/shutdown On the second case (and maybe on the first case, i don't know), if the component is developed on a great way (implied message ), we can start it again after the correction. For examples, do the good rights to the user for the bc filetransfer, or create the MySQL user for the se kpi: that's the 2 points tested today through ant tasks. So we can simply "save" our installation, without do a complete reinstall. Moreover, if we can't restart the artefact, we can at least do a forced uninstall/undeploy...and keep safe the others non impacted artefacts.
The Web Consolle seems to be able to show the atefacts under UNKNOWN state. We "just" have to put them into the lists provided by the Petals ESB.
-
- Environment:
- Petals ESB, Webconsole
Under the last versions (esb 3.1.1, web console 2.0.4, RHEL 5, tomcat 6), we can see (and uninstall overall!) the components, but not the service assemblies. I don't know about the shared library.