Requirements and Recommendations
Planning for Galileo Web Services includes familiarity with not only the required technologies and skill sets, but also preliminary planning to design a client application that can appropriately support Web Services for the expected amount of traffic.
The following elements are required or recommended when developing client applications with Galileo Web Services.
Galileo Web Services Standards and Protocols
Galileo Web Services conforms to the following industry standards and protocols.
Message Envelope |
SOAP 1.1 |
|
Message Transfer |
HTTP 1.1 |
|
Encryption |
TLS 1.2 |
|
Web Service Description Language |
WSDL 1.1 |
|
Discovery and Integration |
UDDI 1.0 |
Note: Galileo Web Services are not currently registered through UDDI. |
Data Transfer |
XML 1.0 |
Tools and Environments
Any development tools or environments that are compatible with the above standards and protocols can be used. These tools and environments include, but are not limited to:
-
Microsoft.NET
-
IBM WebSphere Studio Application Developer
-
Apache Axis (replacing Apache SOAP)
-
Mind Electric GLUE
-
SOAP::Lite (Perl)
Developer Skills
Developers should have familiarity with XML, as well as the standards and protocols listed above. Particularly when using the XML Select Web Service, knowledge of the CRS business model is also helpful.
Connectivity
Galileo Web Services can be supported through an Internet connection. Internet connections must be secured via an SSL (Secured Socket Layer) protocol, as well as the security functions provided for Galileo Web Services. Because Web Services formats and standards are not limited to use on the Internet, the same protocols apply to the message, regardless of the type of network connection.
Security
Galileo Web Services servers are secured, and access is granted only to the specific Web Services for which the client is licensed. Internet connections to Galileo Web Services must also be encrypted via an SSL (Secured Socket Layer) protocol. Because Web Services formats and standards are not limited to use on the Internet, the same protocols apply to the message, regardless of the type of network connection.