| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| Hi, We are having a migration project from WAS 5.1 to WAS 6.1 and we plan to have a parallel run period before all web applications migrated to WAS 6.1 platform. However, due to the limitation of resources, we need to install all web servers into a single machine in production environment. We now have IIS 6.0 and IHS 2.0 on the same machine and IHS 2.0 is working as remote web server for WAS 5.1. Then we install an IHS 6.0 on the same machine with different IP address. Both IHS 2.0 and 6.0 are configured to run as window services. However, it is easy that IHS 6.0 is unable to startup since IHS 2.0 starts up before the 6.0 and the IHS 2.0 binds all two ip addresses. I need to shutdown the IHS 2.0 and then start the IHS 6.0 first and then start the IHS 2.0 at the end. Does anyone know how to make IHS 2.0 binds to its own IP addresses? I already configure "LISTEN 10.49.100.211:80" in its http.conf and "LISTEN 10.49.100.219:80" in IHS 6.0 http.conf. I also encounter a strange problem that when both IHS servers started up and then I shutdown IHS 2.0, I try the link http://10.49.100.219 will direct to IHS 2.0 welcome page. Not sure why this happened? I really appreciate if you have any advice or solutions to share. Thanks for your attention first, Raymond |
|
#2
| |||
| |||
| Normally, if the httpd.conf have correct Listen directives each can be made to listen to its own IP. It's so basic functionality that there must be something stupid involved here... A dirty workaround could be to make one IHS service depend on the other so it won't start too rapidly... |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.