Verastream Host Integrator Glossary

Click a letter to jump to a point within the glossary.


 

access control — Access is being able to get to (having permission to use) particular data on a computer. Access is controlled by requiring a user ID and password.

adjacent entity — An entity that can be reached via one operation.

<any number> — A record is delimited by any numeric text appearing in a specified column of a recordset. Note: If you select this option, the start column entry must have a specific record column, while the end column must be specified as well. If either the start or the end is not set to a specific location, an error message will appear. In addition, selecting <Any number> means that only numeric characters will be recognized by the Design Tool. Any non-numeric characters that are found will result in a false test.

<any text> — A record is delimited by any alphanumeric text appearing in a specified column of a recordset. Note: If you select this option, the start column entry must have a specific record column, while the end column must be specified as well. If either the start or the end is not set to a specific location, an error message will appear.

<user specified text>—A record is delimited by text specified by the user. The user can select specific text from the terminal screen or type text directly into the Text box.

AID key—A key on an IBM terminal keyboard that creates communication with the host. Pressing an AID key signals the host that data entry is complete. On IBM terminals, the other keys usually act locally and do not cause host communication.

The default set of AID keys to be displayed when rejuvenating a 3270 terminal application is:

The default set of AID keys to be displayed when rejuvenating a 5250 terminal application is:

ant
Ant is a Java-based build tool that is an alternative to the make command. It allows developers to build a target defined in an Ant project file. It creates cross-platform scripts and uses XML as its scripting language.

application server — A software program that runs on a mid-sized computer and hosts web or client/server applications. An application running on this kind of server can work as a translator for the many databases that cannot interpret commands written in HTML. For example, it could allow a customer with a browser to search an online retailer's database for pricing information.

attribute — A selected area on an entity containing data that needs to be accessible via the model file. This area might be a text field that changes depending on inputs related to prior screens. For example, an attribute could be the text field where an account number might be typed on the terminal screen.

authentication — Authentication is the process of determining whether a user is who he or she is declared to be.

B

<blank line> — This is the default. A record is delimited by the appearance of one totally blank line. Note: When this option is selected, all other options in the Record size box will be disabled except for the End of screen is always a delimiter box.

block mode — 3270 and 5250 applications and some HP applications are page-oriented, or block mode. When the host sends a screen to the terminal, it informs the terminal that it is transmitting one screen's worth of data. For example, when you type data on a terminal screen, the data entered is local to the terminal; therefore, nothing is sent to the host until an aid key, like the Enter key, is pressed. This makes it easy for the Host Integrator to distinguish one entity from another.

boolean — A data type with only two possible values, True (1) or False (0). Use an integer value to hold a Boolean value. Any integer other than 0 is equivalent to True.

C

certificate — A certificate is an electronic document used to identify an individual, a server, a company, or some other entity and to associate that identity with a public key. Like a driver's license, a passport, or other commonly used personal IDs, a certificate provides generally recognized proof of a person's identity. Public-key cryptography uses certificates to address the problem of impersonation.

.cfgtrc file — A trace configuration file that controls what information is saved during a debug trace session. See the Troubleshooting tracing documentation for more information.

character mode — In VT connections and some HP connections, the data is sent as a constant stream of characters, rather than as a block. For example, if an arrow key is pressed, the arrow key is directly sent to the host, and then the host sends it back to the terminal. Even though a VT application may appear to a user as a series of screens, to the terminal it is just a series of characters and escape sequences. There is nothing in the VT datastream to denote what constitutes a screen. For more information, see configuration options for modeling character mode host applications.

CICS — Customer Information Control System. An online transaction-processing subsystem from IBM. CICS controls the interaction between applications and users, and lets programmers develop screen displays without detailed knowledge of the terminals being used.

client session — A client session refers to a host session that has a client attached. A new client session is created every time a client connects to a host session, and the client session is destroyed when the client disconnects.

column — The area that encompasses a recordset. A recordset can be left as one column or it can be delineated with multiple columns. For more information, see the Recordset tab documentation.

COM (Component Object Model) — Microsoft’s standard for distributed objects, an object encapsulation technology that specifies interfaces between component objects within a single application or between applications. It separates the interface from the implementation and provides APIs for dynamically locating objects and for loading and invoking them.

