As we discuss in this article, all communications in SOA-based systems are messages. Further, a powerful way to implement these systems is to place the service “islands” on a software-level messaging substrate that implements efficient routing, security, reliability and other qualities of service. As we will show, such systems support messages of all types, from infrequent update notification events to continuous streams. We suggest that in the complex evolving technology scene today, not only services but their collection into systems of higher functionality should be as decoupled as possible in architecture and tight timing constraints. This we call the principle of building “Grids of Grids of Simple Services” Many important Grid applications in real-time data mining involve all of these message types. We discuss a GIS (Geographical Information System) example from our SERVOGrid (Solid earth Research Virtual Observatory) work that uses the NaradaBrokering messaging system for managing data streams from GPS stations. We are in the process of connecting these to RDAHMM, a time series data analysis program useful for mode change detection. These streaming services form one sub-Grid in the “Grid of Grids” system supporting solid earth science and also containing (sub)-Grids involving code execution services and information/metadata services.
Secure Service Rating in Federated Software Systems based on SOA, The Service oriented architecture (SOA) paradigm mostly provides a suitable approach as to meet the requirements of flexible distributed software systems. Referring to the activities for the standardization of web service semantics or alternatively the introduction of intelligent search mechanisms future software architectures are supposed to integrate software components as remote services of foreign providers. If the authors assume that such services can be standardized. Example as components of standard business applicationsystems, the vision of a services economy arises where services of the sane type can be marketed by different providers. A service consumer on the other hand could choose the service he likes best at run time. However this vision is clouded by a multiplicity of risks which meet each other in the question of the specific reliability and trust worthiness of service providers in a certain context. Previous research activities picked up these problems where by a lot of promising approaches and frameworks have been developed which concern the negotiation of trust within open network architectures like grids are peer to peer networks. Nevertheless, the genesis of the reuse relationships between two network nodes had been neglected. Presents an approach for the establishment of reputation in federated software systems, where central network instances for the management of evaluations are avoided. Approach the service providers are responsible for this task on their own. The author presents a novel security protocol for the message based exchange of service evaluations that filters service providers from manipulating their own ratings [Nico Brehm].
Nikolay Kakanakov  mainly discussed the possibility of adaption of WEB service architecture (WSA) for implementing distributed embedded systems. The WSA integrates the best aspects of component-based development and World Wide Web. According to R. Pallavi  a service is: “a software system identified by a URI, whose public interfaces and bindings are defined and described using XML. Its definition can be discovered by other software systems. These systems may then interact with the WEBservices in a manner prescribed by its definition, using XML based messages conveyed by Internet protocols.” Applications access WEBservices via common WEB protocols and data formats. The most common used protocol for transferring data in the Internet is HTTP (Hypertext Transfer Protocol) and it is the key transport protocol in the WSA. The universal schema in the Internet is the one that codes the data is XML (Extensible Mark-up Language). The current structure of Internet is based on program-to-user interaction and the WSA is based on program-to-program interaction . The WSA is based on some key standards: XML for data representation; SOAP for accessing services; WSDL for describing services; UDDI - registering and discovery of services.
• SOAP is the standard messaging protocol used by Webservices, an XML-based communication protocol for exchanging messages between computers regardless of their operating systems, programming environment or object model framework.
In fact Grid messaging is more naturally related to message oriented middleware (MOM) [Bernstein1996] [MOM] and software overlay networks [Doval2003] than to MPI or PVM style messaging. The rich MOM infrastructure support messages that are self-describing and as well capture semantic intent. Depending on the application these messages can be made to encapsulate system conditions, method invocations, resource sharing, data interchange among others. Messages may also describe their correlation, dependency and causal relationships to other messages. The SOAP messaging used by WebServices illustrates this richer structure with a body containing the “real message” and separate headers corresponding to systemsservices including security, notification, virtualized addressing, fault tolerance, notification and special operations and relationship to resources. Processing this additional information typically takes a millisecond or so and adds significant functionality at insignificant fractional cost. In designing systems and algorithms for distributed systems it is important to understand this additional functionality and incorporate it into your architecture. Another difference between SOAP and MPI is that MPI only specifies interface and so interoperability between different MPI implementations requires additional work [IMPI]. SOAP however specifies both interfaces and message structure so broad interoperability can be achieved. This is a achieved at a performance cost that we return to in Sec 6.5.
Organisations use Enterprise Service Busses (ESBs) to support enterprise application integration. For a variety of reasons – mergers and acquisitions, geographically distributed enterprise units, distributed governance, scalability – enterprises sometimes need to acquire multiple, disparate ESBs and enable the applications that each one supports to interoperate. However, currently, no standard architecture exists for integrating multiple, disparate ESBs. To begin to address this problem, four candidate disparate ESB integration patterns – directly connected, webservices, homogeneous messaging middleware, and message bridge – were identified from the enterprise application integration literature and tested for their effectiveness in integrating multiple, disparate ESBs. Each pattern was applied in two different scenarios: loan broker request, and inter-divisional messaging. In each scenario a number of enterprise applications were integrated using three disparate ESBs: Oracle Service Bus, Apache ServiceMix, and Mule ESB. The experiments were designed to test how well the different patterns supported effective integration of different ESBs. The results indicate that the webservices and homogeneous messaging middleware patterns are the best for integrating disparate EBS effectively and with minimal difficulty. In addition, it was discovered that the degree to which ESB integration could be achieved depended upon the number of ESBs being integrated, the relevant skills of the integration team, and the types of the ESBs. The results may be of practical benefit to the communities engaged in enterprise application integration research and practice.
6. Related Work. Considerable work is done in the general area of CBR, see e.g.,  for the proceedings of a recent conference. Well received work by several authors reports on CBR systems for the World Wide Web [45, 44, 5]. All these image search engines are based on the client/server paradigm of collecting images from the Web. Mobile agent technology is complementary to this work. It remains to be investigated how well the algorithms developed by the authors mentioned above can be adapted to be used within a mobile agent framework. The idea of using mobile agents for content based image retrieval has been mentioned before [39, 2, 54]. Mobile agents have also been applied in related applications. For instance, in , Johansen reports on the use of mobile agents in the context of a weather information system (mobile agents process and deduce weather information from satellite imagery). Early attempts to integrate static agents and Webservices have been described in [31, 55, 8]. More sophisticated solutions, especially in the context of FIPA-compliant agent platforms, have been presented in [29, 14, 46, 20]. In contrast, the existing contributions based on mobile agents have more diverse goals, and thereby do not completely follow transparent integration of agents and Webservices [9, 30, 35, 13, 24].
This paper explores technology permitting arbitrary application components to be ex- posed for remote access from other software. Using this, the application and its constitu- ent components can be written without concern for its distribution. Software running in different address spaces, on different machines, can perform operations on the remotely accessible components. This is of utility in the creation of distributed applications and in permitting tools such as debuggers, component browsers, observers or remote probes ac- cess to application components. Current middleware systems do not allow arbitrary expo- sure of application components: instead, the programmer is forced to decide statically which classes of component will support remote accessibility. In the work described here, arbitrary components of any class can be dynamically exposed via WebServices. Tradi- tional WebServices are extended with a remote reference scheme. This extension permits application components to be invoked using either the traditional pass-by-value semantics supported by WebServices or pass-by-reference semantics. The latter permits the preser- vation of local call semantics across address space boundaries.
A side-effect of the advancement was that different computing systems were introduced. Some were made too simple to carry out the duties they were supposed to perform while others were made too complex. The cost of building and maintaining them rocketed, not to mention the nearly impossible task of integrating different systems together. As more and more software systems are built, similar situations and patterns appear. Naturally, we want to reuse the functionality of existing systems rather than building them from scratch. This led to the idea of a Service Oriented Architecture (SOA) [1, 2], which is an architectural style for loosely coupling interacting software agents. A SOA provides an interoperable platform that helps maximize reusability of existing software resources. While it is clear that SOA and its current implementation, Webservices , will have profound impact on the next generation of distributed systems, many aspects of this platform still require significant research and development.
Information and content management systems require access controls to information content. In publish/subscribe style systems, for example, there will be various restrictions on access to both topics and particular privileges associated with that topic, or channel. We are particularly interested in access control systems that are associated with XML metadata systems. XML metadata is important for future Web service applications . Open Grid Service Architecture (OGSA)  and Semantic Web  both depend on metadata . We have examined the low-level requirements for managing the XML nuggets of such systems, which include the following: composing tools for creating valid, correct XML metadata nuggets; an architecture and implementation for delivering metadata in the form of messages to listeners who has access to use specific message channel; metadata browsers that can sort and display the nuggets by category; and user role/access control system to define user levels and privileges. The implementation of these ideas is discussed in Ref. . Specific
By employing Webservices technology, the Grid system is evolving to be more manageable service infrastructure, including lifetime management, discovery of characteristics, and notifications. Reliable messaging is one of the key issues addressed for quality of services in Webservices. In this paper, we propose a reliable message scheme designed for mobile environments in the context of a Webservices architecture; Webservices —Wireless Reliable Messaging (WS-WRM). We also consider the federation issues with emerging specifications proposed by leading Webservices standard groups. We eventually intend to extend the reliability to mobile end-nodes in a more efficient way. In this paper, we address the design issues and describe the detailed scheme of messaging architecture.
In addition, we plan to build new interconnection infrastructure for the message delivery between these GIS services, to eliminate the service dependence on HTTP for SOAP transport. We use NaradaBrokering as a message based middleware system between these components to deliver the request and response messages wrapped in SOAP envelope. NaradaBrokering is a distributed messaging infrastructure that provides a message oriented middleware which facilitates communications between the distributed entities through the exchange of messages. NaradaBrokering provides some features that are important in GIS area. These are Quality of Service (QoS) and security profiles for sent and received messages, interface with reliable storage for persistent events, reliable delivery via WS-Reliable messaging, fault tolerant data transport, support for different underlying transport implementations such as TCP, UDP, Multicast, SSL, RTP, HTTP, discovery service to find nearest brokers / resources (efficient routing).
The Insufficient Transport Layer Protection vulnerability is due to the fact that Web applications do not protect or poorly protected the network traffic. SSL/TSL has been used by webapplication only during the authentication phase. data and session IDs are in clear-text in application network flows. Expired certificates or misconfigured can also be the cause of this type of vulnerability. Improper configuration of SSL can facilitate such attacks "phishing" type "man in the middle", etc… An attacker can: