Self-Regenerative Middleware Service for Cross-Standards and Ubiquitous Services Activation

1
Self-Regenerative Middleware Service for
Cross-Standards and Ubiquitous Services Activation

• Mengjie Yu
• (Email cmsmyu_at_livjm.ac.uk )
• Supervisor Prof A.Taleb-Bendiab

2
Contents Overview

• Research Background
• Related Works
• Research Focus
• Research Approach
• Current Work
• Future Work

3
Research Background

• Software/Middleware Architecture Development
  Tendency

Service-Oriented Model
Static Model
Dynamic Approaches
Source Based on Sun
4
Related Works

• CORBA Portable Object Adapter
• Object Request Broker (ORB) interfaces ?
  Varieties types of implementation
• Web Service Invoke Framework (WSIF) SOAP
  Protocol-independent through an abstraction
  representation layer
• OpenWings
• Usage of connectors to create
  protocol-independent abstract layer cross-
  standards.
• OGSA

Grid-enabled Web services , SOAP underlying
protocol, Standard service interface

• Summary
• Design-Time Supports for Service
  Interoperation/Adaptation Cross-standards
• Specific APIs or standardized Technologies
  Implementation

5
Research Focus

• Self-management focusing on
• Runtime Adaptation of Cross-Standards Service
  Invocation

Application 1
Application 2
Runtime
Self-generative Adaptation Code

• Research Challenges
• Interoperation among varieties of
  existing/emerging service bindings Service
  Invocation Programming Models Service
  Interface Definition Interpretation
  etc. WSDL, Java Remote Interface, IDL
• Runtime Self-Regeneration on Adaptation
  Self-awareness/Self-analysis about Legacy
  Services --- through service interface
  descriptions Self-generation on appropriate
  adaptation code

• Self-Regenerative Adaptation
• Coexistence of legacy services or emerging
  service standards, with less modifications on
  service original implements/designs Multiple
  Service Bindings/Implementation/Description
  Interfaces

6
Research Approach

• Generative Programming on Service Adaptation
  Construction

• Utilize Template Class Design Model
• Provide reuse of service invocation code
• Increase efficiency and correctness of runtime
  programming
• Hide away the technical details from end-users

• Self-Regenerative Middleware Adaptation Service

• Provide multiple-access endpoints
• Monitor and manage the process of adaptation
  construction

7
Current Work

• Dynamic Service Adaptation Mechanism

Invocation Adapater
Adaptation Code
8
Current Work

• Service Adaptation Construction by Use of
  Template Class Design

ltwsdlgt ltbindinggt lt/bindinggt ltservicegt
lt/servicegt lt/wsdlgt
public class SoapAdapter implements Adapter //
Constructor public SoapAdapter (String url,
String serviceName, String objectURI,
Vector params) //
standardized method public Object invoke()
throws Exception // Standard
invocation code Call callnew Call()
call.setTargetObjectURI(objectURI)
call.setMethodName(serviceName) ..
call.setParams(params) ..
respcall.invoke(url, ) .
public class SoapAdapter implements Adapter //
Constructor public SoapAdapter (String url,
String serviceName, String objectURI,
Vector params) //
standardized method public Object invoke()
throws Exception // Standard
invocation code Call callnew Call()
call.setTargetObjectURI(HelloWorld)
call.setMethodName(sayHello) ..
call.setParams(params) ..
respcall.invoke(http//localhost8080
/apache-soap/servlet/rpcrouter
, ) .
SOAP-RPC Adapter
9
Current Work

• Polyarchical Middleware Structure

10
Example
Legacy Services
Web service
Polyarchical Middleware
Jini
adapter.invoke()
SOAP-RPC
Synchronous Calls
Service Manager/System Controller
Service 4
Service 1
Service 3
Service 2
Service 2
Service Assembling Workflow (JavaRMI)
11
Future Works

• Extend the approach to Asynchronous Invocation
  Mechanism used in Message-Oriented Middleware
• JXTA Platform (Peer Messages,
  Peer Group Service)
• J2EE, WS (SOAP-Messaging)
• Evaluation
• Thesis Writing-Up

12

• Thank you ?