Thanks for that insight.
We "might not" face that particular bottleneck as the requirement here is a very temp solution while on-boarding users to a newer version of the Remedy systems. Instead of a BB approach, we have decided to run 7.6.04 parallel to 8.1.2 and onboard smaller groups first with fewer users followed by larger groups. So the tickets would be raised by a group either on 7.6.04 or 8.1.2, depending on where they are supposed to be. And if the ticket has to be transferred to a group that is on the other version, that's where there is that data transfer. Else it stays on the system it was raised in. We are attempting to solution that problem, and given our processing power (# of AR Servers, mid tiers, size of machines, etc.), I think we may not have problem with the system unable to process data transferred through WSDL efficiently. But a good thought and I'll keep that in mind in case we need to design searches to extract data. For the moment, I would think we may require a search only if we want to look up the corresponding ticket on the other system - especially work log from the other system prior to the ticket being transferred. Joe _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Terry Bootsma Sent: Monday, August 17, 2015 8:14 PM To: [email protected] Subject: Re: Communicating between ARS Servers 7.6.04 and 8.1.2 using WSDL... Just a note Joe. Depending upon the amount of data and the frequency of the synchronization, you may want to consider another technology other than web services. I was doing some load testing earlier this year and found that the mid-tier didn't scale very well when extracting large amounts of data via a programattic interface. This makes sense since all the parsing of XML/SOAP that the midtier has to do when converting/unconverting the data. Note, that this was not a Remedy ARSystem bottleneck, but the midtier. I worked with BMC support on this and it is something that they hope to fix in Remedy 9. :-) Terry _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Grooms, Frederick W Sent: August-17-15 3:48 PM To: [email protected] Subject: Re: Communicating between ARS Servers 7.6.04 and 8.1.2 using WSDL... ** It had to do with the change in the 7.1 patch where the namespace structure changed. I think prior to the 7.1 patch there was no namespace and after the patch there was. Fred From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe D'Souza Sent: Monday, August 17, 2015 2:04 PM To: [email protected] Subject: Re: Communicating between ARS Servers 7.6.04 and 8.1.2 using WSDL... ** Sally, Thanks for your reply. From what I recollect (very vaguely) it wasn't as much to do with code change inside the AR layer as much it had to do with the structure of the WSDL's itself having changed with some new constructs added, that were not understood by the other system. I wish I had more details to share about that problem. But I do remember BMC Support calling it as a known limitation between those two versions saying that the WSDL would need to be manually tweaked for it to work. Joe _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Ludwig, Sally Sent: Monday, August 17, 2015 2:45 PM To: [email protected] Subject: Re: Communicating between ARS Servers 7.6.04 and 8.1.2 using WSDL... Hi Joe, There was a significant code change for web services between 6.3 and 7.6.04 which would have generated the problems you encountered. To be specific, it was at the 7.0.1 patch 004 level. At that point, all components ( Dev Studio, Midtier and AR server) needed to be at 7.0.1 patch 004 or better). There has not been any major changes between 7.6.04 and 8.1.02, so they should work in either direction. Best regards Sally Ludwig From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe D'Souza Sent: Monday, August 17, 2015 1:40 PM To: [email protected] Subject: Communicating between ARS Servers 7.6.04 and 8.1.2 using WSDL... Importance: High ** On paper - the easy answer is "this should work". However a few years ago (maybe 3 years ago) I was attempting to prototype communication between a 7.6.04 system and a 6.3 system, something failed, of which I do not recall details. It had something to do with one system not recognizing certain constructs in the WSDL in the other system. I am inclined to think it was the 6.3 system that could not understand the 7.6.04 WSDL completely. Hence the intent behind this post - has anyone attempted a unidirectional or a bi directional sync of data between a 7.6.04 system and a 8.1.2 system? I might have to use search options too apart from create and modify options. Has anyone done this? Did you'll use the WSDL that was generated OTB by the Developer Studio? Or did you'll need to modify it in order for it to work? Joe _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
