RSS
All Project Updates
Discussions
Issue Tracker
Releases
Reviews
Source Code
Wiki & Documentation
RSS
Show Page Comments | Print View | Page Info | Change History (all pages)
Home
News Feeds - ESB.NET Support Feeds
Keystroke IT News Feed
Installing and Configuring ESB.NET - Problem in installation
Wednesday, December 27, 2006 | From Keystroke IT
Hi all, I am trying to install the "ESBDeploy_5.1.0.0" but its giving error. the path to which...
Keystroke IT News Feed
ESB.NET and Distribution Topologies - See Reference to Blog Entry...
Wednesday, December 27, 2006 | From Keystroke IT
For some reference deployment architectures, please see thie URL... http://www.esb.net.au/MINAsB...
Keystroke IT News Feed
Last edited Dec 28 2006 at 8:26 AM by MINAS, version 1
Comments
No comments yet.
Downloads

Recommended release:
ESBDeploy_6.3.47.0 (x64 and x86)
Wed Nov 4 2009 at 8:00 AM, Stable Stable: This software is believed to be ready for use
3 ratings
13171 downloads, 3 reviews
More info
Recent reviews (more)
5 stars. A pleasantly well-rounded service host with a captivating approach to service deli... (more)
4 stars. thanks thanks thanks thanks
The Keystroke ESB.NET license is fairly complex at first sight.
The rationale behind the license will help put it into perspective and make it a little more understandable.
Basically, Keystroke ESB.NET consists of a Core codebase that is used to host developed services. It is this Core codebase that Keystroke wishes to protect to a certain degree.
The services developed to run on the core are of little concern to Keystroke in this regard as Keystroke wishes to foster a feature rich yet simple environment for which these services can be deployed onto.
The Core codebase is also fairly modular and extensible and Keystroke wishes to allow people to extend it in certain ways. As a result, part of the Core codebase will also be made available.
The different types of components are therefore covered under different licenses, the details of which are below.
For any issues on licensing, contact Minas Casiou – minas@optusnet.com.au,  www.keystroke.com.au or www.esb.net.au for clarification. 

(1) Release runtime only – potentially release under Microsoft Reference License (MS-RL) in future.
(2) Release source code under Microsoft Reference License (MS-RL).
(3) Release source code under Microsoft Community License (MS-CL). (Not the Microsoft Limited Community License (Ms-LCL),)
(4) Release source code under Microsoft Permissive License (MS-PL). (Not the Microsoft Limited Permissive License (Ms-LPL))

CORE
Kernel
(1) Pipeline manager
(1) Xslt manager

Plugins
(1) Entry Points
(1) Services/Adaptors

(2) Envelopes – License NOT Limited to the Windows Platform for this component.
(2) Transport adaptors
(3) Management portal

LOB SYSTEMS
(4) All Services
(4) All Adaptors

The above source code licensing schema will help guide initial development efforts in the areas that require most work. It will also hide some of the complexities of the system, at least initially. It will also protect critical IP.

Some parts of the product (1) MAY still not have source code generally available in future, however will be available under an NDA upon request, and possibly for a fee. It may also be released on a case by case basic in circumstances where problems require the core source code to troubleshoot or if defects are suspected in those areas. This is to ensure the kernel is patched & load tested in an appropriate manner which may not be otherwise achievable at the moment.

?	If formally released, the kernel & other parts will likely be released under the Microsoft Reference License (MS-RL) in future.
?	The rest of the released Core (Plugins) source code, will be released under the (2) Microsoft Reference License (MS-RL). The purpose of releasing this codebase for reference is so that it can be quickly used as a basis for creating similar components – i.e. More Envelopes and Transport Adaptors.
?	The Management Portal is released under the Microsoft Community License (MS-CL). It is intended that this component is extended & delivered back to the Keystroke ESB.NET community.
?	Line Of Business System related components will likely be released under either the Microsoft Permissive License (MS-PL) or the Microsoft Community License (MS-CL). The particular licenses for each component will be specified by the component owner. Here, the intent is to foster both freely available services for Keystroke ESB.NET, as well as to allow people to create services that run under Keystroke.NET, but that they own & sell these services in any way they see fit.
?	It is likely that all LOB SYSTEMS components released to Codeplex by Keystroke will be under the Microsoft Permissive License (MS-PL).

For more information on using one of these licenses for your project, please visit the Microsoft Shared Source Initiative licensing page:
http://www.microsoft.com/resources/sharedsource/licensingbasics/sharedsourcelicenses.mspx 

