End-to-end paths for web services
This page provides a starting point for finding information about web services.
They implement a services oriented architecture (SOA), which supports the connecting or sharing of resources and data in a very flexible and standardized manner. Services support dynamic, automated discovery and reuse.
Subtopics
- Task overview: Implement web services applications
WebSphere Application Server supports Web services developed and implemented based on various Java programming models. Use web services when operating across multiple platforms, including Java EE and non-Java EE platforms.
- Create a monitor for WebSphere Application Server for WSDM resources (deprecated)
The Web Services Distributed Management (WSDM) monitoring support provided in the Version 6.1 Feature Pack for Web Services uses an external management software. It is, however, more useful to build a custom WebSphere Application Server monitor for WSDM. Use this task to create a WSDM monitor based on the JAX-WS programming model.
- Implement web services applications with JAX-WS
When starting from existing JavaBeans or enterprise beans, we can use a bottom-up approach to developing Web services based on the JAX-WS programming model.
- Implement web services applications from existing WSDL files with JAX-WS
When starting with an existing Web Services Description Language (WSDL) file, we can use a top-down approach to developing web services based on the JAX-WS programming model.
- Customize URL patterns in web.xml for JAX-WS applications
The web.xml file contains information about the structure and dependencies of web components in the module and describes how the components are used at run time. For JAX-WS applications, we can customize the URL pattern in web.xml.
- Use handlers in JAX-WS web services
JAX-WS provides you with a standard way of developing interoperable and portable web services. Use JAX-WS handlers to customize web services requests or response handling.
- Implement static JAX-WS web services clients
We can develop static web services clients based on the Web Services for Java EE specification and the JAX-WS programming model.
- Implement dynamic JAX-WS web services clients
We can develop dynamic web services clients based on the Web Services for Java EE specification and the JAX-WS programming model.
- Configure a web services client to access resources using a web proxy
We can configure a web services client to access resources through a web proxy server.
- Implement web services applications with JAX-RPC
We can use JAX-RPC to develop web services.
- Implement web services applications from existing WSDL files with JAX-RPC
We can develop a web service with an existing WSDL file using JAX-RPC.
- Use WSDL EJB bindings to invoke an EJB from a JAX-RPC Web services client
WebSphere Application Server supports directly accessing an EJB as a web service, as an alternative to using HTTP or Java Message Service (JMS) to transport requests between the server and the client.
- Implement JAX-RPC web services clients
We can develop web services clients based on the Web Services for Java EE specification and JAX-RPC.
Related information:
End-to-end paths for web services - Addressing (WS-Addressing)
End-to-end paths for web services - Reliable messaging (WS-ReliableMessaging)
End-to-end paths for web services - Policy (WS-Policy)
End-to-end paths for web services - UDDI registry
End-to-end paths for web services - Resource framework (WSRF)
End-to-end paths for web services - RESTful services
End-to-end paths for web services - Security (WS-Security)
End-to-end paths for web services - Transaction support (WS-Transaction)
End-to-end paths for web services - Transports