The following discussion provides an overview of the function of each Host Integrator component. For a general overview, see the Host Integrator Overview. For information about configuring Host Integrator, see the How To section.
Host Integrator Server consists of the following components:
These components can be used to create and manage custom client/server and web applications that access legacy host data. They communicate with one another over TCP/IP using the WRQ Communications Protocol (WCP).
The Host Integrator Server works in conjunction with the Host Integrator Design Tool and the Host Integrator Software Connectors to integrate host application data and business logic into client/server and web applications.
Using the Design Tool, a developer builds a model of a host application, accessing fields that contain information needed by the client application. The model is then loaded into Host Integrator Server. The model contains all the information about the host application, including its traversal logic, application screen signatures, and data attributes, and can be accessed from a variety of software development environments using an Application Programming Interface (API) included in the Host Integrator Development Kit. When the Host Integrator Server receives a request from a client application, it instantiates a host session using the logic stored in the model specified in the request. Host Integrator Server navigates through the host application, fetches the requested data, and returns it to the client application.
For more information about creating and working with models and working with Host Integrator connectors, see the Design Tool online help, which is included in the Host Integrator Development Kit.
Host Integrator Domain Servers provide load balancing and failover support for multiple Host Integrator Servers. When a client application sends a request to a data object to connect to a model by means of a Host Integrator Domain, the data object follows this procedure to execute the request:
The Host Integrator Administrative WebStation allows administrators to view and configure Host Integrator Servers, Security, and Domains from a web browser. The Administrative WebStation uses WCP to communicate with Host Integrator Servers and AADS.
The Administrative WebStation must be installed on a web server that is capable of running servlets.
AADS stands for Authentication Authorization and Directory Services. This required Host Integrator component provides security and directory services for Host Integrator deployments. All Host Integration session servers share an AADS symbolic name.
AADS tracks servers and domains in your installation, and it must be installed before you can install Host Integrator Servers or the Administrative WebStation. The AADS security component is installed by default but is not enabled. For information on security, see Host Integrator security. By installing more than one AADS in your deployment and configuring a symbolic name for all the AADS servers in your deployment, you can establish AADS failover support. Although AADS can be installed on the same machine as other Host Integrator components, it is typically installed on a dedicated machine.
AADS performs several functions:
Host Integrator Data Objects allow client/server and web applications to communicate with a Host Integrator Server using a variety of connector technologies, including Java, C, COM, and JDBC. Host Integrator includes a set of APIs for each connector.
A web application can use multiple data objects; each instance of a data object corresponds to a single host session.