Java Solaris Communities About Sun How to Buy United States Worldwide

Jini Network Technology

FAQs

Jini Network Technology
 
   FAQ
  »   Overview
  »   Data Sheet
 
Table of Contents
General
  1. What is Jini network technology?
  2. Where/how do I get Jini technology?
  3. What makes Jini technology different as a networking architecture?
  4. How is Jini technology being used today?
  5. What is Java Dynamic Networking?
  6. What is different about Java Dynamic Networking?
  7. Why is Jini technology well suited to meet the needs of Grid Computing?
  8. Who is using Jini technology as the foundation for compute grid applications today?
Community
  1. What is the Jini Community?
  2. What is the purpose of the Jini Community?
  3. How does the Community accomplish its goals?
Licensing
  1. Why did Sun open up the licensing model for Jini technology in March 2005?
  2. What benefits does the new license model bring to Jini technology users?
  3. Why did Sun choose the Apache License, Version 2.0 for its Jini technology contributions?
  4. What new benefits does Sun's choice of the Apache License, Version 2.0 bring to Jini technology users?
  5. Is Jini technology still available under the Sun Community Source License (SCSL)?
  6. How long will Sun continue to offer Jini technology under the SCSL?
  7. Will Sun make all of its Jini technology contributions available under the Apache License, Version 2.0? If so, when?
  8. Does Sun's move enable other members of the Jini Community to re-release their Jini technology contributions under the Apache License, Version 2.0 (or a different license of their choice)?
  9. Does Sun's move require other members of the Jini Community to re-release their Jini technology contributions under the Apache License, Version 2.0?
  10. Does the Jini Community Decision Process (JDP) go away?
  11. The SCSL describes two different types of uses: "Research Use" and "Commercial Use". What is the distinction between the two?
  12. As a Jini SCSL licensee, can I distribute products that contain some Jini technology but have notpassed the Jini Technology Core Platform Compatibility Kit (TCK)?
  13. I am a consultant. What level of license do I need to adhere to?
 
 

General


Q:
What is Jini network technology?
A:
Jini technology is an open software architecture that enables Java Dynamic Networking for building distributed systems that are highly adaptive to change. Jini technology can be used to deliver adaptive technology systems that are scalable, evolvable, and flexible, as typically required in dynamic runtime environments.

More concretely, Jini technology is defined by a set of specifications that describe how to build adaptive distributed systems that run on the Java platform. The specifications presume, fundamentally, that any aspect of a distributed system is subject to change without notice, and so they provide systems designers and developers with the mechanisms needed to recognize, acknowledge, and build their systems to accommodate change.

Jini technology specifications are straightforward and minimalistic. They describe the following:

  • runtime service discovery mechanisms that enable clients to find and connect to individual services as needed in a dynamic operating environment
  • a programming model that extends the Java programming model to acknowledge and accommodate network behaviors such as partial failure
  • key services, such as shared memory and transactions management services, that enable important functionality to be delivered in a dynamic, distributed environment

Back to top


Q:
Where/how do I get Jini technology?
A:
Jini technology is freely available and can be accessed from the Jini Community Web site. Several popular implementations of Jini technology are available from vendors directly as well. Sun's Jini Technology Starter Kit is available free of charge, and can be accessed from the Jini Community Web site, or from Sun.

Back to top


Q:
What makes Jini technology different as a networking architecture?
A:
Jini technology leverages the unique capabilities of the Java platform to enable Java Dynamic Networking, a fundamentally different approach to networking that only the Java platform can support (see "What makes Java Dynamic Networking different?"). Jini technology is interesting today first because the breadth and credibility of successful Jini technology-based applications now deployed has validated the technology among early majority users, and second, because dynamic networking capabilities are needed by a many major new markets, from RFID systems at the network edge to utility computing infrastructures at its core.

Back to top


Q:
How is Jini technology being used today?
A:
Jini technology is being employed in a wide range of applications that require the ability to respond automatically to changes in their operating environments. Several common scenarios exemplify typical Jini technology use cases today, including:

Edge Networking
Distributed systems deployed beyond the data center are differentiated from their data center-focused counterparts in that they are subject to a wider range of failure modes, and they are not readily accessible to a systems administrator. These systems must be able to automatically recover from failure at the network edge, and must be easy to update and manage without manual administration as well. Jini technology has proven itself up to the task; it is being used today to enable the creation of self-healing edge-networking systems, and to allow new or updated services to be introduced into these systems without the need for an administrator to restart the system

Compute Grids
Jini technology is being used today as the underlying infrastructure supporting compute grid applications in financial services, defense, logistics planning, life sciences, image processing, scientific research, manufacturing, and other domains. Jini technology-based grids automatically accommodate the runtime addition, removal, or loss of compute resources, which means that these grids can scale dynamically to accommodate changing loads, and they keep running even though some large grid networks operate in a near constant state of partial failure.

