OSGi is a modular system and service platform for Java applications that implements a dynamic component model. It allows components called bundles to be installed, started, stopped, updated, and uninstalled remotely without requiring a reboot. Each bundle has its own classloader and dependencies. OSGi supports a service registry that allows bundles to detect when new services are added or removed. Popular implementations of the OSGi framework include Apache Karaf, Apache ServiceMix, and JBoss Fuse.
OSGi For Java Infrastructures [5th IndicThreads Conference On Java 2010, Pune...IndicThreads
Session Presented at 5th IndicThreads.com Conference On Java held on 10-11 December 2010 in Pune, India
WEB: http://J10.IndicThreads.com
------------
Session Abstract
OSGi continues to take over the landscape of Java-based infrastructure products ranging from Integrated Development Environment (like Eclipse), Application servers to enterprise Java systems and now setting horizons at Cloud infrastructures.
In this talk we will see how and why OSGi matters for enterprise Java systems. As a dynamic module system, the session will show how OSGi allows developers to modularize applications to create truly reusable components for enterprise scale. Features like strong modularity, versioning support, declarative services, the run-time ability to add, remove & update modules to build server-side enterprise applications will be discussed.
The session will deep dive into what’s new in OSGi enterprise specifications and how persistence, transaction and dependency injection support like Blueprint Container services addresses Enterprise use cases. The session will illustrate how OSGi Remote Services coupled with SCA configuration services enables creation of distributed, federated service model for heterogeneous systems. Along with above enterprise specifications, specific implementations like Apache Aries will also be highlighted.
The talk will also brief how OSGi is poised to one of key technology for Cloud computing where software components and services can be deployed, managed, dynamically provisioned with enterprise security within cloud based computing infrastructures.
Takeaways for the Audience In this session, audience will learn about:
(a) An overall understanding to view OSGi as THE module system for Java.
(b) How OSGi is poised to be key enabler for enterprise applications whether on servers, or on the cloud.
(c) How OSGi Enterprise specifications can be used in enterprise business applications.
(d) A better understanding of how OSGI will be key technology in Cloud infrastructures
Modules all the way down: OSGi and the Java Platform Module SystemTim Ellison
A talk about the Java Platform Module System defined in JSR 376, and OSGi modularity. Originally delivered at the OSGi Community Event held in conjunction with the EclipseCon Europe 2015 conference in Ludwigsburg, Germany.
OSGi For Java Infrastructures [5th IndicThreads Conference On Java 2010, Pune...IndicThreads
Session Presented at 5th IndicThreads.com Conference On Java held on 10-11 December 2010 in Pune, India
WEB: http://J10.IndicThreads.com
------------
Session Abstract
OSGi continues to take over the landscape of Java-based infrastructure products ranging from Integrated Development Environment (like Eclipse), Application servers to enterprise Java systems and now setting horizons at Cloud infrastructures.
In this talk we will see how and why OSGi matters for enterprise Java systems. As a dynamic module system, the session will show how OSGi allows developers to modularize applications to create truly reusable components for enterprise scale. Features like strong modularity, versioning support, declarative services, the run-time ability to add, remove & update modules to build server-side enterprise applications will be discussed.
The session will deep dive into what’s new in OSGi enterprise specifications and how persistence, transaction and dependency injection support like Blueprint Container services addresses Enterprise use cases. The session will illustrate how OSGi Remote Services coupled with SCA configuration services enables creation of distributed, federated service model for heterogeneous systems. Along with above enterprise specifications, specific implementations like Apache Aries will also be highlighted.
The talk will also brief how OSGi is poised to one of key technology for Cloud computing where software components and services can be deployed, managed, dynamically provisioned with enterprise security within cloud based computing infrastructures.
Takeaways for the Audience In this session, audience will learn about:
(a) An overall understanding to view OSGi as THE module system for Java.
(b) How OSGi is poised to be key enabler for enterprise applications whether on servers, or on the cloud.
(c) How OSGi Enterprise specifications can be used in enterprise business applications.
(d) A better understanding of how OSGI will be key technology in Cloud infrastructures
Modules all the way down: OSGi and the Java Platform Module SystemTim Ellison
A talk about the Java Platform Module System defined in JSR 376, and OSGi modularity. Originally delivered at the OSGi Community Event held in conjunction with the EclipseCon Europe 2015 conference in Ludwigsburg, Germany.
Mit Java 8, Jigsaw und JSR 294 soll über die Java-Plattform ein vereinheitlichtes Modularisierungskonzept eingeführt und die seit 2005 apostrophierte "post-jar-File-Ära" eingeläutet werden.
Etablierte Konzepte und Vorgehensweisen zur Modularisierung wie OSGi und JEE werden in der Session den Ideen von Java 8 gegenübergestellt und der architektonische Aspekt in der technologischen Debatte hinterfragt.
Talk given at JavaOne 2009 discussing how to build web applications using OSGi. The source for the demo found at http://github.com/mrdon/jforum-plugins/tree/master
Session Abstract: Enterprise Web applications tend to grow like weeds in monolithic complexity. OSGi, although more often associated with Java™ technology-based clients and application servers, can bring a new level of modularity, uptime, and stability that is needed with today's always-on hosted Web applications. OSGi gets really interesting when the pretty architecture diagrams meet the real world, because it consists of various deployment platforms, development environments, and application architectures. This presentation, for Java 2 Platform, Enterprise Edition (J2EE™ platform)-savvy architects and senior developers, provides a practical guide to the Web on OSGi, from integration approach to bundle development, to real-world code you can use today.
The session discusses
• What benefits OSGi brings to the J2EE platform
• Three integration strategies
• How to use Spring DM and Maven to ease development
• Lessons learned from Atlassian's recent OSGi deployment
• A production-ready example to use immediately
Travelling Light for the Long Haul - Ian Robinsonmfrancis
OSGi Community Event 2013 (http://www.osgi.org/CommunityEvent2013/Schedule)
ABSTRACT
One of the attractive qualities of OSGi is its role in enabling technologies that adopt it to manage the cost of their own success. Anything that gains adoption - in technology or elsewhere - picks up baggage as a result and needs to figure out how to deal with current installations while expanding in new directions. The WebSphere platform has been around for almost as long as Java and knows a thing or two about baggage but still manages to travel to many places with just a carry-on allowance. We adopted OSGi internally 8 years ago and have gradually increased our exploitation with each passing release, most recently and deeply with the lightweight WAS Liberty Profile. It hasn't all been plain sailing and we learned from a number of mistakes made along the way. When WebSphere Application Server first adopted OSGi it had over 10 million lines of code in a modest number of huge JARs. The engineering effort to modularize that into a “sensible” number of OSGi bundles was fairly significant. We had a global development team spread across a dozen labs and nearly as many timezones, all learning OSGi principles at the same time. What could possibly go wrong? I’ll spend a little time reviewing the consequences of our bundles-first-services-later approach but our success was initially limited to having the equivalent of a well-organized and large container ship which could travel at speed but needed a pretty wide berth. Our initial investment in OSGi delivered on most of the internal benefits we wanted but failed on some of the external ones that matter to our customers.
Application Servers are used in different ways by Developers and IT Operations. Ops teams care about the overall cost, including performance and availability, of the platform and the applications it supports; Dev teams care about how quickly and easily they can create and deliver their applications and treat the server as a tool. Only some of them know or care about OSGi; multi-channel enablement and cloud deployment are the current pressures they are under. Today, WebSphere is a consumer of OSGi in two distinct fashions. Internally we learned from our earlier experiences and embraced an OSGi services model to enable us to run the same runtime just as fast but in a far more dynamic fashion: it’s how we can start/stop individual technologies of the Java EE Web Profile independently on the WAS Liberty profile, in a 50MB install with a 2-second startup while still support all our customers’ existing deployments. Externally we support both Enterprise OSGi and traditional Java EE as application programming models, on the same runtime and using the same Eclipse-based tools. Our customers who understand and care about OSGi can develop and deploy web application bundles and multi-bundle enterprise applications. Those who don’t care about OSGi benefit from it ind
Modularity of the Java Platform (OSGi, Jigsaw and Penrose)Martin Toshev
Seminar "Modularity of the Java Platform" of the Bulgarian Java User Group.
Topics of the seminar:
Modularity 101
Modularity on top of the platform: OSGi
Modularity of the platform: Jigsaw
OSGi and Jigsaw interoperability: Penrose
The Power of Enterprise Java FrameworksClarence Ho
Topics:
- What is an Enterprise Java Framework
- Overview of popular Enterprise Java Frameworks
- The most popular Enterprise Java framework - Spring Framework
- Conclusion
Microservices promise a scalable architecture, increased flexibility, and better performance. But then you find out what’s actually involved in designing, developing, and running a microservices-based architecture. It turns out it’s not that straightforward after all.
Often the discussion around microservices is framed by a false dichotomy between the messy monolith and the lean and mean microservices architecture. Sander Mak explains that there’s a third way: the modularized application. Functional decomposition of your application doesn’t imply that every component has to become its own independent process.
Modularization is about strong encapsulation, well-defined interfaces, and explicit dependencies. Many languages offer in-process modularization features (for example, Java 9 with its upcoming module system), and there’s a strong overlap between the microservices philosophy and development benefits—without incurring the penalty of operational complexity.
Sander explores the right (and wrong) reasons for going with a microservices architecture, as well as what a modularized application entails. You’ll see that splitting up an existing service or application into microservices isn’t always the clear winner. You’ll leave able to choose between the alternatives for the right reasons. There’s a place for both independently deployed microservices and larger applications with a strong internal modular structure. Choose wisely.
Liferay DevCon 2014: Lliferay Platform - A new and exciting visionJorge Ferrer
Liferay is very well known as a good platform for building portals. It provides a nice combination of out of the box features, extensibility and application development options to build almost any website, portal or complex application without starting from scratch every time. But is that all it can do?
For a few years the development world has been focusing more and more on developing for mobile and tablets, glasses and TVs or even provide public web APIs for any developers to build on top of a company’s services and content. And we have noticed “There isn’t a Liferay for those developers!”, most of that type development is started from scratch, “What if Liferay filled that gap?”
During this talk we will show how the most recent developments of the Liferay team are building a more versatile and modular platform than ever, an environment to leverage the most modern frontend development tools for enterprise needs, a set of tools to build mobile apps (for any device) with a powerful backend in a tenth of the time it typically takes. And all of it Open Source and fully standards based.
Liferay Italy Symposium 2015 Liferay Mobile SDK and Liferay ScreensDenis Signoretto
Liferay Italy Symposium 2015 Liferay Mobile SDK and Liferay Screens, Building and Android App with Liferay (Using Liferay as Mobile Backend and Screens for reusable mobile compoents)
VirtualNuggets Offering All Java Technologies Corporate Online Training Services .Here VirtualNuggets Publishing Free Hibernate Tutorials For Java Learners .Topics Covers in Tutorial are Spring Overview,
Spring Architecture,
Spring Environment Setup
Spring Hello World Example
Spring IoC Containers
Spring Bean Definition
Spring Bean Scopes
Spring Bean Life Cycle
Spring Bean Post Processors
Spring Bean Definition Inheritance
Spring Dependency Injection
Spring Injecting Inner Beans
Spring Injecting Collection
Spring Beans Auto-Wiring
Spring Annotation Based Configuration
Spring Java Based Configuration
Spring Event Handling in Spring
Spring Custom Events in Spring
Spring AOP with Spring Framework
Spring JDBC Framework
Spring Transaction Management
Spring Web MVC Framework
Spring Logging with Log4J
Mit Java 8, Jigsaw und JSR 294 soll über die Java-Plattform ein vereinheitlichtes Modularisierungskonzept eingeführt und die seit 2005 apostrophierte "post-jar-File-Ära" eingeläutet werden.
Etablierte Konzepte und Vorgehensweisen zur Modularisierung wie OSGi und JEE werden in der Session den Ideen von Java 8 gegenübergestellt und der architektonische Aspekt in der technologischen Debatte hinterfragt.
Talk given at JavaOne 2009 discussing how to build web applications using OSGi. The source for the demo found at http://github.com/mrdon/jforum-plugins/tree/master
Session Abstract: Enterprise Web applications tend to grow like weeds in monolithic complexity. OSGi, although more often associated with Java™ technology-based clients and application servers, can bring a new level of modularity, uptime, and stability that is needed with today's always-on hosted Web applications. OSGi gets really interesting when the pretty architecture diagrams meet the real world, because it consists of various deployment platforms, development environments, and application architectures. This presentation, for Java 2 Platform, Enterprise Edition (J2EE™ platform)-savvy architects and senior developers, provides a practical guide to the Web on OSGi, from integration approach to bundle development, to real-world code you can use today.
The session discusses
• What benefits OSGi brings to the J2EE platform
• Three integration strategies
• How to use Spring DM and Maven to ease development
• Lessons learned from Atlassian's recent OSGi deployment
• A production-ready example to use immediately
Travelling Light for the Long Haul - Ian Robinsonmfrancis
OSGi Community Event 2013 (http://www.osgi.org/CommunityEvent2013/Schedule)
ABSTRACT
One of the attractive qualities of OSGi is its role in enabling technologies that adopt it to manage the cost of their own success. Anything that gains adoption - in technology or elsewhere - picks up baggage as a result and needs to figure out how to deal with current installations while expanding in new directions. The WebSphere platform has been around for almost as long as Java and knows a thing or two about baggage but still manages to travel to many places with just a carry-on allowance. We adopted OSGi internally 8 years ago and have gradually increased our exploitation with each passing release, most recently and deeply with the lightweight WAS Liberty Profile. It hasn't all been plain sailing and we learned from a number of mistakes made along the way. When WebSphere Application Server first adopted OSGi it had over 10 million lines of code in a modest number of huge JARs. The engineering effort to modularize that into a “sensible” number of OSGi bundles was fairly significant. We had a global development team spread across a dozen labs and nearly as many timezones, all learning OSGi principles at the same time. What could possibly go wrong? I’ll spend a little time reviewing the consequences of our bundles-first-services-later approach but our success was initially limited to having the equivalent of a well-organized and large container ship which could travel at speed but needed a pretty wide berth. Our initial investment in OSGi delivered on most of the internal benefits we wanted but failed on some of the external ones that matter to our customers.
Application Servers are used in different ways by Developers and IT Operations. Ops teams care about the overall cost, including performance and availability, of the platform and the applications it supports; Dev teams care about how quickly and easily they can create and deliver their applications and treat the server as a tool. Only some of them know or care about OSGi; multi-channel enablement and cloud deployment are the current pressures they are under. Today, WebSphere is a consumer of OSGi in two distinct fashions. Internally we learned from our earlier experiences and embraced an OSGi services model to enable us to run the same runtime just as fast but in a far more dynamic fashion: it’s how we can start/stop individual technologies of the Java EE Web Profile independently on the WAS Liberty profile, in a 50MB install with a 2-second startup while still support all our customers’ existing deployments. Externally we support both Enterprise OSGi and traditional Java EE as application programming models, on the same runtime and using the same Eclipse-based tools. Our customers who understand and care about OSGi can develop and deploy web application bundles and multi-bundle enterprise applications. Those who don’t care about OSGi benefit from it ind
Modularity of the Java Platform (OSGi, Jigsaw and Penrose)Martin Toshev
Seminar "Modularity of the Java Platform" of the Bulgarian Java User Group.
Topics of the seminar:
Modularity 101
Modularity on top of the platform: OSGi
Modularity of the platform: Jigsaw
OSGi and Jigsaw interoperability: Penrose
The Power of Enterprise Java FrameworksClarence Ho
Topics:
- What is an Enterprise Java Framework
- Overview of popular Enterprise Java Frameworks
- The most popular Enterprise Java framework - Spring Framework
- Conclusion
Microservices promise a scalable architecture, increased flexibility, and better performance. But then you find out what’s actually involved in designing, developing, and running a microservices-based architecture. It turns out it’s not that straightforward after all.
Often the discussion around microservices is framed by a false dichotomy between the messy monolith and the lean and mean microservices architecture. Sander Mak explains that there’s a third way: the modularized application. Functional decomposition of your application doesn’t imply that every component has to become its own independent process.
Modularization is about strong encapsulation, well-defined interfaces, and explicit dependencies. Many languages offer in-process modularization features (for example, Java 9 with its upcoming module system), and there’s a strong overlap between the microservices philosophy and development benefits—without incurring the penalty of operational complexity.
Sander explores the right (and wrong) reasons for going with a microservices architecture, as well as what a modularized application entails. You’ll see that splitting up an existing service or application into microservices isn’t always the clear winner. You’ll leave able to choose between the alternatives for the right reasons. There’s a place for both independently deployed microservices and larger applications with a strong internal modular structure. Choose wisely.
Liferay DevCon 2014: Lliferay Platform - A new and exciting visionJorge Ferrer
Liferay is very well known as a good platform for building portals. It provides a nice combination of out of the box features, extensibility and application development options to build almost any website, portal or complex application without starting from scratch every time. But is that all it can do?
For a few years the development world has been focusing more and more on developing for mobile and tablets, glasses and TVs or even provide public web APIs for any developers to build on top of a company’s services and content. And we have noticed “There isn’t a Liferay for those developers!”, most of that type development is started from scratch, “What if Liferay filled that gap?”
During this talk we will show how the most recent developments of the Liferay team are building a more versatile and modular platform than ever, an environment to leverage the most modern frontend development tools for enterprise needs, a set of tools to build mobile apps (for any device) with a powerful backend in a tenth of the time it typically takes. And all of it Open Source and fully standards based.
Liferay Italy Symposium 2015 Liferay Mobile SDK and Liferay ScreensDenis Signoretto
Liferay Italy Symposium 2015 Liferay Mobile SDK and Liferay Screens, Building and Android App with Liferay (Using Liferay as Mobile Backend and Screens for reusable mobile compoents)
VirtualNuggets Offering All Java Technologies Corporate Online Training Services .Here VirtualNuggets Publishing Free Hibernate Tutorials For Java Learners .Topics Covers in Tutorial are Spring Overview,
Spring Architecture,
Spring Environment Setup
Spring Hello World Example
Spring IoC Containers
Spring Bean Definition
Spring Bean Scopes
Spring Bean Life Cycle
Spring Bean Post Processors
Spring Bean Definition Inheritance
Spring Dependency Injection
Spring Injecting Inner Beans
Spring Injecting Collection
Spring Beans Auto-Wiring
Spring Annotation Based Configuration
Spring Java Based Configuration
Spring Event Handling in Spring
Spring Custom Events in Spring
Spring AOP with Spring Framework
Spring JDBC Framework
Spring Transaction Management
Spring Web MVC Framework
Spring Logging with Log4J
OSGi & Java EE: A hybrid approach to Enterprise Java Application Development,...OpenBlend society
There's a considerable activity in the enterprise Java community about the use of OSGi in Java EE applications. We call such applications "hybrid applications." With hybrid applications, developers can continue to build standard and familiar enterprise application components, such as Java Servlets and EJBs, and take full advantage of:
* Features such as modularity/dependency management, service dynamism, and more provided by OSGi
* Infrastructure services such as transaction management, security, persistence, and more offered by Java EE
This session will present the current state of affairs, discuss the benefits of hybrid applications, and demonstrate development and deployment of such applications.
GlassFish will be used for demonstration.
GlassFish architect Jerome Dochez presents the architecture (kernel, services, extensibility) and the status of GlassFish v3, a lightweight and modular application server based on OSGi and able to run both Java (EE) and scripting (Rails, Grails, PHP, etc...) applications. Fairly technical.
Liberate your components with OSGi services - Graham Chartersmfrancis
OSGi DevCon 2013
Converting any large application to be OSGi based is a difficult and complex process. Many projects find the fences that OSGi put in place puts insurmountable barriers in the way of success. Many projects get a short way through to embrace the concept of modules, but frequently they get no further and as a result they do not see the many benefits of OSGi.
In this talk the Graham will discuss the trails and tribulations of moving a large software product (WebSphere Application Server) to being based on OSGi and how the new liberty profile embraces OSGi services to produce a more lightweight and flexible server runtime.
For those aware of the Modularity Maturity Model the liberty project aims to move WebSphere Application Server from Level 2 to Level 6.
The talk finishes with an awesome demo of modular hardware paired with modular software showing how building up physical modular tinker-forge bricks crafts the WebSphere App Server by deploying features and applications! A real hands on display of OSGi modularity.
Open Services Gateway Initiative (OSGI)Peter R. Egli
OSGi is a component-based technology and was developed to provide a software platform that allows modularization and dynamic linking of application components.
OSGi components are called bundles and can be exported and imported by application bundles.
OSGi implementations like Apache Felix or Eclipse Equinox provide a runtime container which controls the lifecycle of bundles.
Even though OSGi is hardware independent, it is based on the Java Virtual Machine and as such extends the concepts of the underlying Java language.
An OSGi bundle's capabilities and properties are defined in a manifest file that is packed together with the bundle's Java class files. The manifest file allows compatibility checks by the OSGi runtime between the exporting bundle and the importing bundle.
This export and import mechanism allows highly flexible and dynamic application environments where applications and components are installed, linked and started at runtime without the need to restart the entire system.
May Marketo Masterclass, London MUG May 22 2024.pdfAdele Miller
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
Enhancing Research Orchestration Capabilities at ORNL.pdfGlobus
Cross-facility research orchestration comes with ever-changing constraints regarding the availability and suitability of various compute and data resources. In short, a flexible data and processing fabric is needed to enable the dynamic redirection of data and compute tasks throughout the lifecycle of an experiment. In this talk, we illustrate how we easily leveraged Globus services to instrument the ACE research testbed at the Oak Ridge Leadership Computing Facility with flexible data and task orchestration capabilities.
Globus Connect Server Deep Dive - GlobusWorld 2024Globus
We explore the Globus Connect Server (GCS) architecture and experiment with advanced configuration options and use cases. This content is targeted at system administrators who are familiar with GCS and currently operate—or are planning to operate—broader deployments at their institution.
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
First Steps with Globus Compute Multi-User EndpointsGlobus
In this presentation we will share our experiences around getting started with the Globus Compute multi-user endpoint. Working with the Pharmacology group at the University of Auckland, we have previously written an application using Globus Compute that can offload computationally expensive steps in the researcher's workflows, which they wish to manage from their familiar Windows environments, onto the NeSI (New Zealand eScience Infrastructure) cluster. Some of the challenges we have encountered were that each researcher had to set up and manage their own single-user globus compute endpoint and that the workloads had varying resource requirements (CPUs, memory and wall time) between different runs. We hope that the multi-user endpoint will help to address these challenges and share an update on our progress here.
Check out the webinar slides to learn more about how XfilesPro transforms Salesforce document management by leveraging its world-class applications. For more details, please connect with sales@xfilespro.com
If you want to watch the on-demand webinar, please click here: https://www.xfilespro.com/webinars/salesforce-document-management-2-0-smarter-faster-better/
Listen to the keynote address and hear about the latest developments from Rachana Ananthakrishnan and Ian Foster who review the updates to the Globus Platform and Service, and the relevance of Globus to the scientific community as an automation platform to accelerate scientific discovery.
Understanding Globus Data Transfers with NetSageGlobus
NetSage is an open privacy-aware network measurement, analysis, and visualization service designed to help end-users visualize and reason about large data transfers. NetSage traditionally has used a combination of passive measurements, including SNMP and flow data, as well as active measurements, mainly perfSONAR, to provide longitudinal network performance data visualization. It has been deployed by dozens of networks world wide, and is supported domestically by the Engagement and Performance Operations Center (EPOC), NSF #2328479. We have recently expanded the NetSage data sources to include logs for Globus data transfers, following the same privacy-preserving approach as for Flow data. Using the logs for the Texas Advanced Computing Center (TACC) as an example, this talk will walk through several different example use cases that NetSage can answer, including: Who is using Globus to share data with my institution, and what kind of performance are they able to achieve? How many transfers has Globus supported for us? Which sites are we sharing the most data with, and how is that changing over time? How is my site using Globus to move data internally, and what kind of performance do we see for those transfers? What percentage of data transfers at my institution used Globus, and how did the overall data transfer performance compare to the Globus users?
Cyaniclab : Software Development Agency Portfolio.pdfCyanic lab
CyanicLab, an offshore custom software development company based in Sweden,India, Finland, is your go-to partner for startup development and innovative web design solutions. Our expert team specializes in crafting cutting-edge software tailored to meet the unique needs of startups and established enterprises alike. From conceptualization to execution, we offer comprehensive services including web and mobile app development, UI/UX design, and ongoing software maintenance. Ready to elevate your business? Contact CyanicLab today and let us propel your vision to success with our top-notch IT solutions.
Navigating the Metaverse: A Journey into Virtual Evolution"Donna Lenk
Join us for an exploration of the Metaverse's evolution, where innovation meets imagination. Discover new dimensions of virtual events, engage with thought-provoking discussions, and witness the transformative power of digital realms."
2. What is OSGi?
OSGi 프레임워크는 독립적인 자바/가상 머신 환경에서 제공하고 있
지 않는 세련되고, 완전하며 동적인 SOA(Service Oriented
Architecture) 기반의 컴포넌트 모델을 구현한다. 응용 프로그램 또
는 구성 요소(번들, Bundle)는 재시동 과정 없이 원격지를 통해 설치
(installed), 시작(started), 정지(stopped), 업데이트(updated) 그리고
제거(uninstalled)할 수 있다.
The OSGi (Open Service Gateway initiative) specification describes
a modular system and a service platform for the Java
programming language that implements a complete and dynamic
component model, something that does not exist in standalone
Java/VM environments. Applications or components, coming in
the form of bundles for deployment, can be remotely installed,
started, stopped, updated, and uninstalled without requiring a
reboot; management of Java packages/classes is specified in great
detail. Application life cycle management is implemented via APIs
that allow for remote downloading of management policies. The
service registry allows bundles to detect the addition of new
services, or the removal of services, and adapt accordingly.
3. What does OSGi?
Each plugin is a versioned artifact that has its own classloader.
Each plugin depends on both specific jars that it contains and
also other specific versioned plug-ins.
Because of the versioning and isolated classloaders, different
versions of the same artifact can be loaded at the same time. If
one component of your application relies on one version of a
plug-in and another depends on another version, they both can
be loaded at the same time.
With this, you can structure your application as a set of versioned
plugin artifacts that are loaded on demand. Each plugin is a
standalone component. Just as Maven helps you structure your build
so it is repeatable and defined by a set of specific versions of
artifacts it is created by, OSGi helps you do this at runtime.
7. OSGi Framework Architecture
Bundles - Bundles are the OSGi components made by the developers.
Services - The services layer connects bundles in a dynamic way by offering a publish-find-
bind model for plain old Java objects.
Life-Cycle - The API to install, start, stop, update, and uninstall bundles.
Modules - The layer that defines how a bundle can import and export code.
Security - The layer that handles the security aspects.
Execution Environment - Defines what methods and classes are available in a specific
platform.
8. OSGi System Layering
Services are dynamic. This means that a bundle can decide to withdraw its
service from the registry while other bundles are still using this service.
Bundles using such a service must then ensure that they no longer use the
service object and drop any references. We know, this sounds like a
significant complexity but it turns out that helper classes like the Service
Tracker and frameworks like iPOJO, Spring, and Declarative Services can make
the pain minimal while the advantages are quite large.
OSGi 프레임워크는 크게 번들 실행주기(설치/
시작/제거/업데이트), OSGi 기본 실행단위인
번들과 서비스에 대한 운영 관리 및 리소스와
서비스 레지스트리를 담당 한다. 복수 개의 클
래스 로더에 의해 각각 서로 다른 OSGi 어플리
케이션이 독립성을 가지고 실행되지만,
OSGi Framework Service Registry에 등록된
Sharing Code와 주소에 의해 서로 다른 번들간
의 리소스 공유와 연동/통합으로
무수한 서비스들을 생성하고 실행한다.
9. Bundle Life Cycle
Bundle State Description
INSTALLED The bundle has been successfully installed.
RESOLVED
All Java classes that the bundle needs are available. This state indicates that the bundle is either re
ady to be started or has stopped.
STARTING
The bundle is being started, the BundleActivator.start method will be called, and this method has
not yet returned. When the bundle has an activation policy, the bundle will remain in the STARTIN
G state until the bundle is activated according to its activation policy.
ACTIVE
The bundle has been successfully activated and is running; its Bundle Activator start method has b
een called and returned.
STOPPING
The bundle is being stopped. The BundleActivator.stop method has been called but the stop meth
od has not yet returned.
UNINSTALLED The bundle has been uninstalled. It cannot move into another state.
Karaf Console
10. Service
The OSGi service registry enables a bundle to publish objects to a shared registry,
advertised via a given set of Java interfaces.
Published services also have service properties associated with them in the registry.
The registry is a crucial feature of OSGi, facilitating decoupling between bundles by
promoting a dynamic collaborative model based on a service-oriented paradigm
(publish/find/bind).
Blueprint integrates tightly with the service registry, allowing clients to publish, find
and bind services in a POJO-friendly manner, without coupling themselves to the
OSGi API.
11. Benefits of Using OSGi
Benefits
Reduced Complexity Fast
Reuse Lazy
Real World Secure
Easy Deployment Humble
Dynamic Updates Non Intrusive
Transparency Runs Everywhere
Versioning Widely Used
Simple Supported by Key
Companies
Small
12. Standard Services : OSGi System Services
System Services Description
Logging
The logging of information, warnings, debug information or errors is handled through the Log Ser
vice. It receives log entries and then dispatches these entries to other bundles that subscribed to t
his information.
Configuration Admi
n
This service allows an operator to set and get the configuration information of deployed bundles
Device Access
Facilitates the coordination of automatic detection and attachment of existing devices. This is used
for Plug and Play scenarios.
User Admin
This service uses a database with user information (private and public) for authentication and auth
orization purposes.
IO Connector
The IO Connector Service implements the CDC/CLDC javax.microedition.io package as a service. T
his service allows bundles to provide new and alternative protocol schemes.
Preferences
Offers an alternative, more OSGi-friendly mechanism to using Java’s default Properties for storing
preferences.
Component Runtime
The dynamic nature of services—they can come and go at any time—makes writing software hard
er. The Component Runtime specification can simplify handling these dynamic aspects by providin
g an XML based declaration of the dependencies.
Deployment Admin Standardizes access to some of the responsibilities of the management agent.
Event Admin Provides an inter-bundle communication mechanism based on a publish-and-subscribe model.
Application Admin
Simplifies the management of an environment with many different types of applications that are si
multaneously available.
13. Standard Services : OSGi Protocol Services
Protocol Services Description
HTTP Service Allows information to be sent and received from OSGi using HTTP.
UPnP Device Service
Specifies how OSGi bundles can be developed to interoperate wit
h Universal Plug and Play (UPnP) devices.
DMT Admin
Defines an API for managing a device using concepts from the Op
en Mobile Alliance (OMA) device management specifications.
14. Standard Services : OSGi Miscellaneous
Miscellaneous Services Description
Wire Admin
Allows the connection between a Producer service and a Consumer
service.
XML Parser
The XML Parser service allows a bundle to locate a parser with desir
ed properties and compatibility with JAXP.
Measurement and State
The Measurement and State service allows and simplifies the correct
handling of measurements in an OSGi service platform.
15. iPOJO
iPOJO is a service component runtime aiming to simplify OSGi
application development. It natively supports ALL the dynamism
of OSGi. iPOJO is made to run modern applications exhibiting
modularity and requiring runtime adaption and autonomic
behavior.
Main features
Components are developed as POJOs - no dependencies or complex API
Use annotations, XML or a fluent API to declare your components and
instances
Require and provide services without requiring code, while being amazingly
powerful
iPOJO applications are natively resilient to dynamism
Extensible and customizable, develop your own component model
iPOJO applications are supporting dynamic adaptation, and exhibit
autonomic behavior
Apache Felix iPOJO
16. Blueprint Service
Enterprise Modules Project (Gemini)
The Blueprint Service specification defines a
dependency injection framework, specifically for
OSGi bundles, that understands the unique
dynamic nature of services. It provides an OSGi
bundle programming model with minimal
implementation dependencies and virtually no
accidental complexity in the Java code. Bundles in
this programming model contain a number of XML
definition resources which are used to wire the
application together and start it when the bundle is
active.
This Blueprint Service specification is derived from
the Spring Dynamic Modules project.
There are currently two open source
implementations of the Blueprint:
17. Dependency injection framework
Dependency inj
ection
Declarative Servi
ces
Blueprint iPOJO
Callback injectio
n
Yes Yes (public meth
od only)
Yes
Constructor inje
ction
No Yes Yes
Field injection No No Yes
Setter injection Yes Yes Yes
Proxy injection No Yes Yes
List injection No Yes Yes
Nullable injectio
n
No No Yes
18. Dependency injection framework
Lifecycle
Declarative Servi
ces
Blueprint iPOJO
Callbacks (activa
te/deactivate)
Yes Yes Yes
Factory pattern Yes Yes Yes
Lazy initializatio
n
Yes Yes Yes
Damping No Yes Yes
Field synchroniz
ation
No No Yes
Component lifec
ycle control
Yes Partial Yes
Service lifecycle
control
No No Yes
25. Apache Karaf
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]/deploydirectory. 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.
•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. This shell is easily extensible by deploying new commands
dynamically along with new features or applications.
•Remote access: use any SSH client to connect to Karaf and issue commands in the console
•Security framework based on JAAS
•Managing instances: Karaf provides simple commands for managing multiple instances. You can easily create,
delete, start and stop instances of Karaf through the console.
26. ServiceMix
Apache ServiceMix is a flexible, open-
source integration container that unifies
the features and functionality of
Apache ActiveMQ, Camel, CXF,
andKaraf into a powerful runtime
platform you can use to build your own
integrations solutions. It provides a
complete, enterprise ready ESB
exclusively powered by OSGi.
27. JBoss FUSE
JBoss Fuse is an open source Enterprise
Service Bus (ESB) with an elastic footprint
that supports integration beyond the data
center. The ability to deploy JBoss Fuse in
several different configurations enables
intelligent integration to all facets of your
business – on premise or in the Cloud.
Editor's Notes
iPOJO is a service component runtime aiming to simplify OSGi application development. It natively supports ALL the dynamism of OSGi. Based on the concept of POJO, application logic is developed easily. Non-functional properties are just injected in the component at runtime.
iPOJO strength points are :
components are developed as POJO, nothing else is required !
the component model is extensible, so feel free to adapt it to your needs
the standard component model manages service providing and service dependencies, and so can require any other OSGi services
iPOJO manages the component instance lifecycle and the environment dynamics as it has never been possible
iPOJO provides a powerful composition system to create highly dynamic applications
iPOJO supports annotations, XML or Java-based API to define the componen
The Blueprint Service specification defines a dependency injection framework, specifically for OSGi bundles, that understands the unique dynamic nature of services. It provides an OSGi bundle programming model with minimal implementation dependencies and virtually no accidental complexity in the Java code. Bundles in this programming model contain a number of XML definition resources which are used to wire the application together and start it when the bundle is active.
This Blueprint Service specification is derived from the Spring Dynamic Modules project.
There are currently two open source implementations of the Blueprint:
Apache Aries
Eclipse Gemini