ELM 9.0 Calendar Integration

39
© Copyright Oracle Corporation 2006. All rights reserved. Enterprise Learning Management 9.0 Calendaring Integration By: Sal Taharim August 2006 PeopleSoft Red Paper Series

Transcript of ELM 9.0 Calendar Integration

Page 1: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

Enterprise Learning Management 9.0 Calendaring Integration

By: Sal Taharim August 2006

PeopleSoft Red Paper Series

© Copyright Oracle Corporation 2006. All rights reserved.

Page 2: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

Enterprise Learning Management 9.0 Calendaring Integration Copyright © 2006, Oracle. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are “commercial computer software” or “commercial technical data” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software-- Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Open Source Disclosure Oracle takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims any and all liability or damages resulting from use of said software or documentation. The following open source software may be used in Oracle’s PeopleSoft products and the following disclaimers are provided. Apache Software Foundation This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright 1999-2000. The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED “AS IS'” AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING,

Page 3: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 3

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 ([email protected]). This product includes software written by Tim Hudson ([email protected]). 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

Page 4: ELM 9.0 Calendar Integration

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.

Page 5: ELM 9.0 Calendar Integration

5

Enterprise Learning Management 9.0 Calendaring Integration

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

Page 6: ELM 9.0 Calendar Integration

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

Page 7: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 7

Introduction

Webcast Integration with Collaboration Suite allows the customer to now launch courses hosted by Oracle’s 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. That’s 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 vendor’s 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.

Page 8: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 8

Zip File Requirements

Every enterprise integration point using the new open integration framework requires a zip file. This file is imported into the customer’s PeopleSoft system. These are the requirements for the extraction zip only.

Files required inside the zip file

File Name Description

PSConfig.xsd for Calendar Basic

PSConfig.xsd for Calendar Proxy

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

PSConfig.xml for Calendar Basic

PSConfig.xml for Calendar Proxy

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.

Multiple XSLT Files 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)

Page 9: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 9

Incoming How-To

DESCRIPTION

Every transaction incoming to PeopleSoft can be performed synchronously or asynchronously. The documentation below for each transaction is the synchronous approach. If the message is performed asynchronously then a standard asynchronous response is transformed and sent. The asynchronous response merely says the message was received as the processing is performed later. The synchronous response is sent as listed below.

CONNECTING TO THE PEOPLESOFT SYSTEM

For every incoming request a node and message must be specified. The node is unique to a specific vendor-service combination. Without this we would be unable to determine which transformation to apply. For our purposes there are two messages, HRS_SYNC and HRS_ASYNC. HRS_SYNC represents a synchronous message and HRS_ASYNC is an asynchronous message.

The node and message can be specified in four ways.

Query String

http://localhost/PSIGW/HttpListeningConnector?From={Node}&MessageName={HRS_SYNC|HRS_ASYNC}

HTTP Header

From: {Node} MessageName: {HRS_SYNC|HRS_ASYNC}

SOAPAction Header

SOAPAction: #{HRS_SYNC|HRS_ASYNC}#{Node}##

XML

<?xml version="1.0"?> <IBRequest> <From> <RequestingNode>{Node}</RequestingNode> </From> <MessageName>{HRS_SYNC|HRS_ASYNC}</MessageName> <ContentSections> <ContentSection> <Data><![CDATA[{xml message goes here}]]></Data> </ContentSection> </ContentSections> </IBRequest>

Page 10: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 10

ASYNCHRONOUS RESPONSE

Schema: AsynchronousResponse.xsd

Sample: AsyncResponse.xml

PSConfig Schema

SCHEMA DIAGRAM

Diagram 1. Configuration File Diagram

Page 11: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 11

SCHEMA DETAILS

PSConfig

PSConfig is the main parent element.

Attributes

PSConfig has no attributes.

Contents

Name Boundaries

TransactionGroup 1..1

VendorInfo 1..1

All 1..1

Transaction 1..n

Extended 1..1

TransactionGroup

