DOCSLIB.ORG

Mobile Hosts in Enterprise Service Integration

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Mobile Hosts in Enterprise Service Integration Mobile Hosts in Enterprise Service Integration Von der Fakultät für Mathematik, Informatik und Naturwissenschaften der RWTH Aachen University zur Erlangung des akademischen Grades eines Doktors der Naturwissenschaften genehmigte Dissertation vorgelegt von Master of Science (M.Sc.) Satish Narayana Srirama aus Peddapadmapuram, A.P., India Berichter: Universitätsprofessor Dr. Matthias Jarke, RWTH Aachen Universitätsprofessor Dr. Wolfgang Nejdl, TU Hannover Tag der mündlichen Prüfung: 19. September 2008 Diese Dissertation ist auf den Internetseiten der Hochschulbibliothek online verfügbar. iii Abstract Basic web services are widely being accessed from smart phones due to the advances in wireless devices and mobile communication technologies. While such mobile web service (MWS) clients are common, the thesis addresses the scope of providing web services from smart phones, thus integrating personalized mobile services into cellular enterprises and Internet. A ‘Mobile Host’ capable of providing basic web services from smart phones was developed and the performance analysis of the tool proved the technical feasibility of the concept. Service delivery and management from Mobile Host are now technically feasible. How- ever, the ability to provide proper quality of service (QoS) for the Mobile Host is observed to be very critical, especially in terms of security and reasonable scalability. In the security analysis, the adaptability of the WS- Security specification to the mobile web service provisioning (MWSP) domain is analyzed. The scalability analysis tried to reduce the size of the MWS messages being transmitted by means of different compression technologies. The analyses mainly focused on additional latencies caused to the performance of the Mobile Host by the added QoS features. Mobile Host finds its use in domains like mobile community support, collaborative learning, social systems etc. The smart phone can act as a multi-user device without additional manual effort on part of the mobile user. The thesis extensively studied the appli- cations of Mobile Host in the m-learning domain and developed the MobileHost CoLearn system, as a tool helping in the collaborative learning process. The user evaluation of the system clearly showed the adaptability of Mobile Hosts by different communities. The huge number of web services possible, with each Mobile Host providing some services in the wireless network, makes the discovery of these services quite complex. The traditional centralized UDDI (Universal Description, Discovery and Integration) based registries are not adaptable, as they can have bottlenecks and can make single points of failure. Moreover, the dynamic nature of the mobile nodes makes the binding information change regularly, thus leaving many stale advertisements in the registry. Hence a dynamic MWS discovery mechanism is proposed, that uses the peer to peer network and its features for publishing and discovery of mobile web services. Based on Mobile Host’s application, QoS and discovery research, the deployment scenario of the Mobile Hosts in cellular networks is identified. A ‘Mobile Web Ser- vices Mediation Framework (MWSMF)’ is established as an intermediary between the web service clients and the Mobile Hosts, based on the Enterprise Service Bus (ESB) technology. v Kurzfassung Durch neuere Entwicklungen im Bereich mobiler Geräte haben einfache Web Services, die von Smart Phones aus verwendet werden können, weite Verbreitung gefunden. Während aber MWS Clients bereits weit verbreitet sind, befasst sich diese Arbeit mit der Prob- lematik, Web Services auf Smart Phones bereitzustellen, also mit der Integration personal- isierter mobiler Dienste in Mobilfunknetze und das Internet. Es wurde ein ‘Mobile Host’ entwickelt, der es ermöglicht, einfache Web Services durch Smart Phones anzubieten. Die Performanz-Analyse des Systems hat die technische Machbarkeit des Konzepts bewiesen. Bereitstellung und Verwaltung von Diensten auf mobilen Geräten sind nun technisch machbar. Es hat sich allerdings gezeigt, dass es für den Mobile Host von besonderer Be- deutung ist, eine angemessene Dienst-Qualität (QoS, "quality of service") zu garantieren, insbesondere in Bezug auf Sicherheit und Skalierbarkeit. Bei der Sicherheitsanalyse wurde die Anpassbarkeit der WS-Security-Spezifikation an den Bereich der Bereitstel- lung mobiler Web Services (mobile web service provisioning, MWSP) analysiert. In der Skalierbarkeitsanalyse wurde mit Hilfe verschiedener Komprimierungstechniken versucht, die Größe der übermittelten MWS-Nachrichten zu reduzieren. Der Fokus der Analyse wurde auf die zusätzlichen Latenzzeiten im Mobile Host gelegt, die durch die QoS Merkmale verursacht werden. Anwendungen für Mobile Hosts lassen sich unter anderem in den Bereichen Mobile Community Support, Collaborative Learning und Social Systems finden. Das Smart Phone kann ohne zusätzlichen manuellen Aufwand durch den Anwender als Mehr-Benutzer- Gerät agieren. Im Rahmen der Arbeit wurden Anwendungen für Mobile Hosts im Bereich des m-learning untersucht. So wurde das MobileHost CoLearn System als Werkzeug zur Unterstützung des kollaborativen Lernprozesses entwickelt. Die Nutzer-Evaluaierung des Systems hat die Anpassbarkeit von Mobile Hosts durch verschiedene Communities klar gezeigt. Die hohe Zahl möglicher Web Services, wobei jeder Mobile Host mehrere Dienste im Netzwerk anbieten kann, macht die Ermittlung (discovery) dieser Dienste sehr komplex. Traditionelle zentralisierte UDDI-basierte (Universal Description, Discovery and Inte- gration) registries sind nicht anpassbar, da sie Flaschenhälse aufweisen können und als ’single point of failure’ anfällig sind. Des Weiteren erfordert die dynamische Natur von mobilen Knoten regelmäßige Änderungen der Information über Dienste, wodurch viele veraltete Advertisements in der Registrierung zu finden sind. Daher wird alternativ ein dynamischer MWS-discovery-Mechanismus vorgestellt, der das Peer-to-Peer Netzwerk und seine Merkmale für Publishing und Discovery von Mobile Web Services nutzt. Auf Grundlage bestehender Forschung zu Anwendungen, QoS und Discovery von Mobile Hosts wird ein Deployment-Szenario für Mobile Hosts in Mobilfunknetzen identifiziert. Basierend auf der Enterprise-Service-Bus-Technologie (ESB) wird ein ‘Mobile Web Services Mediation Framework (MWSMF)’ als Schnittstelle zwischen den Web Service Clients und den Mobile Hosts eingeführt. vii Acknowledgements Ever since my engineering days, I always wanted to pursue higher education and head for Doctorate degree. I am fortunate that I could achieve this goal at such a prestigious institute as Rheinisch-Westfaelische Technische Hochschule Aachen (RWTH Aachen). There are several people without whom this dream would not have been a reality. I would like to express my deep and sincere gratitude to all those involved. First of all, I thank Prof. Matthias Jarke for all the support he has extended me, during the past six years. I would also like to thank him for all the confidence he had shown, in me and my work. Secondly, I thank Prof. Wolfgang Nejdl for reviewing the thesis and being my second examiner. Nonetheless I would also like to thank Prof. Wolfgang Prinz and owe him lots of gratitude for having shown me this way of research. I would also like to thank Friedhelm Ramme, Roman Levenshteyn and Martin Gerdes of Ericsson Research for their help and support, during the research. I am especially thankful to Roman Levenshteyn for all his advice, positive criticism, and willingness to discuss any questions or ideas that I have had, during the past years. I would also like to thank all my co-authors: Prof. Matthias Jarke, Prof. Wolfgang Prinz, Mohamed Amine Chatti, David Kensche, Yiwei Cao, Dr. Ralf Klamma, Anton Naumenko, Pravin Pawar, Bert-Jan van Beijnum, Aart van Halteren, Iliyana Ivanova, Hongyan Zhu, Kiran Kumar Pendyala, Kaifei Wang, Rajsekhar Kakumani, Akshaia Aggarwal and Prof. Vagan Terziyan. I am thankful to all my students, whose work contributed my research. The work was initially sponsored by Graduiertenkollegs - "Software für mobile Kom- munikationssysteme" at RWTH Aachen, later by Ultra High-Speed Mobile Information and Communication (UMIC) excellence research cluster, established under the excellence initiative of the German government, and partly supported by Ericsson research. I thank all the funding agencies and appreciate their financial support for my projects. I am also grateful to the Information Systems & Databases Group, at RWTH Aachen for providing me an excellent work environment during the past years. I thank all my colleagues, a slight banter with whom, always made me better focused. I sincerely thank my parents for their never ending support and especially my father, Prof. Lakshminarayana Srirama, for being an inspiration and role model. The blessings of my mother Lolakshi Srirama and the encouragement of my brother Jagadeesh Narayana Srirama, sister Ambika Meesala and brother-in-law Ramesh Naidu Meesala are sincerely acknowledged. Special thanks are to my beloved wife, Gayatri, for her compassion and patience during the last days of my dissertation. Finally I like to thank my friends and relatives for having them on my side, especially Pravin Pawar and Prof. Lakshmana Das Nadukuru for our fruitful discussions before considering the doctoral studies. Aachen Satish Narayana Srirama 22nd September, 2008 Contents Abstract iii Kurzfassung v Acknowledgements vii Contents ix List of Figures xii List of Tables xv 1 Introduction 1 1.1 Motivation . .1 1.2 Contributions
Load more

