Hello all -
We have recently had some confusion regarding architecture optimization in Tessitura. I apologize if I have missed a previous question or note in updated documentation.For items here I refer to the SOAP set up Guide ( Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
http://www.tessituranetwork.com/~/media/Documentation/Web%20API/SOAP_API_Deployment_Guide_V12.ashx )
We had set up a REST service in T_DEFAULTS (for Tessitura Web) as Rest_Service_URI. For SOAP APIs we were balanced over two servers. Within the Web.Config of the SOAP service, we also set the values for TESSITURA_SERVICE_URI. Each SOAP service was attached to a complementary REST service. IN total that makes 3 REST services deployed.
What was a surprise to us was that no matter what the TESSITURA_SERVICE_URI is set to, the respective SOAP service interacts with the service in T_DEFAULTS, presumably deriving this from the T_DEFAULTS table.
While I am sure the REST service is efficient and capable of high load, we had presumed to share load and provide redundancy by altering the TESSITURA_SERVICE_URI . What, then, is the purpose of the TESSITURA_SERVICE_URI? HAve other organizations attempted similarly. (Of course, the same result could be achived via DNS putting the balanced URL in T_DEFAULTS, but we were confused to find doing the other way did not behave as expected.) Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4
Andrew Mulroney Senior Web Developer, Shared IT Services Ticket Philadelphia, The Philadelphia Orchestra Association & The Kimmel Center for the Performing Arts 260 South Broad Street, 16th Floor Philadelphia, PA 19102 T. 215.875.7660 F. 215.875.7624 amulroney@philorch.org