The Ontimize Web Services (OWS) component allows communication between clients and servers using the standard transfer protocols used on the web, HTTP and HTTPS.OWS currently include optional security features they are particularly useful for enterprise and inter-enterprise architectures. Web services are now essential for the new generation of applications that work collaboratively in environments where both application software and data is distributed across different servers.
Ontimize Web Services (OWS) uses open XML-based standards and transport protocols to exchange data with clients that follow the SOAP standard, and a machine-readable description of the operations offered by the service written in the Web Services Description Language (WSDL). OWS enables users to create and deploy secure, reliable, transactional, and interoperable Web services and clients quickly and easily.
Additionally OWS implements the standard WS-SecurityPolicy policy, which is designed to specify security requirements in some detail including security protocols, security algorithms, token types, authentication requirements, and so on, in order to provide secure communication and integrity over both internal and external networks.
You can also see a real example about how the Ontimize Web Services runs in the Ontimize QuickStart (user: "demo" password: "demouser")
• Based on W3C s(user: "demo" password:"demouser")pecifications.
• Use of a standardized interface language.
• Useful for enterprise and inter-enterprise architectures, in that they can be used in extranets and intranets.
• Published in a standard XML format, WDSL, which describes the services available on a given server.
• Clients invoke a web service by sending a request to the server, using the XML-based SOAP protocol.
• Messages are typically sent over an HTTP or HTTPS connection, allowing web services to be easily be published over the internet.
• The web services definition, their supported operations and their additional security is provided using WS-SecurityPolicy assertions, and so on, are specified directly in WSDL.
• Optional security can be added including WS-Security (WSS) with X.509 public key certificates.
• Also asymmetric binding is used for message protection, which allows separated public and private keys to be used to sign and encrypt the exchanged message.
• WS-SecurityPolicy specification defines a whole set of token assertions that can be used for securing SOAP messages.
• Using WS-Trust correctly allows two communicating parties having different security infrastructure to communicate securely with one another.
• Several Web Services Interoperability Technologies (WSIT) features are supported by OWS, where information is saved in WSIT configuration files.
• The SOAP-based OWS also allow users to encapsulate legacy systems.
• Layered system constraints to allow intermediary proxies, gateways, and firewalls are supported by Ontimize SOAP-based Web Services.