This is a discussion on IHS not redirecting http traffic to WAS within the AIX Operating System forums, part of the Unix Operating Systems category; --> >>I've installed IHSv2.x.x.x on one machine and WASv5.1 on another >>machine. I am expecting the IHS to redirect the ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| >>I've installed IHSv2.x.x.x on one machine and WASv5.1 on another >>machine. I am expecting the IHS to redirect the http traffic to the >>WAS machine when I am using the virtual url. However, the IHS is not >>doing the redirecting and it always stop at the HTTP Server Welcome >>page. I've already copied the plugin file from WAS to the IHS server. >>Also, I can launch the url directly from the WAS's browser. > > > > You say that you copied the plugin file, but did you also > copied/updated > the configuration file for IHS and the plugin configuration file? > Also, > which url are you trying? WAS Plugin will only redirect url that he > knows > You mentioned that I need to copied/updated the configuration file for > IHS and the plugin configuration file. Which file should I update. So > far What I did is to just copy the WAS's plugin file and placed it to > the IHS server. > > Rgds. Ok, first you need to install the plug in on the http server machine. It's not enough to just copy the file. With the cd run websphere setup and use custom. Just install the plugin (and the http server if needed) and finish the installation. If you applied any fixpak to the WAS server you must also install the same fixpak on the HTTP server machine. Then you need to update the plugin file on the console. After that you need to copy the pluging configuration file from the WAS machine to the HTTP Server machine. The file is in /usr/WebSphere/AppServer/config/cells/plugin-cfg.xml You then need to restart the HTTP Server or wait a few minutes for the configuration to take place. After that you a ready to go! Everytime your WAS configuration changes (new URI, Servlets, applications, etc) you need to copy the plugin configuration file. Hope this helps. Goodluck! -- BC Hi, Okay. Finally made it. In fact, I've already performed the above steps and the missing point here is that the virtual hosts is using another port number instead of port 80. So, now the virtual host is having 2 ports. Now the question here is do I need to use port 80 in between IHS and WAS? Can I just assign another port other than port 80? Thanks to advise. |
| ||||
| > -- > BC > > > Hi, > > Okay. Finally made it. In fact, I've already performed the above steps > and the missing point here is that the virtual hosts is using another > port number instead of port 80. So, now the virtual host is having 2 > ports. > Now the question here is do I need to use port 80 in between IHS and > WAS? > Can I just assign another port other than port 80? > > Thanks to advise. The port that WAS and IHS use for communication is diferent from the port used for connecting to the application. Normally WAS-IHS port is named transport port. It starts on 9080/9043. By default all aplications are configured for accepting all the ports (*), so, for changing this, you need to change your virtual host. -- BC |