Another idea is to turn on your ARplugin logs to Fine or Finest and you should then be able to see the payload in both directions
Fred From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of strauss Sent: Thursday, October 21, 2010 5:01 PM To: arslist@ARSLIST.ORG Subject: Re: Web Service Issue ** In my case it is usually on the custom, interface form that the roll backs occur - at the point of integration between the external app and the Remedy app (which is where you want them to appear, not in the ticketing form). I still get them today when my integration to LDAP gets a record pushed to it by AIE from SQL Server where there is a duplicate login name or corporate id that already exists; the transaction is refused in the application and rolled back in the ARSystem db in SQL; our peoplesoft app allows people to add records with duplicate (already exists) login names or corporate ids, which push to LDAP and then to me, where my app refuses them. If this is a bi-directional integration (each app tries to update the other) you may have to stage it so that each process on each side allows for (or checks for) completion on the other side before it can move on to the next step. In our old MySoft integration we actually were ftp'ing data back and forth and controlling the timing with SQL Server DTS packages to give each side a chance to do its work, since we were in fact passing record IDs in each direction to give us an external key into each system as it generated new or updated existing records. It was cumbersome and fragile. I can't give you any exact suggestions, just throwing out ideas; we are the last shop to tell anyone how to use web services. We have been trying to get the myriad web service functions in Alarmpoint to work with Remedy for months without success. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Nall, Roger Sent: Thursday, October 21, 2010 4:38 PM To: arslist@ARSLIST.ORG Subject: Re: Web Service Issue ** This is all on a custom application. Nothing OOB. Roger Nall Manager, SA Business Intelligence/Remedy Desk Phone: 972-464-3712 Mobile: 973-652-6723 Helpful Links: | Reports<http://bi.eng.t-mobile.com:8080/InfoViewApp> |SA_Suggestion Box<http://saintake.t-mobile.com/> | SA_Trouble Ticket<http://natweb.eng.t-mobile.com/sites/TTWeb/CreateTicket.aspx> | From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of strauss Sent: Thursday, October 21, 2010 4:24 PM To: arslist@ARSLIST.ORG Subject: Re: Web Service Issue ** Look for a rollback transaction in the SQL logs. It is often a problem when making a custom integration into one of the Remedy applications (saw this in my integration to MySoft telecomm system back on Help Desk 5.5), or trying to set up an AIE job correctly. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Nall, Roger Sent: Thursday, October 21, 2010 4:15 PM To: arslist@ARSLIST.ORG Subject: Web Service Issue ** ARS 7.1 Patch 4 Win2k SQL2k We have a situation where we create tickets in another system consuming a web service. The Output of the web service is the ticket number from the other system. Our process to create this ticket is as follows: * Make a change on Remedy ticket. * Push data from Remedy ticket to an intermediate form in Remedy. * Call web service from intermediate Remedy form. * Push ticket number from other system back to Remedy ticket. On a daily basis, we end up with duplicate tickets in the other system. In all cases, the only record in the intermediate Remedy form has a create date and ticket number from the second ticket in the other system. I have always suspected that on the first web service call, the other system returned an error whereby all changes were backed out of Remedy. On the second submission there was no error and thus all changes were committed. I have one user who is saying that he is not encountering an error when making the first web service call but at the same time he is not getting a ticket number back. Can someone tell me if a ticket number or an error is not returned what happens to the transaction on the Remedy side? Thanks Roger Nall Manager, SA Business Intelligence/Remedy Desk Phone: 972-464-3712 Mobile: 973-652-6723 Helpful Links: | Reports<http://bi.eng.t-mobile.com:8080/InfoViewApp> |SA_Suggestion Box<http://saintake.t-mobile.com/> | SA_Trouble Ticket<http://natweb.eng.t-mobile.com/sites/TTWeb/CreateTicket.aspx> | _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
