Hi.
Was wondering if anyone out there currently hosts the non-ticketing, i.e. static, portions of their Web site with one host and the Tessitura ticketing pages of their site with another host...and if that's even possible or recommended? If so, I'd be interested to hear the pros and cons of doing so or any other comments.
Thanks!Gary
Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
Gary TaylorDir. of Marketing & Audience DevelopmentStrand-Capitol Performing Arts Center717-846-1155 x 132www.strandcapitol.org
Gary,
Our non-ecommerce site is hosting offsite by a third party while our Gateway/API site is hosted locally at our organization.
The main benefits of the split-site environment for us are regarding security, compliance, and reliability. Personally, I like the fact that I only have to administer one site. This allows me to provide additional focus on the reliability and security of our e-commerce site. Another benefit can be associated with your entire site never being down. Our third party hosting provider can direct patrons to our e-commerce site if they’re experiencing issues and I can have them place a splash page on the site in the event that the API has an issue (which never happens of course ) directing patrons to call the box office.
My main disadvantage with this environment is hunting down possible issues, such as timeouts and SOAP exceptions. It drives me crazy at times trying to hunt down who is responsible for what in the communication chain. We’re a part of a university, which adds a lot more players and devices to the chain, so it makes it that much more difficult for us. I suggest having a clear understanding of who hosts what and who’s responsible for what areas of both sites.
David
KC Rep