NonStop SOAP User's Manual

NonStop SOAP User’s Manual—520501-012
C-1
C NonStop SOAP User-Exits
This section provides software development guidelines and examples of how to
implement Service-Oriented Architecture (SOA) services on HP Integrity NonStop
servers. It specifically describes how to use the user-exit facilities of HP NonStop
SOAP software to customize the behavior of the NonStop SOAP server process, in
order to achieve the presentation of NonStop server applications as SOA services
regardless of how they are implemented. An example showing how to develop a
customized NonStop SOAP server to SOA enable a NonStop Tuxedo service is
provided.
Nonstop Soap Server Normal Processing Flow
SOA technologies, for example, Web Services Description Language (WSDL) and
Simple Object Access Protocol (SOAP), enable service consumers to invoke services
across object implementation environments. HP NonStop SOAP software facilitates
this process, working as a SOA service adapter, or bridge. This service adapter
supports standard SOA technologies, enabling Pathway and other service providers
running on the NonStop server to be presented as SOA services and invoked by
service consumers in a standard fashion.
NonStop SOAP software comprises design time and runtime components. At design
time, services are configured for NonStop SOAP software. The runtime component is
the NonStop SOAP server process—actually a pool of processes, a set of Pathway
serverclasses (for scalability and availability). The NonStop SOAP server process
handles the receipt of SOAP requests from service consumers, invocation of the
requested service provider, and return of the SOAP response to the service consumer.
Figure C-1 describes the normal NonStop SOAP server-processing flow.