Deployment Strategies

COM Transaction Integrator should be considered for these deployment scenarios:

• Application-level database integration.
• COM integration with CICS and IMS.
• ADO access to legacy data.
• Integration of mainframe applications that own and control the host data. TPs often contain logic and data structures that define the rules for accessing host data. In some cases, these applications also contain integrity checks and consistency constraints. In these cases, accessing the host data through these TPs is the only safe option.
• Enabling mid-tier applications to take advantage of scalability benefits MTS provides, in addition to providing mainframe application access.
• Deployment of high-integrity, distributed transaction systems that span Windows NT, MVS/CICS, and other XA-compliant environments that are MTS-enabled.
• Mainframe connectivity only.

  OLE DB Provider should be considered for these scenarios:

• Record-level or file-level database integration.
• OLE DB and ADO access to legacy data.
• Ability to rewrite business rules, such as "Year 2000" solutions.
• Mainframe and AS/400 connectivity.

In some cases, you may want to use both COM Transaction Integrator and OLE DB Provider to develop a complete host-connectivity solution.

Sample applications that use COM Transaction Integrator are installed when you install COM Transaction Integrator.