Introduction > SOAP/AM Client Components

The diagram below depicts the SOAP/AM Client components as they are used at design time (during client application development) and at run time.

 

 

The components of the SOAP/AM Client product are described below:

Client Process (SOAPAMCP)

The Client Process relays messages sent from client applications through NonStop’s native inter-process message system to Web services anywhere in the world. SOAPAMCP hides the complexity of the TCP/IP, HTTP, SSL and SOAP protocols required to participate in Web services.

 

When you start the SOAPAMCP process, you specify the name of a Client Definition File (CDF) that contains a description of the Web service you want to access. The CDF is an XML-formatted text file that you create using the WSDL2CDF utility.

 

The SOAPAMCP process can be run as a standalone named process or configured as a Pathway serverclass for scalable access to the target Web service.

WSDL2CDF Utility

The WSDL2CDF utility creates a Client Definition File (CDF) by reading the Web Service Description Language (WSDL) file that describes the target Web service and augmenting it with mapping information. The Client Definition File (CDF) contains all of the information needed by the SOAPAMCP process to map a request IPM to a Web service request and map the Web service response back to an reply IPM.

CDF2DDL Utility

Your NonStop application interfaces with the SOAPAMCP process through the native interprocess message system. The format of the request and response interprocess messages (IPMs) used must correspond precisely to the definitions in the CDF file. The CDF2DDL utility facilitates this by producing NonStop DDL source for the IPMs. You then use the NonStop DDL utility to produce the host language-specific definitions that you compile into your application.