CloudMinga has a descriptive architecture for data storage. It relates business logic part with different web services in such a way that uniquely performs backup operations for different server storage.
Generic Web Service: It is designed to be used by non-programmer people (for example QA testers), but it is very useful also for developer since it is easy to use for rapid tests.
The main feature are:
* User accounts management: each users may save wsdl references in his own profile.
* Support wsdl password and endpoint call protection with BASIC authentication.
* Organize request and response in a human readable tree.
* Automatic generation of requests from associated schema with dymamic creation of optional elements (Arrays, complex types and so on).
Here are some important things to consider about this approach:
It’s based on standards:
The entire Web services approach is based on a set of standard protocols and technologies, so that all participating components understand how to communicate. For example, service discovery in a UDDI registry uses a standard messaging protocol called SOAP. Service definitions follow a Web service description standard called WSDL. And the transactions that involve the exchange of business profiles follow ebXML Messaging standards. The bottom line is that companies no longer have to work out special, proprietary agreements regarding how to communicate requests between their systems, and what the communicated information means.
It offers advantages to service providers and clients
In the big picture, the Web services model offers advantages to Web service providers and the clients that use the services. Web service providers can use the Internet to market their services to a potentially huge set of possible clients. For clients, it can mean quicker and more flexible application development. Instead of creating large applications that include all necessary logic and data, developers can create smaller applications that access needed functions through Web services. For example, instead of including credit card transaction processing functions in an online retail application, an application can access a Web service that provides those functions. Clients can search for registered services that meet their requirements, select the best one, and use it. It doesn’t matter where the Web service is located on the Internet — as long as the Web service is registered, it’s available to clients. In other words, the entire World Wide Web is potentially available to satisfy the service requirements of a client.
In addition, a Web service can locate and use other Web services. For example, the credit card transaction Web service can access a Web service that tracks credit history.
Web Services Technologies:
One of the things that makes the Web services model so attractive is that it’s built on standard technologies, especially Extensible Markup Language (XML) technologies, that have wide industry acceptance. These technologies make for an “open” environment, ensuring that a Web service can be located and used, no matter where it is, what platform it runs on, or who developed it.
XML is emerging as the standard for exchanging data on the Internet.
XML and Hypertext Markup Language (HTML) have the same ancestry: Standard Generalized Markup Language (SGML). SGML is an international standard for defining the structure of electronic documents. These include Web-based and non-Web-based documents. SGML is functionally rich but complex. HTML is a small, simple application of SGML that defines the structure of the type of document you typically see on the Web — that is, one with paragraphs, lists, tables, graphics and so on. XML is a more ambitious application of SGML. It allows you to define your own type of documents.