Global XML Web Services Architecture (hereinafter referred to as GXA) platform is a new term, including many new standards in the field of web services. Very much larger companies are working behind the scenes of GXA, including Microsoft and IBM.
The main goal of GXA is to define the syntax and semantics of the new family of the specified Web service, these protocols bring the basic functions of SOAP and XML to the next generation of mutual adaptability. Although a lot of work has been made to create a standard for web services in the past few years, there is still a lot of work to do. These work consists of enhanced and specializing in web services interactive and interoperability. The purpose of GXA is to define specifications for these services related to infrastructure, which constitute an abstract virtual machine for next-generation Web services.
GXA features
Over the years of real-world experience, most applications achieve repetitive tasks in a wide range of applications. Like safety and packet routing, problems such as many (although not all) distributed enterprise-class applications. Therefore, it is best to solve it through a special line-level protocol, not per application separately.
For example, in 1998, when SOAP was first introduced, it was the first XML-based protocol used for remote processes. Anyone who is called through the remote procedure of the web must learn how to write the original SOAP code. Now, SOAP is seen as a class of low-level drivers that specify the abstract platform library, which is buried in the basic structure of the web server used for web services. This basic structure is an AXIS in the ASP.NET and Apache source open field in the Microsoft .NET platform. In both cases, you can use the object-oriented mode to replace the original SOAP load to create or use a web service.
You must now write a similar style code snippet over and over again to ensure the security of your own web service. You will also be responsible for sending the SOAP message from the initial sender to the final recipient, which may pass through a series of intermediate links.
GXA tries to use common and well-understood grammar and semantic definitions based on SOAP-based protocol to handle security, message routing. Companies involving the development of GXA extended infrastructure may also embed the details of these protocols in a virtual machine one day.
Extension for building applications
The official definition of GXA is an agreement platform that implements SOAP extensions for building web services. This series of extensions includes WS-Security, WS-Routing, and enhance support for transaction collaboration, reliable messaging, metadata, etc.
WS-Security is a set of standard SOAP extensions that can be used to implement data integrity and confidentiality in a web service. Its goal is to allow applications to securely switch SOAP messages, process encoding and certificates by integrating special extensions in SOAP mode.
WS-Routing is a stateless protocol that is used asynchronous routing SOAP messages asynchronous using TCP and HTTP. The heads that make up these different protocols can be formed into a rich context for messages that may have accessories.
WS-Attachments and Direct Internet Message Encapsulation are also included by GXA, and many of GXAs are continuing. DIME is a lightweight binary message format that can be used to encapsulate one or more of any types and sizes from an application-defined payload to a single message configuration. Each payload is described with a type, one length, and an optional identifier. At the same time, the URI and MIME media type configuration are supported as the type identifier.
Microsoft currently supports a specified WS-Security extension for .NET web services; IBM supports the specified WS-Security extension in WebSphere SDK5.0 for web services. Although the WS-Routing specification uses the concept of intermediary built in SOAP, Microsoft and IBM have not supported WS-Routing. GXA and security have grown in the past two years, requiring a voice of a comprehensive security model suitable for Web services, and WS-Security specification is a first step in resolving this demand. WS-Security defines a set of Standard Simple Object Access Protocol (SOAP) extensions or message titles that can be used to achieve integrity and confidentiality in a Web service application. WS-Security provides a standard mechanism to exchange secure and signature messages in a web service environment; and provide an important base layer to facilitate developers to create a more secure, broader interoperability web. service. Various organizations can integrate these new specifications to different levels of its Web service application as needed. Other recommendations include: WS-Policy, WS-Trust, and WS-Privacy: WS-Policy Definitions How to express the functions and restrictions of security policies; WS-Trust is used to establish direct and indirect trust relationships (including third-party and middlemen Model; WS-Privacy Defines how Web Services specifies and implements confidentiality. WS-Secure Conversation, WS-Federation: WS-Secure Conversation describes how to manage and verify messaging between both parties, including security context exchange, and establish and derive session key; WS-Federation introduces how to manage and coordinate differently integrated environments The trust relationship, including support for joint identity; WS-Authorization defines how Web services manage authorization data and policies.