This Element is used to match the configuration file to the proper transaction group.

Attributes

Name Type Description

name groupname For Webcast there is only one valid value “Webcast”.

version groupversion 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.

Page 12: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 12

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 Type Description

shortname xs:string This should be a short name for the vendor. This value can be displayed in areas where the longname may be unwieldy.

longname xs:string This should be the full name of the vendor.

description xs:string This is a description. Keep it to 254 characters.

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 Boundries

Value 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 Type Description

name service This is the name of the transaction.

Page 13: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 13

Contents

Name Boundries

URL 0..1

XSLT 1..1

Header 0..n

Value 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 Boundries

Option 0..30

ShortString 0..3

Number 0..2

LongString 0..1

MeetingType 0..n

BuildURLLocal 1..1

URL

URL only occurs under the Transaction Element. URL stores the primary URL to be used for an outgoing transaction.

Page 14: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 14

Attributes

Name Type Description

value xs:string 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 Type Description

request xs:string This should contain the file name of the xslt file to be used to transform the request.

response xs:string This should contain the file name of the xslt file to be used to transform the response.

Async xs:string This should contain the file name of the xslt file to be used to transform xslt responses made asynchronously.

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

Page 15: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 15

name Header This should contain the header type, such as Content-Type,

value xs:string This should contain the value, such as ‘text/xml’ to be set for the header type.

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 Type Description

label xs:string This is the label displayed to the customer on the peoplesoft system for this value.

tagname xs:string This is the name used for the value in the message. From the example above “sv1” and “taggy” are tag names.

value xs:string This is the value passed. From the example above “1” and “valley” are values.

Page 16: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 16

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.

Run Time Variables

In the value attribute variables are supported. Two types of variables are available, run time and design time. Run time variables are populated when the service is run. Design Time Variables are populated when the xml is imported.

Values Description

%ClientTimeZone %ClientTimeZone returns the current time zone for the current user as a three-character string.

%Currency This system variable returns the preferred currency for the current user.

%Date %Date provides the current server date

%DateTime %DateTime returns the current server date and time.

%EmailAddress This system variable returns the email address of the current user.

%EmployeeId %EmployeeId returns an uppercase character string containing the Employee ID of the user currently logged on.

%Language returns a string value representing the current session's language as selected from the signon page

%UserId a character string containing the user currently logged on

Design Time Variables

Values Description

%Incoming(<Transaction>,<Type>) Generates a default incoming URL for the transaction specified in <Transaction>. The transaction specified should be a value of type service.

<Type> is optional, it can be either Sync or Async. If it is not specified it defaults to Sync.

example

%Incoming(JobBoardExpense V1.0,Async)

Page 17: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 17

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 Type Description

ID optionID 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.

Active xs:Boolean true display it to the end user, false, don’t

Default xs:Boolean true, default checked, false, default unchecked

Label label 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 Type Description

ID stringID 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.

Active xs:Boolean true display it to the end user, false, don’t

Label label The label to be displayed to the user up to 30 chars

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 Type Description

Active xs:Boolean true display it to the end user, false, don’t

Label label The label to be displayed to the user up to 30 chars

Page 18: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 18

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 Type Description

ID xs:nonNegativeInteger The value behind the label, this value is passed back to the vendor in the soap message creating/updating sessions.

Label label The label to be displayed to the user for the meeting type up to 30 chars

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 Type Description

<value> xs:boolean 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

Page 19: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 19

USERDATA

Diagram

UserData Type

Name Type Description

Emplid xsd:string The Emplid of the current user as defined in the peoplesoft system.

UserName xsd:string The username of the current user as defined in the peoplesoft system.

Email xsd:string Main email of the current user as defined in the peoplesoft system.

Name Name The name of the current user, broken out.

Phone Phone Main Phone Number of the current user.

Page 20: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 20

Name Type

Name Type Description

FirstName xsd:string First Name of the current user.

MiddleName xsd:string Middle Name of the current user.

