Download
1 / 45
450 likes | 621 Views
Introducing Zeus ™. The ultimate solution for integration, automation and modernization of enterprise business systems. Practical Examples of Integration, Automation, modernization: Zeus™ at work. Zeus™. Zeus™ Historical Evolution.
E N D
IntroducingZeus™ The ultimate solution for integration, automation and modernization of enterprise business systems.
Practical Examples of Integration, Automation, modernization:Zeus™ at work Zeus™ • Zeus™Historical Evolution This presentation introduces Zeus™, a full-function enterprise and “Cloud” middleware platform for integration, automation and modernization of business systems and business systems management utilities, with an infinitely extensible suite of products running on that platform and targeted to those purposes. Each set of Slides describes a significant component of the technology and/or its practical application at large enterprises. The intention is to highlight the erudition and completeness of the architectural vision inherent in this breakthrough technology. The presentation starts with practical examples of AutoIntegrator’s potential application in three diverse industries, then the evolution of the technology . The presentation then begins on the inside of AutoIntegrator, and expands outwards, to expose not just the powerful capabilities of Zeus™, buts also its industrial strength capacity, performance, resource efficiency, and a complete breadth of features that is an absolute prerequisite to any enterprise software product as critically central and strategic to enterprise business systems. Finally, the market for mainframe and enterprise middleware is described, along with other products compared to AutoIntegrator, and why AutoIntegrator is superior to them all. We, of course, are open to any questions, or requests for any Zeus™ information of any kind. • THE PLATFORM • THE DEVELOPMENT IDE • SOA/BPM VIRTUALIZATION AND ARTIFICIAL INTELLIGENCE • PROCESS CREATION, ORCHESTRATION, AND EXECUTION • Zeus™PRODUCT FAMILY • Zeus™ vs. COMPETITION
Practical Examples of Integration, Automation, modernization:Zeus™at work
A Large Financial Institution J. P. Morgan Chase in Columbus, Ohio, has a DB2 database that includes every single account in the bank. Obviously, this is the central database in the bank. The database is maintained through online transactions in IBM’s CICS, although there is a category of account types that are updated at night through batch programs. all of the web interfaces to the CICS transactions currently utilize expensive Java/J2EE applications in WebSphere Application Server. These front end web applications cost the bank over $25M per year in mainframe processor resources alone, not to mention the software licenses that are based on processor resource consumption. The batch updates mean that critical accounts must wait for updates until third shift. The bank desires a single automated interface for all updates, whether online or sent in batch files. The solution should utilize the online CICS transactions through either a web interface or a 24/7 batch program feeding the CICS transactions. The solution must be ultra-high performance and efficient, as millions of transactions a day are handled by this system. Zeus™ solves each need. First, The applications are all stripped down and simplified to utilize the simple one-process-service method of AutoIntegrator. That is, a single web service call from WebSphere J2EE triggers AutoIntegrator to perform an entire update process, regardless of the account type. For batch updates, Zeus is configured to receive streaming updates and batch file updates, via FTP, from any source, and then perform the all of the same update processes the online performs. Zeus is completely configured and tested in four months. Four fundamental benefits accrue: The $25M bill drops to $8M. Response times improve 170%. The new batch update efficiency provides numerous logistical benefits, based on the more timely updates to important accounts. The nightly batch run is now gone, spread throughout the 24 hour cycle by the new Zeus interface. The bank is impressed so much with Zeus that it is certified as the standard middleware for all departments in the bank for both their batch and online systems. Over 280,00 thousand lines of Cobol and Java/J2EE code are eliminated, reducing annual maintenance costs by $1.5M, and dramatically simplifying future extensions and additions to the system.
A Large Property and Casualty Insurance Company Farmers Insurance in Los Angeles, California, has signed a third party outsourcing contract with CSC, giving CSC responsibility for all hardware systems and their management and control. One of the first things CSC does is to totally revise the billing formula for mainframe resources, such that the P&C systems division, the banks largest by far is facing a 45% increase in annual mainframe billing, such that it would rise from 27M to $40M per year. Farmer’s currently utilizes WebSphere Application Server for zOS, and CTG (CICS Transaction Gateway for all Web-CICS transactions. The WebSphere/CTG combination accounts for 46% of total mainframe resource costs, even though a zAAP processor is utilized for the Java/J2EE code. The Senior V.P. of the division issues a mandate that mainframe costs must be cut substantially in the next six months. In addition, the division must integrate their Auto and Homeowner’s applications, such that clients of one can be convinced, via dual-product discounting, to purchase the other, making Farmer’s their one-stop insurance shop. Zeus is chosen as the best solution for both strategic directives. First, CTG is replaced by Zeus, simplifying and drastically reducing the size and resource requirements of the Websphere/CTG middleware component. Total mainframe resource costs are reduced over 30%, saving $12M under the new billing scheme, keeping mainframe costs equal to current costs, even with the 48% increase in billing rates. Utilizing Zeus, not only are Websphere calls to CICS cut by 40%, but new streamlined dynamic processes bring about a flexible integration of the Auto and Homeowner’s systems, utilizing Zeus’s non-procedural on- demand virtual SOA/BPM process technology. The new conjoined systems are developed tested and installed in eight months, stripping away virtually all of the J2EE code and the CTG middleware. CICS resource costs are reduced by 15%, and systems maintenance and new development are radically simplified. Zeus is soon adopted as the standard enterprise middleware for the claims systems as well.
Manufacturing Company Caterpillar, a large farm and construction equipment company in the Peoria, Illinois, is implementing SAP to replace virtually their entire CICS-based product chain systems from parts purchasing through final pricing and delivery. This is a seven year project with phases, and subphases. Categories fundamental problem is how to shield the user base from the dual-system environment during the seven implementation. Also, certain other systems are not being converted to SAP, yet require tight, seamless integration with SAP throughout the implementation, and into the future. Zeus™ is chosen as the powerful, flexible and economical of all the middleware approached available. First, it shields end users from the constantly evolving dual-system environment, with its virtual process technology that combines SAP and CICS application services into the same unified services that users are accustomed to. Second, Zeus™ also integrates non-SAP systems with both the old CICS and the new SAP systems immediately, such that users are given new access to an integrated enterprise. Third, Zeus™ provides a perfect in-place unit and regression testing environment for the system at each phase. Finally, the Zeus™ project is complete in six months, And only requires minor updates as new project phases are implemented.
CHRONOLOGY OF AUTOINTEGRATOR™ EVOLUTION “The near invisibility of ‘The Integrator’ in the current marketplace will rank as one of the major management blunders in computing history.” • Glenn Bacon, “The Father Of Db2 “, • Former Director, IBM Santa Teresa Labs, • Former Chairman, IBM Strategic Planning Committee, • CUSTOM MIDDLEWARE ─SYSTEMS NETWORK ANALYSIS, Inc.─1980-1988 • SUPERSESSION , VTAMPLUS ENGINE ─ AID/SNA, Inc. ─1983-1988 • CUSTOM SUPERSESSION PROJECTS─ SAA, Inc. ─ 1988-1991 • “THE INTEGRATOR” ─ TRANACTION MANAGEMENT TECHNOLOGIES, Inc . ─ 1991-1996 • ZFUSION, ZINTEGRATOR ─zINTEGRATION, Inc . ─ 2005-2006 • AUTOINTEGRATOR™:MAINSTREAM AUTOMATION Inc. ─2007-2009
Platform Architecture (zOS Resident) Shared Subtasks Co-resident Applications Data Repositories VIRTUAL SERVICES HUB DB2 VIRTUAL TABLE REPOSITORY VSAM FILE SERVICES INTERNAL USER HELPDESK VIRTUAL DATA DICTIONARY Virtual SOA/BPM Workbench SNA/VTAM SYSTEM CATALOG ENTERPRISE MESSAGE ROUTER TCP/IP METADATATABLES EVENT DRIVEN ACTIVITY CONTROL SRM(System Resource Manager) Application Systems Testing Driver VIRTUAL PROCESS PLAN CACHE Bi-directional Hi-Speed Data Relay MASTER CONSOLE TRACING, LOGGING
A Comprehensive Subsystem Zeus™ is built upon a powerful, high-performance, multi-tasking subsystem. This not only enables an Zeus™ instance to support enterprise-level user and transaction volumes, but also to support multiple concurrent enterprise applications. All major zOS facilitiesare supported in the subsystem , including full security support through SAF, consolidated real and virtual storage management, master console interface to zOS and all application subsystems (CICS, IMS, et al), ACF/VTAM Fast Path for ultra-fast, ultra-efficient LU2, and LU 6.2 APPC/CPIC virtual session communications.
High capacity Multi-tenancy In addition to supporting multiple high-volume applications in a single subsystem instance, Zeus™ can support thousands of concurrent users and associated process executions. Each active user in Zeus™ is given a separate zOS subtask, assuring total separation and concomitant isolated recovery and problem resolution. Activities are executed through an exquisite zero-wait-state thread dispatcher, which assures full resource utilization efficiency.
Universal Communications Services Zeus™ supports all major enterprise telecommunications protocols, including TCP/IP, HTTP, WSDL, MQ, ACF VTAM and data-streaming. Inbound users or clients all use the same web service SOAP protocol. All requests are the same format: Virtual table name Input data variables Output variables required or “*” for all. TCP/IP, VTAM or MQ can be the protocol of I/O conveyance between Zeus™ and the client. The full gamut of protocols and interfaces is utilized for the execution of virtual services., which span all operating systems, applications, databases across the enterprise, web and into the “Cloud.”
Ultra-high Efficiency and Throughput Zeus™ is written in zOS Assembler and C languages, effectively “machine language.” Path lengths are all optimized, even down to a single instruction in some cases. All ACF/VTAM code executes in SRB-fast path, and can be enabled to execute on zIIP processors, which are very, very inexpensive for resources. There is no high-resource Java code, no complex application logic, while I/O to data sets and databases is optimized. All mainframe services and transactions execute locally on the host where their application and data reside, through virtual-client interfaces, running at cross-memory transfer speeds.
Parallel Processing. In addition to supporting concurrent users in parallel execution, when discrete virtual services in a dynamic virtual process are independent of other services in the process, they can be executed in parallel. A good example of this is an inventory application, where the user requires status on a large number of related or unrelated parts. Zeus™ dynamically determines the independence of any services, and executes them simultaneously in parallel, providing unsurpassed response time for complex transactions and processes that always previously been executed serially..
Virtual Database Creation Zeus™ creates virtual relational databases from non-relational data, and the requests are non-procedural. What this means is that a single virtual process can span any number and variety of enterpriseapplications. The client, or end-user, doesn’t care what applications are accessed in what order, or even where the applications are resident. Zeus™ figures all this out from encapsulated virtual SOA metadata. Services are encapsulated through a non-invasive, no-programming, no-script workbench recorder. Zeus™ analyzes the web service request, the input variables, and determines how the virtual table can be aggregated by execution of specific virtual services in a required order, and then instantiated in DB2 as a virtual relational table in a virtual relational database. These databases can be very small or very, very large. DB2 SQL allows all available database operations including multiple table joins. The entire enterprise and the entire web become a single unified database, where any column in any row can come from anywhere.
Artificial Intelligence and Non-Procedural Automation Zeus™ is the only middleware to utilize artificial intelligence to create virtual services, processes, tables and databases. Zeus's SOA/BPM Workbench encapsulates all possible virtual services in an application, without having to follow any specific paths through an application. Metadata is generated on the mainframe by the Workbench, which is accessed by Zeus™ in real-time. .When a request comes in, Zeus™ intelligently analyzes the full pool of virtual services through the metadata, to determine the necessary data and applications required, to be executed in what order to instantiate the chosen virtual table. This means that complex systems with many diverse paths and hierarchies need not be navigated or automated manually, because all possible navigation paths are encapsulated by Zeus™, whoknows how to decipher the required paths
Unlimited Co-Resident Applications AutoIntegrator™ supports a set of related applications, running on the same subsystem instance. Moreover, any number of applications can be developed to run together with any other related or unrelated applications together in the same subsystem instance. This provides the perfect environment for developing new applications, such that they can all run together under a single integrated control platform.
Autonomous Monitoring, Control and Recovery Zeus™ has a built-in User Helpdesk and Control application, which tracks every activity and resource at every level. Any combination of functions at every level can be traced and logged. Since fault isolation is enabled, one user’s problem has no impact on other users or the main system. All zOS recovery facilities are fully utilized. Operator commands control and monitor everything! And responses to specific situations can be fully automated, providing complete autonomous control.
Development IDE Goals The product programming development environment (IDE-Independent Development Environment) for Zeus™ is based in many hundreds of Assembler “macros and C language headers. It was designed to provide an eternal base for developing and extending enterprise software products and utilities, such that all key functions are predefined and complex applications and features are trivial to create. Macros can simply expand into required code patterns, or, more significantly, they invoke API’s at any of multiple API hierarchy levels. Assembler and C API’s may be called from either language. High-level API’s are highly abstracted so that the programmer need not know exactly what is happening in the API, only that it achieves the required result. This allows programmers, without in-depth technical training, to create powerful programs and products. This is particularly important on the mainframe, where there is a skills shortage for technical experts.
Interchangeable Assembler and C Zeus™ is coded in zOS Assembler language and C for ultra-high efficiency and performance. Almost any language can be supported, if there is a rationale for doing so. While this includes Java, there is no current need, and Java is the biggest resource hog in the universe. Any API or program, regardless of native programming language, can call any other API written in any other language.
zOS Operating Systems Facilities Zeus™ incorporates nearly all internal facilities and features of IBM’s zOS Operating System, by far the most advanced OS in the world. These facilities include, without limitation: SAF (universal security support) SRM (Shared Resource Management) APF (Authorized Program Facility) MCS (Master Console Services) ABEND Recovery (abnormal termination recovery) VTAM Fast-Path Hipersockets (fast-path TCP/IP) to any local System z platform. Dynamic dataset allocation. The point here is to complete the picture, that Zeus™ can and is everything from an application program to a control application that can literally manage an entire enterprise of users and application systems. It can even automate and control all system utilities from any mainframe software vendor, such that tasks that today might take hours can be completed in five minutes. It is a robust and complete systems program product.
Advanced Application Virtualization Zeus™ is the only software that virtualizes SOA atomic services and transactions, as well as BPM processes, and dynamic relational tables and databases. Advanced table services in Zeus™ enable utilization of internal relational tables to organize metadata, that can be rapidly analyzed ,via artificial intelligence ,to elicit a completely virtual application environment. This is a true “Cloud” enabler This is much more than simple platform virtualization like VMware or IBM’s VM OS. It means that applications and data can be anywhere, and that complex processes against normally non-integrated, unrelated applications can be dynamically, non-procedurally combined into dynamic virtual business processes. This is covered in depth in the next section.
Zeus™ Virtual SOA/BPM Workbench Zeus™ Virtual SOA/BPM Workbench Zeus™ Virtual SOA/BPM Workbench is a Windows based client controlled by the AutoIntegrator™ Workbench Application. The Workbench is a simple 3-stage process that requires no technical knowledge. The Administrator or Administrators need only know how to interact with the particular application(s) being encapsulated. First, the administrator starts an interactive session with the terminal or API-based application, and records the interaction he is driving. Next, the Administrator uses facilities to locate and parse the required variable data provided by the application, or requiring an update through the application. Third, the Administrator defines a virtual table or tables from selected variable data. Not all variables need be included in a virtual table, as some are simply used to drive the application or applications. The Workbench also includes an instant test facility for the table that was defined. The user creates simple SQL statements against the virtual table, which only comes into existence when the application services are executed. The prototype SQL statements created are saved and become the prototypes for the basic web service calls in real-time. Not all potential web service possibilities need to be defined as the user can tailor his requests to his needs, against any defined virtual table. Open and trace Screen or API Session Parse screens or buffers for variable data Define Virtual Tables Dynamic Testing
Real-time Request Processing In real-time (runtime), Zeus™ handles user requests in the following steps. Web service request received, specifying a virtual table, input variables necessary to begin the process (as Zeus™ executes a process it can utilize output variable data as input to a later service in the process). Zeus™ determines what the web service requests, and then dynamically analyzes, using its own artificial intelligence, the workbench metadata tables to derive all the possible virtual services necessary to instantiate the table. It then creates an orchestration plan to execute the services in the required order. Finally, Zeus™ executes the virtual services and moves the newly created virtual table to DB2. The user can request that the table data be delivered immediately in XML format, and/or the user can execute SQL against the virtual table along with others previously created. The table is stored in DB2 until the default timer goes off (two hours) or as long as is optionally specified in the web service. For example, an insurance agent can create a virtual table with all the daily rates for certain types of policy and specific underwriting criteria. He then can use the tabs that day to provide immediate quotes to clients. Process Request Request Parsed and Verified Process Created from Virtual Services Process Plan Built and Executed Virtual table data sent to client in XML and/or instantiated in DB2
PROCESS CREATION, ORCHESTRATION, AND EXECUTION: How Zeus™ Artificial Intelligence Works Zeus™ creates virtual services and processes and tables by intelligently analyzing all the metadata that has been stored from the SOA/BPM Workbench. This metadata is stored in relational tables containing, without limitation, information on: variable data, application segments or screens that contain the variable data, the steps or services are required to expose the data or allow the data to be entered as input, the transition keys must be emulated to move through an application, the application screens or segments, the parsing rules for the application screens or segments recorded, Scrolling rules, where multiple screens or API segments present a sizable number of rows of data. previously generated orchestration plans for the tables, which may be suitable for reuse or minor modification for reuse. virtual table definitions. This intelligent analysis can search for the very best (shortest, most efficient) execution paths through applications and virtual services. Or, the first plan discovered can be used, which is usually efficient, but requires less resources to perform the artificial intelligence necessary to analyze the metadata. Once an orchestration plan is derived, the plan is cached for later reuse, eliminating redundant intelligent processing of the metadata. If an unexpected or error condition occurs in the real-time process execution, Zeus™ can dynamically build a recovery path, to either reset the application or take an alternate path. Pool of Virtual Services Dynamic Virtual Process Virtual Table Navigation Metadata Dynamic Process Orchestration and Execution
Zeus™ Software Product Possibilities When Zeus™was first developed, there were three strategic goals: Build a world-class mainframe software development environment, based on a complete and efficient subsystem platform. Integrate all software utilities for the mainframe enterprise under a single control and automation subsystem/hub, non-invasively and non-procedurally. Integrate all mainframe applications in the client enterprise under a single access hub, non-invasively and non-procedurally. In the last several years, its original creator has designed subtle but substantive enhancements to the original architecture, in order to adapt and appeal to the current market. Because Zeus™was designed originally to be easily extensible, and to evolve rapidly, these architecture changes require only a very limited amount of programming. All of the original technology can continue to work without change. Almost any software product can be created quickly and easily with powerful IDE within the powerful subsystem environment of Zeus™ . the ones that follow are unique high-end strategic products that can each garner a mid-high six-figure license price, plus an annual 20% support renewal. Of course, combination sales would be discounted…
ANY CLIENT WSDL SQL-JDBC XML WSDL Zeus™ Virtual SOA/BPM Process Hub DATA DICTIONARY ORCHESTRATION CACHE AUTOINTEGRATOR™ DB2 VIRTUAL TABLES VIRTUAL SERVICE METADATA VIRTUAL PROCESS VIRTUAL TABLE DICTIONARY 3270 WEB SERVICE APPC CPIC DB2 JDBC
Zeus™ Virtual SOA/BPM Process Hub The Virtual Process Hub is the most amazing middleware technology ever created for enterprise business systems. In 1996, Glenn Bacon, the “Father” of IBM’s DB2 Relational Database Technology and the former chairman of IBM’s International Strategic Planning Committee, wrote an eight page affidavit detailing the unique value and extreme need for a technology like “The Integrator” (Zeus’s original predecessor). His concluding statement is even truer today: “The near invisibility of ‘The Integrator’ in the current market will go down as one of the biggest blunders in computing history.” It is time to fix that blunder!!!!!!!!
AutoIntegrator™ Virtual Testing Simulator AutoIntegrator™ Test web Service Calls AutoIntegrator™ Virtual Testing Simulator will be an easily configurable test environment for any tactical or strategic purpose. The Simulator simply uses the same workbench as the process hub, and generates selected types and volumes of internally generated requests to execute chosen virtual services, transactions and processes. There is no other testing product for the mainframe or the enterprise that can do what the AI Testing Simulator can do, Moreover, it is very easy to administer and configure. AutoIntegrator™ TESTING SIMULATOR Mainframe APP1 UNIX APP2 Cloud App3
Zeus™ SaaS/PaaS Virtual Cloud Hub Software companies are desperately seeking SaaS (Software as a Service and PaaS (Platform as a Service) ideas. They see these technologies generating huge high margin profits. Zeus™ is perfect for this. Moreover, it is a perfect way to garner full-license clients after they have utilized the SaaS/PaaS version of Zeus™. The SaaS/PaaS product could do all the things the entire Zeus™ product line could do, except it would run on a Mainstream Automation mainframe that users would subscribe to. AUTOINTEGRATOR™
Zeus™ Dynamic ETL Hub ETL (Extract, Transform and Load is a huge business for transferring data from its origin to one or many other environments and databases or files. Informatica’s whole business is ETL. Their revenue in 2010 was $650.1 million. Business Objects, Sybase, IBM Datastage are just a few of the current ETL vendors. In a large poll last year, over 50%enterprise managers selected high performance as their most desired quality in ETL software. Zeus’s virtualization, resource efficiency, high speed local access for all data…all these elements assure thatZeus™ should become a major force quickly in ETL and all its adjuncts, including data warehouses and data marts, cross platform database synchronization, MDM (Master Data Management), and EII (Enterprise Information Integration).
Zeus™ Dynamic Data Collector Most large enterprises still run very large batch systems dependent on file input from various places at various times. Man enterprises are forced to support a large number of esoteric protocols from their diverse population of clients. The healthcare claims submission process is a great example of this. AutoIntegrator™ can both schedule and poll for data from the population of users, eliminating heavy client responsibility and assuming the entire load of data gathering as well as batch distribution of the reports and results back to the users. Zeus™ Batch Data Batch Data Batch Data Batch Data Batch Data Batch Data BOTH POLLING AND TIMED COLLLECTION
Zeus™ BSM Automation Hub Companies manage mainframe and enterprise systems with a number of types of utilities for performance, resource utilization, database tuning, etc. There are five major companies in this space and most companies have more than one company’s products. CA has recently released an automation tool for mainframe utilities but they made several critical design mistakes that are not fixed easily. AutoIntegrator™ can automate any combination of both mainframe and enterprise BSM (Business Systems Management) utilities faster and better than anyone else. This product alone could gross $10M in revenue the first year, at $200,000 per license.
Existing Integration Middleware solutions There are many, many mainframe integration software products and techniques. Never, has anyone devised anything closely approximating the power and efficiency and capabilities of AutoIntegrator. Many solutions started out as hurried ad hoc solutions, continually refined to the degree possible. Others are derived from mainframe terminal emulators from the 1980’s. Others are custom Java/J2EE solutions that use intricate connectors and adapters to interact with certain types of mainframe applications. There are no dominant vendors in this space, even IBM, because nobody has ever come up with a complete and reliable middleware design. A list of major vendors follows on the next slide. A description of middleware categories follows on the next Client Population Middleware Siloed Application Siloed Application Siloed Application Siloed Application Siloed Application Siloed Application Siloed Application
Some Current Mainframe Middleware Vendors IBM-Websphere MQ, IBM Business Process Manager, HATS, Tivoli Systems Automation for zOS, CA-TPX, Teleview, UniCenter Oracle-Fusion Compuware-Uniface Rocket Software-Shadow Attachmate-Verastream MicroFocus-Rumba, OnWeb Rocket Software/Seagull-LegaSuite iWay-iWay Enterprise Connectors
Categories and Methods of Mainframe Middleware Invasive-Requires a separate CICS program to run inside of application subsystem, as well as changes to the application subsystem from terminal based to API-based. Messaging, Queuing-IBM’s most popular middleware, Websphere MQ, requires combining multiple terminal based transactions, then modifying them to a messaging interface. Programmable-J2EE programs are written to exchange screen data through connectors or adapters and screen-based program., requiring modifications to every application service Scripted-An external middleware program calls individual screens according to procedural scripts. One service call is required for each screen, or a separate logon-logoff is required for each service executed. TN3270/EHHLAPI –External distributed middleware on a non-mainframe processor accesses 3270 screens through the web, and drives the services a screen at a time, slowing response times and requiring procedural definitions for each service path.
Choosing Middleware for Integration, Automation, Modernization of Legacy and Other Enterprise Applications Middleware There many fundamental concerns when selecting either tactical or strategic middleware to integrate, automate and modernize existing applications, or to replace inefficient, complex existing middleware. Some of the major considerations can be categorized as follows: Ease of implementation and maintenance. SOA/BPM compatibility. Easy Integration across siloed systems Need for changes to existing applications. Response time and performance. Processor resources. Long-term viability.
Why Zeus™: Comparing It To The Rest Need for changes to existing applications. Zeus™ is 100% non-invasive to existing applications, requiring no changes of any kind to existing systems. Response time , performance, resource efficiency.. Zeus™, because of its extremely short and efficient path lengths and its dramatic advantage in reduced network latency, provides the best and most efficient total processing for both online and batch applications. No Java code is required by Zeus™, except for simple programs in the application server to invoke virtual SOA/BPM services/processes. Long-term viability. Zeus™ has indefinite long-term viability because of its ultra-efficiency and seamless, virtually invisible footprint. It can be used for any integration, automation or modernization project! Zeus™ surpasses every other middleware product in each of the categories and more… Ease of implementation and maintenance. Zeus™ requires no programming or scripting of any kind. SOA/BPM compatibility. Zeus™ not only creates SOA services and BPM processes, but it does so dynamically, in real-time, and combines any number of virtual services into a single virtual service to execute an entire process across any number of application systems on any platform in the enterprise, the web or the “Cloud.” Easy Integration across siloed systems. Zeus™ provides a complete access and management hub for any and all applications in the enterprise. Virtual services in multiple applications can be dynamically aggregated into virtual processes, creating relational virtual data from non-relational applications and data. Any integration task is easily accomplished.
Conclusion Zeus™, the Conqueror Zeus™ is as close as anyone has ever come to “perfect, efficient, easy to-use, powerful enough to handle any need” middleware. This is not just a claim but be clearly demonstrated in any case in any environment, Moreover, its open potential for evolution and extension virtually its continuing superiority, With $25M already invested, not to mention the ingenuity that has evolved over 25 years, profit margins should exceed 60% for the indefinite future, as sales climb dramatically, and Zeus™ becomes a commodity at medium to large enterprises world-wide.
