Implementing and deploying Web Services in the Apache Geronimo application

Now, whether your enterprise application is deployed in a small home store or as part of an enterprise infrastructure across multiple domains, it must support WEB services, whether or not the application is collaborating with others.

Way

Modern enterprises are often very complex systems that face many opportunities and challenges every day. Many opportunities involve integration or collaboration with other systems and enterprises. As a result, smart enterprise application developers make sure that other applications can easily access their applications. WEB services are a good way to provide this accessibility.

Apache Geronimo Application Server supports WEB services and other features of the latest java™2 Platform, Enterprise Edition (Java EE) specification. To demonstrate Web service support in the Geronimo application server, the IBM Advanced Technology Solutions team has decided to improve a software simulation program that simulates a simple banking scenario and is for a previous piece of DeveloperWorks The article "Building a secure enterprise infrastructure using Geronimo" (developerworks,2005 July) was developed.

This article uses the business scenario to implement a money transfer use case. Retail bank customers (users) can access the application and transfer funds from their accounts, and the auditor can oversee all banking transactions. The existing funds transfer applications have been improved to allow Web services to provide back-end functionality using simple Object Access protocol/hypertext Transfer Protocol (soap/http) and simply Web service clients.

What is a Web service?

Web services are an application business logic that can be performed using ubiquitous Web protocols and data formats such as HTTP and SOAP. Since the launch of Java EE 1.4, WEB services have been incorporated into the Java EE. In the context of Java EE, Web services are considered to be the appearance (façade) of the backend implementation-the backend implementation may be Enterprise JavaBean (EJB) or servlet. The following artifacts make up the Web service:

A Web service definition Language (Web services defined language, WSDL) document that describes the service interface and port.

A service endpoint interface that is implemented by the server section to invoke the service method on the client. The bindings from the WSDL map to this endpoint interface, which is part of the WSDL and defines the protocol for the WEB service.

The Java API for xml-based RPC (JAX/RPC) descriptor contains different mappings from XML to Java technology, such as mapping XML Schema Definition (XSD) types from WSDL documents to Java types, and XML elements are mapped to endpoint interface method parameters.

Service implementation--EJB or servlet.

WEB Service Deployment Descriptor Webservices.xml.

The following sections develop these artifacts to build a WEB service-enabled application for Geronimo.