Sharp | in business - Hosted at ECIT
Home Sharp UK Glossary About Sharp Infonet Terms and Conditions
Quick Links
How to Buy Support Contact us Partner program


Sharp Open Systems Architecture

   To request more information about Sharp's OSA, please click here.       

Sharp Open Systems Architecture (Sharp OSA) opens the door to a broad array of value-added functionality. By bringing the power of customization closer to the customer; this versatile development platform adds incredible flexibility to Sharp's awarding winning line of MFPs.

It is designed to let network applications control the MFP through bi-directional communication. This allows users to interact with business applications directly from the front panel of the MFP.

By bringing the point of customization closer to the customer, Sharp OSA enables Sharp, its channel members and partners to quickly bring solutions to market that tightly integrate Sharp MFPs with software applications. More importantly, it offers a degree of customization that allows Sharp MFPs to better address unique customer needs. This seamless integration promotes more streamlined customer workflows and business processes.

This flexibility transforms your MFP into a resource designed to evolve with your business. The Sharp OSA development platform allows developers to create custom applications that are specific to your organization's routine processes and procedures. With a Sharp OSA-enabled Digital IMAGER™ you can start and finish a task directly at the MFP, no need to return to your desktop which can drastically reduce your ordinary document workflow and increase efficiency.

To support and foster development, Sharp OSA is complemented by the Sharp Partner Program. Completely modular, this flexible program consists of four separate elements that can be grouped into virtually any combination. Each is intended to support our partners in the various stages of the development life cycle, and as such, offer a unique set of benefits.

Architecture

Sharp OSA is a client/server-based architecture that allows network applications to communicate with the MFP and remotely control MFP functions and operation panel screens. All application code runs on the network server. Communication is divided into two channels: a UI channel and a web service1 channel.

Figure 1. Dual-communication channels in OSA

As shown in Figure 1 above, the UI channel uses XHTML2 messages over an HTTP connection to define custom UI screens and receive user input. The web service channel utilizes XML3/SOAP4 messages for applications to control device functions and receive event notifications.

Inherent in Sharp OSA's web service architecture are certain advantages, they include:

Low cost implementation

Multiple MFPs talk to the same integrated application, minimizing installation and maintenance time. (provides for central administration)

Resource efficiency

Application takes full advantage of server processing power and storage capabilities.

Ease of development

Application development is easier in server environment where common, well-known tools can be utilized, as opposed to embedded Java.

Interoperability

Web Services is the standard for application to application communication.

No embedded development required

Sharp doesn't have to verify or be involved in each and every integration.

1. A web service is a collection of protocols and standards used to exchange data between software applications and systems. Web services commonly use messages composed of XML elements within a SOAP wrapper for interoperability between varying environments.
2. XHTML (Extensible Hypertext Markup Language) is a markup language that uses XML elements to describe data within an HTML document.
3. XML (Extensible Markup Language) is a W3C initiative that allows information to be encoded with meaningful structure and semantics that applications and humans can understand. XML is commonly used for defining data that will be shared between disparate applications.
4. SOAP (Simple Object Access Protocol) is a standard messaging protocol used to encode the information in web service request and response messages.