The License Details that relate to Keystroke ESB refer to the definition of these licenses at the time of this writing. The details of the licenses are therefore reproduced below, and are the definitive licenses. For any issues on licensing, contact Minas Casiou – minas@optusnet.com.au, www.keystroke.com.au or www.esb.net.au for clarification. 
DO NOT use the source without a clear understanding of the licensing implications. Improper use of the license will be acted upon.

START OF KEYSTROKE ESB.NET LICENSE


Microsoft Permissive License (Ms-PL)
The Microsoft Permissive License (Ms-PL) is the least restrictive of the Microsoft source code licenses. It allows licensees to view, modify, and redistribute the source code for either commercial or non-commercial purposes. Under the Ms-PL, licensees may change the source code and share it with others. Licensees may also charge a licensing fee for the modified work.
The copyright and patent grants in this license are both royalty free, meaning that licensees do not have to pay anything to licensor to make use of the source code. There is no obligation for licensees to publish any changes they make in either binary or source code form. The licensee is required to keep notices in the code for copyright, patent, trademarks, or other forms of attribution.
Microsoft has created a limited version, the Microsoft Limited Permissive License (Ms-LPL), of this license to be used for restricting usage to the Windows platform only. The platform restriction is a measure that may be chosen for a particular source code release in order to enable positive interaction with Windows-based developers.
Microsoft Permissive License (Ms-PL)
Published: October 18, 2005
This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software.
1. Definitions
The terms "reproduce," "reproduction" and "distribution" have the same meaning here as under U.S. copyright law.
"You" means the licensee of the software.
"Licensed patents" means any Licensor patent claims which read directly on the software as distributed by Licensor under this license.
 Top of page
