NonStop SOAP User's Manual

NonStop SOAP User-Exits
NonStop SOAP User’s Manual—520501-012
C-30
SOA Enable a Nonstop Server Application With
User-Exits
For example,
wsimpcl: simpcl.c
rm -f $(@)
CFLAGS="$(CFLAGS)" \
TUXDIR=$(TUXDIR) \
$(XCBINDIR)/buildclient \
-w -o wsimpcl \
-f "userexit-cpp/SoapUEHandler_impl.cpp userexit-
cpp/SoapUEClassFactory.cpp" \
-f "${XERCESCROOT}/lib/OssTandemPlatformUtils.o \
${SOAP4NSK}/lib/SoapMain_CGI.a \
${SOAP4NSK}/lib/libcgi.a \
${SOAP4NSK}/lib/SoapLibrary.a \
${SOAP4NSK}/lib/PwayLibrary.a \
${XERCESCROOT}/lib/libxerces-c_icu2_4_0.a \
${XERCESCROOT}/lib/libicu-uc.a \
${XERCESCROOT}/lib/libicu-stubdata.a"
6. Once the Makefile has been created, then execute the OSS make command to
compile and build the NonStop SOAP server with user-exits (for example, “make -
f simpapp.mk“).
On successful compilation, the NonStop SOAP server with user-exits executable will
be built for command-line or Web-hosted execution, as specified in the Makefile.
Start the NonStop SOAP Service
To run the command-line NonStop SOAP server object, use the following command:
simpcl < SOAP Request xml file>
In the case of an iTP WebServer–hosted NonStop SOAP server, the NonStop SOAP
server with user-exits will be started as an integral part of the Web server environment
when the Web server is initialized.
This subsection contains the following examples:
•
Sample SDL file generated for NonStop Tuxedo “TOUPPER” service
•
Files Created When the Example Sdl File is Deployed
Note. Before executing the Makefile, you may need to set the environment required to build
the NonStop Tuxedo application (for example, “simapp_env” provided with the NonStop
Tuxedo SIMPAPP sample program).