LastName xsd:string Last Name of the current user.

Phone Type

Name Type Description

InternationalNumber xsd:string International Number

AreaCode xsd:string Area Code

SubscriberNumber xsd:string Subscriber Number

WEBCASTVALUES

Diagram

WebcastValues Type

Name Type Description

ID xs:nonNegativeInteger The ID depending on the value type. This ID corresponds to the one set in the configuration file.

Value xs:string The value to be passed

WEBCASTUSER

Page 21: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 21

Diagram

WebcastUser Type

Name Type Description

UserName xs:string The username as it is defined in the webcast system.

UserRole xs:string The role of the user in the course, either “Learner” or “Instructor”

FullName xs:string Fullname of the user

SOAP Messages

CALENDARCREATE

CalendarCreate Description

Creates an entry into the target calendar system of an activity session. This service can be initiated during the enrollment to create calendar entries for the learners. During create session upon assigning an instructor this service can be initiated to create calendar entry for the instructor.

CalendarCreate Diagram

Input

Complex [1.. 1] Input CalendarCreateInput

Complex [1.. 1] Values Values

Page 22: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 22

Complex [1.. n] Value Value

[1.. 1] Name xsd:string

[1.. 1] Value xsd:string

[1.. 1] Class xsd:string

[1.. 1] UID xsd:decimal

[1.. 1] StartDate xsd:date

[1.. 1] Duration xsd:string

[1.. 1] Location xsd:string

[1.. 1] Description xsd:string

[1.. 1] Attendee xsd:string

[1.. 1] Subject xsd:string

[1.. 1] EndDate xsd:date

[1.. 1] Organiser xsd:string

[1.. 1] UserId xsd:string

[1.. 1] Password xsd:string

[1.. 1] ProxyAppName xsd:string

