I have been working on segmenting our internal and external SOAP/REST traffic using two servers . The internal server will handle all internal-originating calls (Impresario Client, customizations that access REST/SOAP, etc). The external server will handle all web-originating calls (and live in a DMZ). I have completed with the setup; however, ran into a snag.
In t_defaults there is an entry for REST_SERVICE_URI, which is used by the SOAP API when SOAP needs to access REST (when this occurs exactly, I am not sure). My issue is that I really need two REST_SERVICE_URI entries, one to be used by internal REST and one by external.
Via support, Tessitura told me that "a second instance of the SOAP API is not necessary to run the Tessitura application" and what I am trying to do "falls outside the scope of support" and so must seek assistance here.........
Yet I'm positive others are running w/ segmented traffic similar to this. So, anyone know of a way around the t_defaults entry? Could multiple entries be used? Any help is appreciated.
Sounds good. Thanks!
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Matt Belanger Sent: Friday, March 06, 2015 2:00 PM To: Jason Kaiser Subject: Re: [Tessitura Technical Forum] Segmenting internal/external REST/SOAP traffic
The infrastructure you are suggesting is not unheard of; there are other organizations that have multiple SOAP APIs and thus must also be stuck with only one REST service, which I have never heard of as an issue in terms of performance, likely because of the limited interaction between them. If you find this not to be the case in your testing, we definitely want to hear about it!
Thanks again.
From: Jason Kaiser <bounce-jasonkaiser4021@tessituranetwork.com> Sent: 3/6/2015 2:34:55 PM
This is exactly the info I was after. Thank you for the response and I am glad to see it will be making its way into a future patch!
Since 95% of our SOAP calls are from external website traffic, I'm pretty comfortable with a single REST service servicing both internal and external SOAP services for now.
Only other thing I'm interested in is whether sharing REST like this could cause any problems for either of the SOAP instance? (Assume we have plenty of server resources.)
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!