At one of my customers I was busy with the upgrade their virtual development environment.
Currently we run Websphere Application Sever 8 inside Rational Application Developer on a not so fat virtual development environment. Which cause lots of waiting for the developer to deploy changes of the portal to the local WAS server.
We tried JRebel, but in combination with RAD I can say it is not happy couple. It caused have memory use and after a certain period a not response environment ;-(
New environment and a problem
So we decided to move for the development environment to the latest Eclipse version with Websphere Liberty Profile.
Benefit of Eclipse is a more lean IDE, where we can install SonarLint and Findbugs plugins. WLP for local development is also much more easier to install and much faster.
After I ran the migration tooling in Eclipse I had my server.xml, so that was easy 😉
To run the EAR files of our portals should be untouched, because on production we still use WAS.
The portals run also on JSF 1.2, so we load the JSF and the properties via commonLibrary on the class path.
Voila, one of the portals was running on WLP, which is using Basic Authentication, but……. the others using an external authentication mechanisme. After successful authentication the user is redirected back to the portal.
This redirect caused a connection refused error ;-(
On the website of IBM I found the solution.
By adding host=”*” to the httpEndpoint tag, which tells WLP to accept all incoming requests.
The final httpEndpoint looks like this
<httpEndpoint id="defaultHttpEndpoint" host="*" httpPort="8081" httpsPort="443" />