|
|
|
Verastream and Synapta Terminology
Technical Note 10074
Last Reviewed 01-Feb-2007
Applies To
Verastream Host Integrator
Synapta
Summary
Technical Note 10074
Last Reviewed 01-Feb-2007
Applies To
Verastream Host Integrator
Synapta
Summary
This technical note is intended for users transitioning from Synapta to Verastream Host Integrator and provides a comparison of Synapta and Verastream terms.
For further information about Verastream resources, see http://support.attachmate.com/solutions.html?prod=verastream.
Verastream and Synapta Terminology
| Term |
Verastream Definition |
Synapta Equivalent |
| AADS |
The Authentication Authorization and Directory Services (AADS) provide security and directory services for Host Integrator Servers. (For more information, see Technical Note 10060.) |
MCS Directory Services Support and Authentication |
| API |
Application Programming Interface (API). The instructions that are supported to tell the host how to navigate between entities or fetch data. |
Same |
| attribute |
In a model, a selected area on an entity containing data. For example, this could be a text field that changes depending on inputs related to prior screens or an area where an account number is typed on the terminal screen. |
Task Steps Inputs/Outputs |
| branch entity |
A valid alternative entity destination inserted into a procedure. |
Task Step with multiple Step Destinations |
| command list |
A short script containing a list of commands that controls navigation through the model or the manipulation of data. |
Transition Action/ Everything performed to get from one step to another step |
| Compound procedure |
A collection of one or more SELECT procedures and an UPDATE or DELETE procedure used to perform more than one query level task at the same time. For example, selecting and updating several records within the same procedure. |
No equivalent. The closest equivalent would be Task Chaining. |
| connector |
A collections of runtime objects, APIs, libraries, and programming examples that help you develop efficient client/server and web applications that integrate host data via Host Integrator Server. Each network-enabled connector is customized for a specific development environment. Verastream Host Integrator provides connectors for Java, JDBC, .NET, COM, and C. |
Same. Task interface Objects |
| data fetch termination |
The criteria used to terminate a fetch process for a scrolling recordset. |
Last Page Rule |
| deploy |
Move a model and associated files to a Host Integrator Server. (For more information, see Technical Note 10237.) |
Publish the Navmap |
| descriptor file |
An .xml file that describes a model’s configuration and how it should be deployed. (For more information, see Technical Note 10237.) |
None |
| entity |
A host application screen, as identified in a host model. |
Task Step |
| error entity |
An entity representing the host screen that is displayed when an error occurs in the host application. |
An error branch |
| error pattern |
An area on the entity that identifies an error condition. |
Recognition rule containing an error condition |
| event handler |
Code that suspends the interpretation of a model and then returns control to it. |
Pin Point Customization (PPC) and Server Side API (SSA) |
| event handler template |
Generated by the Design Tool for each type of event handler, a template is a code stub that provides a starting point for creating event handlers. |
The Pin Point Customization (PPC) Navigation Script dialog box help. Server Side API (SSA) must be coded in an outside editor. |
| event source |
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 corresponding event method is implemented in the event handler. |
Pin Point Customization (PPC) source and Server Side API (SSA) source (Java based) |
| field |
A single piece of data in a recordset. A field is to a recordset as an attribute is to an entity. |
Table Fields |
| home entity |
In a Verastream procedure, the home entity is where the procedure starts and where it returns to after it has processed its operations. |
Parking Task End Point |
| Host Integrator Server |
Handles the communication between the model and the host application. |
Services Builder Runtime Engine |
| integration project |
Host application functionality is encapsulated into services that can then be used by client applications. |
Same. Services Builder Project |
| intermediate entity |
An entity that is accessed as part of the destination path. |
Task Step that is part of a task branch |
| life cycle event handler |
An event handler associated with a session. The life cycle begins with the model accessing the host application and ends when the host connection is closed. |
SSA, server side scripting |
| mapping |
To connect fields in one method to the fields in another method. For example, mapping one method's fields for street, city, and state to another method's combined address field. |
Internal NavMap binding between Task Inputs/ Outputs and Task Step Inputs and Outputs |
| model |
A representation of a host application's connections, screens, navigation, and data flow that you build with the Verastream 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. |
NavMap |
| model package |
A single file that combines a model file, its event handler files, and its configuration information so that it can be activated on one or more Host Integrator Servers. |
None |
| model variable |
A placeholder for data. Configure session pools that use model variables to provide values for the host user IDs and passwords. |
Global variables |
| model variable list |
A set of values for a model variable. Often used to store host user IDs and passwords. |
None |
| multi-column recordset |
A recordset that displays more than one entry per line. |
None / Would require SSA code or a PPC |
| non-circular procedure |
A procedure that does not return to its home entity. |
Stateful Task |
| operation |
The instructions that tell the host how to navigate between entities or fetch data. |
Transition Action/ Anything performed to get from one step to another step |
| parameters |
A procedure’s data objects, which are usually mapped to entity attributes or a recordset fields. |
Task Inputs/Outputs |
| pattern |
A selected area on an entity that uniquely identifies the entity. |
Step Recognition Rule |
| procedure |
Defines how Host Integrator locates, retrieves, updates, inserts, or deletes host application data. |
Task |
| procedure-based web application |
A web application created by Web Builder using the procedures web application in a host application model. The web pages are based on the functionality of the procedures, rather than host screens. |
Services Builder web application. Task based |
| recordset |
An area on an entity containing dynamically changing information, usually scrolling sets of data that are a result of a data fetch. The Design Tool treats recordsets as database tables consisting of multiple records of a similar format. |
Tables |
| rejuvenation project |
The conversion of the display of a host terminal screen into an HTML page. Web Builder rejuvenates the host application from the terminal screens. |
Similar functionality in Presentation Builder HTML on the fly. |
| sandbox entity |
An entity that has been removed from the procedure, but retains all the customizing done on that entity. |
An orphaned screen, which is defined in the NavMap but not associated with a task. |
| screen-based web application |
A web application generated by Web Builder using a model’s entities, attributes, and fields. The look of the web application screens can be customized, but the functionality is still based on the host screens. |
None |
| scrolling operation |
An instruction that uses commands to determine how to navigate within a recordset defined on an entity. |
Next Page Inputs |
| session pool |
A set of host sessions on a Host Integrator Server that are preconfigured for access by client applications. |
Same |
| session pool |
Preconfigured host sessions running on a Host Integrator Server. A session pool enables faster host session allocation and access to the host system since the host session can be logged on and waiting at the host application’s main entry screen. |
Services Builder Session Pool |
| table |
An abstraction or “view” of host data. |
None |
| Web Builder project |
The output of Web Builder. This could be a .NET or Java screen-based or procedure-based web application, a web service, JavaBeans, a Visual Basic ActiveX DLL, or a .NET class library. |
None |
| web server |
A program that uses the Hypertext Transfer Protocol (HTTP) to serve web pages to web users. Every computer that contains a web site must have a web server. Verastream Host Integrator includes the Tomcat web server and servlet runner. |
Same |