compound procedure — A collection of one or more SELECT procedures and an UPDATE or DELETE procedure that allows you to perform more than one query level task at the same time, like selecting several records and updating them within the same procedure. Review the overview of procedures.

connectors — In Verastream Host Integrator, connectors are collections of runtime objects, APIs, libraries, and programming examples that help you develop efficient client/server and web applications that integrate host data using a Host Integrator Server. Each connector is customized for a specific development environment. Client/server and Web applications can access data from, and input data to, a host application, by making calls to Host Integrator Server using a Host Integrator API. Upon receiving a client request, Host Integrator Server instantiates a session with the host system using the logic stored in the model. Host Integrator Server navigates through the host application, fetches the requested data, and returns it to the client in a form native to the client development environment.

Verastream Host Integrator provides connectors for Java, .NET, COM, and C.

cursor command list — A list of commands used to define an override to the default Use arrow keys to move cursor option in the Advanced Model Properties dialog box. These can be used in operations or in move cursor command lists for VT and HP block mode applications.

D

.dtool file — See the information on settings files.

data object — 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, and COM. Host Integrator includes a set of APIs for each connector. Client/server and web applications can use multiple data objects; each instance of a data object corresponds to a single host session.

data object to host session — See session.

date (type and format) — A data type for storing date values or a field format for displaying date values.

datetime (type and format) — A data type for storing combined date-and-time values or a field format for displaying combined date-and-time values.

deploying a model — Deployment is the process of transferring a model and its associated files and settings to the production server or servers where it's going to run. Within the Host Integrator Development Kit, there is a local server associated with the Design Tool, allowing you to test a deployed model without using a production server. More information...

Design Tool — A development environment that allows a host expert to encapsulate host functions by modeling and abstracting an existing host application into services. These services can then be integrated into client/server and Web applications.

domain — Host Integrator load distribution domains provide load balancing and failover support for installations that contain multiple Host Integrator session servers. When you configure a load distribution domain client applications can connect to a domain instead of connecting to individual session servers. The management server will apply logic based on the domain configuration to distribute load among the session servers in the domain, and if a session server in a domain becames inactive for whatever reason, client applications will still be able to connect to their active session servers in the domain. Follow the steps described in Adding, Removing, and Configuring Domains. This documentation topic details how to add a domain, and add session servers to the domain with Weight and Priority values.

dynamic traversal — The navigation path taken when a user asks to go to a particular screen but doesn't care what path is taken or which operations are executed.

E

EJB — Enterprise JavaBeans. A Java API developed by Sun Microsystems that defines a component architecture for multi-tier client/server systems and allowing for the development of distributed applications.

encryption — Encryption is the conversion of data into a form, called a ciphertext, that cannot be easily understood by unauthorized people. Decryption is the process of converting encrypted data back into its original form, so it can be understood. In order to easily recover the contents of an encrypted signal, the correct decryption key is required. The key is an algorithm that undoes the work of the encryption algorithm.

Enterprise Application Integration (EAI) — EAI is a set of technologies that allows the movement and exchange of information between different applications and business processes within and between organizations.

entity — A unique host application screen. Once you label your host application screen as an entity, you must define it using entity definitions and entity properties.

.entityx — File extension for files containing Entity definitions and snapshots. The entity file is the component of the model that contains all the data of an entity, such as patterns, attributes, operations, recordsets and recordset fields. Command lists are also kept in the entity file. There is one file per entity, having the name of the entity. This file defines the model, together with the .modelx and all, optional, .tablex files.

entity signature — The definitions and properties that make an entity unique. By default, all patterns are included in an entity signature although an excess may impact server performance. If you do not want to include a pattern in an entity signature, clear the Use in entity signature check box on the Pattern tab. Note: If you are defining an error pattern, clear the Use in entity signature check box.

entity definitions — These include patterns, attributes, operations, recordsets, fields, tables, and table columns. These definitions describe certain discerning characteristics of an entity for host navigation purposes.

enumeration — Properties and values of this type have a predefined list of possible values beginning with the letters "rc." You can use one of the "rc" values or the equivalent number or value.

