WSDL File Information --------------------- Services: TIRLaunch (Synchronous Communications) Author: Prashant Nayak, Bruce Barton, Colin Smythe Date: 28th February, 2006 Version: 1.0 Status: Final Release Description: The Tools Interoperability Launch Service. History: Version 1.0: This is the first formal release of this service. WSDL Binding: This WSDL Binding is based upon the IMS General Web Services Base Profile v1.0 The IMS GWS Basic Profile is derived from the WS-I Basic Profile v1.1. This profile uses: WSDL 1.1, SOAP 1.1, HTTP 1.1 and XML 1.0. Extension profiles to the IMS GWS Base Profile are available but ae not supported using this tool version. UML Source File Information --------------------------- Choreography: Sync Transport: SOAPv1.1 Source XSLT File Information ---------------------------- XSL Generator: UMLtoXSDTransformv0p7.xsl XSLT Processor: Xalan Release: 1.0 Beta 1 Date: 30th November, 2005 Auto-generation Tool -------------------- This WSDL/XSD was auto-generated using the IMS WSDL/XSD auto-generation tool. While every attempt has been made to ensure that this tool auto-generates the XSDs correctly, users should be aware that this is an experimental tool. Permission is given to make use of this tool. IMS makes no claim on the materials created by third party users of this tool. Details on how to use this tool are contained in the IMS document: "IMS General Web Services: WSDL/XSD Binding Auto-generation" available at the IMS web-site. Tool Copyright: 2005 (c) IMS Global Learning Consortium Inc. All Rights Reserved. There is a SOAPHeader extension that is required by the service. PortType Description -------------------- This is the TIR Launch Service port. There are two main components: 1) ProxyTool Host - this performs all the functions related to the launch of the ProxyTool, including generating the relevant ProxyTool launch message and utilizing appropriate security profile; 2) Tool - exposed as a web service that accepts launch messages from the LMS TIR, understands the security profile used therein and responds back to the LMS TIR using the ProxyTool core protocol as to the status of the launch.