Glossary
This glossary lists some of the terms used in this book along with their meanings.
- action
- A defined task that an application performs on a managed object as a result of an event, such as host screen matching the screen recognition criteria specified for a screen customization. A list of actions is part of the definition of each event, including the screen customization resource.
- application
- See HATS application.
- application event
- Any of the events defined by HATS except the recognition of a host screen, such as connect, disconnect, start and stop.
- application keypad
- A set of buttons or links representing HATS application-level functions. (Contrast with host keypad.)
- artifact
- See resource
- assemble
- To collect the resources of a HATS project, along with the necessary executable code, into an application EAR file in preparation for transferring the application to the server.
- background connection
- Any connection defined in a HATS application other than the default connection. HATS does not transform screens from background connections. (Contrast with default connection.)
- bidirectional (bidi)
- Pertaining to scripts such as Arabic and Hebrew that generally run from right to left, except for numbers, which run from left to right.
- business logic
- The part of a distributed application that is concerned with the application logic rather than the user interface of the application, such as a screen customization. Business logic is specific to the application and is not provided as part of HATS.
- checkin screen
- The screen identifying the host screen that should be active for a connection to be considered ready to be returned to the connection pool. If the application is not on the screen specified by the checkin screen, the connection will be discarded or recycled in attempt to return the connection to the host screen specified by the checkin screen. The checkin screen is only meaningful if connection pooling is specified for a connection.
- component
- A visual element of a host screen, such as a command line, function key, or selection list. HATS applications transform host components into widgets.
- connection
- A set of parameters used by HATS to connect to a host application, stored in an .hco file. (See also default connection and background connection.)
- connection pool
- A group of host connections that are maintained in an initialized state, ready to be used without having to create and initialize them.
- credential mapper
- The component of Web Express Logon that handles requests for host credentials, which have been previously authenticated by a network security layer. (See network security layer.)
- default connection
- The connection on which HATS transforms and presents host application screens to the user. (Contrast with background connection.)
- default rendering
- The method used by HATS to render parts of the host screen for which no specific transformation is specified.
- deploy
- To make a HATS application ready for use on the server, using functions in WebSphere Application Server, after transfer has taken place. Note that WebSphere documentation sometimes uses the term install as a synonym for this process. (See also transfer.)
- descriptor
- See screen recognition criteria.
- developer
- The person who uses HATS Studio to develop applications; also application developer or Web developer. (Contrast with user.)
- display terminal
- A host screen used by the HATS developer to observe interactions between a HATS application and a host application.
- Eclipse
- An open-source initiative that provides ISVs and other tool developers with a standard platform for developing plug-compatible application development tools. Eclipse is available for download from http://www.eclipse.org.
- editor
- An application that enables a user to modify existing data. In HATS Studio, editors are used to customize resources that have been created by wizards.
- enterprise archive (EAR)
- A specialized Java archive (JAR) file, defined by the J2EE standard used to deploy J2EE applications to J2EE application servers. An EAR file contains enterprise beans, a deployment descriptor, and Web archive (WAR) files for individual Web applications.
- Enterprise JavaBeans (EJB)
- A component architecture defined by Sun Microsystems for the development and deployment of object-oriented, distributed, enterprise-level applications.
- event
- An action, series of actions, or an occurrence that is significant to a HATS application, The matching of a host screen by a screen customization's screen recognition criteria is an event, as are a user connecting to or disconnecting from a HATS application, and the failure of a host screen to match any screen customizations.
- Extensible Markup Language (XML)
- A standard metalanguage for defining markup languages that was derived from and is a subset of SGML.
- global rule
- A rule specifying the project-wide replacement of a certain type of host input field with a particular widget.
- global variable
- A variable used to contain information for the use of actions. The values of global variables can be extracted from a host screen or elsewhere, and can be used in templates, transformations, macros, Integration Objects, or business logic. A global variable can be a single value or an array, and it can be shared with other HATS applications sharing the same browser session.
- HATS
- See Host Access Transformation Services.
- HATS application
- An application that presents a Web-enabled version of a host application to users. A HATS application is created in HATS Studio from a HATS project and deployed to WebSphere Application Server and/or interacts with other host applications or e-business applications to present combined information to an end user.
- HATS EJB project
- A project that contains the HATS EJB and Integration Objects that other applications can use to get host data. A HATS EJB project does not present transformed screens from a host application.
- HATS entry servlet
- The servlet that is processed when a user starts your HATS application.
- HATS project
- A collection of resources (also sometimes called "artifacts") created and customized in HATS Studio, which can be assembled into a HATS application.
- HATS Studio
- The component of HATS that runs on WebSphere Studio and enables you to work with HATS projects to create HATS applications.
- Host Access Transformation Services (HATS)
- An IBM software set of tools which provides Web-based access to legacy data sources and host-based applications
- host component
- See component.
- host keypad
- A set of buttons or links representing functions typically available from a host keyboard, such as function keys or the Enter key. (Contrast with application keypad.)
- host terminal
- A HATS Studio tool. A session tied to a particular HATS connection, which the HATS developer can use to capture screens, create screen customizations, and record macros.
- HTML
- Hypertext Markup Language.
- Integration Object
- A Java bean that encapsulates an interaction with a host screen. Integration Objects are constructed from macros and can be included in Web services or HATS EJB projects.
- Java 2 Platform Enterprise Edition (J2EE)
- An environment for developing and deploying enterprise applications, defined by Sun Microsystems Inc. The J2EE platform consists of a set of services, application programming interfaces (APIs), and protocols that provide the functionality for developing multitiered, Web-based applications.
- JavaServer Pages (JSP)
- A server-side scripting technology that enables Java code to be dynamically embedded within Web pages (HTML files) and executed when the page is served, returning dynamic content to a client.
- JSP
- See JavaServer Pages.
- macro
- An XML script that defines a set of screens. Each screen includes a description of the screen, the actions to perform for that screen, and the screen or screens that can be presented after the actions are performed. A macro can be specified as one of the actions to be taken when a host screen matches the screen recognition criteria of a screen customization.
- network security layer
- Software that is responsible for authenticating end users and authorizing them to access network resources, such as IBM Tivoli Access Manager.
- perspective
- In the WebSphere Studio workbench, a group of views that show various aspects of the resources in the workbench. The HATS perspective is a collection of views and editors that allow a developer to create, edit, view, and run resources which belong to HATS applications.
- pooling
- See connection pool.
- portal
- An integrated Web site that dynamically produces a customized list of Web resources, such as links, content, or services, available to a specific user, based on the access permissions for the particular user.
- project
- See HATS project or HATS EJB project.
- resource
- Any of several data structures included in a HATS project. HATS resources include templates, screen customizations, transformations, screen captures, connections, and macros. Other WebSphere Studio plug-ins sometimes call these "artifacts."
- Run On Server
- A feature of WebSphere Studio, which enables the developer to test or preview a project using the embedded WebSphere Application Server. Sometimes referred to as "WebSphere Application Server Test Environment."
- screen capture
- An XML representation of a host screen, used to create or customize a screen customization or transformation.
- screen customization
- A HATS resource with two parts: a set of screen recognition criteria used to match host screens, and a list of actions to be taken when a host screen matches the screen recognition criteria.
- screen recognition criteria
- A set of criteria used to determine whether a host screen matches a screen customization and should have that screen customization's actions applied. Screen recognition criteria are also used in the process of recording a macro; in this context they are sometimes called descriptors.
- Secure Sockets Layer (SSL)
- A security protocol that provides communication privacy. SSL enables client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery. SSL was developed by Netscape Communications Corp. and RSA Data Security, Inc.
- source
- The markup-language pertaining to files that define a HATS project or one of its resources. Also the name of a folder contained in each HATS project.
- SSL
- See Secure Sockets Layer.
- template
- A HATS resource that describes the relatively static portion of the Web pages presented by the HATS application, including a banner and navigation area.
- transfer
- To copy an application EAR file to the server, usually by FTP. (See also deploy.)
- transformation
- A HATS resource that specifies how to convert components of a host screen into widgets on a Web page.
- Unicode
- A universal character encoding standard that supports the interchange, processing, and display of text that is written in any of the languages of the modern world. It also supports many classical and historical texts in a number of languages. The Unicode standard has a 16-bit international character set defined by ISO 10646.
- user
- Any person, organization, process, device, program, protocol, or system that uses the services of a computing system.
- user list
- A list containing information about accounts (user IDs) that a HATS application can use to access a host or database. User lists contain user IDs, passwords, and descriptions for the accounts.
- UTF-8
- Unicode Transformation Format, 8-bit encoding form, which is designed for ease of use with existing ASCII-based systems.
- Web archive (WAR)
- A compressed file format, defined by the J2EE standard, for storing all the resources required to install and run a Web application in a single file.
- Web Express Logon (WEL)
- A HATS feature that enables users to log onto several hosts using a set of credentials that are authenticated by a network security layer. (See network security layer.)
- WebSphere
- An IBM brand name that encompasses tools for developing e-business applications and middleware for running Web applications. Sometimes used as a short name for WebSphere Application Server, which represents the run-time half of the WebSphere family of products.
- WebSphere Application Server
- Web application server software that runs on a Web server and that can be used to deploy, integrate, execute, and manage e-business applications. HATS applications, when assembled and transferred to a server, run as WebSphere Application Server applications.
- WebSphere Studio
- A family of IBM software products that are based on the Eclipse open-source platform and provide a consistent set of tools for developing e-business applications.
- WEL
- See Web Express Logon.
- widget
- A reusable user interface component such as a button, scrollbar, control area, or text edit area, that can receive input from the keyboard or mouse and can communicate with an application or with another widget. HATS applications transform host components into widgets.
- wizard
- An active form of help that guides users through each step of a particular task.
- workbench
- The user interface and integrated development environment (IDE) in Eclipse-based products such as WebSphere Studio.
- XML
- See Extensible Markup Language.
Home