In our WAS7 ND environments, we use scripts to manage our installed applications.
From time to time, we've got a problem with plugin-cfg.xml generation: After "redeploying" (uninstall & install in one script), one of our two IHS/plugin-cfg.xml does not contain the "redeployed" application.
Script workflow:1.) uninstallation of the application (old version)
2.) save
3.) sync
4.) install of the application (new version)
5.) save
6.) sync
7.) start of the application
From what I understand, plugin-cfg.xml generation is started everytime I save the changes made during script workflow. Therefore I assume that there is kind of a race condition going on: the first plugin-cfg.xml generation made after uninstalling the application takes too long / the plugin-cfg.xml generation taks overtake each other, i.e. due to dmgr system load. Is that plausible?
I thought of removing steps 2&3, therefore performing uninstallation&installation without save&sync in between. As then there is only one save left, plugin-cfg.xml generation should only take place once, after installing the new version of the application, thus removing the assumed race condition.
What is your opinion of this alternative script workflow?
We implemented this workflow to make 100% sure that all artifacts of the old version of the application are removed before installing a new version. By removing step 2&3, is there a danger of getting "mixed version" applications (applications with out-of-date artifacts)?