2. Grant of Rights
(A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, the Licensor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce the software, prepare derivative works of the software and distribute the software or any derivative works that you create.
(B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, the Licensor grants you a non-exclusive, worldwide, royalty-free patent license under licensed patents to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the software or derivative works of the software.
 Top of page
3. Conditions and Limitations
(A) No Trademark License- This license does not grant you any rights to use Licensor’s name, logo, or trademarks.
(B) If you begin patent litigation against the Licensor over patents that you think may apply to the software (including a cross-claim or counterclaim in a lawsuit), your license to the software ends automatically.
(C) If you distribute copies of the software or derivative works, you must retain all copyright, patent, trademark, and attribution notices that are present in the software.
(D) If you distribute the software or derivative works in source code form you may do so only under this license (i.e., you must include a complete copy of this license with your distribution), and if you distribute the software or derivative works in compiled or object code form you may only do so under a license that complies with this license.
(E) The software is licensed "as-is." You bear the risk of using it. The Licensor gives no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the Licensor excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

Microsoft Community License (Ms-CL)
The Microsoft Community License (Ms-CL) is a license that is best used for collaborative development projects. This type of license is commonly referred to as a reciprocal source code license and carries specific requirements if licensees choose to combine Ms-CL code with their own code. Nearly all current reciprocal licenses are based on the act of distribution to trigger their terms. The Ms-CL seeks to apply the reciprocal terms in a commercially reasonable fashion and to give developers clear guidance as to when the Ms-CL’s reciprocal provisions come into play. 
Developers often have a range of architectural options at their disposal when crafting a particular product or solution. They frequently have the option to design a larger work as a series of separate files or components that communicate with each other at runtime on the end user’s computer, as opposed to one monolithic piece of code that is distributed to the end user as a single file. Although these architectural differences may not be obvious to the end user, they may have significant licensing implications for a developer, particularly if the developer uses Ms-CL code in creating a larger work. The Ms-CL (like the Mozilla Public License) works on a “file-by-file” basis. This means that if a developer uses Ms-CL code in a particular file then the entire file that contains the Ms-CL source code (including any other code in that file, no matter who wrote it), must be redistributed in source code form under the terms of the Ms-CL. On the other hand, for any files in larger works that do not contain Ms-CL code, the developer is free to license those files under the terms of their choice. This is true regardless of how these “non-Ms-CL” files interact with or communicate with the Ms-CL files at runtime. In other words, if the developer releases code under the Ms-CL and someone includes it in a file in their project (and then distributes their project to others), they must distribute under the Ms-CL anything that is in the specific file that contains the original developer’s work. While this file-by-file threshold might at first seem arbitrary, it has the benefit of being an easy to interpret, bright-line rule.
Thus, the intent of the reciprocal license is to use licensing as a mechanism to keep certain community-based code “in the community,” while allowing companies to commercialize and license (under terms of their choice) their “value add” code that interacts with the community-based code.
The copyright and patent grants in this license are both royalty free, meaning that licensees do not have to pay anything to the licensor to make use of the source code. The Licensee is required to keep any notices in the code for copyright, patent, trademarks, or other forms of attribution.
Microsoft has created a limited version, the Microsoft Limited Community License (Ms-LCL), of this license to be used for restricting usage to the Windows platform only. The platform restriction is a measure that may be chosen for a particular source code release in order to enable positive interaction with Windows-based developers.

Microsoft Community License (Ms-CL)
Published: October 18, 2005

This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software.
1. Definitions
The terms "reproduce," "reproduction" and "distribution" have the same meaning here as under U.S. copyright law.
"You" means the licensee of the software.
"Larger work" means the combination of the software and any additions or modifications to the software.
"Licensed patents" means any Licensor patent claims which read directly on the software as distributed by the Licensor under this license.
2. Grant of Rights
(A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, the Licensor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce the software, prepare derivative works of the software and distribute the software or any derivative works that you create.
(B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, the Licensor grants you a non-exclusive, worldwide, royalty-free patent license under licensed patents to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the software or derivative works of the software.
3. Conditions and Limitations
(A) Reciprocal Grants- Your rights to reproduce and distribute the software (or any part of the software), or to create and distribute derivative works of the software, are conditioned on your licensing the software or any larger work you create under the following terms:
1.	If you distribute the larger work as a series of files, you must grant all recipients the copyright and patent licenses in sections 2(A) & 2(B) for any file that contains code from the software. You must also provide recipients the source code to any such files that contain code from the software along with a copy of this license. Any other files which are entirely your own work and which do not contain any code from the software may be licensed under any terms you choose.
2.	If you distribute the larger work as a single file, then you must grant all recipients the rights set out in sections 2(A) & 2(B) for the entire larger work. You must also provide recipients the source code to the larger work along with a copy of this license.
(B) No Trademark License- This license does not grant you any rights to use the Licensor’s name, logo, or trademarks.
(C) If you distribute the software in source code form you may do so only under this license (i.e., you must include a complete copy of this license with your distribution), and if you distribute the software solely in compiled or object code form you may only do so under a license that complies with this license.
(D) If you begin patent litigation against the Licensor over patents that you think may apply to the software (including a cross-claim or counterclaim in a lawsuit), your license to the software ends automatically.
(E) The software is licensed "as-is." You bear the risk of using it. The Licensor gives no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the Licensor excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

Microsoft Reference License (Ms-RL) 
The Microsoft Reference License (Ms-RL) is the most restrictive of the Microsoft source code licenses. The license prohibits all use of source code other than the viewing of the code for reference purposes. The intent of this license is to enable licensors to release, for review purposes only, more sensitive intellectual property assets.
Microsoft commonly uses this license for developer libraries where modification is not required to make use of the source code. In these cases, the importance of transparency is based on the need for developers to more deeply understand the inner workings of the source code. In doing so, the licensees will be more effective in writing software that makes use of the licensed source code.
The copyright and patent grants in this license are both royalty free, meaning that the licensee does not have to pay anything to the licensor to make use of the source code. The license limits the source code release to use on the Windows platform only.
Microsoft Reference License (Ms-RL)
Published: October 18, 2005
This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software.
1. Definitions
The terms "reproduce," "reproduction" and "distribution" have the same meaning here as under U.S. copyright law.
"You" means the licensee of the software.
"Your company" means the company you worked for when you downloaded the software.
"Internal use" means use within your company and specifically excludes the right to distribute the software outside of your company.
"Licensed patents" means any Licensor patent claims which read directly on the software as distributed by the Licensor under this license.
2. Grant of Rights
(A) Copyright Grant- Subject to the terms of this license, the Licensor grants you a non-transferable, non-exclusive, worldwide, royalty-free copyright license to reproduce the software and reference it for internal use.
(B) Patent Grant- Subject to the terms of this license, the Licensor grants you a non-transferable, non-exclusive, worldwide, royalty-free patent license under licensed patents to use the software within your company.
3. Limitations
(A) No Trademark License- This license does not grant you any rights to use the Licensor’s name, logo, or trademarks.
(B) Platform Limitation- The licenses granted in section 2 extend only to the software or larger works that you create that run on a Microsoft Windows operating system product.
(C) If you begin patent litigation against the Licensor over patents that you think may apply to the software (including a cross-claim or counterclaim in a lawsuit), your license to the software ends automatically.
(D) The software is licensed "as-is." You bear the risk of using it. The Licensor gives no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the Licensor excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

END OF KEYSTROKE ESB.NET LICENSE
Activity

7 30 All days
Page Views	569
Visits	255
Downloads	139
View Detailed Stats