Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- DevNet
- DevNet Collaboration
- Collaboration Knowledge Base
- XML API - Unable to schedule training session
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
252
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-24-2014 05:57 PM
This document was generated from CDN thread
Created by: Sreejith Pm on 17-10-2013 07:30:52 AM
Hi,
As a part of webex integration to my application, I'm trying to schedule training session using XML API in webex sandbox environment.
It always return a error like 'validation: unable to validate timeZone to '<schedule>''...
Response I got is given below
Thanks in advance.
Subject: RE: XML API - Unable to schedule training session
Replied by: Nathan Morrow on 17-10-2013 12:44:08 PM
Hello, <timeZone> is a child of <schedule> but there could be another reason this is failing schema check. Note that timeZone value is a literal string that must exactly match the defined value for the time zone (ex: <timeZone>GMT-08:00, Pacific (San Jose)</timeZone>). timeZoneID is preferred, time zone ID is an enumerated index. Alternately, not specifying a time zone will cause the scheudling request to use the site default time zone.
Subject: RE: XML API - Unable to schedule training session
Replied by: Sreejith Pm on 18-10-2013 12:05:09 AM
Hi Nathan,
Thanks for your response.
Can you please find and check the XML structure which I have created to schedule Training Session with Webex?
Thanks in advance...
Subject: RE: XML API - Unable to schedule training session
Replied by: Nathan Morrow on 18-10-2013 12:01:19 PM
Hello,
securitycontext should be securityContext. webexid should be webExID. siteid should be siteID. partnerid should be partnerID. bodycontent should be bodyContent, and should be a child of body. etc.
XML API attributes are case sensitive and should match the defined schema. Please refer to the XML API reference guide for correct case for each of these attributes, as most are incorrect in your listing.
As for your time zone, the literal string, as defined in the XML API reference guide, should be "GMT+05:30, India (Bombay)", again this must match exactly.
Subject: RE: XML API - Unable to schedule training session
Replied by: Sreejith Pm on 18-10-2013 08:38:10 PM
Hi Nathan,
The problem has been solved by getting exact Time Zone from XML api reference guide. The problem caused because of that. I was followed the Time Zones from URL API reference guide because I first tried to implement Webex Conference functionality with URL API. Since it is not suitable for our requirements, I changed to XML api and forgot to change the time zone details. Now it is working fine.
Thanks a lot for your valuable replies...
Created by: Sreejith Pm on 17-10-2013 07:30:52 AM
Hi,
As a part of webex integration to my application, I'm trying to schedule training session using XML API in webex sandbox environment.
It always return a error like 'validation: unable to validate timeZone to '<schedule>''...
Response I got is given below
1<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:com="http://www.webex.com/schemas/2002/06/common"><serv:header><serv:response><serv:result>FAILURE</serv:result><serv:reason>validation: unable to add 'timeZone' to <schedule> </serv:reason><serv:gsbstatus>PRIMARY</serv:gsbstatus><serv:exceptionid>999999</serv:exceptionid></serv:response></serv:header><serv:body><serv:bodycontent></serv:bodycontent></serv:body></serv:message>
Please help me....Thanks in advance.
Subject: RE: XML API - Unable to schedule training session
Replied by: Nathan Morrow on 17-10-2013 12:44:08 PM
Hello, <timeZone> is a child of <schedule> but there could be another reason this is failing schema check. Note that timeZone value is a literal string that must exactly match the defined value for the time zone (ex: <timeZone>GMT-08:00, Pacific (San Jose)</timeZone>). timeZoneID is preferred, time zone ID is an enumerated index. Alternately, not specifying a time zone will cause the scheudling request to use the site default time zone.
Subject: RE: XML API - Unable to schedule training session
Replied by: Sreejith Pm on 18-10-2013 12:05:09 AM
Nathan Morrow:Hello, <timeZone> is a child of <schedule> but there could be another reason this is failing schema check. Note that timeZone value is a literal string that must exactly match the defined value for the time zone (ex: <timeZone>GMT-08:00, Pacific (San Jose)</timeZone>). timeZoneID is preferred, time zone ID is an enumerated index. Alternately, not specifying a time zone will cause the scheudling request to use the site default time zone.
Hi Nathan,
Thanks for your response.
Can you please find and check the XML structure which I have created to schedule Training Session with Webex?
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
3 <header>
4 <securitycontext>
5 <webexid>cordiantlearn</webexid>
6 <password>cordiantlearn</password>
7 <siteid>690319</siteid>
8 <partnerid>g0webx!</partnerid>
9 <email>[email protected]</email>
10 </securitycontext>
11 </header>
12
13 <bodycontent xsi:type="java:com.webex.service.binding.training.CreateTrainingSession">
14 <accesscontrol>
15 <listing>PUBLIC</listing>
16
17 </accesscontrol>
18 <schedule>
19 <startdate>10/25/2013 10:28:00</startdate>
20
21 <timezone>GMT +05:30, India Time (Bombay)</timezone>
22 <duration>60</duration>
23 <timezoneid>41</timezoneid>
24 <opentime>5</opentime>
25 </schedule>
26 <metadata>
27 <confname>Sample Training 1</confname>
28 <agenda>Sample test agenda</agenda>
29 <description>Sample test description</description>
30 </metadata>
31 <enableoptions>
32 <javaclient>false</javaclient>
33 <nativeclient>true</nativeclient>
34 <poll>false</poll>
35 <presentation>false</presentation>
36 <applicationshare>false</applicationshare>
37 <desktopshare>false</desktopshare>
38 <webtour>false</webtour>
39 <importdocument>false</importdocument>
40 <pointer>false</pointer>
41 <fullscreen>false</fullscreen>
42 <zoom>false</zoom>
43 <copypage>false</copypage>
44 <rcappshare>false</rcappshare>
45 <rcdesktopshare>false</rcdesktopshare>
46 <rcwebtour>false</rcwebtour>
47 <voip>false</voip>
48 <faxintotrainingsession>false</faxintotrainingsession>
49 <attendeelist>true</attendeelist><chat>true</chat><audiovideo>true</audiovideo><fileshare>true</fileshare><trainingsessionrecord>false</trainingsessionrecord><attendeerecordtrainingsession>false</attendeerecordtrainingsession><annotation>false</annotation><savedocument>false</savedocument><printdocument>false</printdocument><switchpage>false</switchpage><thumbnail>false</thumbnail><autodeleteaftermeetingend>true</autodeleteaftermeetingend>
50 </enableoptions>
51 <telephony>
52 <telephonysupport>CALLIN</telephonysupport>
53 <numphonelines>4</numphonelines>
54
55 </telephony>
56 <repeat>
57 <repeattype>SINGLE</repeattype>
58 </repeat>
59 <remind>
60 <enablereminder>true</enablereminder><emails><email>[email protected]</email></emails><sendemail>true</sendemail><daysahead>1</daysahead><hoursahead>0</hoursahead><minutesahead>0</minutesahead>
61 </remind>
62 <presenters>
63 <participants>
64 <participant><person><name>Spm Official</name><email>[email protected]</email><type>VISITOR</type></person><role>HOST</role></participant>
65 </participants>
66 </presenters>
67 <attendees>
68 <participants>
69 <participant><person><name>Deepak G Nair</name><email>[email protected]</email><type>VISITOR</type></person><role>HOST</role></participant>
70 </participants>
71 </attendees>
72 <attendeeoptions>
73 <request>true</request><registration>true</registration><auto>false</auto><registrationpwd></registrationpwd><maxregistrations>10</maxregistrations><registrationclosedate>10/24/2013 10:28:00</registrationclosedate>
74 <emailinvitations>true</emailinvitations>
75 </attendeeoptions>
76 </bodycontent>
77
78 </serv:message>
Please check and let me know if anything wrong.2<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
3 <header>
4 <securitycontext>
5 <webexid>cordiantlearn</webexid>
6 <password>cordiantlearn</password>
7 <siteid>690319</siteid>
8 <partnerid>g0webx!</partnerid>
9 <email>[email protected]</email>
10 </securitycontext>
11 </header>
12
13 <bodycontent xsi:type="java:com.webex.service.binding.training.CreateTrainingSession">
14 <accesscontrol>
15 <listing>PUBLIC</listing>
16
17 </accesscontrol>
18 <schedule>
19 <startdate>10/25/2013 10:28:00</startdate>
20
21 <timezone>GMT +05:30, India Time (Bombay)</timezone>
22 <duration>60</duration>
23 <timezoneid>41</timezoneid>
24 <opentime>5</opentime>
25 </schedule>
26 <metadata>
27 <confname>Sample Training 1</confname>
28 <agenda>Sample test agenda</agenda>
29 <description>Sample test description</description>
30 </metadata>
31 <enableoptions>
32 <javaclient>false</javaclient>
33 <nativeclient>true</nativeclient>
34 <poll>false</poll>
35 <presentation>false</presentation>
36 <applicationshare>false</applicationshare>
37 <desktopshare>false</desktopshare>
38 <webtour>false</webtour>
39 <importdocument>false</importdocument>
40 <pointer>false</pointer>
41 <fullscreen>false</fullscreen>
42 <zoom>false</zoom>
43 <copypage>false</copypage>
44 <rcappshare>false</rcappshare>
45 <rcdesktopshare>false</rcdesktopshare>
46 <rcwebtour>false</rcwebtour>
47 <voip>false</voip>
48 <faxintotrainingsession>false</faxintotrainingsession>
49 <attendeelist>true</attendeelist><chat>true</chat><audiovideo>true</audiovideo><fileshare>true</fileshare><trainingsessionrecord>false</trainingsessionrecord><attendeerecordtrainingsession>false</attendeerecordtrainingsession><annotation>false</annotation><savedocument>false</savedocument><printdocument>false</printdocument><switchpage>false</switchpage><thumbnail>false</thumbnail><autodeleteaftermeetingend>true</autodeleteaftermeetingend>
50 </enableoptions>
51 <telephony>
52 <telephonysupport>CALLIN</telephonysupport>
53 <numphonelines>4</numphonelines>
54
55 </telephony>
56 <repeat>
57 <repeattype>SINGLE</repeattype>
58 </repeat>
59 <remind>
60 <enablereminder>true</enablereminder><emails><email>[email protected]</email></emails><sendemail>true</sendemail><daysahead>1</daysahead><hoursahead>0</hoursahead><minutesahead>0</minutesahead>
61 </remind>
62 <presenters>
63 <participants>
64 <participant><person><name>Spm Official</name><email>[email protected]</email><type>VISITOR</type></person><role>HOST</role></participant>
65 </participants>
66 </presenters>
67 <attendees>
68 <participants>
69 <participant><person><name>Deepak G Nair</name><email>[email protected]</email><type>VISITOR</type></person><role>HOST</role></participant>
70 </participants>
71 </attendees>
72 <attendeeoptions>
73 <request>true</request><registration>true</registration><auto>false</auto><registrationpwd></registrationpwd><maxregistrations>10</maxregistrations><registrationclosedate>10/24/2013 10:28:00</registrationclosedate>
74 <emailinvitations>true</emailinvitations>
75 </attendeeoptions>
76 </bodycontent>
77
78 </serv:message>
Thanks in advance...
Subject: RE: XML API - Unable to schedule training session
Replied by: Nathan Morrow on 18-10-2013 12:01:19 PM
Hello,
securitycontext should be securityContext. webexid should be webExID. siteid should be siteID. partnerid should be partnerID. bodycontent should be bodyContent, and should be a child of body. etc.
XML API attributes are case sensitive and should match the defined schema. Please refer to the XML API reference guide for correct case for each of these attributes, as most are incorrect in your listing.
As for your time zone, the literal string, as defined in the XML API reference guide, should be "GMT+05:30, India (Bombay)", again this must match exactly.
Subject: RE: XML API - Unable to schedule training session
Replied by: Sreejith Pm on 18-10-2013 08:38:10 PM
Hi Nathan,
The problem has been solved by getting exact Time Zone from XML api reference guide. The problem caused because of that. I was followed the Time Zones from URL API reference guide because I first tried to implement Webex Conference functionality with URL API. Since it is not suitable for our requirements, I changed to XML api and forgot to change the time zone details. Now it is working fine.
Thanks a lot for your valuable replies...
Labels:
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Customers Also Viewed These Support Documents