H06.21 Release Version Update Compendium

4 Database and Transaction Processing Products
NonStop SOAP 4
• NonStop SOAP 4 supports:
— SOAP 1.1 and SOAP 1.2 standards
— WS standards such as WS-Policy and WS-Security
— Transaction management
— Services running under TS/MP
— Services running as NonStop processes
— Services developed using service APIs (DLLs)
— Customization using pluggable modules, handlers, and Message Receiver User Functions
— Hot deployment of services
• NonStop SOAP 4 provides tools to develop applications using the Contract-first development
approach.
• NonStop SOAP 4 also provides a client API library that can be used to develop SOAP clients
on an HP NonStop platform.
Migration Considerations
• Both NonStop SOAP 3 and NonStop SOAP 4 can coexist on the same HP NonStop system.
• Migrating the NonStop SOAP 3 SDL file to NonStop SOAP 4:
Issue: The SoapAdminCL tool does not accept the NonStop SOAP 3 SDL file as an input.
Solution: Provide NonStop SOAP 3 SDR as an input to the SoapAdminCL tool to generate
the corresponding NonStop SOAP 4 SDL file.
• Migrating applications generated using the NonStop SOAP 3 WSDL file:
Issue: The WSDL file generated using the NonStop SOAP 3 Soap Admin tool and the NonStop
SOAP 4 SoapAdminCL tool is different. Therefore, applications cannot be easily migrated
from Nonstop SOAP 3 to NonStop SOAP 4.
Solution: Use the -m|-migration command line option in the SoapAdminCL tool to generate
WSDL files similar to NonStop SOAP 3.
• Migrating NonStop SOAP 3 user-exits to NonStop SOAP 4:
Issue: User-exits in NonStop SOAP 3 enable you to customize the default NonStop SOAP
3 behavior. NonStop SOAP 4 does not support user-exits but provides modules, handlers,
and Message Receiver User Functions that enable you to customize NonStop SOAP 4
behavior.
Solution: NonStop SOAP 4 is developed in the C programming language, while NonStop
SOAP 3 is a C++ library. Therefore, while migrating NonStop SOAP 3 user-exits to NonStop
SOAP 4, you must either develop a wrapper class to access the existing C++ library or develop
the application again using the C programming language.
NOTE: Modules, handlers, and Message Receiver User Functions are functionally equivalent
to user-exits in NonStop SOAP 3.
Fallback Considerations
To fallback to NonStop SOAP 3, redeploy your web services under NonStop SOAP 3. If the
NonStop SOAP 4 client applications to be migrated to NonStop SOAP 3 are based on the WSDL
generated using the NonStop SOAP 4 Admin Tool, they will need major modifications when
falling back to NonStop SOAP 3. However, if the migrated NonStop SOAP 4 client applications
NonStop SOAP 4 17