Escolar Documentos
Profissional Documentos
Cultura Documentos
Team members
-Mayank Pandey[11MCMB05] -Deepak Gupta[11MCMB13] -Vivek Kumar Yadav[11MCMB30]
Abstract:
In this era of information technology revolution our goal is making efficient, accurate and fast result in short time period. As the Internet is widely accepted throughout the globe, our aim is to get dynamically selecting services for satisfaction of users requirement. for this purpose many different approaches are being suggested. In this paper we are describing one of them. Thai is Dynamic Web Service Composition, in which we combine different web services to achieve better functionality. Here we will discuss different approaches, framework, techniques, step involved in process challenges and some future work.
Introduction:
To understand this topic first we have to understand different terms like web services, web service composition. The term web service describes a standardized way of integrating Web-based applications using various technologies such as SOAP, XML and JSP. For example bank website where you can use various services of bank like viewing transition history, requesting a cheque book on demand. In web service composition many web services are grouped together to perform a specific output according to the request by user. This composition can be static or dynamic. Static composition is totally manual composition where various services are grouped together manually where as in Dynamic web service composition some automated tools are used to understand the users problem and then different services are grouped together automatically.
feed my problems and it will automatically combine different web services and produce the output for me.
of automation. That is why modeling the control flow and data flow is a time consuming process. 3. Execution: Once required web services are composed their execution takes place. For the execution basically it involve two processes. They are i. Choreography: it is the interaction of various services with user or client in order to understand the problem or question. By this process services determine the specification of operations, different conditions, various states. The W3c organization also introduced some language called choreography description language(ws-cdl) and it captures the interaction between the participating services. ii. Orchestration : In orchestration process it define the sequence and condition in which one service invoke other services to carry out any give task. Or we can say it is the process in which different services communicate with each other in order to perform a task.
functions and for this we define an interaction protocol which allows services/agents to dialogue. In service dialogue we tell the mediator what the users requirement based on their question which are stored in registry and from there we analyze all queries. Overview of Multi-Agent-System: This service is viewed as part of agents. It is based on interactive agents that provides web services. Agents are combination of three layers: y Concrete Agent- it provides reasoning of offered services. y Abstract Agent- It represent XML based declaration of functionalities of services. y Web Service- It is WSDL interface of concrete services which are deployed on web. To construct such agent we use VDL(View Design Language).VDL is a programming language for interacting with human and other agents. Agent Interaction Protocol: Requests are stored in mediator agent in a record. Agents behavior are defined according to their role. Mediator agent receives users request and start process. They compose message to answer every questions and used the information stored in received message. Within a the mediator agent proceed to service selection. It aim to select the services that best fit to users requirement.
in centralized dataflow there is a center services location from where the data flows to various services while in decentralized dataflow services exchange data directly. Both of these models have some advantages and disadvantages in terms of network traffic, latency etc but Decentralized method is more efficient for dynamic services. The quality of service of depends upon the complexity of web services and the protocol or methods used by the user.
required expertise and human resources. So here a new approach i.e. model driven approach is given There are three phase in this approach: 1. Modeling Phase The designers make web services and business process. By using two models UML Service Model (USM) and UML Process Model (UPM). Because of these models designer only focus on business requirements. UML is widely used in object oriented software development. As we need information to make the web services so we use the USM. The UPM defines the interaction between the business process and its partners. And gives the variable definition and tells that a task will be executed in which direction. 2. Generation Phase To generate any web service we need to generate first its description, for this we use WSDL and we need to change USM to WSDL, the data type should be change first, then interface and then binding and development.
3. Binding Phase In the binding phase we need to make the matching between different entities and bind them. Then select the operation which are matched and finally we need to have the technical details for each selected operations using WSDL. By this way the executable process proceeds. We have to make a prototype system for execution and make our approach effective. The prototype system is having different parts like Web Service Modeler, Business Process Modeler, APT binder and web service engine. We implement this prototype system in our approach and define different methods.
Various Challenges:
Although dynamic web service composition is is very good technique for automation and fast results yet there are some challenges that are involved and to be faced. some of them are: 1. Interoperability- While executing a composed web service , a web services interact with other and generate output, this output is used by another services to obtain final output. if some parameter is missing or not available for next service then it will fail and hence whole operation will fail. That is why there should be high interoperability. 2. Degree of automation- How much automation is required for a dynamic web composition is not described or defined anywhere. Because many times, for real world application , fully automation does not provide good results. Fully automation is only applicable where problem is well defined. 3. Dynamic nature of market- As nature of market keep on changing with time so a business process have to change with changing time and hence web services related to that process must have to change. 4. Heterogeneity- as we know there are different platforms, software, and operating systems are used worldwide and these web services resides in these environment. So composition of these web services in such environment is also a challenge. 5. Availability of lots of same services- As there are many service provider that provide similar services and also these services have different version available in the market like same services having version 1.0/1.5/1.8.4 etc. so choosing appropriate service is a big challenge.
Conclusion:
Dynamic web service composition is a very important aspect of web services now a day. In this report we have discussed approaches, composition methods and various challenges involved in dynamic web service. Web services are composed and coordinated to execute business processes which uses process based approach. Web service basically provide a suitable technical base for development and deploying loosely coupled and reusable software component and these web services are composed to use these
services collectively for fulfilling the user requirement. Dynamic web service composition is a very important topic of research. Various kind of researches are going on in this topic to improve the performance of web services. In future work we need to consider several improvements to achieve greater performance and scalability in web services.