DOCSLIB.ORG

T-110.5140 Network Application Frameworks and XML Mobile

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Contents T-110.5140 Network Application Frameworks and XML Mobile Middleware Motivation Mobile Middleware Examples Summary 18.3.2008 Sasu Tarkoma Mobile Middleware I Mobile Middleware II Middleware is typically designed and Goals for middleware: implemented for fixed-network hosts fault-tolerance, adaptability, High bandwidth, low latency, reliable heterogeneity,scalability, resource sharing communication Mobile middleware Persistent storage and sufficient computing dynamically changing context power decoupled No mobility ) events, tuple spaces Mobile environment requires new Basic solution for wireless solutions ) Use a proxy Existing middleware services do not scale Previous lectures: mobility is challenging Small devices / embedded systems pose totally different challenges Secure Reflection WAE mobile XML Middleware routing In general, middleware provides IPv6 .NET Objects transparency to the underlying conditions XML mobility, Location transparency in RPC/RMI J2ME HIP In mobile environments this is not always desired Symbian NAF Sometimes we need to know about location changes, QoS changes, etc. Mobility Security Requirement for reflective middleware Wireless Should expose APIs for querying / changing CORBA important parameters Under development Plain IPv4 MIP 1 WAE Examples Wireless Application Environment (WAE) A suite of protocols and specifications for WAE optimizing data transfer for wireless communication J2ME WAP stack Symbian Focus on binary transmission MAEMO Protocols Android ) WSP (Wireless Session Protocol) Wireless CORBA • HTTP replacement, “compressed” ) WTP (Wireless Transaction Protocol) Mobile Web Server • Request/response, more efficient than TCP Pervasive Computing Middleware ) WTLS (Wireless Transport Layer Security) Fuego • Based on TLS, may not be end-to-end with a gateway ) WDP (Wireless Datagram Protocol) • UDP replacement Programming model Web Access Data transformation encoded Client Gateway Server WAP gateway performs data transformation request request between WML (or XHTML) and HTML Data compression Encoders HTTP Technique are used for dealing with images and Decoders Server Web wireless other graphics Browser Adaptability User profile and device characteristics are stored in the WAP gateway Protocol encoded Gateways response CGI,.. Security response Secure Enterprise Proxy (SEP) using 128-bit encryption in WAP 1.2 Service discovery and mobility support WAP’s “walled garden” – WAP gateways are provided by ISP such as AOL Comparison WAE: current status WAE Other WAP Forum now in OMA (Open Mobile Alliance) HTML/JSHTML/JS WAE Other WAP 2.0, is a re-engineering of WAP using a cut- down version of XHTML with end-to-end HTTP SessionSession Layer Layer (WSP) (WSP) Gateway and custom protocol suite is optional. HTTP HTTP WAP used by many handsets TransactionTransaction Layer Layer (WTP) (WTP) 1.2 version introduced WAP Push (typically using an SMS message) TLSTLS - - SSL SSL SecuritySecurity Layer Layer (WTSL) (WTSL) Typically versatile networking stacks with also IPv6 support TransportTransport Layer Layer (WDP,UDP) (WDP,UDP) TCP/IPTCP/IP UDP/IPUDP/IP Bearers:Bearers: SMS,CDMA,.. SMS,CDMA,.. 2 Java 2 Platform Micro Edition (J2ME) Java for consumer electronics and embedded devices A virtual machine and a set of APIs Configurations and profiles Configurations ) two-low level APIs and optimized VMs • CDC, CLDC Profiles ) API specification on top of a configuration for complete runtime ) CLDC: MIDP ) CDC: Foundation, Personal Basis, Personal ) Specify both APIs and Configurations Source: http://developers.sun.com/techtopics/mobility/getstart/articles/survey/ ) Profiles defined using Java Community Process (JCP) J2ME optional packages CLDC Technology Connected Limited Device Configuration (CLDC); JSR 30, JSR 172: J2ME Web Services Specification JSR 139 Content Handler API (CHAPI) JSR 211 Mobile Information Device Profile (MIDP); JSR 37, JSR 118 Information Module Profile, (IMP); JSR 195 allows the invocation of J2ME platform applications Java Technology for the Wireless Industry, (JTWI); JSR 185 from native applications and vice versa Wireless Messaging API (WMA); JSR 120, JSR 205 Security and Trust Services JSR-177 Mobile Media API (MMAPI); JSR 135 Location API for J2ME; JSR 179 J2ME Client Provisioning JSR-124 SIP API for J2ME; JSR 180 J2ME Client Provisioning Specification defines a FileConnection and PIM API (JSR-75) server partitioning standard for provisioning Security and Trust Services API for J2ME, (SATSA); JSR-177 applications. Mobile 3D Graphics; JSR-184 J2ME Web Services APIs, (WSA); JSR 172 Mobile Media API JSR-135 Bluetooth API (JSR-82, Motorola, Java Partner Site) J2ME Content Handler API, (CHAPI); JSR 211 CDC Technology Symbian Connected Device Configuration (CDC); JSR 36, OS for handheld devices with limited JSR 218 resources Foundation Profile, (FP); JSR 46, JSR 218 User interface framework Personal Basis Profile, (PBP); JSR 129, JSR 217 APIs (C++) Personal Profile, (PP); JSR 62, JSR 216 Tools J2ME RMI Optional Package, (RMI OP); JSR 66 Operating System JDBC Optional Package for CDC/Foundation Pre-emptive, multitasking, multithreading, Profile API; JSR 169 memory protection Java TV API; JSR 927 Event-based, active objects Java Secure Socket Extension for Connected Memory conservation, reliability, CPU Device Configuration (JSSE) optimizations 3 Software Components Symbian architecture Kernel UI Framework Manages and controls access to hw Java J2ME Hw-supported privileges, kernel mode Application Services Application Program with a user interface Runs in user mode in its own process Generic OS Comms Multimedia & Connec- Server Services Services Graphics Srv. tivity Srv. Program without a user interface Manages resources, provides interface to clients Base Services File server, window server, comms, .. Engine Application part that manipulates data, typically Kernel Services & Hardware Abstraction separate DLL MAEMO Open Source development platform for Nokia Internet Tablets and other Linux- based devices Maemo SDK www.maemo.org Android Wireless CORBA Mobile OS and application platform from Google CORBA does not support accessing Open Handset Alliance mobile objects or wireless Linux kernel communication Open Source (not yet available) Wireless CORBA specification Uses Java to build applications (Java SE class library parts from Apache Harmony project) Three basic requirements Optimized virtual machine called ”Dalvik” Invocations from mobile objects Runs .dex files (derived from .class or .jar) Invocations to mobile objects Relies on underlying system for process isolation, memory mng, and threading Wireless communication Independent of Sun and JCP Home bridge Java APIs for basic comms, location, SQLite, Access bridges OpenGL, SyncML Tunnelling over wireless Handoff protocols 4 Mobile IP vs. WCORBA Architecture• Redirects requests for • Abstract transport-independentservices on the terminal tunnel• Encapsulates, for GIOP forwardsmessages• Keeps or ignores track of the current • Other side end of the Access Bridgeaccess bridge MIP addresses host mobility, not object incoming GIOP messages • Encapsulate/decapsulates• Concrete tunnels for msgs TCP/IP, mobility • Decapsulates and forwards • GeneratesUDP/IP mobility and events WAP WDP. MIP does not specifically support • Protocolmessages requires from thereliable GIOP and tunnel wireless protocols ordered• Generates delivery mobility events • Lists available services MIP hides all handoff events location-aware services difficult to implement Handoffs Network Initiated Handoff Network initiated handoff started by an external application optional to support make-before-break Terminal initiated handoff terminal discovered a new Access Bridge make-before-break is required Access recovery The Home Location Agent is updated Old Access Bridges are informed Mobility events are generated in the visited domain and the terminal domain Mobile Web Server Overview Port of Apache web server to Symbian S60 Custom gateway to connect mobile servers with the Internet The firewall/NAT problem Webserver Browser Link 2 1 http://research.nokia.com/research/projects/m 3 obile-web-server/index.html 2.5/3G Operator Firewall DNS Gateway Internet By courtesy of Johan Wikman Presented in EuroOSCON 2006 5 Pervasive computing middleware Projects Key Issues UIC Heterogeneity of devices and networks: It helps users to specialize to the particular Fuego Core (HIIT) properties of different devices and network environments X-Middle Disconnected operations in mobile applications: It allows mobile users to share data when they are connected, or replicate the data and perform operations on them off-line when they are disconnected; data reconciliation takes place when user gets reconnected Mobile and wireless environments have different requirements than desktop Gaia Dynamic adaptation to the context of mobile applications: It supports the development and execution of portable applications in active spaces systems Lime Programming constructs which are sensitive to the mobility constraints: It explores User mobility, terminal mobility, connectivity, the idea by providing programmers with a global virtual data structure and a tuple space device characteristics, dynamic environments (Tspace), whose content is determined by the connectivity among mobile hosts Vision: A service application is Tspaces Asynchronous messaging-based
Recommended publications
  • Technique: HTTP the Java Way

    Technique: HTTP the Java Way

    Technique: HTTP the Java way An article from Android in Practice EARLY ACCESS EDITION Charlie Collins, Michael D. Galpin, and Matthias Kaeppler MEAP Release: July 2010 Softbound print: Spring 2011 | 500 pages ISBN: 9781935182924 This article is taken from the book Android in Practice. The authors demonstrate how to send simple HTTP requests to a Web server using Java’s standard HTTP networking facilities. Tweet this button! (instructions here) Get 35% off any version of Android in Practice with the checkout code fcc35. Offer is only valid through www.manning.com. The standard Java class library already has a solution for HTTP messaging. An open-source implementation of these classes is bundled with Android’s class library, which is based on Apache Harmony. It’s simple and bare- bones in its structure and, while it supports features like proxy servers, cookies (to some degree), and SSL, the one thing that it lacks more than anything else is a class interface and component structure that doesn’t leave you bathed in tears. Still, more elaborate HTTP solutions are often wrappers around the standard Java interfaces and, if you don’t need all the abstraction provided, for example, by Apache HttpClient interfaces, the stock Java classes may not only be sufficient, they also perform much better thanks to a much slimmer, more low-level implementation. Problem You must perform simple networking tasks via HTTP (such as downloading a file) and you want to avoid the performance penalty imposed by the higher-level, much larger, and more complex Apache HttpClient implementation. Solution If you ever find yourself in this situation, you probably want to do HTTP conversations through a java.net.HttpURLConnection.
  • SUSE® LINUX Enterprise Jeos 11 Novell® Software License Agreement

    SUSE® LINUX Enterprise Jeos 11 Novell® Software License Agreement

    NOTICE: This document includes the SUSE Linux Enterprise JeOS 11 Novell Software License Agreement followed by other license agreements. By indicating your acceptance of these terms, including by use, you are agreeing to the terms and conditions of each these agreements. SUSE® LINUX Enterprise JeOS 11 Novell® Software License Agreement PLEASE READ THIS AGREEMENT CAREFULLY. BY INSTALLING OR OTHERWISE USING THE SOFTWARE (INCLUDING ITS COMPONENTS), YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE WITH THESE TERMS, DO NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE. RIGHTS AND LICENSES This Novell Software License Agreement ("Agreement") is a legal agreement between You (an entity or a person) and Novell, Inc. ("Novell"). The software product identified in the title of this Agreement, together with any media and accompanying documentation, is referred to in this Agreement as the "Software." The Software is protected by the copyright laws and treaties of the United States ("U.S.") and other countries and is subject to the terms of this Agreement. Any update or support release to the Software that You may download or receive that is not accompanied by a license agreement expressly superseding this Agreement is Software and governed by this Agreement; You must have a valid license for the version and quantity of the Software being updated or supported in order to install or use any such update or support release. The Software is a modular operating system comprised of numerous components that may be accompanied by separate license terms. The Software is a collective work of Novell; although Novell does not own the copyright to every component of the Software, Novell owns the collective work copyright for the Software.
  • Open Source Used in Cisco Unity Connection 11.5 SU 1

    Open Source Used in Cisco Unity Connection 11.5 SU 1

    Open Source Used In Cisco Unity Connection 11.5 SU 1 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-132949842 Open Source Used In Cisco Unity Connection 11.5 SU 1 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-132949842 Contents 1.1 ace 5.3.5 1.1.1 Available under license 1.2 Apache Commons Beanutils 1.6 1.2.1 Notifications 1.2.2 Available under license 1.3 Apache Derby 10.8.1.2 1.3.1 Available under license 1.4 Apache Mina 2.0.0-RC1 1.4.1 Available under license 1.5 Apache Standards Taglibs 1.1.2 1.5.1 Available under license 1.6 Apache STRUTS 1.2.4. 1.6.1 Available under license 1.7 Apache Struts 1.2.9 1.7.1 Available under license 1.8 Apache Xerces 2.6.2. 1.8.1 Notifications 1.8.2 Available under license 1.9 axis2 1.3 1.9.1 Available under license 1.10 axis2/cddl 1.3 1.10.1 Available under license 1.11 axis2/cpl 1.3 1.11.1 Available under license 1.12 BeanUtils(duplicate) 1.6.1 1.12.1 Notifications Open Source Used In Cisco Unity Connection
  • Talend Open Studio for Big Data Release Notes

    Talend Open Studio for Big Data Release Notes

    Talend Open Studio for Big Data Release Notes 6.0.0 Talend Open Studio for Big Data Adapted for v6.0.0. Supersedes previous releases. Publication date July 2, 2015 Copyleft This documentation is provided under the terms of the Creative Commons Public License (CCPL). For more information about what you can and cannot do with this documentation in accordance with the CCPL, please read: http://creativecommons.org/licenses/by-nc-sa/2.0/ Notices Talend is a trademark of Talend, Inc. All brands, product names, company names, trademarks and service marks are the properties of their respective owners. License Agreement The software described in this documentation is licensed under the Apache License, Version 2.0 (the "License"); you may not use this software except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.html. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software developed at AOP Alliance (Java/J2EE AOP standards), ASM, Amazon, AntlR, Apache ActiveMQ, Apache Ant, Apache Avro, Apache Axiom, Apache Axis, Apache Axis 2, Apache Batik, Apache CXF, Apache Cassandra, Apache Chemistry, Apache Common Http Client, Apache Common Http Core, Apache Commons, Apache Commons Bcel, Apache Commons JxPath, Apache
  • Apache Harmony Project Tim Ellison Geir Magnusson Jr

    Apache Harmony Project Tim Ellison Geir Magnusson Jr

    The Apache Harmony Project Tim Ellison Geir Magnusson Jr. Apache Harmony Project http://harmony.apache.org TS-7820 2007 JavaOneSM Conference | Session TS-7820 | Goal of This Talk In the next 45 minutes you will... Learn about the motivations, current status, and future plans of the Apache Harmony project 2007 JavaOneSM Conference | Session TS-7820 | 2 Agenda Project History Development Model Modularity VM Interface How Are We Doing? Relevance in the Age of OpenJDK Summary 2007 JavaOneSM Conference | Session TS-7820 | 3 Agenda Project History Development Model Modularity VM Interface How Are We Doing? Relevance in the Age of OpenJDK Summary 2007 JavaOneSM Conference | Session TS-7820 | 4 Apache Harmony In the Beginning May 2005—founded in the Apache Incubator Primary Goals 1. Compatible, independent implementation of Java™ Platform, Standard Edition (Java SE platform) under the Apache License 2. Community-developed, modular architecture allowing sharing and independent innovation 3. Protect IP rights of ecosystem 2007 JavaOneSM Conference | Session TS-7820 | 5 Apache Harmony Early history: 2005 Broad community discussion • Technical issues • Legal and IP issues • Project governance issues Goal: Consolidation and Consensus 2007 JavaOneSM Conference | Session TS-7820 | 6 Early History Early history: 2005/2006 Initial Code Contributions • Three Virtual machines ● JCHEVM, BootVM, DRLVM • Class Libraries ● Core classes, VM interface, test cases ● Security, beans, regex, Swing, AWT ● RMI and math 2007 JavaOneSM Conference | Session TS-7820 |
  • Webservices - Axis

    Webservices - Axis

    WebServices - Axis 1. Axis ######### ##### 1.2 #######: [email protected] 1.1. ## • ######### • WSDL2Java ###### • Java2WSDL ###### • ####(WSDD)###### • ##### Axis ## • ######### • Axis ###### • ####### • ########## Axis ############# • #### • ####### 1.2. ######### 1.2.1. WSDL2Java ###### ###: java org.apache.axis.wsdl.WSDL2Java [#####] WSDL-URI #####: -h, --help ################# -v, --verbose ############## -n, --noImports ######## WSDL ########## WSDL ############### ###### -O, --timeout <##> ############# (######45######## -1 ######) -D, --Debug ############ -W, --noWrapped "wrapped" document/literal ######### Page 1 Copyright © 2000-2005 The Apache Software Foundation All rights reserved. WebServices - Axis -s, --server-side Web########################### -S, --skeletonDeploy <##> deploy.wsdd ######(true)#######(false)###### ###### false ###--server-side ####### -N, --NStoPkg <##>=<#> ################### -f, --fileNStoPkg <##> NStoPkg ################ (###### NStoPkg.properties) -p, --package <##> ####################################### ## -o, --output <##> ######################## -d, --deployScope <##> deploy.xml ########### : "Application", "Request", "Session" -t, --testCase Web######## junit ############### -a, --all #####(############)########## -T, --typeMappingVersion 1.1##### 1.2 ############## 1.1 ## (SOAP 1.1 JAX-RPC ## #1.2 # SOAP 1.1 ############)# -F, --factory <##> GeneratorFactory #############(Java #############)# ############### -i, --nsInclude <####> ###################(-x ################## ##################)
  • Apache AXIS2 Release Notes

    Apache AXIS2 Release Notes

    AXIS2 for OpenVMS I64 July 2017 1. Introduction Apache AXIS2 for OpenVMS is the core engine for web services. It is a complete redesign and rewrite of the previously used Apache AXIS SOAP stack. This release of AXIS2 for OpenVMS is based on the latest 1.7.3 release from the Apache Software Foundation, and includes various new features and bug fixes. The release also provides a prebuilt Java servlet, which can be deployed within an application server such as Tomcat. Users are strongly encouraged to upgrade to 1.7-3 to take advantage of these improvements. This OpenVMS port of AXIS2 includes all Apache AXIS2 functionality provided by the Open Source 1.7.3 release. 2. Acknowledgements VMS Software Inc. would like to acknowledge the work of the Apache AXIS2 development team for their ongoing efforts in developing and supporting this software. 3. What’s new in this release AXIS2 Version 1.7-3 for OpenVMS is based on Apache AXIS2 1.7.3, and includes the following changes: Apache Axis2 1.7.3 is a security release that contains a fix for CVE-2010-3981. That security vulnerability affects the admin console that is part of the Axis2 Web application. The admin console now has a CSRF prevention mechanism and all known XSS vulnerabilities as well as two non-security bugs in the admin console (AXIS2-4764 and AXIS2-5716) have been fixed. Users of the AXIS2 WAR distribution are encouraged to upgrade to 1.7.3 to take advantage of these improvements. This release also fixes a regression in the HTTP client code that is triggered by the presence of certain types of cookies in HTTP responses (see AXIS2-5772).
  • Android Geeknight Presentation 2011-03

    Android Geeknight Presentation 2011-03

    Android Geek Night 3.0 Per Nymann Jørgensen [email protected] Niels Sthen Hansen [email protected] Android Geek Night 3.0 Android at a glance New features in Gingerbread & Honeycomb Demos & Code Android 101 Operating system targeting mobile devices/Tables devices Linux based - with additions Open source under the Apache License Allows development in Java Share of worldwide 2010 Q4 smartphone sales to end users by Or Scala, JRuby, Groovy .. operating system, according toCanalys.[35] Two new versions just came out.. Android 101 - Dalvik VM Virtual machine developed by Google for mobile devices Uses the Dalvik Executable (.dex) format Designed for limited processing power and memory Register-based architecture as opposed to stack machine Java VMs Class library based on Apache Harmony No AWT, Swing No Java ME Android 101 - SDK Android libraries The SDK and AVD manager, for maintaining the SDK components and creating virtual devices LogCat to capture logs from running device DDMS – Dalvik Debug Monitor Tools to convert Java .class files to Dalvik bytecode and create installable .apk files Plugin for Eclipse - Android Development Tools (ADT) Android 101 - Components Activity GUI Service non-GUI Broadcast Receiver Events Content Provider Exposing data/content across applications An Android application can be seen as a collection of components. Android API 10 New stuff New Sensors / New Sensor APIs Gyroscope Rotation vector Acceleration Linear acceleration (acceleration without gravity) Gravity (gravity without acceleration) Barometer (air pressure) Android API 10 New stuff NFC Short range wireless communication. Do not require discovery or pairing Supported mode as of 2.3.3 (reader/writer/P2P limited) Enable application like Mobile ticketing (dare we say rejsekort), Smart poster, etc.
  • Reading the Runes for Java Runtimes the Latest IBM Java Sdks

    Reading the Runes for Java Runtimes the Latest IBM Java Sdks

    Java Technology Centre Reading the runes for Java runtimes The latest IBM Java SDKs ... and beyond Tim Ellison [email protected] © 2009 IBM Corporation Java Technology Centre Goals . IBM and Java . Explore the changing landscape of hardware and software influences . Discuss the impact to Java runtime technology due to these changes . Show how IBM is leading the way with these changes 2 Mar 9, 2009 © 2009 IBM Corporation Java Technology Centre IBM and Java . Java is critically important to IBM – Provides fundamental infrastructure to IBM software portfolio – Delivers standard development environment – Enables cost effective multi platform support – Delivered to Independent Software Vendors supporting IBM server platforms . IBM is investing strategically in virtual machine technology – Since Java 5.0, a single Java platform technology supports ME, SE and EE – Technology base on which to delivery improved performance, reliability and serviceability • Some IBM owned code (Virtual machine, JIT compiler, ...) • Some open source code (Apache XML parser, Apache Core libraries, Zlib, ...) • Some Sun licensed code (class libraries, tools, ...) . Looking to engender accelerated and open innovation in runtime technologies – Support for Eclipse, Apache (Harmony, XML, Derby, Geronimo, Tuscany) – Broad participation of relevant standards bodies such as JCP and OSGi 3 Mar 9, 2009 © 2009 IBM Corporation Java Technology Centre IBM Java – 2009 key initiatives . Consumability – Deliver value without complexity. – Ensure that problems with our products can be addressed quickly, allowing customers to keep focus on their own business issues. – Deliver a consistent model for solving customer problems. “Scaling Up” - Emerging hardware and applications – Provide a Java implementation that can scale to the most demanding application needs.
  • Xerox® Igen™ 150 Press 3 Party Software License Disclosure

    Xerox® Igen™ 150 Press 3 Party Software License Disclosure

    Xerox® iGen™ 150 Press 3rd Party Software License Disclosure October 2013 The following software packages are copyrighted for use in this product according to the license stated. Full terms and conditions of all 3rd party software licenses are available from the About screen under the Help menu on the Press Interface or by accessing the Support & Drivers page located on the http://www.xerox.com website. Adobe Icons and Web Logos, license: Adobe Icons and Web Logos License Apache log4j 1.2.8, Apache log4j 1.2.9, Apache Web Services XML-RPC 1.2.b1, Apache Lucene Java 1.3, Apache Tomcat 4.1.27, license: Apache License 1.1 Apache Axis 1.x 1.4, Apache Jakarta Commons HttpClient 3.0.alpha1, Apache Jakarta Commons Logging 1.0.4, Apache Jakarta Lucene 1.9.1, Apache XML Security Java 1.3.0, saxpath 1.0 FCS, Skin Look And Feel (skinlf) 1.2.8, Spring Framework Utilities 0.7, Apache Web Services Axis 1.2rc3, Apache Xerces Java XML Parser 2.7.1, Apache XML Xalan-Java 2.7.0, Jetty - Java HTTP Servlet Server 4.0.D0, Lucene Snowball, Streaming API for XML (StAX) - JSR-173 20040819, license: Apache License 2.0 Perl 5.8.5, Perl 5.10.0, AppConfig-1.66, Archive-Tar-1.58, Compress::Zlib-2.020, Expect.pm- 1.21, File-NCopy-0.36, File-NFSLock-1.20, Filesys-Df-0.92, Filesys-DiskFree-0.06, HTML- Parser-3.69, HTML-Tagset-3.20, HTML-Template-2.9, IO-Stty-0.02, IO-Tty-1.08, IO-Zlib- 1.09, libxml-perl-0.08, Net-Netmask-1.9015, Net-Telnet-3.03, perl-5.8.3, perlindex-1.605, Pod- Escapes-1.04, Pod-POM-0.25, Pod-Simple-3.13, Proc-ProcessTable-0.45, Socket6-0.23, Stat-
  • 7.1 Oracle Bpel Process Manager

    7.1 Oracle Bpel Process Manager

    Institute of Architecture of Application Systems University of Stuttgart Universitätsstraße 38 D–70569 Stuttgart Diplomarbeit Nr. 2728 Fault Handling Across the Web Services Stack Pablo Fuentetaja Abad Course of Study: Computer Science Examiner: Prof. Dr. Frank Leymann Supervisor: Dipl.-Inf. Oliver Kopp Commenced: January ,14 2008 Completed: July, 15 2008 CR-Classification: C.2.0, C.2.1, C.2.2, C.2.4, D.2.11 Acknowledgments To my family and friends. Their support has helped me during the difficult moments. Without them this would have not been possible. To Prof. Dr. F. Leymann. For offer me the opportunity of developing this work in the Institut für Architektur von Anwendungssystemen. To Dipl.-Inf. O. Kopp. For his work, help, and supervision during these months. To Dipl.-Inf. Matthias Wieland. For his last supervision and comments. Abstract The Business Process Execution Language (BPEL) is an XML based language for describing business process behaviour based on Web services. The BPEL notation includes flow control, variables, concurrent execution, input and output, transaction scoping/compensation, and error handling. These processes are executed on a BPEL engine which calls and receives messages from external parties. The BPEL process is suspended or terminated if such communication fails, not providing any detailed information about the cause. The aim of this diploma thesis is the description of the different communication faults that can be found throughout the Web Services Stack, how they are reflected and describe a general concept of fault handling. Two BPEL engines are use on this thesis “Oracle BPEL Process Manager” and “Apache ODE”.
  • Xti 9.5.41.3

    Xti 9.5.41.3

    Open Source Used In XTI 9.5.41.3 Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-163479699 Open Source Used In XTI 9.5.41.3 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-163479699 Contents 1.1 activation 1.0.2 1.2 Apache Commons Lib Apache 2.0 1.2.1 Available under license 1.3 Apache Derby 10.10.1.1 1.3.1 Available under license 1.4 Apache HTTP Server 2.2.9 1.4.1 Available under license 1.5 Apache Jakarta Commons Configuration 1.9 1.5.1 Available under license 1.6 Apache Jakarta Commons Lang 3.1 1.6.1 Available under license 1.7 Apache Log4j 1.2.16 1.7.1 Available under license 1.8 apache-log4j 1.2.15 1.8.1 Available under license 1.9 apache-log4j 1.2.15 :DUPLICATE 1.9.1 Available under license 1.10 apache-log4j-extras-1.0.jar 1.0 1.10.1 Available under license 1.11 args4j 2.0.12 1.11.1 Available under license 1.12 axis 1.2.1 1.12.1 Available under license 1.13 axis-jaxrpc 1.2 1.13.1 Available under license 1.14 axis-saaj 1.2.1 Open Source