error entity — An entity that you arrive at as a result of an error within an operation. For example, the host application returns an error because it was unable to fulfill an SQL request from a client application. If an error entity is defined, the Design Tool will relocate to that error entity. To define an error entity from an operation, add it to the User-defined error entities box in the Operation Destinations dialog box. If you're using table procedures, you can also insert an error entity into your procedure. See Troubleshooting Error Patterns and Error Entities for more information.

error pattern — A user defined error that occurs on the host and can be stored in your model as a pattern. Using an error pattern as an operation condition is helpful in determining why an operation failed. Make sure to define this pattern on the start entity of your operation. To create an error pattern out of a terminal error message:

  1. Select the message on the terminal screen and add it to your entity as a pattern.
  2. Clear the Use in entity signature check box and click Apply.
  3. On the Operation tab, click the Conditions button to open the Operation Conditions dialog box.
  4. Under Error patterns, move the pattern from the Available list to the Error patterns list and close this dialog box.

See Troubleshooting Error Patterns and Error Entities for more information about trapping error messages that result from writing attribute data to the terminal screen.

error processing — The Design Tool handles errors by displaying a popup error message.

event — There are two different contexts for this term in Host Integrator:

event handler
In Host Integrator, an event handler is procedural code that implements an interface that allows the Host Integrator Server to suspend the interpretation of a model. More information...

An event source is a specified point in the execution of a model, such as the reading of an attribute, the authentication of a user, or the writing of a recordset field. An event source generates an event only if a corresponding event method is implemented in the event handler. The event, when delivered to the event handler, describes the environment in which the event occurred. The event handler code uses this description to accomplish its task.

F

failover — Failover handling detects when a session server is unreachable or offline. In this situation, another server in the domain is used to serve requests. If all servers in the domain with the lowest "priority" value (such as 1) are unavailable, then the request goes to the set of servers with the next-lowest priority value (such as 2). Failover configuration provides fault tolerance for production environments.

field — A selected area on a recordset containing data that needs to be accessible via the model file. An example of a field might be a specific record within a recordset. Defining a field on a recordset is similar to defining an attribute on an entity.

FIPS — Federal Information Processing Standards, the United States government technical standards published by the National Institute of Standards and Technology. These are standards that government agencies and contractors must meet. FIPS standards encompass security standards such as SSL and TLS.

G

global event — A change in the state of an object that can be included in operations throughout more than one entity in a model. To define a global event using the WaitForMultipleEvents command, click Host Events on the Model menu. To view a list of single events that can be used as commands in an operations, see the Host Events Commands help.

H

home entity — In the Design Tool, this entity is identified with a house icon in the Entity box on the Entity window. On the a Host Integrator Server, the home entity represents where a session can sit while it is not in use. From the perspective of the API programmer, this is the first entity that you would expect to see when you connect to a session on a host application model. To configure a default home entity, click Properties on the Model menu to open the Model Properties dialog box.

Host Integrator Connectors — See connectors.

Host Integrator Host Emulator — The Host Emulator is a browser-based tool that allows you to run 3270 and 5250 models created with the Host Integrator Design Tool without having a live connection to a host. Once you've created a model using the Design Tool, you can load it in the Host Emulator and play it back to simulate the host communication from which your models were created, allowing you to test your client or Web application. The Host Emulator does not actually connect to the host.

host session — See session.

HP terminal — Host Integrator can connect to two types of HP terminals: HP 70092 or HP 2392A using two possible transport types: NS/VT or Telnet. Select Session Setup to configure a host session. Note: If you are connecting to an HP terminal using Telnet as your transport type, use a host event command such as WaitForNewHostScreen between HP TransmitTerminalKey commands in operations.

.hst file — A host trace file that contains datastream information from the host that can be captured by the Design Tool to help diagnose emulation bugs. The user typically generates one at the request of a Verastream engineer and then sends the file for inspection. See Troubleshooting tracing for more information.

I

integer — A data type that holds integer variables stored as 32-bit whole numbers in the range of -2,147,483,648 to 2,147,483,647.

introspection — The process of inspecting components of a program for meta-information (information about the component, as opposed to information about what the component is used for).

J

J2EE — Java 2 Platform, Enterprise Edition (J2EE) - a version of Java for developing and deploying enterprise applications.

JCA — J2EE Connector Architecture. A standard architecture for connecting the J2EE platform to enterprise information systems.

