International Journal of Computer Science Trends and Technology (IJCST) – Volume 3 Issue 6, Nov-Dec 2015 ISSN: 2347-8578 www.ijcstjournal.org Page 140 Middleware Interoperability using SOA for Enterprise Business Application T Sathis Kumar Assistant Professor Department of Computer Science and Engineering Saranathan College of Engineering, Trichy Tamil Nadu - India ABSTRACT In general a business level service can be implemented by multiple objects/components, or by a non-OO approach. SOA can be achieved with many types of middleware. The middleware works in terms of services. Quality of Service based on Security , Transactions, Routing, Logging, Failover, Protocols and of course Message formats. This may help to keep the business and implementation levels separate for the designers and implementers. To get an enterprise-wide SOA, we need to have middleware interoperability. The interoperability takes care of the ability of software and hardware on different machines from different vendors to share data. But middleware doesn’t interoperate; even the “service” interfaces are different. A service has an interface, and this is the key to hiding details such as the operating system, programming language, network addresses, etc.But this interface doesn’t hide/abstract the middleware itself. In this paper, I examine how the security applies to the Service Oriented Architecture (SOA) through the interoperability . Keywords:- Web Services, SOA, Interoperability, SOAP, WSDL, WSARCH. I. INTRODUCTION A service is a Software component that is well-defined, well-structured, self-contained, and does not depend on the context or state of other services. Nowadays, service-oriented architecture (SOA) is used as an efficient solution to integrate the distributed applications in an enterprise model. In a SOA- based environment, Security is one of the major concerns when developing enterprise business applications. Fig. 1 SOA Components and Operations SOA is used to provide an integrated, flexible, and cost efficient (Web) Service-based enterprise. It promises interoperability, reusability, loose coupling, and protocol independency of services as core principles of SOA ([1][2]). Normally, this standard-based approach uses Web Services as building block to support particular business tasks. Web Services are published with Web Services Description Language (WSDL) interface and they use Simple Object Access Protocol (SOAP) as a communication protocol. In the context of SOA, developers must focus the interoperability of services. Thus, SOA experts must provide the capability to secure the architecture instead of securing a service itself [1]. In order to overcome these matters, the various functional and non-functional security requirements are needed to be considered. So me of these requirements such as authentication, end-to-end security, interoperability, access control, auditing, secure configuration, assurance, and compliance have been presented by [1], [2], and [4]. In addition, some technologies and standards such as XML Signature [7], XML Encryption [8], WS-Security [9], XKMS [10], SAML [11], and XACML [12] have been developed to support the above requirements. RESEARCH ARTICLE OPEN ACCESS