[1.. 1 ProxyAppPass xsd:string

Page 23: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 23

Output

Complex [1.. 1] Output CalendarCreateOutput

[1.. 1] faultcode xsd:string

[1.. 1] faultstring xsd:string

[1.. 1] description xsd:string

[1.. 1] GUID xsd:string

CalendarCreate Input

Name Type Description

Values Values These are the values as described in the Values section of the Schema Details.

Class xsd:string Calendar Class: PUBLIC/ CONFIDENTIAL/PRIVATE

UID xsd:decimal A numeric value identifying the current user.

StartDate xsd:string Specifies the date and time that a calendar component begins.

Duration xsd:string Specifies a positive duration of time.

Location xsd:string Defines the intended venue for the activity defined by a calendar component.

Description xsd:string Description

Attendee xsd:string Learner name display

Subject xsd:string Activity subject

EndDate xsd:string Specifies the date and time that a calendar component ends.

Organiser xsd:string Defines the organizer for a calendar component.

UserId xsd:string The learner’s 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.

Password xsd:string The password to the calendar system. This password encrypted and stored in HRS_CAL_USER

ProxyAppName xsd:string Application Name (For Proxy Authentication)

ProxyAppPass xsd:string Application Password (For Proxy Authentication)

Page 24: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 24

Calendar Create Output

Name Type Description

faultcode xsd:string Specifies if the edit as successfully completed, true for success

faultstring xsd:string If a failure occurred this is where the error message goes

description xsd:string Return message description

GUID xsd:string Globally Unique Identifier

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 CalendarDeleteInput

Complex [1.. 1] Values Values

Complex [1.. n] Value Value

[1.. 1] Name xsd:string

[1.. 1] Value xsd:string

[1.. 1] GUID xsd:string

[1.. 1] UserId xsd:string

[1.. 1] Password xsd:string

[1.. 1] ProxyAppName xsd:string

Page 25: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 25

[1.. 1 ProxyAppPass xsd:string

Output

Complex [1.. 1] Output CalendarDeleteOutput

[1.. 1] faultcode xsd:string

[1.. 1] faultstring xsd:string

[1.. 1] description xsd:string

CalendarDelete Input

Name Type Description

Values Values These are the values as described in the Values section of the Schema Details.

GUID xsd:string Globally Unique Identifier

UserId xsd:string The username of the user being edited, this will be set to the user’s current ELM UserID. This user name is then tied to the user’s EMPLID in table HRS_CAL_USER and they cannot be re-added.

Password xsd:string This password encrypted and stored in HRS_CAL_USER

CalendarDelete Output

Name Type Description

faultcode xsd:string Specifies if the edit as successfully completed, true for success

faultstring xsd:string If a failure occurred this is where the error message goes

description xsd:string Return message description

WSDL

CalendarDelete.wsdl

Page 26: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 26

Appendix

PSCONFIG.XSD FOR CALENDAR BASIC <?xml version="1.0" ?>

- <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">

- <xs:element name="PSConfig">

- <xs:complexType>

- <xs:sequence>

<xs:element ref="TransactionGroup" />

<xs:element ref="VendorInfo" />

<xs:element ref="All" />

<xs:element ref="Transaction" maxOccurs="unbounded" />

</xs:sequence>

</xs:complexType>

</xs:element>

- <xs:element name="Value">

- <xs:complexType>

<xs:attribute name="label" type="xs:string" use="required" />

<xs:attribute name="tagname" type="xs:string" use="required" />

<xs:attribute name="value" type="xs:string" use="required" />

<xs:attribute name="readonly" type="xs:boolean" use="optional" default="true" />

</xs:complexType>

</xs:element>

- <xs:element name="Header">

- <xs:complexType>

<xs:attribute name="name" type="header" use="required" />

<xs:attribute name="value" type="xs:string" use="required" />

</xs:complexType>

</xs:element>

- <xs:element name="URL">

- <xs:complexType>

<xs:attribute name="value" type="xs:string" use="required" />

Page 27: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 27

</xs:complexType>

</xs:element>

- <xs:element name="XSLT">

- <xs:complexType>

<xs:attribute name="request" type="xs:string" use="required" />

<xs:attribute name="response" type="xs:string" use="required" />

</xs:complexType>

</xs:element>

- <xs:element name="All">

- <xs:complexType>

- <xs:sequence>

<xs:element ref="Value" minOccurs="0" maxOccurs="unbounded" />

</xs:sequence>

</xs:complexType>

</xs:element>

- <xs:element name="Transaction">

- <xs:complexType>

- <xs:sequence>

<xs:element ref="URL" />

<xs:element ref="XSLT" />

<xs:element ref="Header" maxOccurs="unbounded" />

<xs:element ref="Value" minOccurs="0" maxOccurs="unbounded" />

</xs:sequence>

<xs:attribute name="name" type="service" />

</xs:complexType>

</xs:element>

- <xs:element name="TransactionGroup">

- <xs:complexType>

<xs:attribute name="name" type="groupname" />

<xs:attribute name="version" type="groupversion" />

</xs:complexType>

</xs:element>

- <xs:element name="VendorInfo">

- <xs:complexType>

Page 28: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 28

<xs:attribute name="shortname" type="xs:string" />

<xs:attribute name="longname" type="xs:string" />

<xs:attribute name="description" type="xs:string" />

</xs:complexType>

</xs:element>

- <xs:simpleType name="groupname">

- <xs:restriction base="xs:string">

<xs:enumeration value="Calendar" />

</xs:restriction>

</xs:simpleType>

- <xs:simpleType name="groupversion">

- <xs:restriction base="xs:string">

<xs:enumeration value="1" />

</xs:restriction>

</xs:simpleType>

- <xs:simpleType name="header">

- <xs:restriction base="xs:string">

<xs:enumeration value="Accept" />

<xs:enumeration value="Accept-Charset" />

<xs:enumeration value="Accept-Encoding" />

<xs:enumeration value="Accept-Language" />

<xs:enumeration value="Accept-Ranges" />

<xs:enumeration value="Age" />

<xs:enumeration value="Allow" />

<xs:enumeration value="Authorization" />

<xs:enumeration value="Cache-Control" />

<xs:enumeration value="Connection" />

<xs:enumeration value="Content-Encoding" />

<xs:enumeration value="Content-Length" />

<xs:enumeration value="Content-Location" />

<xs:enumeration value="Content-MD5" />

<xs:enumeration value="Content-Range" />

<xs:enumeration value="Content-Type" />

<xs:enumeration value="Date" />

Page 29: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 29

<xs:enumeration value="ETag" />

<xs:enumeration value="Expect" />

<xs:enumeration value="Expires" />

<xs:enumeration value="From" />

<xs:enumeration value="Host" />

<xs:enumeration value="If-Match" />

<xs:enumeration value="If-Modified-Since" />

<xs:enumeration value="If-None-Match" />

<xs:enumeration value="If-Range" />

<xs:enumeration value="If-Unmodified-Since" />

<xs:enumeration value="Last-Modified" />

<xs:enumeration value="Location" />

<xs:enumeration value="Max-Forwards" />

<xs:enumeration value="Pragma" />

<xs:enumeration value="Proxy-Authenticate" />

<xs:enumeration value="Proxy-Authorization" />

<xs:enumeration value="Range" />

<xs:enumeration value="Referer" />

<xs:enumeration value="Retry-After" />

<xs:enumeration value="SOAPAction" />

<xs:enumeration value="TimeOut" />

<xs:enumeration value="Trailer" />

<xs:enumeration value="Transfer-Encoding" />

<xs:enumeration value="Upgrade" />

<xs:enumeration value="User-Agent" />

<xs:enumeration value="Vary" />

<xs:enumeration value="Via" />

<xs:enumeration value="WWW-Authenticate" />

<xs:enumeration value="Warning" />

<xs:enumeration value="sendUncompressed" />

</xs:restriction>

</xs:simpleType>

- <xs:simpleType name="service">

- <xs:restriction base="xs:string">

Page 30: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 30

<xs:enumeration value="CalendarCreate" />

<xs:enumeration value="CalendarDelete" />

</xs:restriction>

</xs:simpleType>

</xs:schema>

PSCONFIG.XSD FOR CALENDAR PROXY <?xml version="1.0" ?>

- <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">

- <xs:element name="PSConfig">

- <xs:complexType>

- <xs:sequence>

<xs:element ref="TransactionGroup" />

<xs:element ref="VendorInfo" />

<xs:element ref="All" />

<xs:element ref="Transaction" maxOccurs="unbounded" />

</xs:sequence>

</xs:complexType>

</xs:element>

- <xs:element name="Value">

- <xs:complexType>

<xs:attribute name="label" type="xs:string" use="required" />

<xs:attribute name="tagname" type="xs:string" use="required" />

<xs:attribute name="value" type="xs:string" use="required" />

<xs:attribute name="readonly" type="xs:boolean" use="optional" default="true" />

</xs:complexType>

</xs:element>

- <xs:element name="Header">

- <xs:complexType>

<xs:attribute name="name" type="header" use="required" />

<xs:attribute name="value" type="xs:string" use="required" />

</xs:complexType>

</xs:element>

- <xs:element name="URL">

Page 31: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 31

- <xs:complexType>

<xs:attribute name="value" type="xs:string" use="required" />

</xs:complexType>

</xs:element>

- <xs:element name="XSLT">

- <xs:complexType>

<xs:attribute name="request" type="xs:string" use="required" />

<xs:attribute name="response" type="xs:string" use="required" />

</xs:complexType>

</xs:element>

- <xs:element name="All">

- <xs:complexType>

- <xs:sequence>

<xs:element ref="Value" minOccurs="0" maxOccurs="unbounded" />

</xs:sequence>

</xs:complexType>

</xs:element>

- <xs:element name="Transaction">

- <xs:complexType>

- <xs:sequence>

<xs:element ref="URL" />

<xs:element ref="XSLT" />

<xs:element ref="Header" maxOccurs="unbounded" />

<xs:element ref="Value" minOccurs="0" maxOccurs="unbounded" />

</xs:sequence>

<xs:attribute name="name" type="service" />

</xs:complexType>

</xs:element>

- <xs:element name="TransactionGroup">

- <xs:complexType>

<xs:attribute name="name" type="groupname" />

<xs:attribute name="version" type="groupversion" />

</xs:complexType>

</xs:element>

Page 32: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 32

- <xs:element name="VendorInfo">

- <xs:complexType>

<xs:attribute name="shortname" type="xs:string" />

<xs:attribute name="longname" type="xs:string" />

<xs:attribute name="description" type="xs:string" />

</xs:complexType>

</xs:element>

- <xs:simpleType name="groupname">

- <xs:restriction base="xs:string">

<xs:enumeration value="Calendar" />

</xs:restriction>

</xs:simpleType>

- <xs:simpleType name="groupversion">

- <xs:restriction base="xs:string">

<xs:enumeration value="1" />

</xs:restriction>

</xs:simpleType>

- <xs:simpleType name="header">

- <xs:restriction base="xs:string">

<xs:enumeration value="Accept" />

<xs:enumeration value="Accept-Charset" />

<xs:enumeration value="Accept-Encoding" />

<xs:enumeration value="Accept-Language" />

<xs:enumeration value="Accept-Ranges" />

<xs:enumeration value="Age" />

<xs:enumeration value="Allow" />

<xs:enumeration value="Authorization" />

<xs:enumeration value="Cache-Control" />

<xs:enumeration value="Connection" />

<xs:enumeration value="Content-Encoding" />

<xs:enumeration value="Content-Length" />

<xs:enumeration value="Content-Location" />

<xs:enumeration value="Content-MD5" />

<xs:enumeration value="Content-Range" />

Page 33: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 33

<xs:enumeration value="Content-Type" />

<xs:enumeration value="Date" />

<xs:enumeration value="ETag" />

<xs:enumeration value="Expect" />

<xs:enumeration value="Expires" />

<xs:enumeration value="From" />

<xs:enumeration value="Host" />

<xs:enumeration value="If-Match" />

<xs:enumeration value="If-Modified-Since" />

<xs:enumeration value="If-None-Match" />

<xs:enumeration value="If-Range" />

<xs:enumeration value="If-Unmodified-Since" />

<xs:enumeration value="Last-Modified" />

<xs:enumeration value="Location" />

<xs:enumeration value="Max-Forwards" />

<xs:enumeration value="Pragma" />

<xs:enumeration value="Proxy-Authenticate" />

<xs:enumeration value="Proxy-Authorization" />

<xs:enumeration value="Range" />

<xs:enumeration value="Referer" />

<xs:enumeration value="Retry-After" />

<xs:enumeration value="SOAPAction" />

<xs:enumeration value="TimeOut" />

<xs:enumeration value="Trailer" />

<xs:enumeration value="Transfer-Encoding" />

<xs:enumeration value="Upgrade" />

<xs:enumeration value="User-Agent" />

<xs:enumeration value="Vary" />

<xs:enumeration value="Via" />

<xs:enumeration value="WWW-Authenticate" />

<xs:enumeration value="Warning" />

<xs:enumeration value="sendUncompressed" />

</xs:restriction>

</xs:simpleType>

Page 34: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 34

- <xs:simpleType name="service">

- <xs:restriction base="xs:string">

<xs:enumeration value="CalendarCreate" />

<xs:enumeration value="CalendarDelete" />

</xs:restriction>

</xs:simpleType>

</xs:schema>

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>

Page 35: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 35

- <xsd:complexType hcmSchema:ownerid="LELM" hcmSchema:uuid="HC_UUID_42343141106062006" name="CalendarCreateOutput">

- <xsd:sequence>

<xsd:element minOccurs="1" name="Complex" type="" />

<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:element minOccurs="1" name="GUID" type="xsd:string" />

</xsd:sequence>

</xsd:complexType>

</xsd:schema>

</wsdl:types>

- <wsdl:service name="HCM">

- <wsdl:port binding="tns:Learning_Solutions_Open_Integration_Framework" name="Learning_Solutions_Open_Integration_Framework">

<soap:address location="http://ple-pvashist/PSIGW/HttpListeningConnector" />

</wsdl:port>

</wsdl:service>

- <wsdl:portType name="Learning_Solutions_Open_Integration_Framework">

- <wsdl:operation name="CalendarCreate_DoService_1_0">

<wsdl:documentation>CalendarCreate&Version=1.0</wsdl:documentation>

<wsdl:input message="tns:CalendarCreate_DoService_1_0_input_msg" name="CalendarCreate_DoService_1_0_input" />

<wsdl:output message="tns:CalendarCreate_DoService_1_0_output_msg" name="CalendarCreate_DoService_1_0_output" />

</wsdl:operation>

</wsdl:portType>

- <wsdl:binding name="Learning_Solutions_Open_Integration_Framework" type="tns:Learning_Solutions_Open_Integration_Framework">

<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />

- <wsdl:operation name="CalendarCreate_DoService_1_0">

<soap:operation soapAction="#HMCR_SYNCH_PORT.VERSION_1#PSFT_XINBND" />

- <wsdl:input name="CalendarCreate_DoService_1_0_input">

<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://xmlns.oracle.com/Enterprise/HCM/2005/service/CalendarCreate/DoService/1.0" use="encoded" />

</wsdl:input>

- <wsdl:output name="CalendarCreate_DoService_1_0_output">

<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://xmlns.oracle.com/Enterprise/HCM/2005/service/CalendarCreate/DoService/1.0" use="encoded" />

</wsdl:output>

</wsdl:operation>

Page 36: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 36

</wsdl:binding>

- <wsdl:message name="CalendarCreate_DoService_1_0_input_msg">

<wsdl:part hcmSchema:uuid="HC_UUID_85824051106062006" name="Input" type="hcmSchema:CalendarCreateInput" />

</wsdl:message>

- <wsdl:message name="CalendarCreate_DoService_1_0_output_msg">

<wsdl:part hcmSchema:uuid="HC_UUID_42343141106062006" name="Output" type="hcmSchema:CalendarCreateOutput" />

</wsdl:message>

</wsdl:definitions>

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>

Page 37: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 37

</wsdl:types>

- <wsdl:service name="HCM">

- <wsdl:port binding="tns:Learning_Solutions_Open_Integration_Framework" name="Learning_Solutions_Open_Integration_Framework">

<soap:address location="http://ple-pvashist/PSIGW/HttpListeningConnector" />

</wsdl:port>

</wsdl:service>

- <wsdl:portType name="Learning_Solutions_Open_Integration_Framework">

- <wsdl:operation name="CalendarDelete_DoService_1_0">

<wsdl:documentation>CalendarDelete&Version=1.0</wsdl:documentation>

<wsdl:input message="tns:CalendarDelete_DoService_1_0_input_msg" name="CalendarDelete_DoService_1_0_input" />

<wsdl:output message="tns:CalendarDelete_DoService_1_0_output_msg" name="CalendarDelete_DoService_1_0_output" />

</wsdl:operation>

</wsdl:portType>

- <wsdl:binding name="Learning_Solutions_Open_Integration_Framework" type="tns:Learning_Solutions_Open_Integration_Framework">

<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />

- <wsdl:operation name="CalendarDelete_DoService_1_0">

<soap:operation soapAction="#HMCR_SYNCH_PORT.VERSION_1#PSFT_XINBND" />

- <wsdl:input name="CalendarDelete_DoService_1_0_input">

<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://xmlns.oracle.com/Enterprise/HCM/2005/service/CalendarDelete/DoService/1.0" use="encoded" />

</wsdl:input>

- <wsdl:output name="CalendarDelete_DoService_1_0_output">

<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://xmlns.oracle.com/Enterprise/HCM/2005/service/CalendarDelete/DoService/1.0" use="encoded" />

</wsdl:output>

</wsdl:operation>

</wsdl:binding>

- <wsdl:message name="CalendarDelete_DoService_1_0_input_msg">

<wsdl:part hcmSchema:uuid="HC_UUID_87835161606062006" name="Input" type="hcmSchema:CalendarDeleteInput" />

</wsdl:message>

- <wsdl:message name="CalendarDelete_DoService_1_0_output_msg">

<wsdl:part hcmSchema:uuid="HC_UUID_47207201606062006" name="Output" type="hcmSchema:CalendarDeleteOutput" />

</wsdl:message>

</wsdl:definitions>

Page 38: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 38

SAMPLE XML

ASYNCRESPONSE.XML <?xml version="1.0"?>

<SOAP-ENV:Envelope xmlns:m="http://peoplesoft.com/HCM/Schema" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP-ENV:Body>

<m:Output>

<Recieved>True</Recieved>

<ErrorText/>

</m:Output>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

PSCONFIG.XML FOR CALENDAR BASIC <?xml version="1.0" encoding="UTF-8" ?>

- <!--

- <PSConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PSConfig.xsd">

<TransactionGroup name="Calendar" version="1" />

<VendorInfo shortname="OCS" longname="Basic Auth" description="Collab suite Oracle" />

<All />

- <Transaction name="CalendarCreate">

<URL value="http://adas0119.peoplesoft.com:7778/ocws-bin/ocas.fcgi" />

<XSLT request="CreateAppRequestTransform.xslt" response="CreateAppResponseTransform.xslt" />

<Header name="Content-Type" value="text/xml" />

<Header name="SOAPAction" value=""http://www.oracle.com/WebServices/Calendaring/1.0/Create"" />

</Transaction>

- <Transaction name="CalendarDelete">

<URL value="http://adas0119.peoplesoft.com:7778/ocws-bin/ocas.fcgi" />

<XSLT request="DeleteAppRequestTransform.xslt" response="DeleteAppResponseTransform.xslt" />

<Header name="Content-Type" value="text/xml" />

<Header name="SOAPAction" value=""http://www.oracle.com/WebServices/Calendaring/1.0/Delete"" />

Page 39: ELM 9.0 Calendar Integration

Enterprise Learning Management 9.0 Calendaring Integration

© Copyright Oracle Corporation 2005. All rights reserved. 39

</Transaction>

</PSConfig>

PSCONFIG.XML FOR CALENDAR PROXY <?xml version="1.0" encoding="UTF-8" ?>

- <!--

- <PSConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PSConfig.xsd">

<TransactionGroup name="Calendar" version="1" />

<VendorInfo shortname="OCS" longname="Collab Suite Calendar" description="Oracle Collab suite Calendar" />

- <All>

<Value label="ApplicationName" tagname="ApplicationName" value="ConsolidatedCalendar" readonly="false" />

<Value label="ApplicationPassword" tagname="ApplicationPassword" value="calendar" readonly="false" />

</All>

- <Transaction name="CalendarCreate">

<URL value="http://adas0119.peoplesoft.com:7778/ocws-bin/ocas.fcgi" />

<XSLT request="CreateAppRequestTransform.xslt" response="CreateAppResponseTransform.xslt" />

<Header name="Content-Type" value="text/xml" />

<Header name="SOAPAction" value=""http://www.oracle.com/WebServices/Calendaring/1.0/Create"" />

</Transaction>

- <Transaction name="CalendarDelete">

<URL value="http://adas0119.peoplesoft.com:7778/ocws-bin/ocas.fcgi" />

<XSLT request="DeleteAppRequestTransform.xslt" response="DeleteAppResponseTransform.xslt" />

<Header name="Content-Type" value="text/xml" />

<Header name="SOAPAction" value=""http://www.oracle.com/WebServices/Calendaring/1.0/Delete"" />

</Transaction>

</PSConfig>