• Replies 3 replies
  • Subscribers 357 subscribers
  • Views 18 views
  • Users 0 members are here
Related

Single web site with virtual directories for application server in v11

David Frederick
$organization

Hi everyone,

I have a v11 technical question related to the application (gateway) server... The server configuration v11 training emphasized creating separate web sites for each API, thus requiring multiple IP addresses and SSL certificates. In our current gateway server, we use a single web site with each API instance running as a virtual directory within that site. So, we have urls like:

  • https://api.domain.org/live_1/tessitura.asmx
  • https://api.domain.org/live_2/tessitura.asmx
  • etc

This allows us to use a single IP address and single SSL certificate, which simplifies administration. We can specify separate application pools per virtual directory, so I see nothing in IIS that would technically prohibit this. 

Is there any reason why we should not continue this approach? Can we run both REST and SOAP APIs in one web site, as long as each virtual directory is configured with the appropriate application pool? Are there any downsides to taking that approach that perhaps I'm not considering?

Thanks!
David 

  • $organization

    We were considering that but then decided against it because of future server changes.  We will be moving the SOAP API server onto a server in our DMZ and keeping the REST API on a seperate server within our internal network.  This works for us because for the foreseeable future we won't be using REST for our website.

  • Former Member
    Former Member $organization

    There is no technical reason you cannot run everything under a single website, either directly or using virtual directories.  The only thing you need to allow for is that if that site has an SSL certificate that is linked to an external address, in many cases by default that certificate may not be resolvable on your internal network.  (Remember that in V11 the internal client also uses the services.)  This is pretty easily resolved by adding some DNS entries within your domain such that the certificate name is resolved to an internal address when referenced from inside your domain.  So long as the certificate name can be used internally, all else should be fine.

     

    Ron

     

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Simon Davidson
    Sent: Friday, January 13, 2012 4:08 AM
    To: Ron Wilson
    Subject: Re: [Tessitura Next Generation Forum] Single web site with virtual directories for application server in v11

     

    We were considering that but then decided against it because of future server changes.  We will be moving the SOAP API server onto a server in our DMZ and keeping the REST API on a seperate server within our internal network.  This works for us because for the foreseeable future we won't be using REST for our website.

    From: David Frederick <bounce-davidfrederick9045@tessituranetwork.com>
    Sent: 1/12/2012 7:34:45 PM

    Hi everyone,

    I have a v11 technical question related to the application (gateway) server... The server configuration v11 training emphasized creating separate web sites for each API, thus requiring multiple IP addresses and SSL certificates. In our current gateway server, we use a single web site with each API instance running as a virtual directory within that site. So, we have urls like:

    This allows us to use a single IP address and single SSL certificate, which simplifies administration. We can specify separate application pools per virtual directory, so I see nothing in IIS that would technically prohibit this. 

    Is there any reason why we should not continue this approach? Can we run both REST and SOAP APIs in one web site, as long as each virtual directory is configured with the appropriate application pool? Are there any downsides to taking that approach that perhaps I'm not considering?

    Thanks!
    David 




    You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!