The choice of technology for writing programs that access the OM Web Services depends on corporate standards and the type of application being built. After selecting a technology to implement an application, there are often many stack technologies or interfaces available for creating code to access a Web Service. For example, in Java several technologies are available for writing code to access Web Services. One choice, the Apache Axis2 SOAP stack, includes classes to invoke Web Services and is included with the OM Web Services
Note: The Apache Axis2 SOAP stack is also the SOAP stack that is discussed in this guide.
The following table provides a list of technologies that can be used for writing applications that access OM Web Services:
|
Technology Choice |
Technologies and Interfaces Available |
|---|---|
|
Java |
Apache Axis2 Apache CXF |
|
Perl |
SOAP:Lite for Perl |
|
PHP |
PHP SoapClient (built-in) |
|
.NET MS Office |
Microsoft WCF |
|
C++ |
gSOAP |
Note: This is not an endorsement of those technologies or an indication that we have tested and certified them for this use.
These technologies help programmers build applications that use the OM Web Services. They often hide the SOAP request generation and SOAP response processing by converting structures and classes that are passed to them into SOAP requests (serialization) and converting the SOAP response into structures and classes in the native language (de-serialization). These technologies provide tools for using the OM Web Services WSDL statement as input and generate code to access the OM Web Services.
Two of the technologies available for writing applications that access the OM Web Servicesare discussed in this guide – Java and .NET platform. The Java programmers use Java with the Apache Axis2 engine. Microsoft Visual Studio uses built-in Web Services support to generate Visual Basic or C# classes that can be accessed from custom code and integrated into Office applications as a COM component.
|
Copyright © 2013 CA.
All rights reserved.
|
|