Hi Kalpesh; The way IIS connects to Tomcat is using the ISAPI filter. If you install windows distro of Tomcat/LiveServer on the machine w/ teh web server, it will automatically be added in. If your web server is a separate machine (which it should be in a production config), you can just copy the isapi_redirector.dll from that machine into your web server. This link provides instructions on how to configure an IIS web server: http://tomcat.apache.org/connectors-doc-archive/jk2/jk/iishowto.html.
However, if you want multiple websites on a single IIS machine or cluster, you would have to use something like Helicon: http://www.isapirewrite.com/ to inspect the domain of the request and point it to the correct project in LiveServer. It allows you to create rules that include filtering by domain. An example of one of these rules is: <VirtualHost www.project1.com> RewriteEngine on #Rules for: /en-us/page.htm RewriteRule ^/([a-zA-Z]{2}\-[a-zA-Z]{2})/(.*) /xchg/PROJECT1/ls/xsl/ hs.xsl/-/ls/dynaments/locate-url-request.xml?page=$2&locale=$1 [PT,L] #Rules for: /businessUnit/page.htm RewriteRule ^/(.*)/(.*) /xchg/PROJECT1/ls/xsl/hs.xsl/-/ls/dynaments/ redirect-to-page.xml?page=$1/$2 [PT,L] #Rules for: /page.htm OR / RewriteRule ^/(.*) /xchg/PROJECT1/ls/xsl/hs.xsl/-/ls/dynaments/ redirect-to-page.xml?page=$1 [PT,L] RewriteRule ^/ /xchg/PROJECT1/ls/xsl/hs.xsl/-/ls/dynaments/redirect-to- page.xml?page=home.html [PT,L] </VirtualHost> <VirtualHost www.project2.com> RewriteEngine on #Rules for: /en-us/page.htm RewriteRule ^/([a-zA-Z]{2}\-[a-zA-Z]{2})/(.*) /xchg/PROJECT2/ls/xsl/ hs.xsl/-/ls/dynaments/locate-url-request.xml?page=$2&locale=$1 [PT,L] #Rules for: /businessUnit/page.htm RewriteRule ^/(.*)/(.*) /xchg/PROJECT2/ls/xsl/hs.xsl/-/ls/dynaments/ redirect-to-page.xml?page=$1/$2 [PT,L] #Rules for: /page.htm OR / RewriteRule ^/(.*) /xchg/PROJECT2/ls/xsl/hs.xsl/-/ls/dynaments/ redirect-to-page.xml?page=$1 [PT,L] RewriteRule ^/ /xchg/PROJECT2/ls/xsl/hs.xsl/-/ls/dynaments/redirect-to- page.xml?page=home.html [PT,L] </VirtualHost> Also, here are some other tips on LiveServer performance tuning that we've been working on: http://www.oshyn.com/BlogRetrieve.aspx?BlogID=1906&PostID=66520&A=Trackback Good luck! Christian Oshyn - OpenText Web Content Management Experts - www.oshyn.com On May 22, 4:47 am, charliev <[email protected]> wrote: > Hi, > > Thanks for this information. We are looking to do something very > similar to what Prasanth seems to have done. What I am confused about > is how we configure IIS and the website underneath it. At the moment > we have a separate ip address for each site we host, and in IIS we > have a separate website setup with its own home directory etc... We > are going to deploy IIS, Tomcat and Delivery server in a new > environment to replace our current systems. > > How do we go about setting up IIS and the websites underneath it so > that each website has its own ip address. The sites will all be load > balanced behind a load balancer but we can figure that bit out, the > bit Im confused about is about how we link separate ip's for websites > in IIS to Delivery server. > > We can find nothing about how to do this anywhere on the internet. > Any guidance would be much appreciated or if you have any links to > where I can get some more info would be a great help. > > Many Thanks in Advance. > Regards > Kalpesh. > > On Apr 15, 7:15 pm, "Prasanth Nittala" <[email protected]> wrote: > > > > > Hi Chandrakanth, > > > The environment generally constitutes as below: > > > 1) CMS servers where content is managed > > 2) A clustered environment of Live Servers or single Live Server where CMS > > content is published, and other Dynaments are programmed for purpose of > > personalized content delivery. Content is published to this from cms server > > 3) Verity server on a isolated server to index the published content of Live > > Server. > > 4) 2 or more webservers behind the loadbalancer with rewrite rules to > > request the live server appropriately and having sessions handled > > appropriately. Assets are published to these servers from cms. > > 5) A load balancer sitting in front of the webservers to balance the load > > appropriately > > > Thanks, > > Prasanth. > > > --------------------------------------------- > > Prasanth Nittala > > Oshyn, Inc. -http://oshyn.com > > w 213.483.1770 ext 111 > > f 213.483.1934 > > Recently launched :http://neamb.com > > --------------------------------------------- > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On Behalf Of Chandrakanth > > > Ramireddy > > Sent: Tuesday, April 14, 2009 6:23 PM > > To: Prasanth Nittala > > Subject: [!! SPAM] [reddot] Load balancing in RedDot > > > Hi, > > > We are using RedDot CMS 7.5 and Liveserver 4.0. I wanted to know the > > various options of implementing a new load balancing server for the > > website. > > > Please share your experiences. > > > Regards, > > Chandrakanth- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
