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,
If you’re asking what I think you’re asking, we do exactly that. Our main website is hosted in one location and our ticketing site is hosted by Tessitura (TNEW). I also have a few resident companies who do the same thing, only they use POP ExpressTix for their ticketing sites and they are hosted by us (ATTPAC) on our web server.
We’ve always been set up this way and haven’t really had any issues other than having to rely on POP and wait on them to fix issues that might happen with the ticketing sites for my resident companies. There haven’t been very many issues over the 4 years we’ve been operating though as long an there aren’t any changes requested. The TNEW team is very quick to resolve any issues that I have on my ticketing site.
The one con that I have is that since I don’t have a web developer, I have to rely on outside sources to write code for me for any additional functionality I need on my ticketing websites. With Tessitura (TNEW), it’s not an issue….they are really quick to help me. For my resident companies, it’s different. They have to go through the process of a SOW and long process of designing what they want. It usually takes several months to get anything major and the cost is prohibitive for them usually, that they can’t make any changes and are limited with the functionality. If we had a web developer on staff, I think the situation would be much different.
Teresa
From: Tessitura Web Forum [mailto:forums-tessitura-web@tessituranetwork.com] On Behalf Of Gary TaylorSent: Monday, December 13, 2010 8:47 AMTo: Teresa DeanSubject: [Tessitura Web Forum] Split Web site?
You were sent this email automatically because you subscribed to the Tessitura Web forum. You may reply to this message to post to the Web forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
We are also using TNEW while hosting the non-ecommerce pages (built on the WordPress platform) with another hosting provider.
I echo all of Teresa's comments. I'd add to that one advantage of doing it this way is that the security aspect also gets separated, which I see as a huge benefit. The TNEW team takes care of it for the transactional portion of the site which is one more thing that is taken off my plate.
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
Hi Gary,
As a consortium, each of our member organizations maintains their own non-commerce sites. We handle all of the commerce in a central site, but brand it to maintain the look & feel of the organization.
It allows them to maintain their own sites for things like content updates, promotions, marketing, etc, but centralizes the commerce portions.
Here's a quick example:
Non-commerce:http://www.pbt.org/
Commerce:http://pbt.culturaldistrict.org/production/22531/the-nutcracker#tab=buy_tickets&performance=26410
There aren't many drawbacks. There's a slight design sacrifice, but we try to keep the brand identity on the commerce path and it's really pretty close. We also don't have any metrics tagging on the organization sites, so our analytics might not tell the full story. Let me know if you have any questions.
Thanks,
Patrick
Patrick FitzGerald Technical Project Analyst The Pittsburgh Cultural Trust 803 Liberty Avenue Pittsburgh, PA 15222 fitzgerald@pgharts.org w 412-325-7061 c 646-434-8955
Thanks Teresa and everyone who replied! All very helpful info. I may be in touch with some of you offline down the road a bit for some more in-depth info and conversation.
Appreciate it.
Gary