You may have experienced that you cannot access your WAS installation anymore for whatever reason. If you are sure that you haven’t changed the credentials or something like that, there’s still a way to fix it.
I tried to inspect the services.msc on Windows. You can see there the WebSphere Application Server service. If its startup type is Automatic, change it to Manual. Then restart the machine. Start the deployment manager or server (depends on your environment) manually. Based on my experience, this should be okay now. If WAS is inaccessible again, change the startup type to Automatic and then restart the machine.
If you still cannot login, there must be some problem with your WAS configuration.
If anyone know the exact solution, please comment! 😀
I always want to use the command-line interface and not clicking the batch files to stop and start everything. Actually there’s a simpler way. If there’s a sequence of series of commands to execute, you can type them first in a text editor and provide a carriage return for each command. Then paste it in the command-line interface. Automated.
You may want to use the Download Director rather than FTP. Not only it checks whether the fix you downloaded is OK (meaning, it’s not a bad/broken file), but it also downloads fast! Neat.
Maybe you have encountered searching for a fix at Fix Central but a webpage with a disappointing message appears that says “An error occurred.” Well, it may be true, or not! Click again the link of that fix for several times. Maybe it will be available again!
This message “You are no longer logged in. Click OK to discard your current work and go to the log in screen. Press Cancel to stay on this page so you can copy your current work and preserve any input you have entered.” is immediately showing up after logging in IBM Connections 4.0! This just happened when I configured the social discovery XML…
Well, we have already fixed it! It looks like that we had a misconfiguration in our LDAP (Domino) regarding SSO. We have done the instructions all over again and everything went fine. Too bad we have forgotten what was the exact misconfiguration… But I am sure it was on the side of Domino. We fixed it last December and I left my blog unattended due to busy schedule… 😐
The IBM Connections 4.0 documentation says that the required fix pack for WebSphere Application Server 7.0 is fix pack 21 together with 5 interim fixes. However, I did not find the interim fixes (I became lazy in reading the labyrinth webpage). What I did was I proceeded with the installation of IBM Connections 4.0 later on.
There was a problem, however. During the validation of the first step of installation, it said that WebSphereOauthsp.ear is missing. Hmmm… A very vague error that misled me! Well, that was the consequence of not finding the interim fixes…
I did not stop thinking and come up with the installation of the latest fix pack for the AppServer, which is fix pack 25. Hooray! The error was gone!
But there’s more! When I successfully installed IBM Connections 4, there was a problem with logging out. When I logged out from some components (Activities, Profiles, etc.), it says “Access Denied”. What the…??
I thought that there might be a problem with the fix pack installed with the IHS and its Plugin. I did some reinstallation of fixes and after long time of working I came up with installing the fix pack 21 for the AppServer, again. And…. hooray!!!
And that’s the end of the story. I just wish that there won’t be any problems in the future with what I did…
Well, there are! In the end I just followed the documentation properly and did not deviate from the procedures.