Payment gateway home

Jason,

In our environment we segregate our servers by function.  Database servers are only database servers and other applications are not installed upon them.  We then have application servers dedicated to applications.  There are several factors that go into why we isolate functions.  1., We can tune a server for its primary function for maximum performance. 2., We can assign priority of particular applications and separate Tier I, Tier II, and Tier III applications based on availability requirements, uptime commitments, etc.  3., If function is balanced properly and you  have to reboot a server for some reason, it will not impact your other applications. Some servers end up performing a single function or serving a single application to meet both performance and uptime objectives.

As for Tessitura; we maintain a dedicated SQL server and a dedicated application server.  The application server hosts all of the related applications for Tessitura, API gateway, Element Gateway, Seat Server, NScan Server, Prints  Server.  This configuration has worked well in our environment without any latency issues.  Both servers run as virtual machines in VMWare.

Hope this helps,

David Lane

Dallas Symphony

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Jason Kaiser
Sent: Monday, February 09, 2015 2:33 PM
To: David E. Lane
Subject: [Tessitura Technical Forum] Payment gateway home

We're in the process of moving our Tessy environment to new servers (Windows 2012 r2 paired with SQL Server 2014). In our existing environment the payment gateway service lives on its own server.  Having since moved away from Transcend, we no longer require this particular server...so we're hoping to consolidate.   In our environment this basically means either our REST/SOAP gateway server (or) tessitura db server.

I have asked Tessitura in the past if either location is more ideal and was told that either is fine so long as you have the resources.  Though we do have ample scalable resources (virtual servers) and I like the idea of housing the pmt gateway on our rest/soap server overall, high on sale situations have potential to really slam the API...which leads me to believe that the database server may be a better location overall.

I plan on doing stress testing once all systems are configured, but am hoping to make a good informed decision before getting to that point.

All that said, I'm curious what ya'll's setup is like (and why)?

Thanks!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!

Jason,

In our environment we segregate our servers by function.  Database servers are only database servers and other applications are not installed upon them.  We then have application servers dedicated to applications.  There are several factors that go into why we isolate functions.  1., We can tune a server for its primary function for maximum performance. 2., We can assign priority of particular applications and separate Tier I, Tier II, and Tier III applications based on availability requirements, uptime commitments, etc.  3., If function is balanced properly and you  have to reboot a server for some reason, it will not impact your other applications. Some servers end up performing a single function or serving a single application to meet both performance and uptime objectives.

As for Tessitura; we maintain a dedicated SQL server and a dedicated application server.  The application server hosts all of the related applications for Tessitura, API gateway, Element Gateway, Seat Server, NScan Server, Prints  Server.  This configuration has worked well in our environment without any latency issues.  Both servers run as virtual machines in VMWare.

Hope this helps,

David Lane

Dallas Symphony

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Jason Kaiser
Sent: Monday, February 09, 2015 2:33 PM
To: David E. Lane
Subject: [Tessitura Technical Forum] Payment gateway home

We're in the process of moving our Tessy environment to new servers (Windows 2012 r2 paired with SQL Server 2014). In our existing environment the payment gateway service lives on its own server.  Having since moved away from Transcend, we no longer require this particular server...so we're hoping to consolidate.   In our environment this basically means either our REST/SOAP gateway server (or) tessitura db server.

I have asked Tessitura in the past if either location is more ideal and was told that either is fine so long as you have the resources.  Though we do have ample scalable resources (virtual servers) and I like the idea of housing the pmt gateway on our rest/soap server overall, high on sale situations have potential to really slam the API...which leads me to believe that the database server may be a better location overall.

I plan on doing stress testing once all systems are configured, but am hoping to make a good informed decision before getting to that point.

All that said, I'm curious what ya'll's setup is like (and why)?

Thanks!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!