JSP — (JavaServer Page) An extension to the Java servlet technology from Sun that provides a simple programming vehicle for displaying dynamic content on a Web page. The JSP is an HTML page with embedded Java source code that is executed in the Web server or application server. HTML provides the page layout that will be returned to the Web browser, and Java provides the processing; for example, to deliver a query to the database and fill in the blank fields with the results. The JSP is compiled into bytecode (into a servlet) when first encountered by the server.

K

key — A field in a record that is used to uniquely identify that record.

L

load distribution — Load distribution (also known as load balancing) spreads out client connection requests across multiple session servers in a Host Integrator domain. Each server in the domain is configured for a “weight” which is used for proportional allocation with a pseudo-random distribution algorithm.

login command list — Enables a quick and reliable login to a host. It is also helpful when the first screen that appears on a host, like a splash screen, is not a good candidate to be an entity. Open the Command List Edit dialog box to create a login command list. To view an example of a login command list, see the Pine model. Note: Configure your login or logout command lists to be automatically executed on a host connect or disconnect by selecting the Execute login command list and Execute logout command list check boxes on the General tab of the Preferences Setup dialog box.

logout command list — Enables quick logout from the host. Open the Command List Edit dialog box to create a logout command list. To view an example of a logout command list, see the Pine model. Note: Configure your login or logout command lists to be automatically executed on a host connect or disconnect by selecting the Execute login command list and Execute logout command list check boxes on the General tab of the Preferences Setup dialog box.

M

model — A representation of a host application's connections, screens, navigation, and data flow that you build with the Host Integrator Design Tool. Once you have modeled your host application, you deploy the resulting model to a Host Integrator Server, where it can provide real-time access to host data through web-enabled services.

model package — An assemblage of files that you use to deploy a model on one or more session servers. It consists of the model file and optional files, including event handler files and descriptor files.

move cursor command list — Move forward and move backward command lists are used specifically with character mode hosts to make it easier to move the cursor from one attribute to another on an entity. On the Model menu, click Properties and then click Advanced to create a move cursor command list.

.modelx file — File extension for files containing general model and variable definitions. The model file is the main component of the model that contains, together with the .entityx and optional .tablex files, the data that is required to execute data retrieval. The model file also contains Event definitions, Design Tool test data and Design Tool preferences. The Design Tool data is ignored by the Host Integrator Server.

.model file — File extension for files containing a complete Model definition (older format, replaced by .modelx, .entityx and .tablex). The model file is the component of the model that contains all the data that is required to execute data retrieval. This includes objects such as entities, patterns, attributes, operations, recordsets, recordset fields, and variables. If the user has defined tables, columns, and queries, those are also stored in this file. Command lists are also kept in the model file. The Host Integrator Server uses this file at runtime to define execution requirements and the Host Integrator connectors expose the information stored in this file with the Host Integrator connector API after the model has been copied to the Host Integrator Server. The model file also contains Design Tool preferences, but these are ignored by the Host Integrator Server.

N

NS/VT — Network Services Virtual Terminal. A transport type that uses a proprietary HP protocol for connecting to HP3000 hosts.

O

object — A combination of code and data that can be treated as a unit; for example, a control, form, or application component. Each object is defined by a class.

offline mode — A mode in which the Design Tool allows you to scroll through the entities in your host application without requiring a connection to a host. You can display any entity in your model, regardless of whether there is a traversal operation defined to go between any two entities. To activate offline mode, click Offline Mode on the Connection menu or use the Offline button on the standard toolbar.

offset — The row and column coordinates on a terminal screen. The offset is calculated for you by the Design Tool in the status bar of the Terminal window.

The offset is zero-based and is the equivalent of the following formula:

offset = [(row - 1) x width] + (col - 1) 

The reverse formulas (offset to row/col) are as follows:

row = (offset / width) + 1, where the division operation uses integer logic
  remainder of the division operation is ignored)
col = (offset % width) + 1, where % means modulo (use only the remainder of
  a division operation)

Example: For an 80-column terminal screen:

row 1, col 1 = offset zero (always true)
row 1, col 2 = offset 1 (always true)
row 2, col 1 = offset 80 *(depends on the screen width)

