User:Pawelpacewicz/sandbox

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. 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. 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.

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 . 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 . In China for example SORCER is used as noise mapping platform for urban traffic, a resource integration platform , engineering collaborative design environment, and at the Wright State Unversity as a collaborative computational framework for multidisciplinary and reliability-based analysis and optimization.

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


 * A self-healing runtime environment using Jini network discovery/join protocols and dynamic lookup services. SORCER is build on top of Jini's Service-object-oriented architecture (SOOA)

History

 * The FIPER project (1999-2003) - funded by NIST Advanced Technology Program, $21.5 million. The FIPER software environment developed and demonstrated at GE Global Research Center (Chief architect and lead developer: M. Sobolewski) in collaboration with GE Aircraft Engines (Cincinnati, OH), Goodrich Corp. Aerostructures Group (Chula Vista, CA), Parker Hannifin Corporation (Mentor, OH), Engineous Software, Inc. (Cary, NC), Ohio University (Athens, OH).
 * M. Sobolewski established the SORCER Laboratory at Texas Tech University (2002-2009) to continue his FIPER-based research funded by General Electric, Texas Tech University, Sun Microsystems, Air Force Research Laboratory, and others). 25 graduate research studies completed to support the development of the SORCER platform and foundations of federated service-oriented computing.
 * Collaborative SORCER-based projects (2007-2010) with Beijing Jiaotong University, China; Beihang University, China; and Ulyanovsk State University, Russia.
 * From 2008 M. Sobolewski is continuing his SORCER applied research at Multidisciplinary Science and Technology Center, Air Force Research Laboratory/WPAFB and from 2010 at Polish Japanese Institute of IT.
 * From 2010 the SORCER Laboratory becomes the independent research organization focused on federated service-oriented computing.
 * Development of SORCER-based Engineering Toolkit (2013) by Sorcersoft.com in cooperation with the Polish-Japanese Institute of Information Technology and SMT Software.