HooX

Host object oriented conneXion

The Gartner Group identifies four phases in the development of the Internet: presence, interaction, transaction and transformation. Most enterprises are currently between the transaction and transformation phases. This evolution has led to the development of new component-oriented applications, with three major implications:
- The integration of existing software - especially transactional applications - to get new e-business   transactions up and running as soon as possible;
- The use of standards to accelerate development and enable the developers to focus on the new   applications logic;
- The availability of new tools to hide the complex applications architecture, especially as regards   connections.

With HooX, Bull offers developers a range of connector solutions that conform to prevailing standards and a set of tools for generating transaction components. HooX makes the developer's task easier by reusing the host systems' existing transactions in new transactional applications, and by integrating the legacy in a transparent way.

HooX in the e-infrastructure


HooX: a family of transactional connectors with matching interface component generators.

HooX generates call components to GCOS 7, GCOS 8 and MVS transactions and supports both line and screen-mode transactions.
The family consists of:
- HooX JCA (J2EE Connector Architecture) connectors and EJB generators for the J2EE application   servers that support them;
- HooX COM+ connectors and COM+ component generators for the Microsoft .Net framework.
  HooX connectors support local transactions.

 

Bull and Gallagher & Robertson commit to J2EE-standard connector architecture and announce HooX Java connectors for Bull and IBM systems.


HooX Java connectors provide standardized access to existing GCOS and MVS-based transactions for applications developed in environments compatible with J2EE 1.3. They encapsulate existing transactions in EJBs (Enterprise Java Beans).

The JCA (J2EE Connector Architecture) standard governs integration and interoperability between application servers and heterogeneous 'back-end' systems. JCA defines a standard API for the connector, as well as support for key services: connection pools, global transactions and application server security.
The benefits of this connection architecture include simplified, scalable access and the guaranteed integrity and security of the enterprise's mission-critical resources.

Application environment View


The HooX Java offering on GCOS 7, GCOS 8 and MVS hosts consists of the following elements:
- a JCA-standard transactional connector (resource adapter);
- a toolkit for generating EJB transaction components.
This offering is developed by Bull in partnership with Gallagher & Robertson.
So far, it has already been validated on BEA's WebLogic Server.

To help developers create new Java-based e-business applications, HooX provides:
- the ability to use components that can access existing host transactions without having to know the   transactions or their underlying connections;
- independence from J2EE application servers and platforms.

HooX your legacy up with your e-business future

 

HooX J2EE™ Connector for GCOS 8

The J2EE Connector architecture provides a Java solution to the problem of connectivity between the many application servers and EIS already in existence.
By using the J2EE Connector architecture, EIS vendors no longer need to customize their product for each application server.

shema

Application server vendors who conform to the J2EE Connector architecture do not need to add custom code whenever they want to add connectivity to a new EIS. The J2EE Connector architecture is based on the technologies that are defined and standardized as part of the Java 2 Platform, Enterprise Edition (J2EE). The J2EE Connector architecture is proposed to be part of version 1.3 of the J2EE platform. The J2EE Connector Architecture , defines a standard set of services that allow developers to quickly connect and integrate their applications with virtually any back-end enterprise information system (EIS) such as ERP, CRM, legacy systems (Mainframes, databases servers). These services are supplied as "plug-in" connectors ( aka "resource adapters") that will be supplied by EIS and Java software application server vendors, as the J2EE Connector Architecture catches on among J2EE technology shops.

The HooX J2EE Connector for GCOS 8 consists of two software parts delivered to GCOS 8 customers at the same time :
- the connection middleware per se, i.e. the connector (or Resource Adapter) delivered as a specific Java   library GCOS 8 to be added to the J2EE 1.3 compliant application server platform
- the Component Generator Tool

The Component Generator Tool allows Java developers to build TPRs access components classes acting as a functional connectivity layer from which the new business user applications will get or update data from the GCOS 8 back-end, "pipelined" through the Resource Adapter of the J2EE CA compliant connector.

HooX J2EE™ Connector for GCOS 8
Architecture overview

Architecture overview

 

