In our experience with 7.0 and 7.1, the web services were not good at or 
capable of returning a large number of records.  We found that we had to limit 
things to around 100 records max or performance just tanked, and it put a very 
heavy burden on the web server.  As a result of that, we pretty much just 
limited our use to single record updates and queries.  The last time we looked 
at that was a year to a year and a half ago, so I don't know if that was ever 
fixed in 7.0/7.1 implementation.

It looks like they may have picked up a new architecture in 7.5, but I haven't 
tried testing it yet.

Lyle

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of LJ Longwing
Sent: Friday, May 08, 2009 8:38 AM
To: [email protected]
Subject: Re: Webservices

**
Does it count if I don't like how the target URI isn't data 
referenceable?....by this I mean that when I consume an external web service, I 
need to point my Dev, Test, and Prod to different URIs.  This means that I 
either can't have the same workflow in all environments, or I need to develop a 
complicated data driven structure (which is what we have done here) that 
determines which filter to fire based on what environment we are in, and have 
as many copies of the filter with the same workflow, but different URIs as I 
have environments.  This is the biggest hurdle I have had to face in regard to 
Remedy's implementation of web services.

________________________________
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Axton
Sent: Friday, May 08, 2009 8:27 AM
To: [email protected]
Subject: Webservices
** I wanted to get a feel from the group on some of the headaches and 
limitations of the Remedy web services implementation.  I've avoided the 
interface, much like the palgue, since it was first adopted.  I'm looking for 
limitations when people interface bi-directionally with other applications, 
performing operations like creating incidents, in relation to things like not 
being able to support certain data types, not being able to query certain 
outside webservices due to how they are structured, etc.

Axton Grams

The opinions, statements, and/or suggested courses of action expressed in this 
E-mail do not necessarily reflect those of BMC Software, Inc.  My voluntary 
participation in this forum is not intended to convey a role as a spokesperson, 
liaison or public relations representative for BMC Software, Inc. _Platinum 
Sponsor: [email protected] ARSlist: "Where the Answers Are"_
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_


 NOTICE: This email message is for the sole use of the intended recipient(s) 
and may contain confidential and privileged information. Any unauthorized 
review, use, disclosure or distribution is prohibited. If you are not the 
intended recipient, please contact the sender by reply email and destroy all 
copies of the original message.



_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to