1. Self-Regenerative Middleware Service for Cross-Standards and Ubiquitous Services Activation Mengjie Yu (Email: cmsmyu@livjm.ac.uk ) cmsmyu@livjm.ac.uk Supervisor: Prof A.Taleb-Bendiab

2. Contents Overview n Research Background n Related Works n Research Focus n Research Approach n Current Work n Future Work

3. Research Background n Software/Middleware Architecture Development Tendency Static Model Dynamic Approaches Service-Oriented Model Source: Based on Sun

4. Related Works n CORBA Portable Object Adapter Object Request Broker (ORB) interfaces  Varieties types of implementation n Web Service Invoke Framework (WSIF) SOAP Protocol-independent through an abstraction representation layer n OpenWings Usage of connectors to create protocol-independent abstract layer cross- standards. Usage of connectors to create protocol-independent abstract layer cross- standards. n OGSA Summary:  Design-Time Supports for Service Interoperation/Adaptation Cross-standards  Specific APIs or standardized Technologies Implementation Grid-enabled Web services, SOAP underlying protocol, Standard service interface

5. n Self-management focusing on: –Runtime Adaptation of Cross-Standards Service Invocation  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 Application 1 Application 2 Self-generative Adaptation Code Runtime Research Focus 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

6. Research Approach n Generative Programming on Service Adaptation Construction n Self-Regenerative Middleware Adaptation Service  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  Provide multiple-access endpoints  Monitor and manage the process of adaptation construction

7. n Dynamic Service Adaptation Mechanism Application 1 (Protocol 1) Adaptation Code Application 2 (Protocol 2) Protocol 1 Method Call Protocol 2 Method Call Invocation Adapater Application Parameters Extra File ( I.e RMI Interface) WSDL Invocation Information e.g. Description Documents (WSDL file) or Interface (Java Remote Interface) Current Work

8. n Service Adaptation Construction by Use of Template Class Design 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 call=new Call(); call.setTargetObjectURI(objectURI); call.setMethodName(serviceName); ….. call.setParams(params); ….. resp=call.invoke(url, “”); …. } … SOAP-RPC Adapter 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 call=new Call(); call.setTargetObjectURI(“HelloWorld”); call.setMethodName(“sayHello”); ….. call.setParams(params); ….. resp=call.invoke(“http://localhost:8080 /apache-soap/servlet/rpcrouter”, “”); …. }

9. Current Work n Polyarchical Middleware Structure

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

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

12. Thank you Thank you