I have used a stand alone WAS 6.0 server with a IBM HTTP 6.0 web server . And I have also installed the plugin . So on my WAS administrative consloe , I can see the webserver , but i CANT START OR STOP IT AS i HAVE NOT USED THE DEPLOYMENT manager, so problem.
But My problem is , Even if my Web Server is Stopped that HHTP server is stopped I can still access the application from the browser. It looks like the request to my WAS is not through HTTP SERVER .Though in the plugin-cfg.xml has the name of my application that has been deployed on WAS .
Any thing that I have missed . Can any one help .
Joined: May 25, 2006
I did a bit of research and came to know that WebSphere Application Server has an internal HTTP transport that accepts HTTP requests, So if we do not configure the HTTP SERVER seperatly it will still work.
Now as Im trying out new new things , i have a new problem can not I just use this standalone server without HTTP Webserver and Websphere Plugin.
And make use of SSL (self cert) for WAS alone, trying to configure only the inbuilt HTTP transport to handle SSL based requests .... Any ideas anyone ...
Well I haven't worked with WAS 6.0 yet, but it should be pretty much the same for WAS 5.1.
Each Application Server confiured in WAS (aka each Java process) has it's own embedded HTTP server. This allows you to POST HTTP requests to the Java process directly, bypassing the need for a Web Server. This is usefull for development and possibly troubleshooting.
HOwever, in production you would want to utilize an external WebServer where you can host your static content and relay HTTP requests to your Application Server. This has advantages such as keeping static content on your Web Server and not your App Server, it also allows you to place your App Server behind a secure firewall while placing you Web Server in a DMZ, and finally it is the only way (I know of) to implement load-balancing when configuring a cluster. The plugin simply tells the Web Server how the App Server is configured and mainly takes care of making sure the requests are forwaded to the correct ports, as well as handeling load balancing in a cluster.
That's the basic gist and there is more that can be said, but I hope that helps a little. You should see the WAS info center for more detail, or maybe someone here could explain further.
Java has 99 problems but a pointer ain't one
Joined: Mar 13, 2005
And yes you can configure just your App Server's HTTP Transport for SSL requests, and make direct HTTPS posts to that port. To use the IBM HTTP server you would then have to configure it to trust your App Server.