Well, if you a regular reader of our blog, you’ll know that I started my WebSphere Portal installation (see Installing WebSphere Portal 8) but forgot to check the system requirements. So I stopped when Installation Manager told be that Windows Server 2003 was not supported. Well I got a couple of comments that basically said, come on you baby, just go ahead and install it on Windows Server 2003 Server, it’ll probably work.
So I restarted the install. Never mind that I didn’t have enough memory (RAM, not mine). I accepted the defaults and entered an ID and password for my portal/websphere administrator. The fixpacks started to download and as I mentioned before, our network seemed slow, so I closed out my remote connection and decided to check back at a later time to see if the install worked.
Ok, the install finished. Installation manager wanted to know if I wanted to install a profile or run portal. Since I had not read the documentation too thoroughly, I assumed that a WebSphere profile was created, so I chose to just start Portal. It seemed that Portal was already started, so I simply opened the browser and navigated to the correct portal page: http://____:10039/wps/portal. In the screen shot you can see the initial portal screen loaded.
I checked the logs and didn’t see any major issues there. Overall, the installation went very smoothly. Except for the initial worries about disk space, operating system and memory requirements, I went through the rest of the process without a hitch.
So I’m going to start playing with Portal 8 and see how it goes.