operation — The instruction that uses commands to determine what kind of actions the host should take to navigate between entities or fetch data. When executed, an operation can tell the host how to traverse from one entity to another.

P

pattern — A selected area on an entity that does not contain data that changes from session to session.

procedure — A procedure defines how Host Integrator locates, retrieves, updates, inserts, and/or deletes data when it fulfills a request submitted by a client application using a Host Integrator API. A procedure can be a set of operations that define how the Host Integrator fulfills SQL queries from client applications.

public key cryptography — Public key cryptography is a method for authenticating a message sender or encrypting a message. In public key cryptography, a public and private key are created simultaneously by a certificate authority using the same algorithm. The private key is given only to the requesting party and the public key is made publicly available as part of a digital certificate. The private key is never shared with anyone or sent across the Internet.

Q

R

record index — The record line number to begin with when retrieving records from a recordset.

recordset — An area on an entity containing dynamically changing information, usually scrolling sets of data that are a result of a data fetch. When a recordset is defined in the Design Tool, the position on the screen as well as the layout of the recordset on the screen are defined. The Design Tool treats recordsets as database tables consisting of multiple records of a similar format. These recordsets can often be scrolled through using terminal keys. Operations, scroll termination criteria, and options for filtering records on the last page in a recordset can be set from within each recordset. In addition, fields can be defined in recordsets just as attributes are defined in entities.

recordset scrolling operation — The instruction that uses commands to determine how to navigate within a recordset defined on an entity. To configure a recordset scrolling operation, use the options available in the Scrolling box of the Recordset Operations dialog box.

recordset synchronization — In order to resolve which record is the "current" record in a recordset, you must define how Host Integrator synchronizes to the current record. This depends greatly on how the application represents the current record. Host Integrator models use recordset synchronization in two ways:

regular expression — A regular expression is a pattern that can match various text strings; for example, l[0-9]+ matches l followed by one or more digits.

replication — Replication is the process of sharing information between management servers. This ensures that the content is consistent between each server. Multiple management servers, called a cluster, increase the number of computers available to clients and so reduces the load on each one.

rogue session — A rogue session within a session pool exhibits a circular behavior when attempting to log in and reconnect. See General Server Properties in the Administrative Console to configure the server to handle rogue sessions.

S

script manager — A process that determines the available event handlers for a given model and manages their execution, including any callbacks to the terminal session. The script manager runs in its own process that is started by the Host Integrator Design Tool and the Session Server. It defines handler class formats and provides an interface to call back to the terminal to retrieve data or to send commands.

session — In this documentation, the term "session" is a general term that describes a single session between a client or Web application and the host. The term "host session" refers to the connection between a Host Integrator Server and the host; host sessions run over Telnet or NS/VT. The term "data object to host session" refers to an active connection between a data object and a host.

settings file — This file is used as a starting point for creating new model files. This file contains settings information configured in the Design Tool for the model file, such as window size, colors, keymapping, and preferences). Creating a settings file is optional; it is a starting point for creating a new model. Settings files have the extension .dtool.

.snapshot file — This file contains screen information used by the Design Tool when in offline mode.

SSL — SSL (Secure Sockets Layer) is a protocol for managing the security of message transmissions on the Internet. SSL uses a program layer located between the Hypertext Transfer Protocol (HTTP) and Transport Control Protocol (TCP) layers. SSL is included as part of both the Microsoft and Netscape browsers and most Web server products. SSL was developed by Netscape and is now supported by Microsoft and other Internet client/server developers. Also see TLS.

static section — An area on a terminal screen that does not contain data that changes from session to session. You can choose how to position the cursor by using the Selection mode option on the Pattern tab.

string expression — A sequence of contiguous characters that represent the characters themselves rather than their numeric values. A string can include letters, numbers, spaces, and punctuation.

settings file — Contains Design Tool settings, such as window size, colors, keymapping, and preferences. Creating a settings file is optional; it is a starting point for creating a new model. Settings files have the extension .dtool.

string (type and format) — A data type for storing alphanumeric characters. A field format for displaying alphanumeric characters.

synchronization commands — These commands, also known as Host Events, are listed on the Operation Edit or Command List Edit dialog box when you click the right arrow button. Host Event commands often request the host to wait for certain commands to complete before executing the next command.

T