HooX J2EE Connector for GCOS 8 is a Transactional connector which will extend the GTEA basic connector capabilities for seamless integration of GCOS 8 line-mode applications with applications running on J2EE Application Servers.

Application environment View

Application environment View

This connector will provide the Common Client Interface (API), and the services specified in the J2EE Connector Architecture standard (connection management, transaction management, and security). Thanks to a close cooperation with Gallagher & Robertson a Bull partner for a long time, HooX J2EE Connector for GCOS 8 will include a J2EE Connector Architecture compliant connector to access existing screen-mode TP8 TPR's on a non-intrusive way (that is without modification of the applications).
The Component Generator Tool : This tool will generate Interface beans that contain all connector calls and provides abstract view of the TP8 TPRs. The Component Generator Tool simplifies the process of developing middle-tier components, such as Enterprise Java Beans, which will be used to communicate with TPRs running on GCOS. The Component Generator Tool will automatically generate Java classes using a combination of COBOL data descriptions and class templates.


As Java enterprise access scenarios become more complex, programmers are under increased pressure to generate code that runs on a variety of middleware. Tools that help generate code for client/server access can
greatly help productivity.

HooX J2EE™ Connector for GCOS 8
Architecture & Component Generator Tool

Architecture & Component Generator Tool

The Component Generator Tool that is included with HooX J2EE™ Connector for GCOS 8 generates access code, allowing the developer to quickly and easily access legacy GCOS 8 applications, transactions, and data. Not only is the need to write middleware code eliminated; it is no longer necessary to rigorously test this highly error-prone code. The developer needs only to test that the generated code provides the desired behavior. In this way, the developer can focus on the application's business logic, rather than on generic access code. The most difficult aspect of accessing most TP8 transactions from Java is understanding and creating the code to convert between Java and COBOL types, and their representation at the system level. By creating Interface access beans, it is not necessary, for the Java developer to understand and use the Common Client Interface (API), available in the connector Java libraries to write the access code.

 

HooX COM+ for GCOS 8

Thanks to HooX COM+ Connector for GCOS 8, the GCOS 8 corporate data can be accessed from new E-Business applications developed on Microsoft .NET enterprise server.
The tools provided with HooX COM+ Connector for GCOS 8 allow GCOS customers to define interface components that are easy to use and intuitive for the COM+ programmers (VB, VC++ …). Thanks to the Component Generator Tool, COM+ application component developers are shielded from the complexity of transaction, connection and security concerns when accessing GCOS 8 data through TP8 TPRs and concentrate instead on developing business and application logic. HooX COM+ Connector for GCOS 8 provides the tools and technology necessary to integrate GCOS transactions into the .NET framework without need for additional GCOS skills.
Much of the data of value to organizations has been collected over the years by existing GCOS 8 information systems. Much of the programming investment resides in applications on those same systems. The challenge for developers of enterprise applications is how to reuse and commoditize this value. Thanks to HooX COM+ Connector for GCOS 8, existing business logic on GCOS 8 / TP8 will reused in the scope of new E-Business .NET solutions.

Application environment View

Application environment View

The HooX COM+ Connector for GCOS 8 consists of two software parts delivered to GCOS 8 customers at the same time :
- the connection middleware per se, i.e. the connector that allows COM+ applications to access GCOS 8 TP8 over GTEA.
- the Component Generator Tool

The Component Generator translates COBOL data definitions into a Windows Script Component (WSC). This script is used by customer business logic to access GCOS 8 through the GCOS Connector. The GCOS Connector uses GTEA for communications with GCOS. It may also use DTC and TX for transaction services. The connection parameters for the GCOS Connector are set by the Configurator.

The GCOS Connector is a standard COM+ Dual Interface Component and as such it is created and deleted using standard conventions .The Connector interfaces with the application business logic, the Microsoft Distributed Transaction Coordinator, the Microsoft Transaction Manager, COM+ services and the GTEA service.
e-Commerce TP8 transaction programs are executed through EGATE 8 That is, the first TPR executed is the gateway TPR. It in turn invokes the application TPR. This enables applications to use existing TUXEDO TPR's with the new Connector architecture.

HooX COM+ for GCOS 8 : Architecture

HooX COM+ for GCOS 8 : Architecture