This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I've just installed WebSphere Portal Server on my Win2k machine. My machine's fully qualified host name is "troia.com" . But at the last step of the installation. The set up manager gives me a error: It can not find the page "http://troia.com/wps/portal". After 12 attempts the setupe manages says that I have to check that my WebSphere Portal Server is running. But I'm sure it is running correctly (according to the log files and the messages that the application console gives). I can not see the Portal homepage. When I search the disk I couldn't find the wps/portal directory. But if I create such directories in the "IBM HTTP Server/htdocs" and I put any html file in that directory ("C:\IBM HTTP Server\htdocs\wps\portal\") I can see this html file on my browser. Can anybody help me.
Hi, there, The reason that putting html in the htdocs directory is that the HTTP Server is serving your home pages instead of the Portal Server serving them through HTTP. You won't find the directory wps/portal anywhere on your hard drive because it is a base URI configuration that is set during the install and it's virtual. If you just let it default, then WPS sets it up for you in the directory that you've been trying to find, so I don't think that's the root of your problem. This is a really difficult product to install. To make it run successfully on my machine, I had to install it, uninstall it, reinstall Windows 2000 and start from scratch. Hopefully this won't be the case with you. A few suggestions: If you didn't use the default id and password (wpsadmin), go back and reinstall using these. Make sure that DB2 has the correct fixpack installed and that you can connect to the WPS40 DB. If you're using Single Server Edition of WAS, make sure that you start the server with the correct configuration file (portal-cfg.xml I think). Regenerate the WebSphere plugin in WAS on the node associated with your host. Most of the install went through, I'm guessing from your post, so if you haven't read the 'Troubleshooting' Section in the InfoCenter, it might behoove you to do so to see if you've missed anything (although this section is about 10 times too short!)
I agree that this install is a real bear and I hope IBM takes steps to improve it. Another thing I would check for is error messages in the Websphere admin console. I was seeing a bunch of servlet exceptions in there when I would try to start the portal server. This seemed to correlate to the inability of the URL to work.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com