table — A table is a structure that contains columns that are used as input and output parameters for procedures. Typically, table columns are named to match their corresponding model attributes and fields. Tables are a way of organizing host data into a database-like view of the data, and procedures manipulate that data. The only way to access the abstracted table data is through a procedure.

.tablex — File extension for files containing Table definitions. If the user has defined tables, columns, and queries, those are stored in this file. There is one file per table, having the name of the table. This file defines the model, together with the .modelx and all .entityx files.

tabstop — Valid screen coordinates that indicate to Host Integrator the valid "at rest" positions on an entity. It's helpful to create tabstops at input fields like attributes or recordset fields, but it is also possible to create them in protected fields. The order of tabstops on an entity does not have an effect on how Host Integrator handles tabstops. When moving the cursor, Host Integrator issues the command(s) and then waits for any tabstop that is not the same location as where it started. Host Integrator never waits for a particular tabstop.

timout — A timeout is the default length of time that a computer will wait for a task to be completed before the task is canceled. The cancellation of a task is usually indicated by an error message. Timeouts can almost always be adjusted by the user or system administrator. Search the Design Tool online help on Timeouts for topics containing timeout information.

TLS — Transport Layer Security, a protocol that secures communication between client/server applications on the Internet. This is the successor to SSL.

terminal attribute— A property of characters that appear in a terminal field of a host application screen. For example, a property of a terminal field might be host color, protected normal numeric, or unprotected highlight alpha. To view the host name for a terminal attribute represented on a terminal that is being emulated by the Design Tool, open the Settings menu and click Display to open the Colors tab of the Display Setup dialog box. Point and click the terminal field on the terminal screen, and the terminal attribute will display on the Colors tab in the Item box.

terminal field — A text field on a terminal screen dictated by the host application. When modeling a host application, entity attributes are often created to represent terminal fields.

time notation (HH:MM:SS) — HH is hours, MM is minutes, and SS is seconds. This is how the Host Integrator interprets various strings:

45

forty-five seconds

2:30

two minutes and thirty seconds

1:2:3

one hour, two minutes, and thirty seconds

.trace — Contains the data generated during a debug trace session. This is the file that should be sent to Technical Support for diagnosing model problems. See Troubleshooting tracing for more information.

.trc and .trc_GROOMED — Contains the data generated during a Host Emulator recording. This is the file that, when copied to Micro Focus\Verastream\HostIntegrator\hostemulator\recordings, is used by the Administrative Console to access Host Emulator Recordings and is connected to using the Design Tool.

U

user-defined project type — Web Builder creates projects based on the settings in a project type. You can define your own project type by modifying settings of a default project type and saving it under a new name.

<user specified text> — A record is delimited by text specified by the user. The user can select specific text from the terminal screen or type text directly into the Text box.

V

.vmr — File extension for model debug message files. The Model Debug Messages option provides a view of past behavior, demonstating a model interacting with a terminal datastream. See Model Debug Messages for more information.

variable — A global placeholder for a piece of data that you want to use during execution of a model. Defining variables in your model provides: (1) a level of abstraction from attributes, (2) temporary storage during navigation, and (3) access to this data via the Host Integrator connector.

W

WCP — WRQ Communication Protocol is an application layer protocol, used for all inter- and intra-process communications between all Host Integrator services. This is an implementation of platform independent distributed communications.

Web application — An application that uses a Web browser as its user interface and usually runs on an application server. A Web application may combine business logic with back-end data sources like relational databases, application mining information, and MQSeries. A web application can generate HTML pages or download Java applets to a Web browser.

Web project — Output of the Host Integrator Web Builder. This could be a Web application, Web service, or component interface.

Web server — A Web server is a program that uses the client/server model and the Hypertext Transfer Protocol (http), serves the files that form Web pages to Web users. Every computer that contains a Web site must have a Web server. Commonly-used Web servers include Microsoft's Internet Information Server (IIS), and Apache, an open source Web server for Windows and UNIX systems from The Apache Software Foundation. Host Integrator includes a >Web server and servlet runner.

weight — Weight values are used for load distribution. Priority values are used for failover. For each set of servers with the same Priority, make their Weight values total to 100. This makes it easier to identify each server’s load as a percent of the total.

X

Y

Z