Network Deployment (Distributed operating systems), v8.0 > End-to-end paths
End-to-end paths for web services - Transports
Transport chains represent a network protocol stack used for I/O operations within an application server environment. Transport chains are part of the channel framework function that provides a common networking service for all components.
- Use HTTP session management support for JAX-WS applications
HTTP session management is performed in the HTTP transport layer by using either cookies or URL rewriting. By providing multiple options for tracking a series of requests, HTTP session management enables JAX-WS applications to appear dynamic to application users.
- Use HTTP to transport web services requests for JAX-RPC applications
We can develop an HTTP accessible Java API for XML-based remote procedure call (JAX-RPC) web service when you already have a JavaBeans object to enable as a web service.
- Use HTTP to transport web services requests for JAX-WS applications
We can develop an HTTP accessible JAX-WS web service when we have an existing JavaBeans object to enable as a web service.
- Use HTTP to transport web services
We can develop an HTTP accessible web service when we have an existing JavaBeans object to enable as a web service.
- Configure a permanent reply queue for web services using SOAP over JMS
When using two-way web service communications using the industry standard SOAP over JMS protocol, you can benefit from configuring a permanent reply queue on a Java API for XML Web Services (JAX-WS) or JAX-RPC web services client. The use of a permanent reply queue can improve performance because this reply queue prevents the client from having to create a temporary reply queue each time a web services request is invoked.
- Configure a permanent replyTo queue for JAX-RPC web services using SOAP over JMS (deprecated)
When using two-way web service communications using the IBM proprietary SOAP over JMS transport, you can benefit from configuring a permanent replyTo queue on JAX-RPC web services client to prevent the client from having to create a temporary reply queue each time a web service request is made.
- Use SOAP over JMS to transport web services
We can use the SOAP over JMS transport protocol as an alternative to SOAP over HTTP for communicating SOAP messages between clients and servers.
End-to-end paths for web services
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)