Dynamic Systems Integration
Jini technology is today supporting many companies' needs to keep their systems up and running while dynamically integrating in house or third-party services whenever they are available. The technology is helping these users deal with service failures, updates, and implementation details that are beyond their control, often stemming from their need to integrate services from external sources. Also, by isolating clients from the need to implement any of the multiple proprietary communications protocols that many different service providers use, Jini technology is simplifying these users' approach to integrating services that use a variety of communication protocols.

Dynamic Clustering
Whether they are used to increase availability or scalability, clusters created with Jini technology are successfully accommodating the run time addition, loss, or removal of clustered services for many users today. These Jini technology-based clusters scale out readily with the simple addition of service instances to be clustered, and they scale down just as easily by removing unneeded service instances. The location, name, or provider or any service to be clustered can be changed without the need to bring these clusters down.

Workflow/Message Switching
Jini technology, and especially the JavaSpaces service, provides a simple way to share Java objects across a dynamic network. Telecommunications, financial services, and other applications are exploiting the technology's support for loosely coupled interactions and its ability to transfer data (and/or code) through the system.

Ad-hoc networking
Jini technology is today being used to enable the spontaneous bootstrapping of a network of services that come together in an ad-hoc fashion. Current deployments are using this capability to power solutions in a range of new ad-hoc networking markets, including home networking, telematics systems, and sensor networks, to name a few.

Dynamic Service Provisioning
The ability to flexibly provision networks to offer specific configurations of services that may be re-provisioned to accommodate changing needs over time is what underlies the move to utility computing today. Developers have leveraged Jini technology's support for dynamic service discovery and delivery, as well as its straightforward service substitution capabilities, to create such dynamic service provisioning infrastructures.

Back to top


Q:
What is Java Dynamic Networking?
A:
Java Dynamic Networking, enabled exclusively by Jini technology, is a form of networking in which interchangeable network system components are bound together as needed at runtime. What makes Java Dynamic Networking unique is that network clients bind dynamically to any network service that is capable of providing needed functionality, regardless of the name, location, wire protocol, or other implementation details of the particular service instance used.

Back to top


Q:
What is different about Java Dynamic Networking?
A:
Java Dynamic Networking, enabled exclusively by Jini technology, is focused around an application level abstraction of networking in which network system components are presented through Java programming language interfaces. Using this abstraction, the contract between a network client and a network service is reduced to its simplest and most flexible form: the networking contract is defined in terms of a client's functional needs and a service's functional capabilities.

This contrasts sharply with other approaches to networking, in which networking contracts are defined in terms of how clients and services interact, rather than in terms of what functionality is needed/provided. Traditional network clients and services must be implemented against a pre-defined and shared understanding of service naming conventions, IP addresses, or over-the-wire communication protocols. Using these traditional network architectures, running clients may be unable to bind dynamically to services that provide needed functionality if the names, locations, or wire protocols used by those services vary from time to time or place to place.

Java Dynamic Networking places no such conditions on the networking contract between a client and service: as long as a service is capable of providing the functionality needed by a client, that service can be bound to the client at runtime. This leads to more flexible component interchangeability, and ultimately increases the adaptivity of systems that use Jini technology and Java Dynamic Networking.

Back to top


Q:
Why is Jini technology well suited to meet the needs of Grid Computing?
A:
Jini technology enables the creation of distributed systems that are highly adaptive to change, and is well suited for use as the underlying architecture of compute grid applications. Jini technology enables compute grid masters and workers to find and connect to a grid in dynamic operating environments, which simplifies the runtime scaling and failure recovery of compute grid applications. Extending the Java platform programming model to recognize and accommodate partial failure, Jini technology enables the creation of compute grid applications that remain highly available, even if some of the grid's component parts are not. Robustness is further enhanced with Jini technology's support for distributed systems security. And finally, the JavaSpaces service contributes a simple yet powerful coordination point that facilitates task distribution, load balancing, scaling, and failure recovery of compute grid applications.

Back to top


Q:
Who is using Jini technology as the foundation for compute grid applications today?
A:
Successful Jini technology-based compute grids are today serving the needs of a wide range of users, including many in financial services, defense, logistics planning, life sciences, image processing, scientific research, and manufacturing. The many problems to which Jini technology-based compute grids are currently being applied include modeling, simulations, data processing, rendering, and pattern matching.

Back to top

Community


Q:
What is the Jini Community?
A:
The Jini Community is a dynamic, diverse, and globally distributed group of individuals, companies, and organizations that are bound together by their shared interest in Jini technology.

Back to top


Q:
What is the purpose of the Jini Community?
A:
The Jini Community aims to foster broad adoption, technical advancement, and standardization around Jini technology.

Back to top


Q:
How does the Community accomplish its goals?
A:
The Jini Community leverages a wide range of tools, resources, and activities to accomplish its goals. The Jini Community Web site is a focal point for information exchange, sharing, and collaboration. Events, like Community Meetings, regular Web events, and other gatherings, as well as discussion lists, project groups, newsletters, and other vehicles also provide opportunities for Community engagement. The Community also approves Jini Community Standards, following an opened decision making process in which all Community members may participate. Governance is defined in a constitution and guided by a technical oversight committee, and decisions are made through an open process in which all Community members may participate.

