UI services extend the use of software services and SOA to introduce a well-defined service interface on top of an otherwise untapped resource - the application user interface. Just as business services provide access to re-usable capabilities that provide data and logic, UI services provide access to re-usable pieces of user interface that can be combined into new solutions.

Key UI functions can now be coded and deployed once by a service producer, either as a new service or as part of a previously created / purchased legacy application, and then consumed in multiple solutions without the composite application builder requiring detailed knowledge of its implementation.

Beyond portlets and gadgets

Portlets and gadgets can be viewed as primitive UI services – they provide UI functionality that can be re-used remotely, and are ideal for allowing an end user to add functionality to a portal such as igoogle™

However as monolithic building blocks that are designed to be placed side by side on the user’s screen they provide little or no integration and only provide options as to appearance and function anticipated by the producer. As a result they are not suitable building blocks for composite application building.

In contrast, UI services are designed to power the creation of composite applications in a loosely coupled fashion. Because they expose their structure and form, consumers can choose how to leverage them in ways the producer needs never be concerned with. At the same time, the service producer has control over the core functionality provided, ensuring re-use, consistency and governance crucial in an enterprise setting.


_{UI services turn UI into a structured, re-usable asset. They allow composite application builder to reuse and integrate UI functionality from coarse grained page flows to fine grained page elements and their attributes}

UI Service interface Technically the UI Services employ a REST based interface. It provides access to page flows, individual pages, page elements and page attributes, allowing each to be recovered for re-use in a composite application. The service interface makes all attributes of a web UI re-usable including styling (CSS), interactivity (JavaScript) & AJAX behaviors as well as any embedded binary objects (images, flash, applets etc). The Corizon UI Service interface provides: Design time browsing of the contents of the UI service – allowing technical and non-technical users to explore the functionality available in a visual, interactive environment. Run-time access to the resources of the service via a standards based XML/HTTP(S) interface. Management functionality including security and service availability monitoring/alerts.

Open, standards based for maximum re-use

UI services created by Corizon use a published interface based on open, widely used standards. As a result they can be leveraged in a wide range of scenarios.

• By business-based analysts and web developers using Corizon Platform Studio and Composer for maximum speed of business-led development and ease of management and control.
• By developers using any programming technology that supports HTTP/XML and HTML. For example UI services can be consumed directly in the browser by Javascript, can be leveraged via jsp tags or can be integrated into custom controls provided by enterprise application vendors.
• By end users an enterprise portal or desktop.

Closing a gap: fit in an enterprise SOA

Corizon’s UI services can be deployed alone but will also complement and extend a broader set of SOA technologies.

• UI services can be deployed by service providers alongside more conventional SOAP or REST services to allow consumers to choose the from re-usable logic and UI as appropriate.
• UI service providers integrate with service directory, governance and discovery mechanisms.
• UI service security integrates with SOA security and authentication mechanisms.
• Mashups can be presented in existing enterprise portals.