Re: XML DateTime vs Time - different TZ offset
Hi Fred, What OS is your AR Server? I've seen issues with HP-UX where webservices publish the incorrect offset for DT fields... Stephen On Tue, Mar 25, 2008 at 4:03 PM, Grooms, Frederick W [EMAIL PROTECTED] wrote: Has anybody seen this... When consuming a web service that has both an XML DateTime field and an XML Time field, when Remedy generates the data it puts a different time zone offset on each of them. Here is an example. A Remedy filter is consuming a web service that has 4 elements (String, Date, DateTime, and Time). I put the same date (and/or time) in each field (String is just for comparison purposes). Remedy creates the XML (as seen in the Plugin Log file of: ROOT xmlns=urn:Template xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; String03/25/2008 02:30:00 PM/String Date2008-03-25/Date DateTime2008-03-25T14:30:00-05:00/DateTime Time14:30:00-06:00/Time /ROOT As you can see by the XML the DateTime field has a time zone offset of -5 hours while the Time field has an offset of -6. Date is a Remedy Date field (not DateTime showing only the Date) and Time is a Remedy Time field (not DateTime showing only the time). This is using ARS 6.3.0 patch 20 on Sun Solaris 9 with Oracle. Fred ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: XML DateTime vs Time - different TZ offset
SUN Solaris 9 And since this is when consuming a service Mid-Tier does not apply. We are planning our 7.1.0 upgrade for late this summer so I am wondering if this problem still happens in 7.1.0. A quick and dirty test is to create a form. Put a Date field, a DateTime field, and a Time field on it. Create a webservice on that form. Create a filter on the form that consumes the service sending Date to Date, DateTime to DateTime, Time to Time, and Assigned To to Short Description (so you don't end up in an endless loop). With the plugin log level set to 400 you can see the XML in the arplugin log file on the server. Fred From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Earl Sent: Wednesday, March 26, 2008 8:10 AM To: arslist@ARSLIST.ORG Subject: Re: XML DateTime vs Time - different TZ offset Hi Fred, What OS is your AR Server? I've seen issues with HP-UX where webservices publish the incorrect offset for DT fields... Stephen On Tue, Mar 25, 2008 at 4:03 PM, Grooms, Frederick W [EMAIL PROTECTED] wrote: Has anybody seen this... When consuming a web service that has both an XML DateTime field and an XML Time field, when Remedy generates the data it puts a different time zone offset on each of them. Here is an example. A Remedy filter is consuming a web service that has 4 elements (String, Date, DateTime, and Time). I put the same date (and/or time) in each field (String is just for comparison purposes). Remedy creates the XML (as seen in the Plugin Log file of: ROOT xmlns=urn:Template xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; String03/25/2008 02:30:00 PM/String Date2008-03-25/Date DateTime2008-03-25T14:30:00-05:00/DateTime Time14:30:00-06:00/Time /ROOT As you can see by the XML the DateTime field has a time zone offset of -5 hours while the Time field has an offset of -6. Date is a Remedy Date field (not DateTime showing only the Date) and Time is a Remedy Time field (not DateTime showing only the time). This is using ARS 6.3.0 patch 20 on Sun Solaris 9 with Oracle. Fred ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
Re: XML DateTime vs Time - different TZ offset
Hmmm I've only seen this on HP-UX myself I would contact support as I did to get a workaround or fix. on HP-UX we had to reconfigure the OS Kernel itself to the correct timezone but I don't believe Solaris has this restriction... Stephen On Wed, Mar 26, 2008 at 9:34 AM, Grooms, Frederick W [EMAIL PROTECTED] wrote: ** SUN Solaris 9 And since this is when consuming a service Mid-Tier does not apply. We are planning our 7.1.0 upgrade for late this summer so I am wondering if this problem still happens in 7.1.0. A quick and dirty test is to create a form. Put a Date field, a DateTime field, and a Time field on it. Create a webservice on that form. Create a filter on the form that consumes the service sending Date to Date, DateTime to DateTime, Time to Time, and Assigned To to Short Description (so you don't end up in an endless loop). With the plugin log level set to 400 you can see the XML in the arplugin log file on the server. Fred -- *From:* Action Request System discussion list(ARSList) [mailto: [EMAIL PROTECTED] *On Behalf Of *Stephen Earl *Sent:* Wednesday, March 26, 2008 8:10 AM *To:* arslist@ARSLIST.ORG *Subject:* Re: XML DateTime vs Time - different TZ offset Hi Fred, What OS is your AR Server? I've seen issues with HP-UX where webservices publish the incorrect offset for DT fields... Stephen On Tue, Mar 25, 2008 at 4:03 PM, Grooms, Frederick W [EMAIL PROTECTED] wrote: Has anybody seen this... When consuming a web service that has both an XML DateTime field and an XML Time field, when Remedy generates the data it puts a different time zone offset on each of them. Here is an example. A Remedy filter is consuming a web service that has 4 elements (String, Date, DateTime, and Time). I put the same date (and/or time) in each field (String is just for comparison purposes). Remedy creates the XML (as seen in the Plugin Log file of: ROOT xmlns=urn:Template xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; String03/25/2008 02:30:00 PM/String Date2008-03-25/Date DateTime2008-03-25T14:30:00-05:00/DateTime Time14:30:00-06:00/Time /ROOT As you can see by the XML the DateTime field has a time zone offset of -5 hours while the Time field has an offset of -6. Date is a Remedy Date field (not DateTime showing only the Date) and Time is a Remedy Time field (not DateTime showing only the time). This is using ARS 6.3.0 patch 20 on Sun Solaris 9 with Oracle. Fred __Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
XML DateTime vs Time - different TZ offset
Has anybody seen this... When consuming a web service that has both an XML DateTime field and an XML Time field, when Remedy generates the data it puts a different time zone offset on each of them. Here is an example. A Remedy filter is consuming a web service that has 4 elements (String, Date, DateTime, and Time). I put the same date (and/or time) in each field (String is just for comparison purposes). Remedy creates the XML (as seen in the Plugin Log file of: ROOT xmlns=urn:Template xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; String03/25/2008 02:30:00 PM/String Date2008-03-25/Date DateTime2008-03-25T14:30:00-05:00/DateTime Time14:30:00-06:00/Time /ROOT As you can see by the XML the DateTime field has a time zone offset of -5 hours while the Time field has an offset of -6. Date is a Remedy Date field (not DateTime showing only the Date) and Time is a Remedy Time field (not DateTime showing only the time). This is using ARS 6.3.0 patch 20 on Sun Solaris 9 with Oracle. Fred ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
