NonStop SOAP User's Manual

NonStop SOAP User-Exits
NonStop SOAP User’s Manual—520501-012
C-23
SOA Enable a Nonstop Server Application With
User-Exits
3. Confirm the services that will be deployed on the target system and click “OK” as
shown in Figure C-14, Confirmation of services to be deployed. Once this process
is completed, the newly created SDL file will be stored into the SDR on the target
NonStop server.
Alternatively, the steps required to deploy the SDL file using the command-line
SoapAdmin tool are as follows:
1. Save the SDL file on the Windows PC.
2. FTP the saved SDL file to the required location on the target HP NonStop server.
3. Using SoapAdminCL, compile the SDL file.
> SoapAdminCL -I <sdl file>
Once you have deployed the SDL file using either method, the userexit-cpp
directory will be created with the SoapUEClassFactory.cpp,
SoapUEHandler_impl.h, and SoapUEHandler_impl.cpp files, ready to develop
the required user-exit code. In addition, a Makefile is produced that, once the user-exit
methods are completed, is used to build the customized NonStop SOAP server object.
Implement the User-exit Methods
Deploying the SDL file generates the user-exit class header (.h) and implementation
(.cpp) files, as described above. The .cpp files contain a skeleton class for each
service defined in the SDL. The class name has the format
“SoapPW_UEHandler_<servicename>”. For this example, the class name will be
“SoapPW_UEHandler_TOUPPER”. The skeleton classes must then be expanded with
the necessary user-exit code. This custom code is then linked with the NonStop SOAP
Figure C-14. Confirmation of services to be deployed