White Paper Makes the Case for ClearPath as an Open System

Organizations such as The Open Group and the World Wide Web Consortium (W3C) define an open system as one that exposes industry-standard internal and external interfaces. “ClearPath as an Open System,” a new white paper by Peter Bye, examines ClearPath systems from four key perspectives to show how they conform to this definition.

The four perspectives are:

• Internal interfaces – Developers are presented with industry-standard application environments and interfaces, reducing the need for specialized knowledge. Software and applications written in other systems, but conforming to the same standards, can be hosted on ClearPath systems.
• Application development – Graphical and integrated development environments, such as the ClearPath OS 2200 and ClearPath MCP IDE for Eclipse™ and Agile Business Suite, help developers leverage familiar and easy-to-use tools and languages.
• External interfaces – ClearPath systems facilitate participation in distributed environments, including a service-oriented architecture (SOA).
  
• Systems management – ClearPath management tools span the systems included in both distributed and SOA environments, and integrate with other management products.

And unlike many other open systems, ClearPath systems also exhibit mission-critical attributes – especially reliability and security. As the paper contends, this combination of open and mission-critical attributes makes ClearPath systems the ideal platform for enterprise transaction processing.

To see exactly what makes ClearPath an open system, read the full paper on Unisys.com.