Back to top

Licensing


Q:
Why did Sun open up the licensing model for Jini technology in March 2005?
A:
Sun opened up the licensing model for Jini technology to facilitate its broader adoption and technical advancement. Sun implemented the license change in March 2005 to meet the needs of an expanding Jini Community that is now well positioned to thrive in a more open environment.

Back to top


Q:
What benefits does the new license model bring to Jini technology users?
A:
By facilitating the broader adoption and advancement of Jini technology on the whole, the new licensing model supports the development of a richer ecosystem for Jini technology users to operate within.

Back to top


Q:
Why did Sun choose the Apache License, Version 2.0 for its Jini technology contributions?
A:
Sun chose to use the ALv2 for its Jini technology contributions following extensive, open, and collaborative discussions with the Jini Community, in which the ALv2 was determined to best meet the licensing requirements most important to Sun and the Jini Community.

Back to top


Q:
What new benefits does Sun's choice of the Apache License, Version 2.0 bring to Jini technology users?
A:
Sun's release of its Jini technology contributions under the ALv2 allows developers to more freely license, use and distribute Jini technology-based code and specifications. The availability of Jini technology under this commonly accepted license may also simplify prospective users' license review processes, and significantly ease the introduction of Jini technology into many companies.

Back to top


Q:
Is Jini technology still available under the Sun Community Source License (SCSL)?
A:
Yes; Jini technology contributions made by many members of the Jini Community remain available under the SCSL model today. Among them, Sun's Jini technology contributions made prior to March, 2005 are currently available under the SCSL model. These releases include v2.0.1 and v1.2.1 of Sun's Jini Technology Starter Kit and numerous Jini Community project contributions.

Back to top


Q:
How long will Sun continue to offer Jini technology under the SCSL?
A:
Sun encourages use of its ALv2-based contributions and expects demand for its SCSL-based Jini technology offerings to wane significantly with the availability of the more open Jini technology licensing model. A SCSL discontinuation plan has not yet been defined.

Back to top


Q:
Will Sun make all of its Jini technology contributions available under the Apache License, Version 2.0? If so, when?
A:
Sun currently plans to re-release all of its existing Jini technology contributions, and to release all of its future Jini technology contributions under the ALv2. The specific timeline for these re-releases has not yet been determined.

Back to top


Q:
Does Sun's move enable other members of the Jini Community to re-release their Jini technology contributions under the Apache License, Version 2.0 (or a different license of their choice)?
A:
Yes; as part of this license model change, Sun has published a Notice of Relief from Certain Obligations that allows members of the Jini Community to re-release code that they have written using Jini technology under any license they choose, including ALv2.

Back to top


Q:
Does Sun's move require other members of the Jini Community to re-release their Jini technology contributions under the Apache License, Version 2.0?
A:
No; current Jini technology SCSL licensees are encouraged, but are not required, to take advantage of the license model change.

Back to top


Q:
Does the Jini Community Decision Process (JDP) go away?
A:
No; the Jini Community Decision Process (JDP) remains a fundamental structure for the Jini Community to reach agreements on such things as Standards.

Back to top


Q:
The SCSL describes two different types of uses: "Research Use" and "Commercial Use". What is the distinction between the two?
A:
The SCSL defines two different types of licensee to meet the unique requirements of each. The Research Use category is designed to allow individuals, businesses and academic institutions to become familiar with the technology, to modify the source code, to create implementations, and to try it in their own applications. The Commercial Use category establishes a mechanism to reasonably ensure compatibility among Jini services and clients. If you are a SCSL licensee, you must agree to the terms of the The Commercial Use Supplement (CUSupp) in order to deploy your Jini technology-based product internally or distribute it outside of your organization for any commercial or strategic gain or advantage. The CUSupp must be executed by both you and Sun to be effective.

Back to top


Q:
As a Jini SCSL licensee, can I distribute products that contain some Jini technology but have notpassed the Jini Technology Core Platform Compatibility Kit (TCK)?
A:
Except under the limited terms of the Research Use license, all products that are distributed either internally or externally under the terms of the CUSupp must pass the compatibility tests of the TCK.

Back to top


Q:
I am a consultant. What level of license do I need to adhere to?
A:
If you are a consultant working directly for an organization that is a Jini technology licensee, you are considered an agent of it and are subject to the terms of the Jini technology license it has agreed to. If you are a Jini SCSL licensee and you create a solution using Jini network technology for an organization that is not a Jini SCSL licensee, you must sign the Commercial Use Supplement (CUSupp) and its Technology Specific Attachment (TSA).

Back to top

 
Contact About Sun News & Events Employment Site Map Privacy Terms of Use Trademarks Copyright 1994-2008 Sun Microsystems, Inc.