Mobile Advertising Using J2me
Construction companies Basic Service – Soa
SOA as Service Oriented Architecture is an architecture for building systems based on coupling loose interoperable services. SOA is a broad term that goes beyond the software architecture. SOA is a guideline to build a system architecturual based services. What are services? In SOA, software and hardware and the system built around it is called a service. Although SOA is especially given the context software, but nothing stops him from being a hardware. Services can be both welcomed as software or hardware. These services are offered in a common communication link (such as the Internet) so that consumers (customers) can see what services are offered. The term loosely coupled in SOA is very important. Loose coupling means that the Service is mainly independently with little or no dependencies. This means that the consumer is assured of getting the expected result of the call service if the service parameters within specification. A service expected receive the data on which it operates. These data are fed to the service in different ways. Among the many ways in which property Data can be fed a standard way of sending and receiving data is REST (Represental State Transfer) and SOAP (Simple Object Access Protocol). These formats are unrelated to the service itself (hence the loose coupling), but rather represents the data and the data structure. Therefore, both REST and SOAP messages can be performed by any service and the customer.
The reason for SOA to be interoperable is in fact derived from loose coupling. The adoption of a format message dependent data such as REST or SOAP makes the service work on all platforms. SOA is not associated with HTTP or JMS service. A service of SOA can be based on REST, SOAP or some proprietary format as long as the services are loosel coupled and interoperable. If the protocol is SOAP, it is also called Web Services. If the format is REST, it is called RESTful service. A single service can support both SOAP and REST. Both SOAP and REST are data representation format, not a transport. Because the service and client must be somehow connected, transport can be HTTP / HTTPS, JMS, FTP, files, etc. SOA does not limit the type of transport. The most popular are, however, HTTP (S) and JMS. HTTP (S) is the most popular reason for his support by web browsers making firewall security and the web browser loan. SOA services can be consumed by web applications and any other platform specific applications. JMS (Java Messaging Service) is generally used in cases of asynchronous communication between the client and service. An ideal SOA service should be able to handle both synchronous and asynchronous transport. In general, transport synchronous uses RPC-based protocol and transport protocol using asynchronous message based.
Consider that we have a service address book SOA as a service that can be consumed by both a written request J2ME mobile phone and a PC application written in C #. NET. AddressBook service must be interoperable because he is consumed by two different applications written in two different programming languages. The mobile phone sends REST data format through HTTP-based address book service, while the PC application sends SOAP format via JMS. The Address Book service is designed to support both REST and SOAP, as the data format is received by the address book, it can process data and returns the result in the same format in which it has received. Note that the transport layer was not a concern for Service address book. Service is between SOA and client is a middleware routing called an ESB (Enterprise Service Bus). It is almost a router that converts data or transport, in one form to another. Although BSE is much more modern than just a router, but router is the part that is responsible routing of any activity for the service address book. In general, BSE is not a necessity, but if not present, should the service itself supports multiple protocols and message formats. This makes it difficult to maintain each service. Therefore, having an ESB from a service and customer service is easy to develop and maintain.
SOA achieves loose coupling by eliminating the transport layer and join the data structure and maintaining the data represented in a standard format, it becomes interoperable. SOA services are also described in standard. Web Services uses the XML model called WSDL (Web Services Description Language) to describe the messaging format to communicate with the service. WSDL can be discovered by having advertised in registries. A register is conceptually similar to the registration of domain names, except that now it is for a SOA service.
About the Author
Soalib is in the business of building loosely coupled interoperable applications (SOA), which is proven to work from embedded systems, mobile phones, PCs and mainframes. By utilizing SOALIB libraries one may build their own interoperable applications for multiple operating environment. For more information, visit http://soalib.com
NOM – Rotating mobile game – GAMEVIL Korean Commercial
