Professional Documents
Culture Documents
ELM 9.0 Calendar Integration
ELM 9.0 Calendar Integration
0 Calendaring Integration
Enterprise Learning Management 9.0 Calendaring Integration BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. OpenSSL Copyright 1998-2003 The OpenSSL Project. All rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. SSLeay Copyright (C) 1995-1998 Eric Young. All rights reserved. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com). Copyright (C) 1995-1998 Eric Young. All rights reserved. THIS SOFTWARE IS PROVIDED BY ERIC YOUNG AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDEING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Loki Library Copyright 2001 by Andrei Alexandrescu. This code accompanies the book: Alexandrescu, Andrei. Modern C++ Design: Generic Programming and Design Patterns Applied. Copyright (c) 2001. Addison-Wesley. Permission to use, copy, modify, distribute and sell this software for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Helma Project Copyright 1999-2004 Helma Project. All rights reserved. THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE HELMA PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
Copyright Oracle Corporation 2005. All rights reserved.
Enterprise Learning Management 9.0 Calendaring Integration PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Helma includes third party software released under different specific license terms. See the licenses directory in the Helma distribution for a list of these license. Sarissa Copyright 2004 Manos Batsis This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
Table of Contents
TABLE OF CONTENTS........................................................................................................................................................... 5 INTRODUCTION...................................................................................................................................................................... 7 ZIP FILE REQUIREMENTS ................................................................................................................................................... 8 INCOMING HOW-TO.............................................................................................................................................................. 9 Description .................................................................................................................................................................................. 9 Connecting to the PeopleSoft System ....................................................................................................................................... 9 Asynchronous Response........................................................................................................................................................... 10 PSCONFIG SCHEMA............................................................................................................................................................. 10 Schema Diagram....................................................................................................................................................................... 10 Schema Details.......................................................................................................................................................................... 11 PSConfig ................................................................................................................................................................................ 11 TransactionGroup................................................................................................................................................................... 11 VendorInfo ............................................................................................................................................................................. 12 All........................................................................................................................................................................................... 12 Transaction............................................................................................................................................................................. 12 Extended................................................................................................................................................................................. 13 URL........................................................................................................................................................................................ 13 XSLT...................................................................................................................................................................................... 14 Header .................................................................................................................................................................................... 14 Value ...................................................................................................................................................................................... 15 Option..................................................................................................................................................................................... 17 ShortString ............................................................................................................................................................................. 17 LongString.............................................................................................................................................................................. 17 MeetingType .......................................................................................................................................................................... 18 BuildURLLocal...................................................................................................................................................................... 18 Schema File ............................................................................................................................................................................... 18 Sample PSConfig.xml............................................................................................................................................................... 18 COMMON TYPES .................................................................................................................................................................. 18 UserData ................................................................................................................................................................................... 19 Diagram.................................................................................................................................................................................. 19 UserData Type ....................................................................................................................................................................... 19 Name Type ............................................................................................................................................................................. 20 Phone Type............................................................................................................................................................................. 20 WebcastValues.......................................................................................................................................................................... 20 Diagram.................................................................................................................................................................................. 20 WebcastValues Type.............................................................................................................................................................. 20 WebcastUser ............................................................................................................................................................................. 20 5
Enterprise Learning Management 9.0 Calendaring Integration Diagram.................................................................................................................................................................................. 21 WebcastUser Type ................................................................................................................................................................. 21 SOAP MESSAGES .................................................................................................................................................................. 21 CalendarCreate ........................................................................................................................................................................ 21 CalendarCreate Description ................................................................................................................................................... 21 CalendarCreate Diagram ........................................................................................................................................................ 21 CalendarCreate Input.............................................................................................................................................................. 23 Calendar Create Output .......................................................................................................................................................... 24 WSDL .................................................................................................................................................................................... 24 CalendarDelete ......................................................................................................................................................................... 24 CalendarDelete Description .................................................................................................................................................. 24 CalendarDelete Diagram ........................................................................................................................................................ 24 CalendarDelete Input.............................................................................................................................................................. 25 CalendarDelete Output ........................................................................................................................................................... 25 WSDL .................................................................................................................................................................................... 25 APPENDIX ............................................................................................................................................................................... 26 PSConfig.xsd for Calendar Basic........................................................................................................................................... 26 PSConfig.xsd for Calendar Proxy.......................................................................................................................................... 30 CalendarCreate.wsdl ............................................................................................................................................................... 34 CalendarDelete.wsdl ................................................................................................................................................................ 36 Sample XML............................................................................................................................................................................. 38 AsyncResponse.xml .................................................................................................................................................................. 38 PSConfig.xml for Calendar Basic .......................................................................................................................................... 38 PSConfig.xml for Calendar Proxy ......................................................................................................................................... 39
Introduction
Webcast Integration with Collaboration Suite allows the customer to now launch courses hosted by Oracles Collaboration Suite. At a very high level once the system is configured properly a learner will be able to enroll into an Activity and then be able to launch it from within the ELM system. In order for this to occur there are several services that need to run behind the scene as a user uses the ELM system. First when a session for an Activity is created the create service is triggered, which will create the session in Oracle system and return the URL to use when a user launches the session. Now a learner can enroll in the newly created session. When the learner enrolls, the Add User service is kicked of to add the user to the Oracle system if the user does not already exist. Next the Enroll service is kicked off to enroll the learner in the session in the Oracle system. If a learner needed approval in order to enroll in the class the Add User and Enroll service will be kicked of from the approval process. The Add User and Enroll service are kicked of in a similar fashion from other places with ELM where a learner can be enrolled. For example, a manager enrolling a team member, an Admin enrolling a single learner or group of learners. The complete list can of trigger points are listed in the Unit Test section. Also show below in a graphical picture, one can see all the places the services are triggers from. The new open integration framework is designed to be easy for the customer to implement. In general, to setup a new vendor for a specific integration the customer imports a zip file provided by the vendor. Thats it! Loading the zip file does the job. Other setup steps are optional and will likely occur in practice: such as data mapping setup. However, the integration is up and running as soon as the customer loads the zip file. Among other things, loading the vendors zip file implements a specific transaction group. A transaction group is defined on the PeopleSoft system and consists of one or more services, both incoming and outgoing, that should be implemented for an integration to take place. The services referenced in the Transaction Group may be declared required or optional. Every service requires two XSLT transformations. These transformations allow PeopleSoft to define separate Request and Response messages from the vendor. Separate transformations should be implemented on the Request and the Response. What then occurs is the messages are generated as described below, however before the peoplesoft system attempts to send/process these messages they are run through the xslt transform. These transformations are a required part of the process.
Files required inside the zip file File Name PSConfig.xsd for Calendar Basic PSConfig.xsd for Calendar Proxy PSConfig.xml for Calendar Basic PSConfig.xml for Calendar Proxy Description This is the schema file for the configuration file, it should be included unedited as delivered by PeopleSoft. This file should be located in the root of the zip file This is the xml configuration file, it must comply to PSConfig.xsd, be called PSConfig.xml and be located in the root of the zip file. These XSLT files are referenced in the configuration file. ! ! ! ! ! ! ! ! ! ! ! Request & Response Transform for each Transaction Enroll Service UnEnroll Service CreateSession Service EditSession Service RemoveSession Service GetLearner Service GetHost Service GetRecorded Service WebcastAuthentication (Only required for Colaboration Suite) WebcastGetPolicyToken (Only required for Collaboration Suite)
ASYNCHRONOUS RESPONSE
Schema: AsynchronousResponse.xsd
Sample: AsyncResponse.xml
PSConfig Schema
SCHEMA DIAGRAM
10
SCHEMA DETAILS
PSConfig
PSConfig is the main parent element.
Attributes
PSConfig has no attributes.
Contents
Name TransactionGroup VendorInfo All Transaction Extended Boundaries 1..1 1..1 1..1 1..n 1..1
TransactionGroup
This Element is used to match the configuration file to the proper transaction group.
Attributes
Name name version Type groupname groupversion Description For Webcast there is only one valid value Webcast. This determines which version of the transaction group to use. Currently there is only one version available for Webcast, 2.
Contents
Transaction Group has no value or sub elements.
11
VendorInfo
The attributes of VendorInfo contain general information about the vendor to populate the Vendor Profile. These are basic elements like name and description.
Attributes
Name shortname Type xs:string Description This should be a short name for the vendor. This value can be displayed in areas where the longname may be unwieldy. This should be the full name of the vendor. This is a description. Keep it to 254 characters.
longname description
xs:string xs:string
Contents
Vendor Info has no values or sub elements.
All
The values specified in All will be included in all messages sent by the PeopleSoft system.
Attributes
All has no attributes.
Contents
Name Value Boundries 1..n
Transaction
Transaction defines data required to set up an individual service. For each transaction specified as required in the transaction group there should be one (and only one) transaction defined here. If a transaction specified as optional is not defined here it will not be supported.
Attributes
Name name Type service Description This is the name of the transaction.
12
Contents
Name URL XSLT Header Value Boundries 0..1 1..1 0..n 0..n
Extended
For Integration with Collaboration Suite the Attribute OptionID = 31 needs to be added to the Extended section of the XML file. Collaboration Suite requires a second level of authentication that WebEx does not require. This flag will allow the system to know if it needs to perform the second level of authentication. For all vendors the second attribute shown below BuildURLLocal needs to be present as well in order to determine if the URL used for launching sessions should be built locally or not. This is explained more in section 4.2.15.
Attributes
<Option ID="31" Active="true" Default="true" Label=" "/> <BuildURLLocal BuildURLLocal="true"/>
Contents
Name Option ShortString Number LongString MeetingType BuildURLLocal Boundries 0..30 0..3 0..2 0..1 0..n 1..1
URL
URL only occurs under the Transaction Element. URL stores the primary URL to be used for an outgoing transaction.
13
Attributes
Name value Type xs:string Description This value should be the URL to be used for outgoing transaction. The customer can later override this value if the need arises. If the transaction is incoming simply put N/A.
Contents
URL has no values or sub elements.
XSLT
XSLT only occurs under the Transaction Element. XSLT references the xslts to be used for transformation on request and response.
Attributes
Name request Type xs:string Description This should contain the file name of the xslt file to be used to transform the request. This should contain the file name of the xslt file to be used to transform the response. This should contain the file name of the xslt file to be used to transform xslt responses made asynchronously.
response
xs:string
Async
xs:string
Contents
XSLT has no values or sub elements.
Header
Header only occurs under the Transaction Element. Header is used to set the data to be included in the http header. So things like Content-Type text/xml and SOAPActions should be set here.
Attributes
Name Type Description
14
name
Header
This should contain the header type, such as ContentType, This should contain the value, such as text/xml to be set for the header type.
value
xs:string
Contents
Header has no values or sub components.
Value
Value contains values that are passed with every message sent from the Peoplesoft system. All the values returned are passed in an object called Values. These can be used to set any values, For example if a username and password are required they can be specified as values here. As long as read-only is set to false the customer can change these values. However, keep in mind all values specified here have no dependencies, so they will not change based on the current user, or anything like that. Here is an example of how the values are shown in a message.
<Values> <Value> <Name>sv1</Name> <Value>1</Value> </Value> <Value> <Name>taggy</Name> <Value>valley</Value> </Value> </Values>
Attributes
Name label Type xs:string Description This is the label displayed to the customer on the peoplesoft system for this value. This is the name used for the value in the message. From the example above sv1 and taggy are tag names. This is the value passed. From the example above 1 and valley are values. 15
tagname
xs:string
value
xs:string
read-only
xs:Boolean
If read-only is set to true then the customer cannot modify the value from within the peoplesoft system.
Contents
Values has no values or sub elements.
%Language
%UserId
16
Option
Custom options can be added for individual webcast vendors. Since different vendors may offer extra options and it would be futile to try to support every single option we let the vendor decide which options to offer. This section has to do with custom yes/no checkboxes.
Attributes
Name ID Type optionID Description This should be a number between 1 and 30 and should not repeat on any option. So the first option is 1, the second is 2, etc. true display it to the end user, false, dont true, default checked, false, default unchecked The label to be displayed to the user up to 30 chars
ShortString
Short String is another generic option available to vendors. This is a string the user can input up to 254 characters. This string is entered free form.
Attributes
Name ID Type stringID Description This should be a number between 1 and 3 and should not repeat on any option. So the first ID is 1, the second is 2, etc. true display it to the end user, false, dont The label to be displayed to the user up to 30 chars
Active Label
xs:Boolean label
LongString
Long string is similar to short string, only the max length the user can enter is 2000 characters, and they are restricted to a single long string.
Attributes
Name Active Label Type xs:Boolean label Description true display it to the end user, false, dont The label to be displayed to the user up to 30 chars
17
MeetingType
Since most vendors support multiple different meeting types this allows for the user to select which type of meeting this course should be scheduled as. This will be presented to the user as a drop down.
Attributes
Name ID Type xs:nonNegativeInteger Description The value behind the label, this value is passed back to the vendor in the soap message creating/updating sessions. The label to be displayed to the user for the meeting type up to 30 chars
Label
label
BuildURLLocal
This specifies if the URL should be built locally on our system on redirect or if a message requesting a URL should be sent to the vendor. Originally in V1 only local building of the URL was supported. This is explained further on the message
WebcastGetRedirectURL.
Content
Name <value> Type xs:boolean Description true, build the URL locally, false, request it from the external vendor.
SCHEMA FILE
PSConfig.xsd
SAMPLE PSCONFIG.XML
PSConfig WebEx.xml
PSConfig RTC.xml
Common Types
18
USERDATA
Diagram
UserData Type
Name Emplid Type xsd:string Description The Emplid of the current user as defined in the peoplesoft system. The username of the current user as defined in the peoplesoft system. Main email of the current user as defined in the peoplesoft system. The name of the current user, broken out. Main Phone Number of the current user.
UserName
xsd:string
xsd:string
Name
Name
Phone
Phone
19
Name Type
Name FirstName MiddleName LastName Type xsd:string xsd:string xsd:string Description First Name of the current user. Middle Name of the current user. Last Name of the current user.
Phone Type
Name InternationalNumber AreaCode SubscriberNumber Type xsd:string xsd:string xsd:string Description International Number Area Code Subscriber Number
WEBCASTVALUES
Diagram
WebcastValues Type
Name ID Type xs:nonNegativeInteger Description The ID depending on the value type. This ID corresponds to the one set in the configuration file. The value to be passed
Value
xs:string
WEBCASTUSER
20
Diagram
WebcastUser Type
Name UserName UserRole Type xs:string xs:string Description The username as it is defined in the webcast system. The role of the user in the course, either Learner or Instructor Fullname of the user
FullName
xs:string
CalendarCreate Diagram
Input Complex [1.. 1] Input [1.. 1] CalendarCreateInput Values Values
Complex
21
Complex
[1.. n]
[1.. 1] [1.. 1]
[1.. 1] [1.. 1] [1.. 1] [1.. 1] [1.. 1] [1.. 1] [1.. 1] [1.. 1] [1.. 1] [1.. 1] [1.. 1] [1.. 1] [1.. 1] [1.. 1
Class UID StartDate Duration Location Description Attendee Subject EndDate Organiser UserId Password ProxyAppName ProxyAppPass
xsd:string xsd:decimal xsd:date xsd:string xsd:string xsd:string xsd:string xsd:string xsd:date xsd:string xsd:string xsd:string xsd:string xsd:string
22
Output Complex [1.. 1] Output [1.. 1] [1.. 1] [1.. 1] [1.. 1] CalendarCreateOutput faultcode faultstring description GUID xsd:string xsd:string xsd:string xsd:string
CalendarCreate Input
Name Values Class UID StartDate Duration Location Description Attendee Subject EndDate Organiser UserId Type Values xsd:string xsd:decimal xsd:string xsd:string xsd:string xsd:string xsd:string xsd:string xsd:string xsd:string xsd:string Description These are the values as described in the Values section of the Schema Details. Calendar Class: PUBLIC/ CONFIDENTIAL/PRIVATE A numeric value identifying the current user. Specifies the date and time that a calendar component begins. Specifies a positive duration of time. Defines the intended venue for the activity defined by a calendar component. Description Learner name display Activity subject Specifies the date and time that a calendar component ends. Defines the organizer for a calendar component. The learners e-mail address as valid user identification to the calendar system. This user identification is tied to the Person-ID in the HRS_CAL_USER. The password to the calendar system. This password encrypted and stored in HRS_CAL_USER Application Name (For Proxy Authentication) Application Password (For Proxy Authentication)
Password
xsd:string
ProxyAppName ProxyAppPass
xsd:string xsd:string
23
WSDL
CalendarCreate.wsdl
CALENDARDELETE
CalendarDelete Description
Deletes an entry from the target calendar system of an activity session. This service can be initiated when learner drop the activity session.
CalendarDelete Diagram
Input Complex [1.. 1] Input [1.. 1] CalendarDeleteInput Values [1.. n] Value Name Value Values Value xsd:string xsd:string
Complex
Complex
[1.. 1] [1.. 1]
24
[1.. 1
ProxyAppPass
xsd:string
Output Complex [1.. 1] Output [1.. 1] [1.. 1] [1.. 1] CalendarDeleteOutput faultcode faultstring description xsd:string xsd:string xsd:string
CalendarDelete Input
Name Values GUID UserId Type Values xsd:string xsd:string Description These are the values as described in the Values section of the Schema Details. Globally Unique Identifier The username of the user being edited, this will be set to the users current ELM UserID. This user name is then tied to the users EMPLID in table HRS_CAL_USER and they cannot be re-added. This password encrypted and stored in HRS_CAL_USER
Password
xsd:string
CalendarDelete Output
Name faultcode faultstring description Type xsd:string xsd:string xsd:string Description Specifies if the edit as successfully completed, true for success If a failure occurred this is where the error message goes Return message description
WSDL
CalendarDelete.wsdl
25
26
27
28
29
30
31
32
33
CALENDARCREATE.WSDL
<?xml version="1.0" ?> - <wsdl:definitions targetNamespace="http://xmlns.oracle.com/Enterprise/HCM/2005/service" xmlns:hcm="http://xmlns.oracle.com/Enterprise/HCM/2005" xmlns:hcmSchema="http://xmlns.oracle.com/Enterprise/HCM/2005/schema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapEncoding="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://xmlns.oracle.com/Enterprise/HCM/2005/service" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> - <wsdl:types> - <xsd:schema targetNamespace="http://xmlns.oracle.com/Enterprise/HCM/2005/schema" xmlns="http://xmlns.oracle.com/Enterprise/HCM/2005/schema" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> - <xsd:complexType hcmSchema:ownerid="LELM" hcmSchema:uuid="HC_UUID_85824051106062006" name="CalendarCreateInput"> - <xsd:sequence> <xsd:element name="Values" type="" /> <xsd:element minOccurs="1" name="Class" type="xsd:string" /> <xsd:element minOccurs="1" name="UID" type="xsd:decimal" /> <xsd:element minOccurs="1" name="StartDate" type="xsd:date" /> <xsd:element minOccurs="1" name="Duration" type="xsd:string" /> <xsd:element minOccurs="1" name="Location" type="xsd:string" /> <xsd:element minOccurs="1" name="Description" type="xsd:string" /> <xsd:element minOccurs="1" name="Attendee" type="xsd:string" /> <xsd:element minOccurs="1" name="Subject" type="xsd:string" /> <xsd:element minOccurs="1" name="EndDate" type="xsd:date" /> <xsd:element minOccurs="1" name="Organiser" type="xsd:string" /> <xsd:element minOccurs="1" name="UserId" type="xsd:string" /> <xsd:element name="Password" type="xsd:string" /> <xsd:element minOccurs="1" name="ProxyAppName" type="xsd:string" /> <xsd:element minOccurs="1" name="ProxyAppPass" type="xsd:string" /> </xsd:sequence> </xsd:complexType>
34
35
CALENDARDELETE.WSDL
<?xml version="1.0" ?> - <wsdl:definitions targetNamespace="http://xmlns.oracle.com/Enterprise/HCM/2005/service" xmlns:hcm="http://xmlns.oracle.com/Enterprise/HCM/2005" xmlns:hcmSchema="http://xmlns.oracle.com/Enterprise/HCM/2005/schema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapEncoding="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://xmlns.oracle.com/Enterprise/HCM/2005/service" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> - <wsdl:types> - <xsd:schema targetNamespace="http://xmlns.oracle.com/Enterprise/HCM/2005/schema" xmlns="http://xmlns.oracle.com/Enterprise/HCM/2005/schema" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> - <xsd:complexType hcmSchema:ownerid="LELM" hcmSchema:uuid="HC_UUID_87835161606062006" name="CalendarDeleteInput"> - <xsd:sequence> <xsd:element minOccurs="1" name="Values" type="" /> <xsd:element minOccurs="1" name="GUID" type="xsd:string" /> <xsd:element minOccurs="1" name="UserId" type="xsd:string" /> <xsd:element name="Password" type="xsd:string" /> <xsd:element minOccurs="1" name="ProxyAppName" type="xsd:string" /> <xsd:element minOccurs="1" name="ProxyAppPAss" type="xsd:string" /> </xsd:sequence> </xsd:complexType> - <xsd:complexType hcmSchema:ownerid="LELM" hcmSchema:uuid="HC_UUID_47207201606062006" name="CalendarDeleteOutput"> - <xsd:sequence> <xsd:element minOccurs="1" name="faultcode" type="xsd:string" /> <xsd:element minOccurs="1" name="faultstring" type="xsd:string" /> <xsd:element minOccurs="1" name="description" type="xsd:string" /> </xsd:sequence> </xsd:complexType> </xsd:schema>
36
37
38
39