Unisys OS 2200 distributed processing
OS 2200 supports all commonly used, and many not so commonly used, distributed processing protocols, APIs, and development technology.
![OS 2200 Distributed Processing.png](http://upload.wikimedia.org/wikipedia/commons/2/24/OS_2200_Distributed_Processing.png)
The X/Open Distributed Transaction Processing model and standards are the basis for much of the OS 2200 capability.[1] Full support for the X/Open XA APIs including two-phase commit are built into transaction middleware, the database managers, and even clustering.
The J2EE model[2] is also fully supported. It uses the XA capabilities of the system but provides the J2EE APIs and protocols.
IBM WebSphere MQ (AKA MQSeries),[3] MSMQ,[4] and others are all fully integrated into the system taking advantage of the XA and integrated recovery facilities.
Distributed Transactions[]
![OS 2200 Distributed Transactions.png](http://upload.wikimedia.org/wikipedia/commons/f/fc/OS_2200_Distributed_Transactions.png)
Distributed Data Access[]
![OS 2200 Distributed Data Access.png](http://upload.wikimedia.org/wikipedia/commons/e/e7/OS_2200_Distributed_Data_Access.png)
Access to OS 2200 data can be made from virtually any platform and technology.
Similarly, OS 2200 applications can access data on almost any other platform.
Composite Applications[]
![OS 2200 Composite Applications.png](http://upload.wikimedia.org/wikipedia/commons/4/45/OS_2200_Composite_Applications.png)
It is rare to find an application that is written completely in one language with one set of middleware. The languages and middleware continue to evolve and applications adopt new technologies when they best fit the business requirements. That is often dictated by the need to integrate with applications written by partners, clients, suppliers, and third-party software providers. They do not all make the same choices and are in any case evolving as well.
A composite application may be created by combining existing transaction logic with different middleware or a front-end written for a specific purpose. Unisys supports the X/Open DTP model (also implemented in Tuxedo) as Open DTP[1] and J2EE. They fully interoperate with each other and with the rest of the system. Two-phase commit processing is supported within the database managers including clustered environments. Connectors are available to other common distributed transaction processing environments.
References[]
- ^ a b Unisys Corporation (2000). Open Distributed Transaction Processing Getting Started. (Unisys publication 7833 5007). Roseville, MN. http://public.support.unisys.com/2200/docs/cp14.0/pdf/78335007-007.pdf
- ^ Unisys Corporation (2009). OS 2200 Transaction Resource Adapter for Java(tm) User's Guide. (Unisys publication 4729 1992). Roseville, MN. http://public.support.unisys.com/2200/docs/cp14.0/chm/47291992-007/47291992-007.chm
- ^ Unisys Corporation (2013). WebSphere MQ for OS 2200 Installation, Administration, and Programming Guide. (Unisys publication 3843 3744). Roseville, MN. http://public.support.unisys.com/2200/docs/cp14.0/pdf/38433744-004.pdf
- ^ Unisys Corporation (2013). ClearPath OS 2200 Interface for Microsoft Message Queuing Help. (Unisys publication 6885 2722). Roseville, MN. http://public.support.unisys.com/2200/docs/cp14.0/chm/68852722-003/68852722-003.chm
- Unisys software