You can use the following features to capture the functionality of your host application:
The Design Tool is capable of connecting to any one of following hosts:
|IBM 3270||Models 2 (24x80) Normal and Extended, 3 (32x80) Normal and Extended, 4 (43x80) Normal and Extended, and 5 (27x132) Normal and Extended|
|IBM 5250||Models 3179-2, 3180-2 (132 Column Capable), 3196-A1, 3477-FC (132 Column Capable), 3477-FG (132 Column Capable) , 3486-BA, 3487-HA (132 Column Capable) , 3487-HC (132 Column Capable), 5251-11, and 5291-1|
|VT||VT102, VT400-7, VT400-8, and VT52 terminals|
|HP||HP2392A and HP 70092 terminals|
You select the host connection type on the New Model or Session Setup dialog box, accessible from the File or Connection menu respectively.
The main feature of the Design Tool is the modeling feature, which enables a host expert to create a model of a host application. First, you connect to a host via the Design Tool and then define entities for terminal screens, which may include patterns for identification, attributes to specify the location to input data, and one or more operations to allow programmed traversal of the host application, and variables which can be mapped to various attributes or various entities.
In most cases, you will use tables and procedures to create an abstraction of the host data so that it can be queried through a subset of the industry-standard Structure Query Language (SQL). See "Abstracting a Host Application" below.
This model, an object in the form of a .model file, is saved in the Design Tool and then copied to a Host Integrator Server. For more information, see The Modeling process.
You can create procedures (and underlying tables) to add a database abstraction layer on top of your host application model. Client application programmers can then access this database abstraction layer, either by a direct call to a procedure or through a subset of the industry-standard Structured Query Language (SQL). For an SQL query, the client application specifies a table, a set of input parameters, and a set of desired output parameters. Host Integrator then returns the desired data to the client application.
In addition to the definition process, the Design Tool provides server-like services for the modeling and procedure definitions. This permits the user to test and debug models and database procedures prior to deployment. The model layer requires entity recognition, operation execution, and variable reads and writes. The debug layer takes arbitrary input and resolves a query (or returns an error) or executes a specified query.
The command list recorder records host commands for operations required by the debug layer. On the Model menu, point to Record and then click Start Recording to begin. For information about creating login, logout, and move cursor command lists see Command List Edit.
There are several functional user preferences that can be implemented, including creating default names for attributes, automatic pattern generation, and proposing new operations when appropriate. On the Settings menu, click Preferences for more information.
The Design Tool has the ability to display in online and offline design modes. As each entity is defined, two files are created to enable the design mode process.
Offline mode is available for all emulation options, while Host Emulator is available for IBM 3270 and 5250 emulations only.
You can import portions of models for use in other models, making model creation more efficient. Multiple developers can work on large models similtaneously and pull the various pieces together at a later time. See Importing Model Elements for more information.
An event handler gives you the ability to customize the behavior of a model.
The Design Tool offers a variety of features that assist you in creating event handlers. The result is a Java class that conforms to rules for event handling. This class is then mapped (attached) to specific objects of a model to customize its behavior.
You can attach event handlers to events associated with the entire model, a life cycle event, or to entities, attributes, operations, recordsets and recordset fields, and procedures. You can reuse a handler in multiple models or with multiple objects of the same type within the same model.