End-to-end paths for web services
This page provides a starting point for finding information about web services.
Web services are self-contained, modular applications that can be described, published, located, and invoked over a network. 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 are described and organized to support their dynamic, automated discovery and reuse.
Subtopics
Task overview: Implementing web services applications
Use this topic as an introduction to using web services. WebSphere® Application Server supports Web services that are developed and implemented based on various Java™ programming models. Use web services when operating across multiple platforms, including Java Platform, Enterprise Edition (Java EE) and non-Java EE platforms.Creating 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 that is based on the Java API for XML Web Services (JAX-WS) programming model.Implementing web services applications with JAX-WS
When starting from existing JavaBeans or enterprise beans, you can use a bottom-up approach to developing Web services based on the Java API for XML-Based Web Services (JAX-WS) programming model.Implementing web services applications from existing WSDL files with JAX-WS
When starting with an existing Web Services Description Language (WSDL) file, you can use a top-down approach to developing web services based on the Java API for XML-Based Web Services (JAX-WS) programming model.Customizing URL patterns in the web.xml file for JAX-WS applications
The web.xml file contains information about the structure and external dependencies of web components in the module and describes how the components are used at run time. For Java API for XML-Based Web Services (JAX-WS) applications, you can customize the URL pattern in the web.xml file.Using handlers in JAX-WS web services
Java API for XML 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.Implementing static JAX-WS web services clients
You can develop static web services clients based on the Web Services for Java Platform, Enterprise Edition (Java EE) specification and the Java API for XML-Based Web Services (JAX-WS) programming model.Implementing dynamic JAX-WS web services clients
You can develop dynamic web services clients based on the Web Services for Java Platform, Enterprise Edition (Java EE) specification and the Java API for XML-Based Web Services (JAX-WS) programming model.Configuring a web services client to access resources using a web proxy
You can configure a web services client to access resources through a web proxy server.Implementing web services applications with JAX-RPC
You can use the Java API for XML-based RPC (JAX-RPC) programming model to develop web services.Implementing web services applications from existing WSDL files with JAX-RPC
You can develop a web service with an existing Web Services Description Language (WSDL) file using the Java API for XML-based RPC (JAX-RPC) programming model.Using WSDL EJB bindings to invoke an EJB from a JAX-RPC Web services client
WebSphere Application Server supports directly accessing an Enterprise JavaBeans (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.Implementing JAX-RPC web services clients
You can develop web services clients based on the Web Services for Java Platform, Enterprise Edition (Java EE) specification and the Java API for XML-based RPC (JAX-RPC) programming model.
Related information:


File name: welc6tech_wbs_thr.html