Transport chains represent a network protocol stack that is 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.
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 Java API for XML-Based Web Services (JAX-WS) applications to appear dynamic to application users.
You 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.
You can develop an HTTP accessible Java API for XML-Based Web Services (JAX-WS) web service when you have an existing JavaBeans object to enable as a web service.
You can develop an HTTP accessible web service when you have an existing JavaBeans object to enable as a web service.
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 Java API for XML-based RPC (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.
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 Java API for XML-based RPC (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.
You can use the SOAP over Java Message Service (JMS) transport protocol as an alternative to SOAP over HTTP for communicating SOAP messages between clients and servers.