Recommended publications
  • 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
    [Show full text]
  • Return of Organization Exempt from Income
    OMB No. 1545-0047 Return of Organization Exempt From Income Tax Form 990 Under section 501(c), 527, or 4947(a)(1) of the Internal Revenue Code (except black lung benefit trust or private foundation) Open to Public Department of the Treasury Internal Revenue Service The organization may have to use a copy of this return to satisfy state reporting requirements. Inspection A For the 2011 calendar year, or tax year beginning 5/1/2011 , and ending 4/30/2012 B Check if applicable: C Name of organization The Apache Software Foundation D Employer identification number Address change Doing Business As 47-0825376 Name change Number and street (or P.O. box if mail is not delivered to street address) Room/suite E Telephone number Initial return 1901 Munsey Drive (909) 374-9776 Terminated City or town, state or country, and ZIP + 4 Amended return Forest Hill MD 21050-2747 G Gross receipts $ 554,439 Application pending F Name and address of principal officer: H(a) Is this a group return for affiliates? Yes X No Jim Jagielski 1901 Munsey Drive, Forest Hill, MD 21050-2747 H(b) Are all affiliates included? Yes No I Tax-exempt status: X 501(c)(3) 501(c) ( ) (insert no.) 4947(a)(1) or 527 If "No," attach a list. (see instructions) J Website: http://www.apache.org/ H(c) Group exemption number K Form of organization: X Corporation Trust Association Other L Year of formation: 1999 M State of legal domicile: MD Part I Summary 1 Briefly describe the organization's mission or most significant activities: to provide open source software to the public that we sponsor free of charge 2 Check this box if the organization discontinued its operations or disposed of more than 25% of its net assets.
    [Show full text]
  • Apache Karaf Users' Guide
    Apache Karaf Users' Guide Copyright 2010 The Apache Software Foundation 1 Table of contents • 1. Overview • 2. Quick start • 2.1. Quick Start (Source) • 3. Installation • 4. Understanding Karaf • 4.1. Console and Commands • 4.2. Remote Console • 4.3. Logging system • 4.4. Deployer • 4.5. Security framework • 4.6. Provisioning • 4.7. Administration • 4.8. Configuration • 5. Using Karaf • 5.1. Troubleshooting, Debugging and Profiling • 5.2. Developping applications • 5.3. Creating bundles for third party dependencies • 6. Advanced uses • 6.1. Extending the console • 6.2. Building custom distributions • 6.3. Programmatically connect to the console • 6.4. Embedding Karaf • 6.5. Deploying security providers • 6.6. Installing additional features • 6.7. Configuring Failover Deployments • 7. Optional Features • 7.1. Enabling Colorized Console Output On Windows 2 1. Overview Apache Karaf is a small OSGi based runtime which provides a lightweight container onto which various components and applications can be deployed. Here is a short list of features supported by the Karaf: • Hot deployment: Karaf supports hot deployment of OSGi bundles by monitoring jar files inside the [home]/deploy directory. Each time a jar is copied in this folder, it will be installed inside the runtime. You can then update or delete it and changes will be handled automatically. In addition, the Karaf also supports exploded bundles and custom deployers (blueprint and spring ones are included by default). • Dynamic configuration: Services are usually configured through the ConfigurationAdmin OSGi service. Such configuration can be defined in Karaf using property files inside the [home]/etc directory. These configurations are monitored and changes on the properties files will be propagated to the services.
    [Show full text]
  • Apache Karaf 2.2.3, the Transitive Dependencies for This POM and the Bundles Listed in Src/Main/Resources/ Bundles.Properties
    Apache Karaf Version 2.2.3 Apache Karaf Users' Guide 1 Copyright 2011 The Apache Software Foundation 2 Table of contents Overview Quick Start Users Guide Developers Guide 3 Overview 4 OVERVIEW Karaf Overview Apache Karaf is a small OSGi based runtime which provides a lightweight container onto which various components and applications can be deployed. Here is a short list of features supported by the Karaf: • Hot deployment: Karaf supports hot deployment of OSGi bundles by monitoring jar files inside the [home]/deploy directory. Each time a jar is copied in this folder, it will be installed inside the runtime. You can then update or delete it and changes will be handled automatically. In addition, Karaf also supports exploded bundles and custom deployers (Blueprint and Spring ones are included by default). • Dynamic configuration: Services are usually configured through the ConfigurationAdmin OSGi service. Such configuration can be defined in Karaf using property files inside the [home]/etc directory. These configurations are monitored and changes on the properties files will be propagated to the services. • Logging System: using a centralized logging back end supported by Log4J, Karaf supports a number of different APIs (JDK 1.4, JCL, SLF4J, Avalon, Tomcat, OSGi) • Provisioning: Provisioning of libraries or applications can be done through a number of different ways, by which they will be downloaded locally, installed and started. • Native OS integration: Karaf can be integrated into your own Operating System as a service so that the lifecycle will be bound to your Operating System. • Extensible Shell console: Karaf features a nice text console where you can manage the services, install new applications or libraries and manage their state.
    [Show full text]
  • Hänninen, Arttu Enterprise Integration Patterns in Service Oriented Systems Master of Science Thesis
    CORE Metadata, citation and similar papers at core.ac.uk Provided by Trepo - Institutional Repository of Tampere University Hänninen, Arttu Enterprise Integration Patterns in Service Oriented Systems Master of Science Thesis Examiner: Prof. Tommi Mikkonen Examiners and topic approved in the council meeting of Faculty of Information Technology on April 3rd, 2013. II TIIVISTELMÄ TAMPEREEN TEKNILLINEN YLIOPISTO Tietotekniikan koulutusohjelma Hänninen, Arttu: Enterprise Integration Patterns in Service Oriented Systems Diplomityö, 58 sivua Kesäkuu 2014 Pääaine: Ohjelmistotuotanto Tarkastajat: Prof. Tommi Mikkonen Avainsanat: Enterprise Integration Patterns, Palvelukeskeinen arkkitehtuuri (SOA), Viestipohjainen integraatio Palvelupohjaisen integraation toteuttaminen mihin tahansa tietojärjestelmään on haas- tavaa, sillä integraatioon liittyvät järjestelmät voivat muuttua jatkuvasti. Integraatiototeu- tusten tulee olla tarpeeksi joustavia, jotta ne pystyvät mukautumaan mahdollisiin muu- toksiin. Toteutukseen voidaan käyttää apuna eri sovelluskehyksiä, mutta ne eivät vält- tämättä takaa mitään standardoitua tapaa tehdä integraatio. Tätä varten on luotu joukko ohjeita (Enterprise Integration Patterns, EIP), jotka kuvaavat hyväksi havaittuja tapoja tehdä integraatioita. Tässä työssä keskitytään näiden mallien tutkimiseen ja siihen, miten niitä voidaan hyödyntää yritysjärjestelmissä. Jotta tutkimukseen saadaan konkreettinen vertailutulos, erään järjestelmän integraatioratkaisu tullaan päivittämään uuteen. Uusi ratkaisu hyödyntää sovelluskehystä,
    [Show full text]
  • Full-Graph-Limited-Mvn-Deps.Pdf
    org.jboss.cl.jboss-cl-2.0.9.GA org.jboss.cl.jboss-cl-parent-2.2.1.GA org.jboss.cl.jboss-classloader-N/A org.jboss.cl.jboss-classloading-vfs-N/A org.jboss.cl.jboss-classloading-N/A org.primefaces.extensions.master-pom-1.0.0 org.sonatype.mercury.mercury-mp3-1.0-alpha-1 org.primefaces.themes.overcast-${primefaces.theme.version} org.primefaces.themes.dark-hive-${primefaces.theme.version}org.primefaces.themes.humanity-${primefaces.theme.version}org.primefaces.themes.le-frog-${primefaces.theme.version} org.primefaces.themes.south-street-${primefaces.theme.version}org.primefaces.themes.sunny-${primefaces.theme.version}org.primefaces.themes.hot-sneaks-${primefaces.theme.version}org.primefaces.themes.cupertino-${primefaces.theme.version} org.primefaces.themes.trontastic-${primefaces.theme.version}org.primefaces.themes.excite-bike-${primefaces.theme.version} org.apache.maven.mercury.mercury-external-N/A org.primefaces.themes.redmond-${primefaces.theme.version}org.primefaces.themes.afterwork-${primefaces.theme.version}org.primefaces.themes.glass-x-${primefaces.theme.version}org.primefaces.themes.home-${primefaces.theme.version} org.primefaces.themes.black-tie-${primefaces.theme.version}org.primefaces.themes.eggplant-${primefaces.theme.version} org.apache.maven.mercury.mercury-repo-remote-m2-N/Aorg.apache.maven.mercury.mercury-md-sat-N/A org.primefaces.themes.ui-lightness-${primefaces.theme.version}org.primefaces.themes.midnight-${primefaces.theme.version}org.primefaces.themes.mint-choc-${primefaces.theme.version}org.primefaces.themes.afternoon-${primefaces.theme.version}org.primefaces.themes.dot-luv-${primefaces.theme.version}org.primefaces.themes.smoothness-${primefaces.theme.version}org.primefaces.themes.swanky-purse-${primefaces.theme.version}
    [Show full text]
  • Talend Open Studio for Big Data Release Notes
    Talend Open Studio for Big Data Release Notes 6.5.1 Contents Copyleft.......................................................................................................................3 System requirements...................................................................................................4 Talend Open Studio for Big Data: new features........................................................4 Talend Open Studio for Big Data: bug fixes............................................................. 7 Talend Open Studio for Big Data: deprecated items................................................. 7 Talend Open Studio for Big Data: known issues and limitations...............................7 Talend Open Studio for Big Data: hints and notes.................................................... 8 Documentation............................................................................................................ 9 Reporting defects and issues.................................................................................... 10 Talend Open Studio for Big Data 6.5.1 © Talend 2018 Copyleft Adapted for 6.5.1. Supersedes previous releases. Publication date: January 18, 2018 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
    [Show full text]
  • Service Oriented Integration with Servicemix and Camel
    Service Oriented Integration with ServiceMix and Camel Chris Custine Principal Engineer IONA Technologies Agenda What is an ESB? What is JBI? Introduction to ServiceMix Introduction to Camel ServiceMix and Camel Working Together Roadmap for Servicemix 4.0 2 © 2007 IONA Technologies What is... an ESB? 3 © 2007 IONA Technologies What is an ESB? "An Enterprise Service Bus (ESB) is a new architecture that exploits Web services, messaging middleware, intelligent routing, and transformation. ESBs act as a lightweight, ubiquitous integration backbone through which software services and application components flow.” (Gartner) 4 © 2007 IONA Technologies What is an ESB? An ESB acts as a shared messaging layer for connecting applications and other services throughout an enterprise computing infrastructure. It supplements its core asynchronous messaging backbone with intelligent transformation and routing to ensure messages are passed reliably. Services participate in the ESB using either web services messaging standards or JMS (LooselyCoupled.com) 5 © 2007 IONA Technologies What is an ESB? An ESB is an open standards, message-based, distributed, integration solution that provides routing, invocation, and mediation services to facilitate the interactions of disparate distributed information technology resources (applications, services, information, platforms) in a reliable manner. (Brenda Michelson, Elemental Links) 6 © 2007 IONA Technologies What is... JBI? 7 © 2007 IONA Technologies What is JBI? JBI defines an architecture that allows the construction
    [Show full text]
  • Apache Karaf 2.4.1 Guides
    Apache Karaf Version 2.4.1 Apache Karaf Users' Guide 1 Copyright 2011 The Apache Software Foundation The PDF format of the Karaf Manual has been generated by Prince XML (http://www.princexml.com). 2 Table of contents Overview Quick Start Users Guide Developers Guide 3 Overview 4 OVERVIEW Karaf Overview Apache Karaf is a small OSGi based runtime which provides a lightweight container onto which various components and applications can be deployed. Here is a short list of features supported by the Karaf: • Hot deployment: Karaf supports hot deployment of OSGi bundles by monitoring jar files inside the deploy directory. Each time a jar is copied in this folder, it will be installed inside the runtime. You can then update or delete it and changes will be handled automatically. In addition, Karaf also supports exploded bundles and custom deployers (Blueprint and Spring ones are included by default). • Dynamic configuration: Services are usually configured through the ConfigurationAdmin OSGi service. Such configuration can be defined in Karaf using property files inside the etc directory. These configurations are monitored and changes on the properties files will be propagated to the services. • Logging System: using a centralized logging back end supported by Log4J, Karaf supports a number of different APIs (JDK 1.4, JCL, SLF4J, Avalon, Tomcat, OSGi) • Provisioning: Provisioning of libraries or applications can be done through a number of different ways, by which they will be downloaded locally, installed and started. • Native OS integration: Karaf can be integrated into your own Operating System as a service so that the lifecycle will be bound to your Operating System.
    [Show full text]
  • Red Hat Fuse 7.3 Release Notes
    Red Hat Fuse 7.3 Release Notes What's new in Red Hat Fuse Last Updated: 2020-06-26 Red Hat Fuse 7.3 Release Notes What's new in Red Hat Fuse Legal Notice Copyright © 2020 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Interop.Jar Activation
    Resource name License name License reference Usage Type a-j-interop.jar Eclipse 1.0 http://www.j-interop.org/license.html Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/activation/act activation-1.1.jar CDDL 1.0 ivation/1.1/activation-1.1.pom Dynamic library activation.jar LGPL 2.1 https://github.com/wildfly/wildfly/blob/master/README.md Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/activem activemq-all-5.7.0.jar Apache 2.0 q/activemq-all/5.7.0/activemq-all-5.7.0.pom Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/activem activemq-core-5.7.0.jar Apache 2.0 q/activemq-core/5.7.0/activemq-core-5.7.0.pom Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/activem activemq-pool-5.7.0.jar Apache 2.0 q/activemq-pool/5.7.0/activemq-pool-5.7.0.pom Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/activem activemq-protobuf-1.1.jar Apache 2.0 q/protobuf/activemq-protobuf/1.1/activemq-protobuf-1.1.pom Dynamic library http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/axis2/a addressing-1.6.2.jar Apache 2.0 ddressing/1.6.2/addressing-1.6.2.pom Dynamic library advancedPersistentLookupLib-1.0.jar Commercial http://www.talend.com Dynamic library aether-api-1.11.jar Eclipse 1.0 https://www.eclipse.org/aether/download/ Dynamic library aether-connector-asynchttpclient-1.11.jar Eclipse 1.0 https://www.eclipse.org/aether/download/ Dynamic library aether-connector-wagon-1.11.jar Eclipse 1.0 https://www.eclipse.org/aether/download/ Dynamic
    [Show full text]
  • Apache Karaf Cave 4.X - Documentation Apache Software Foundation
    Apache Karaf Cave 4.x - Documentation Apache Software Foundation Apache Karaf Cave 4.x - Documentation Overview User Guide 1. Installation 1.1. Pre-installation requirements 1.2. Registration of the Apache Karaf Cave features 1.3. Starting Apache Karaf Cave Server 2. Repository 2.1. Create 2.2. List 3. Populate repository 3.1. Upload a single artifact 3.2. Populate from an external repository 4. Proxy repository 5. HTTP wrapper service 5.1. Repository metadata access 6. Maven wrapper service 7. Administration 7.1. JMX 7.2. REST Overview Apache Karaf Cave is an Apache Karaf sub-project. Cave is an implementation of the OSGi Repository specification, providing additional features such as a complete Maven repository support, a REST API for management, support of remote repository proxy. Cave deals with the requirements and capabilities of all artifacts. Apache Karaf Cave provides the following features: • Storage: Cave includes a storage backend. The default one is a simple filesystem backend. As the Cave backend is designed in a plugin way, you can implement your own backend (for instance, JDBC or LDAP backend). • Repository Metadata Generation: Cave creates the repository metadata for you, using the artifacts presents in the repository storage. • Maven support: Cave repositories act as a complete Maven repository, allowing you to use Cave directly with Maven. • REST API: Cave provides a REST API to manipulate the repositories. • Artifact Upload: Users can upload OSGi bundle in a Cave repository. It supports URLs like mvn:groupId/artifactId/version, file:, http:, etc. • Repository proxy: Cave is able to proxy an existing repository, for instance an existing Maven repository.
    [Show full text]