NonStop SOAP User's Manual

NonStop SOAP User-Exits
NonStop SOAP User’s Manual—520501-012
C-10
SOA Enable a Nonstop Server Application With
User-Exits
2. Define and create a new NonStop SOAP Service Description Language (SDL) file
for the service of either type “Pathway” or “Process”, as applicable.
3. Deploy the SDL definition and create the WSDL using the SOAP Admin tool.
4. Start the NonStop SOAP server.
SOA Enable a Nonstop Server Application With User-Exits
The steps to SOA enable a NonStop server application using the NonStop SOAP
server with user-exits are as follows:
1. Create the DDL for the service request and response message structures and
compile them.
2. Define and create a new NonStop SOAP SDL file for the service of type “Process”
with the attribute “GenerateUserExits” set to “yes” and the attribute “Generate” set
to “no.”
3. Deploy the SDL file and create the WSDL using the SOAP Admin tool.
On successful deployment, the “userexit-cpp” directory will be created, which
includes the skeleton template classes for implementing the user-exit methods,
along with a Makefile to compile them.
4. Implement the user-exit methods in the “SoapUEHandler_impl.cpp”,
“SoapUEClassFactory.cpp”, and “SoapUEHandler_impl.h” files. Note that the
generated “SoapUEClassFactory.cpp” file instantiates the service type object, and
that users generally do not need to modify this file.
5. Modify the Makefile as necessary and compile the user-exit classes to create the
customized NonStop SOAP server executable.
6. Start the NonStop SOAP server.
The major difference between constructing the NonStop SOAP server with and without
user-exits is that, in the former case, the various user-exit methods must be generated
and implemented. This process is triggered by specifying “yes” for the
GenerateUserExits attribute in the SDL file for the new service. When this is done,
skeleton classes for each of the user-exit methods are created and are ready to be
expanded with the specific user-exit implementation code. Once the user-exit coding is
completed, these methods can be compiled with the automatically generated Makefile,
modified as necessary, to create the customized NonStop SOAP server object. In the
case where user-exits are not being used to construct the SOAP server, no coding is
required and the NonStop SOAP server object is created automatically.
The following sections provide more details about how to accomplish each of the six
steps described above using a NonStop Tuxedo application as an example
(specifically, the NonStop Tuxedo supplied–sample application, “SIMPAPP”). Note that
the information provided here is generally applicable, even if NonStop Tuxedo is not
being used.