Guess how did I spend the last three days ? I tried to get passed the WebSphere Portal Installation Wizard on Windows, on subsequent attempts to install it on my machine.
After the first successful install, I upgraded to 6.0.1.3, but I had the impression that Portal is hanging on the Internationalization service. This was not the case as it turned out, I still have to figure why Portal is spending almost 15 minutes to this point, when starting. But this is another story, I'm working on it :)
So I said, I upgraded without thinking, my Portal is not starting. OK ! Let's approach the Microsoft way of doing things ! uninstall, then reinstall !
Uninstall from Add/Remove ... waiting another hour or so .... then delete everything under d:\ibm\ (didn't deleted the ibm folder and this is the trick which perhaps is the explanation why I failed) .... reboot the machine, start over, wait another 2 hours or so for the Wizard .... and bang ! the error message that script wmm_cfg.xml:512 line didn't executed.
hmmm .... start searching on net .... some other folks complained about the same error, but could not found an explanation.
good. ok, this happens from time to time. I found that Portal actually was installed but at that moment it was trying to enable global security on WAS. I tried manually with WPSConfig, I managed to do it but I had no idea what password it had set on cloudscape, so I lost all access to WAS and Portal :)
So, instead of mocking around with it (I think I'm getting older for this), I started again, with the wizard, but this time I made sure I deleted ALL the installation path. That is, including the ibm folder.
And, to my surprise, this time it got through. The installation wizard for the Portal showed the 'successful message'.
And here comes the thing: appears that this wizard wants to create the install path by itself (as d:\ibm existed when it failed). I don't have another explanation.
No comments:
Post a Comment