AXS-One’s e-Cellerator™ architecture is based on the latest technology, including Web Services, SOAP, XML, HTTP and other standards. At the same time, AXS-One’s e-Cellerator architecture delivers a highly scalable, flexible environment that runs on industry standard platforms and database systems.

AXS-One’s architecture delivers an adaptable suite of interoperability choices, creating abundant flexibility in integration and business process management strategies.

Customers can use pre-packaged AXS-One solutions, adjust AXS-One solutions to meet specific business requirements, connect existing systems with AXS-One, or build completely new solutions in-house, supported by AXS-One products. Interoperability choices include real-time and batch Web services interfaces, XML documents, reports, e-mail, faxes, images, relational database systems, even websites.

Web services can be used to look beyond specific systems and focus on business processes.

Business Process Components

As a standard development methodology, AXS-One has always identified modular business functions, and then proceed to implement those functions as re-usable business components. This ensures consistent business processes in the application suite, as well as providing for rigorous code re-use as a normal part of the development process.

These business components contain all the logic necessary to perform a specific business function.

AXS-One has connected these robust business components to a new Web services architecture. This architecture provides a simple, firewall friendly, easily deployable Web services interface. At the same time, this architecture provides for excellent scalability and reliability through the use of sophisticated resource pooling and request routing techniques.

On the back end, the Web services infrastructure provides access to both new and existing business process components.

The Web Services infrastructure front-end sits "behind" a standard Web server. The infrastructure front-end will connect to an application server and create an instance of the business component on the application server. The message is then repackaged and sent to the application server, where the service request is actually processed. On the application server, the business component interprets the request, and performs the desired function, including constructing a reply message. This message is in turn passed back to the infrastructure front-end and returned in the HTTP reply to the original (client) message sender.

The request message structure and the reply message structure are both defined in an interface specification file specific to a business process component. These files are in WSDL format, which allows the AXS-One Web services to potentially be deployed to a UDDI registry.

Application Web Services

AXS-One has created a new architecture for the presentation portion of its user interface (UI) to be based on XML messages. This approach allows customers to control pre-built AXS-One applications using well-defined XML messages. In addition, application based XML messages can be combined with XSL style sheets to create ultra-thin browser-based user interfaces.