Dynamic Aspects of Industrial Middleware Applications Public

Dynamic Aspects of Industrial Middleware Applications Public examination of the dissertation 25.03.11, 12:00, Villa Rana, Blomstedt hall Industrial Ontologies Group Sergiy Nikitin [email protected]

Industrial Ontologies Group one more thesis “Device” Group supervised by Prof. Vagan Terziyan [email protected] Industrial Ontologies Group

Who is this guy?

Contents What is middleware and what architectures are available? Industry vs. Middleware Dynamics and key aspects in industrial software How to keep it simple? Conclusions

What is middleware? Middleware is computer software that connects software components or some people and their applications. The software consists of a set of services that allows multiple processes running on one or more machines to interact. Source: wikipedia (http://en.wikipedia.org/wiki/Middleware)

Middleware is

Middleware is

A honest confession Middleware is a fine-grained standalone runnable API allowing to connect your IT-system to other software It is running somewhere independently It provides clear API to access it It may connect to or use other software

So, where is middleware?

You’re right! Middleware is in the middle!

Industry perspective

Production line life time All those systems stay in use! 1980 1990 2000 2010 2020 2030

Product supplier’s perspective We want our software to: Integrate with legacy systems (still cheaper than build new ones) Integrate with new components Establish new networked business processes at no pain and fast Be ready to meet unforeseen customer wishes and requests

Middleware vs. industry Middleware is used to: provide interoperability simplify complex distributed applications support application development and delivery Middleware in IT based on XML, SOAP, Web services, and service-oriented architecture includes web servers, application servers, and similar tools Industry looks for ways to: lower the product cost offer a competitive advantage but stay within attractive price boundaries ICT-solutions (of any type) supplied with the product are getting more and more complex, thus becoming a burden for a product price

Middleware today IBM middleware services SAP NetWeaver (SOA middleware) Oracle Fusion Middleware Microsoft SharePoint

A middleware marketing outlook: Oracle Fusion Middleware Complete Integrated Hot-pluggable Best-of-Breed Enterprise application server Integration- and process-management Application development tools Business intelligence Systems management User interaction Content management Enables Agile and Intelligent Business Applications Exporting new HW and SW architectures App-Centric approach to security Connecting people, processes and applications http://www.oracle.com/us/products/middleware/index.html

But why is it still so hard? It is great and powerful, but It is all extremely expensive It is all extremely complicated It is all technology- and language-specific 空中客車 A380 It all requires huge expertise to drive

Want to become a pilot?

And what about customers? They rather appreciate coffee you serve on board, than a complexity of your plane

A bit of controversy Industry wants middleware to be: As simple to use as e.g. coffee maker As efficient as A380

How to make middleware simple? Make it smart Delegate the complexity to intelligent selfaware tools, able to manage themselves

Simple yet smart middleware? We want it to be: as reliable and smart as autopilot still as simple to use as coffee maker but what are the preconditions for that?

What middleware ”seed” we need? A proper ”seed” is a language that supports: Extensive usage of consistent feature-rich vocabulary for content management Vocabulary-based annotations of services, applications, etc. Vocabulary-based connector and adapter framework

What middleware “soil” we need? Component Autonomy (Goaldriven behaviour, learning) Cloud Computing A common “matrix office” for software Plug and Play approach Use software pieces on the fly

A middleware sprout

GUN Environment (A middleware field) GUN – Global Understanding eNvironment GUN Global Environment Global Understanding Proactive Self-Managed Semantic Web of Everything http://www.mit.jyu.fi/ai/OntoGroup/projects.htm http://www.mit.jyu.fi/ai/Industrial Ontologies Group booklet print.doc

Global Understanding Environment (GUN) GUN can be considered as a kind of Ubiquitous Eco-System for Ubiquitous Society, which will be such proactive, self-managed evolutionary Semantic Web of Things, People and Abstractions where all kinds of entities can understand, interact, serve, develop and learn from each other. Human-to-Human Human-to-Machine Machine-to-Human Machine-to-Machine Software-to-Human Software-to-Machine Software-to-Software Human-to-Software Agent-to-Agent

Conclusions Middleware is about minimizing programmer efforts when developing complex distributed applications Middleware architectures themselves are getting too complex, therefore the utility of those is decreasing The complexity can be tackled by involving intelligent goal-driven entities and tools that are only applicable, when a certain degree of disambiguation and detail achieved within the environment True utility of new middleware can be achieved when a programming language and development tools provide native support for above mentioned features

But we should keep the button