Jump to content

User:Pawelpacewicz/sandbox: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
No edit summary
No edit summary
Line 11: Line 11:
}}
}}


'''SORCER''' (stands for '''S'''ervice '''OR'''iented '''C'''omputing '''E'''nvi'''R'''onment) is computing platform that integrates various applications (i.e engineering systems) in large complex IT environments into one dynamically manageable cloud of services. Additionally, SORCER delivers Programming languages that enable users to flexibly manipulate, interactions of services available within these SORCER service clouds. SORCER merges various IT systems and engineering applications from different vendors and this way helps to manage complexity of modern challenges (i.e. aircraft design) including complexity of challenge itself and complex interactions of applications, tools, and utilities used.
'''SORCER''' (stands for '''S'''ervice '''OR'''iented '''C'''omputing '''E'''nvi'''R'''onment) is computing platform that integrates various applications from various vendors (i.e engineering systems) in complex IT environments into one easly manageable cloud of services (applications). On top of this SORCER delivers programming language that allows users to manipulate interactions of those services. This way SORCER helps to manage complexity of big, modern challenges (i.e. aircraft design) including complexity of challenge itself and complex interactions of applications, tools, and utilities used.


==Detailed Description==
==Detailed Description==
Line 193: Line 193:
*From 2010 the [http://sorcersoft.org SORCER Laboratory] becomes the independent research organization focused on federated service-oriented computing.
*From 2010 the [http://sorcersoft.org SORCER Laboratory] becomes the independent research organization focused on federated service-oriented computing.
*Development of SORCER-based Engineering Toolkit (2013) by [http://Sorcersoft.com Sorcersoft.com] in cooperation with the [http://www.pjwstk.edu.pl/?kat=239 Polish-Japanese Institute of Information Technology] and [http://www.smtsoftware.com/en SMT Software].
*Development of SORCER-based Engineering Toolkit (2013) by [http://Sorcersoft.com Sorcersoft.com] in cooperation with the [http://www.pjwstk.edu.pl/?kat=239 Polish-Japanese Institute of Information Technology] and [http://www.smtsoftware.com/en SMT Software].

== Requirements ==
Java 1.6+ (tested on Windows, Mac OS X, and Linux).


== References ==
== References ==

Revision as of 13:03, 23 November 2013

SORCER
Working stateCurrent
Source modelFree and open source software with proprietary components
Initial release2003 (2003)
Latest release1.0-M2 / 24 July 2013 (2013-07-24)
LicenseApache License
Official websitesorcersoft.com

SORCER (stands for Service ORiented Computing EnviRonment) is computing platform that integrates various applications from various vendors (i.e engineering systems) in complex IT environments into one easly manageable cloud of services (applications). On top of this SORCER delivers programming language that allows users to manipulate interactions of those services. This way SORCER helps to manage complexity of big, modern challenges (i.e. aircraft design) including complexity of challenge itself and complex interactions of applications, tools, and utilities used.

Detailed Description

SORCER is a federated service-oriented computing platform that allows the end user to program dynamic front-end compound services, called exertions, bound at runtime by the SORCER OS (SOS) to federations of service providers as new back-end dynamic services. The SOS utilizes the service object-orient architecture (SOOA) and a federated method invocation.[1] The front-end services created by the end users are service collaborations of users' applications, tools, and utilities with their data and corresponding control strategies, all seamlessly collaborating in the network. [2]The end users in understandable domain specific languages (DSL) define only their service-oriented process expressions and the SOS makes that process expressions actualized by the corresponding dynamic service federations in the network.

Computing requires a platform (runtime system) to operate. Computing platforms that allow programs to run require a processor, operating system, and programming environment that allow creation of symbolic process expressions. SORCER is a well-defined federated service-oriented platform with a front-end federated service-oriented programming environment, a matching operating system, and a federated virtual processor. The architecture of SORCER is based on the concept: Everything Anywhere Anytime As a Service (EaaaS). Therefore the end user service requests (front-end expression) as well service providers (back-end federations) are treated as services. SORCER is the first platform that created front-end service-oriented mogramming (programming or modeling or both) as the key element of its federated service orientation. SORCER mograms are called exertions. The exertion-oriented programming has its roots in the FIPER project. An exertion as the front-end service composition defined by the user is bound by the SORCER OS (SOS) to service providers (local and/or remote) to form a matching collaborative service federation at runtime - a virtual service processor of the SORCER platform.

Exertions represent front-end "services" that are hierarchically organized with data contexts (attributes that describe the service data), control contexts (attributes that describe the service control strategy), and associated service providers' signatures based on service types (local-Java classes or remote-interfaces). The associated signatures are bound to service providers to collaborate according to control strategies imposed by exertion's control contexts to process data contexts of the service federation created at runtime by the SOS. SORCER is the first system enabling front-end service-oriented programming with the relevant operating system and dynamic back-end service federations as its virtual processor.

SOS
The SORCER Operating System

The SORCER operating System (SOS) manages execution of front-end service-oriented mograms and related resources including required service providers. The SOS kernel by itself is the service-oriented system made up of system service providers architecturally equivalent to domain specific service providers. A service provider is a container for service beans that is responsible for deploying services in the network, publishing their proxies to registries, and allowing the SOS to access proxies of deployed providers. Providers maintain their availability in the network continuously by renewing leases for their registered object proxies; registries intercept these announcements and cache/remove proxy objects per providers’ requests. The SOS looks up proxies by sending queries to registries and making selections from the currently available providers or provisions on-demnad required ones. Queries generally contain search criteria related to the type and quality of service. Registries facilitate searching by storing proxy objects of services and making them available to the SOS. Providers use discovery/join protocols to publish services in the network and the SOS uses discovery/join protocols to discover registries and lookup proxies in those registries.

The basic exertion-oriented platform was developed at GE Global Research Center with the partners of the FIPER project (1999-2003). FIPER was used at that time to design aircraft engines[3] [4] .[5] The Multidisciplinary Science and Technology Center, the United States Air Force Research Laboratory/WPAFB is using and developing SORCER to address the physics-based distributed collaborative design for aerospace vehicle development[6] [7] .[8] In China for example SORCER is used as noise mapping platform for urban traffic,[9] a resource integration platform ,[10] engineering collaborative design environment,[11] and at the Wright State Unversity as a collaborative computational framework for multidisciplinary and reliability-based analysis and optimization.[12]

Features

  • Based on the concept: Everything Anywhere Anytime As a Service (EaaaS), including front-end services (process expressions-exertions) and back-end services (process actualizations-federations of service providers).
  • Introduction of a service variable (var) with multifidelity evaluation and related var-orineted modeling
  • Unification of programming styles (procedural, functional, block-structured, and workflow-structured) with var-oriented modeling into the service-oriented mogramming (programming or modeling or both) environment with a matching operating system and a federated virtual processor.
  • The front-end mogramming with the capability of both back and front-end service provider deployment;
  • Ease of parallelization with self-balanced space computing for exertions with transactional semantics,
  • Front-end selection of mixed synchronous and asynchronous execution of service federations;
  • Front-end (on-demand) autonomic service provider provisioning/unprovisioning;
  • Context awareness of the service-oriented computing with service context-based interoperability across service federations; and
  • Location/implementation neutrality, but most importantly wire protocol neutrality and transport protocol selection at service deployment (transport endpoints);
  • Smart proxying for balancing execution of business logic between service requestors and providers, with fat proxying for running the provider’s code completely at the requestor side;
  • Code mobility across service federations – dynamic behavioral transfer between requestors and providers; and

History

References

  1. ^ Sobolewski, Michael (2009). Metacomputing with Federated Method Invocation. In-Tech, intechweb.org. pp. 337–363. ISBN 978-953-7619-51-0. Retrieved 2010-01-27. {{cite book}}: Unknown parameter |booktitle= ignored (help); Unknown parameter |editors= ignored (|editor= suggested) (help)
  2. ^ Thompson, Ernest D (2012). "University of Dayton, 2012". University of Dayton: 230–241. {{cite journal}}: |access-date= requires |url= (help); |chapter= ignored (help); Cite journal requires |journal= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help)
  3. ^ Seeley, C.E. (2001). "Multidisciplinary analysis and optimization of combustion sub-system using a network-centric approach". 42nd AIAA/ASME/ASCE/AHS/ASC Structures, Structural Dynamics, and Materials Conference AIAA-2001-1270. American Institute of Aeronautics and Astronautics. doi:10.2514/6.2001-1270. {{cite book}}: |access-date= requires |url= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  4. ^ Tappeta, R.V. (2002). "Application of Approximate Optimization to Turbine Blade Design in a Network-Centric Environment". 43rd AIAA/ASME/ASCE/AHS/ASC Structures, Structural Dynamics and Materials Conference AIAA-2002-1588. American Institute of Aeronautics and Astronautics. doi:10.2514/6.2002-1588. {{cite book}}: |access-date= requires |url= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  5. ^ Liao, Li (2004). "2D/3D CFD Design Optimization Using the Federated Intelligent Product Environment (FIPER) Technology". 9th AIAA/ISSMO Symposium on Multidisciplinary Analysis and Optimization AIAA-2002-5479. IAIAA. doi:10.2514/6.2004-1847. {{cite book}}: |access-date= requires |url= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  6. ^ Kolonay, Raymond (2004). "Object Models for Distributed Multidisciplinary Analysis and Optimization (MAO) Environments that Promotes CAE Interoperability". 10th AIAA/ISSMO Multidisciplinary Analysis and Optimization Conference AIAA 2004-4599. AIAA. doi:10.2514/6.2004-4599. {{cite book}}: |access-date= requires |url= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  7. ^ Kolonay, Raymond (2013). "Physics-Based Distributed Collaborative Design for Aerospace Vehicle Development and Technology Assessment". Proceedings of the 20th ISPE International Conference on Concurrent Engineering. IOS Press. pp. 381–390. ISBN 978-1-61499-301-8. {{cite book}}: |access-date= requires |url= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help); Unknown parameter |editors= ignored (|editor= suggested) (help)
  8. ^ Scott A., Burton (2012). "Efficient Supersonic Air Vehicle Analysis and Optimization Implementation using SORCER". 12th AIAA Aviation Technology, Integration, and Operations (ATIO) Conference and 14th AIAA/ISSM, AIAA 2012-5520. AIAA. pp. 381–390. {{cite book}}: |access-date= requires |url= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  9. ^ Li, Nan (2011). "A SOOA Based Distributed Computing Mechanism for Road Traffic Noise Mapping". IEEE Computer Society Washington, DC, USA: 109–112. ISBN 978-0-7695-4455-7. {{cite journal}}: |access-date= requires |url= (help); |chapter= ignored (help); Cite journal requires |journal= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  10. ^ Lingjun, Kong (2011). "Electronic and Mechanical Engineering and Information Technology (EMEIT), 2011 International Conference on (Volume:3 )": 1466–1469. ISBN 978-1-61284-087-1. {{cite journal}}: |access-date= requires |url= (help); |chapter= ignored (help); Cite journal requires |journal= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)
  11. ^ ZHANG, Rui-hong (2008). "Engineering Collaborative Design Environment Based on Service-oriented Architecture". JOURNAL OF HEBEI UNIVERSITY OF TECHNOLOGY, Vol.37 No.4. pp. = 40–44. {{cite book}}: |access-date= requires |url= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help); Unknown parameter |coauthors= ignored (|author= suggested) (help)CS1 maint: extra punctuation (link)
  12. ^ Aithala, Karkada Nagesha (2011). "Wright State University, 2011". Wright State University. {{cite journal}}: |access-date= requires |url= (help); |chapter= ignored (help); Cite journal requires |journal= (help); External link in |chapterurl= (help); Unknown parameter |chapterurl= ignored (|chapter-url= suggested) (help)