IBM TXSeries: Difference between revisions
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
'''Common Deployment Scenarios''' |
'''Common Deployment Scenarios''' |
||
| ⚫ | |||
| ⚫ | |||
As a distributed transaction server, IBM TXSeries ®for Multiplatforms provides base-level CICS® programming interfaces, allowing industry-specific COBOL®, C, C++, PL/1, and Core Java™ specialists to create simple solutions for business-critical transaction processing. TXSeries supports screen-based terminals and provides programming interfaces for connectivity with graphics-rich displays, depending on the business requirement. Data can be accessed from the integrated CICS Structured File Server, local and remote RDBMS such as DB2®, or messaging subsystems like WebSphere® MQ. With excellent enterprise integration support, TXSeries is ideal for creating mainframe value-add or stand-alone distributed transaction processing solutions. Common transaction server deployment scenarios include: |
As a distributed transaction server, IBM TXSeries ®for Multiplatforms provides base-level CICS® programming interfaces, allowing industry-specific COBOL®, C, C++, PL/1, and Core Java™ specialists to create simple solutions for business-critical transaction processing. TXSeries supports screen-based terminals and provides programming interfaces for connectivity with graphics-rich displays, depending on the business requirement. Data can be accessed from the integrated CICS Structured File Server, local and remote RDBMS such as DB2®, or messaging subsystems like WebSphere® MQ. With excellent enterprise integration support, TXSeries is ideal for creating mainframe value-add or stand-alone distributed transaction processing solutions. Common transaction server deployment scenarios include: |
||
| Line 23: | Line 23: | ||
Ideal solution for customers who do not have CICS or large-scale EIS systems, but require the transaction handling qualities of service offered by CICS |
Ideal solution for customers who do not have CICS or large-scale EIS systems, but require the transaction handling qualities of service offered by CICS |
||
'''A rapid deployment integration server''' |
'''A rapid deployment integration server''' |
||
Revision as of 11:59, 27 July 2009
TXSeries for Multiplatforms is CICS (Customer Information Control System) on distributed platforms. It is a transaction server available on AIX, Windows, Solaris and HP-UX. TXSeries shares with CICS on mainframe similar design principals and some functions. End of 2006 saw a major and popular release of TXSeries V6.1, with DCE and IBM Encina components removed. This brought huge simplification to the product. There is also a new graphical web-based administration console.
TXSeries 7.1 is the latest version available, that includes new features such as Channels and Containers that eliminate the 32KB size restriction that previously existed for data being passed between programs. It also includes a new protocol, IPIC that enables communication with mainframes using TCP/IP protocols.
Common Deployment Scenarios
A distributed transaction server
As a distributed transaction server, IBM TXSeries ®for Multiplatforms provides base-level CICS® programming interfaces, allowing industry-specific COBOL®, C, C++, PL/1, and Core Java™ specialists to create simple solutions for business-critical transaction processing. TXSeries supports screen-based terminals and provides programming interfaces for connectivity with graphics-rich displays, depending on the business requirement. Data can be accessed from the integrated CICS Structured File Server, local and remote RDBMS such as DB2®, or messaging subsystems like WebSphere® MQ. With excellent enterprise integration support, TXSeries is ideal for creating mainframe value-add or stand-alone distributed transaction processing solutions. Common transaction server deployment scenarios include:
As a stand-alone distributed transaction server for industry-specific applications written in COBOL, C, C++, PL/1, or Core Java applications running inside TXSeries, or where TXSeries provides the transactional run time for a vendor-produced packaged application
As a stand-alone COBOL, C, C++, PL/1 or Core Java transaction server, connecting to a stand-alone J2EE application server, such as WebSphere, delivering high performing transactional applications that are tightly integrated with graphics-rich intuitive applications developed in Java EE™
As a physically distributed transaction server for simple CICS workloads that require a level of local branch level processing before periodically replicating the data with a back-end mainframe system
The key features of this deployment are:
Cost-effective and robust solution for deploying and running business transaction
Ideal solution for customers who do not have CICS or large-scale EIS systems, but require the transaction handling qualities of service offered by CICS
A rapid deployment integration server
As a rapid deployment integration server, TXSeries for Multiplatforms has extensive support for many enterprise information systems (EIS), such as CICS Transaction Server, IMS, DB2, WebSphere MQ, and WebSphere Application Server. It can use TCP/IP and SNA-based communication protocols. The ability to run intelligent business logic in a mid-tier environment that supports the same languages and APIs as the systems that require the integration enables a complex integration solution to be deployed extremely rapidly. Common integration server deployment scenarios include:
As a consolidating mid-tier terminal server, between internal customer service representatives at end-user terminals, using industry-specific graphical or screen-based interfaces to access applications and data from more than one EIS
As an intelligent mid-tier gateway between a Java EE application server that delivers intuitive interface rich Web content to Internet users who are unknowingly accessing applications and data from more than one EIS
As a comprehensive mid-tier integration server for applications and data residing on more than one heterogeneous EIS, as a result of consolidation within a corporation, or after a merger or acquisition, for example.
The key features of this deployment:
Reduced resource consumption on the EIS because TXSeries takes over a number of business operations
Intuitive and rich Web-based interfaces are now available to users
Consolidated data from multiple EIS systems before presentation to users