Previous     Contents     Index     DocHome     Next     
iPlanet Application Server 6.0 Programmer's Guide (C++)



Glossary


administrator. See system administrator.

aggregate expression. An expression in a query that summarizes values from one database column across several rows. You can use aggregate expressions to specify computed fields. The aggregate functions available depend on your database server, but those typically supported are Min( ), Max( ), Count( ), Avg( ), Sum( ), First( ), and Last( ).

alias. An alternate name. In a query, an alias is a name given to a database table, column, or computed field.

API. See application programming interface (API).

applet. An applet is a small application written in Java that runs in a web browser. Typically, applets are called by web pages to provide special functionality.

application flow. The perceived progress of activity from page to page in a browser-oriented application.

application programming interface (API). A set of instructions that a computer program can use to communicate with other software or hardware that is designed to interpret that API. In an iPlanetApplication Server application, the API consists of the iPlanet Application Server Foundation Class Library. Computer programs can use this API to communicate with iPlanetApplication Server.

application server. A program that runs an application in a client/server environment, executing the logic that makes up the application and acting as middleware between a browser (client) and a data source (server).

AppLogic object. A special Java class responsible for completing a well-defined, modular task within a iPlanet Application Server application. Use AppLogics to perform actions such as handling form input, accessing data, or generating data used to populate HTML templates.

banded report. See grouped report.

base class. See also superclass. A class from which another class is derived.

base session resource. The class defined to handle the iPlanet Application Server application session variables.

binary large object (BLOB). A large block of bits that can be stored in a database. A BLOB is useful for storing any large piece of data, such as pictures or sounds, that does not need to be interpreted by the database.

BLOB. See binary large object (BLOB).

browser. See web browser.

browser events. Actions that occur on the browser page, such as passing the cursor over a particular component, that can trigger actions specified by JavaScript objects on the page.

build project. Compile all source files in the project that have been edited since the last time they were compiled.

business logic. The implementation rules determined by an application's requirements and processed by AppLogics on the iPlanet Application Server.

cache. See result cache.

cell tag. A type of GX markup tag that displays a dynamic data value.

child query. A flat query that represents an inner level of data in a hierarchical query. Each child query is nested relative to another flat query, which is its parent query. Every flat query in a hierarchical query is a child query, except the outermost.

class. A named set of methods and member variables that define the characteristics of a particular type of object. The class defines what types of data and behavior are possible for this type of object.

clean project. Remove all object files from the project, leaving only source.

client. A computer or application that contacts and obtains data from a server on another computer. A client program is designed to work with one specific type of server.

column. A field in a database row.

compile. To translate source code written by a programmer into object code that can run on a computer. A compiler is a program that performs this translation.

component. Reusable objects that you can place on a page or template to perform a certain task. For example, an ImageLink component uses a GIF or JPG image as an anchor for an HTML hypertext link. The behavior and appearance of components are determined by their properties.

Component Object Model (COM). A specification that provides a standard way for objects and their clients to interact. COM specifies only how objects interact, not how applications are structured internally or how they are implemented.

computed field. A field in a query that displays the result of an expression rather than stored data. The database engine recalculates the value each time it runs the query.

connection. A database connection is a communication link with a database or other data source. AppLogics can create and manipulate several database connections simultaneously to access data.

connection validation. Guarantees that an IDataConn can be built for a set of named connections listed for an AppLogic.

constructor. A method that instantiates a class.

cookie. A variable that your application can send to a web browser to be stored there for a specified length of time. Each time a web browser views an HTML page in your application, the cookies from that browser are sent to the application. Cookies are domain-specific and can take advantage of the same web server security features as other data interchange between your application and the server. Thus, cookies are useful for privately exchanging data between your application and the web browser.

custom property editor. A dialog box that helps you determine the correct value for a complex property definition.

database forms wizard. A wizard that produces an HTML page with a data input form, a data model to establish database table relationships, a query based on the data model, an AppLogic to process the query, an HTML template to display the results of the query, and an optional search form to enable user-initiated database queries.

data-bound properties. Properties that enable components to be bound to a data set in an AppLogic.

data connection. A logical connection between an application and a relational database.

data expression. An expression containing one or more columns of data, which consist of a data set and a data field, with an optional display format.

data field. One column of data in a data set.

data model. An entity relationship (ER) diagram that specifies the data source tables and relationships used in your application.

data set. A user-populated data source for the iPlanet Application Server template engine.

data source. A collection of data electronically stored within a relational database, legacy system, or object database.

default. A value that is automatically assigned by the application when the user or programmer does not specify a value.

DELETE query. A statement that specifies which data to delete from a database.

deploy. Create a copy of all the files in a project on one or more servers, in such a way that one or more iPlanet Application Servers and (optionally) one or more web servers can run the application.

design-time. The behavior (in the test server) or appearance (in the iPlanet Application Builder windows) of an object when the application is being developed.

detail record. The result of a secondary query, based on a master record.

display format. See format mask.

distributed computing. A collection of computers linked together. Such systems can exist on a local area network (LAN), a wide area network (WAN), or the Internet. Distributed systems make several types of advanced computing systems possible, including client/server, multi-tier, and partitioned applications.

DLM. See dynamically loadable module (DLM).

dockable window. A window, such as the Project or Properties window, that has the ability to "snap into place" against the workspace border. When a window is attached in this way, it cannot be overlapped by other windows.

download project. Copying application files from a server back to a development machine. Note that this does not re-create the development environment if the files were filtered during development.

drag and drop. Clicking an object, holding the mouse button down while moving the cursor and the object to a destination (dragging), and then releasing the button to insert the object at the destination (dropping).

dynamically loadable module (DLM). A binary executable file that can be loaded while an application is running. In Windows NT or Win95 systems, DLM is another name for a Dynamic-Link Library (DLL). In UNIX systems, DLMs are implemented as ELF shared libraries.

Editor Beans. Java objects which generate and maintain components.

enable (AppLogic). Enable the application server to run registered AppLogics.

ER diagram. Describes the attributes of database entities and the relationships among them.

event. Named actions that you register with the iPlanetApplication Server. The event occurs either when a timer expires or when the event is called from application code at run time. Typical uses for events include periodic backups, reconciling accounts at the end of the business day, or sending alert messages.

event handler. JavaScript object on an HTML page or template that handles a browser event at run time.

execute server. Part of the iPlanetiPlanet Application Server that handles executive functions such as load balancing and process management.

field. The smallest identifiable part of a table in a database. A field is the intersection of a row and a column.

Also, a unit of data in a result set. Each field in a result set has a name, which corresponds to either a database column or an expression. Each field contains a single data value.

filtering. Removing development-oriented information from files while deploying.

flat query. A query that produces a result set that is not divided into levels or groups. The result set of a flat query is like a table.

floating toolbar. The state of a toolbar when it appears unattached in the center of the workspace, as opposed to being docked along the workspace borders. Floating toolbars have title bars to identify them.

format mask. A mask applied to data to specifically tailor its format for display. Options include numeric formats (integer, percentage), and custom date formats. Also known as display format.

generated code. JavaScript code generated by Editor Beans which should not be edited.

globally unique identifier (GUID). A unique number that identifies an AppLogic object and is used to request that iPlanetApplication Server runs that AppLogic object.

group. A set of rows in a result set that have one or more field values in common.

grouped report. A report that shows records in logical groups, such as sales grouped by geographic region, and can show summary data for each group.

GUID . See globally unique identifier (GUID).

GX markup tag. A special type of syntax used in templates to indicate where dynamic data is to be merged with the template. A GX tag is made up of two tags, <GX ...> and </GX>, and the text between them. Some GX tags are represented with % rather than < or >, as in %GX TYPE="cell" ...% %/GX%. This is equivalent to <GX TYPE="cell" ...> </GX> at run time.

.gxm file. A file that keeps track of all files belonging to a project. Also called a project file.

GXML template. A definition for a dynamically generated set of output data. Data retrieved from a database or other data source at run time is sent back to the client in a self-describing stream of output.

.gxr file. A file containing information that allows .java files and other files in a project to be registered with the iPlanet Application Server. Also called a registration.

handle. The verticle strip on the left side of a toolbar by which you can drag the toolbar.

hierarchical query. A query that combines several flat queries to construct a result set with multiple nested levels of data.

HTML. See Hypertext Markup Language (HTML).

HTML page. A page coded in HTML and intended for display in a web browser. Many HTML pages are view-only images and text, but HTML pages can also form the interface of a web application. A user can type data in an HTML page, then click a button on the page to submit the data. The web application manipulates the data and sends a response to the user on another HTML page.

HTML template. A definition for a dynamically generated HTML page. AppLogic uses HTML templates to present dynamic data. Data retrieved from a database, or otherwise generated dynamically, is merged with the template to create a database report or other type of HTML page, which is displayed to the user. Contrast with HTML page.

HTTP . See Hypertext Transport Protocol (HTTP).

hyperlink. A word or phrase that the user can click to display another page in an online document.

Hypertext Markup Language (HTML). The coding language used to create documents that can be displayed by web browsers. Each block of text is surrounded by codes that indicate the nature of the text, such as heading, body paragraph, or list item. Additional codes are used to create hyperlinks and call applets or AppLogic objects. HTML codes are surrounded by angle brackets < >.

Hypertext Transport Protocol (HTTP). The protocol for communicating hypertext documents across the Internet and the World Wide Web. HTTP provides a structure for communication between HTTP clients and HTTP servers.

image URL. Source code for an image. The URL can be relative (local server) or absolute (local or remote server). The URL can be determined dynamically if the component that requires it is in a template.

include tag. A type of GX markup tag that displays HTML output created by evaluating another template.

inheritance. A mechanism in which a subclass automatically includes the method and variable definitions of its superclass. A programmer can change or add to the inherited characteristics of a subclass without affecting the superclass.

input validation. The set of rules which defines a valIn.

input wizard. A wizard that produces a static HTML page containing an input form, an AppLogic to process the form, an HTML template to display the results, and optionally a query to retrieve data from a data source.

INSERT query. A statement that specifies which data to add to a database.

instance. An object that is based on a particular class. Each instance of the class is a distinct object, with its own variable values and state. However, all instances of a class share the variable and method definitions specified in that class.

instantiation. The process of allocating an object to memory at run time.

interface. Description of the services provided by an object. An interface defines a set of functions, called methods, and includes no implementation code. An interface, like a class, defines the characteristics of a particular type of object. However, unlike a class, an interface is always abstract. A class can be instantiated to form an object, but an interface can not be instantiated.

JavaScript. A language that can run as a script in an HTML page, allowing screen actions outside the scope of HTML, including responses to browser events.

Java server. Part of the iPlanet Application Server that runs and manages Java objects.

layout view. An HTML editor window display that shows the HTML page similarly to how it appears in a browser at runtime.

link URL. A target for a hypertext link. These include static pages, AppLogics, and other web sites. The URL can be relative (local server) or absolute (local or remote server). The URL can be determined dynamically if the component that requires it is in a template.

listing. See tabular report.

load balancing. A technique for distributing the user load evenly among identical AppLogic objects distributed across several computers running iPlanetApplication Server.

login wizard. A wizard that produces a static HTML page containing a login form, an AppLogic to verify a user name and password, and an HTML template to display the results of a successful login.

master record. The primary target of a query.

member. A variable or method declared in a class.

member variable. A variable with the following characteristics:

The variable is declared inside a class declaration.

A member variable specifies a piece of data that can be stored by an object instantiated from that class.

method. A function with the following characteristics:

The method is declared inside a class or interface.

A method specifies an action that can be performed by an object instantiated from that class.

metadata. Represents information that is passed into the run time's BaseResource constructor.

iPlanet Application Server Foundation Class Library. A set of interfaces and classes provided by iPlanet that can be used to develop object-oriented iPlanetApplication Server applications. The classes in the iPlanet Application Server Foundation Class Library define many types of objects you can include in iPlanetApplication Server applications, such as AppLogic objects, data connections, queries, and result sets.

object. A programmed entity with the following characteristics:

An object embodies both data and behavior.

Objects come into existence at run time through the process of instantiation.

Each object is based on a definition, which is called a class.

Many parts of an iPlanetApplication Server application, such as AppLogic objects, queries, and result sets, are objects.

object-oriented programming. A method for writing programs using classes, not algorithms, as the fundamental building blocks. At run time, the classes give rise to objects, which perform the tasks of the application.

ODBC. Open Database Connectivity (ODBC)

online application server. A server that stores, manages, and executes dynamic Internet and intranet applications. An online application server is specifically designed to run such applications quickly and efficiently. iPlanetApplication Server is an online application server.

Open Database Connectivity (ODBC). A standard protocol used by many database vendors to provide an interface to outside applications. iPlanetApplication Server applications can interact with databases that comply with ODBC 1.0 and 2.0.

outline view. An HTML editor window display that shows the structural relationships between HTML tags on the page.

override. To write new code that replaces the default code of an inherited method.

palette. A window containing components that you can drag and drop into HTML files to create pages and templates.

palette tabs. Individual sections of the palette that contain similar elements.

parameter. The data passed between methods, AppLogic objects, and other program code.

A placeholder for dynamic data that is passed into a prepared database command at run time.

parent query. A flat query that represents an outer level of data in a hierarchical query. Each parent query is nested outside another flat query, which is its child query. Every flat query in a hierarchical query is a parent query, except the innermost.

prepared command. A database command (INSERT, UPDATE, DELETE, or query) that is precompiled to make repeated execution more efficient. Prepared commands can contain parameters.

presentation logic. The process of generating output for an iPlanet Application Server application.

project. A collection of related files that, when deployed, constitute a web application.

project file. See .gxm file.

project map. A window that displays file dependencies. A project map is useful for visually representing the page flow of an application.

project window. A directory listing of files in a project. Files can be grouped by folder or listed alphabetically.

properties window. A window showing the properties for a selected object.

property. Name-value pairs that indicate how an object behaves or appears. For example, a Name property might contain a name that identifies the object to other objects, while a Background Color property defines a background color for the object.

property definition. Value associated with a given property that, together with the other properties for a given object, determines the object's appearance and/or behavior.

query. A statement that specifies which data to retrieve from a database. Typically, the results of a query are displayed in a report.

query file. A query file is a file that contains the specification for a flat or hierarchical query. Query files are useful for running legacy SQL SELECT statements. You can also use query files to write new queries.

rebuild project. Remove all object files (clean project) and compile all source files in the project.

register (AppLogic). Register the Java methods that make up an AppLogic with the Java Virtual Machine running on the application server.

registered servers. Servers registered to iPlanet Application Builder for the purpose of deployment. You can not deploy to a server until it is registered.

registration. The process of informing iPlanetApplication Server of the existence of an AppLogic object, code module, or security information.

registry file. See .gxr file.

relationship. A named connection between data source tables.

replace tag. A type of GX markup tag that substitutes a dynamic data value for a specified string.

report. A formatted presentation of data. In an iPlanetApplication Server application, a report is an HTML page presented to the user in response to a request for information. AppLogic objects create reports by combining hierarchical result sets and HTML templates.

request. A message from a client to a server, asking for data or another service.

In an iPlanetApplication Server application, a request is a message that causes an AppLogic object to run on the iPlanetApplication Server. A request uses a unique name or globally unique identifier (GUID) to identify the proper AppLogic object to handle the request. The request can include parameters to be passed to the AppLogic object. Requests can come from clients, AppLogic objects, or other code.

result cache. Storage in iPlanetApplication Server that holds the output from an AppLogic object so that the output can be accessed repeatedly without the necessity of running the AppLogic object again.

results wizard. A wizard that produces an AppLogic to retrieve data, optionally accessing a query to retrieve data from a data source, and an HTML template to display the results.

result set. A set of data records returned by a query. A record is a set of fields. Each field in the record has a name, which corresponds to either a database column or an expression, and each field contains a single data value.

row. A record in a database table. Each row is made up of several columns.

runtime. The behavior (in the server) or appearance (in a browser) of an object when the application runs.

select distinct (query). A query type that retrieves only the unique instances of the requested target search items.

SELECT query. A statement that specifies which data to retrieve from a database, as specified by your data model.

sequence. A sequential number generator which exists in a database. Some database vendors refer to a sequence as a serial, identity, or autoincrement. A sequence is useful for generating transaction-safe numbers for database transaction applications.

server. A computer or software package that provides a specific kind of service to client software running on other computers. A server is designed to communicate with a specific type of client software.

session. A continuous series of interactions between a user and an iPlanet Application Server application.

session accessors. Any method that starts with set and takes a String or starts with "get".

session validation. The set of rules that guarantees that the application is in a valid state to perform the functionality of a specific AppLogic.

session variables. Used by many AppLogics in an application to store and access data that is shared throughout the application.

source view. An HTML editor window display that shows the source code for the page.

SQL . See Structured Query Language (SQL).

standard query. A query that produces a result set that is not divided into levels or groups. The result set of a standard query is like a table.

state. A distributed data storage mechanism which you can use to store the state of an application. The application state is a collection of application variables whose scope is global within the application. Information in the state layer can be organized in a hierarchical structure, or tree.

stored procedure. A block of statements written in SQL or programmatic SQL and stored in a database. You can use stored procedures to perform any type of database operation, such as modifying, inserting, or deleting records. The use of stored procedures improves database performance by reducing the amount of information that is sent over a network.

streaming. A technique for managing how data is communicated via HTTP. When results are streamed, the first portion of the data is available for use immediately. When results are not streamed, the whole result must be received before any part of it can be used. Streaming provides a way to allow large amounts of data to be returned in a more useful way, increasing the perceived performance of the application.

Structured Query Language (SQL). A language commonly used in relational database applications. In an iPlanetApplication Server application, you can specify SQL SELECT, INSERT, UPDATE, and DELETE commands.

subclass. A class that is derived from and is a special case of another class, called a base class or superclass.

superclass. A class from which another class, called a subclass, is derived. See also base class.

system administrator. The person who is responsible for installing and maintaining iPlanetApplication Server software and for deploying production iPlanetApplication Server applications.

table. A named group of related data in rows and columns in a database.

tabular report. A report, sometimes called a listing, that prints all the records retrieved from the database.

tag. See GX markup tag or HTML.

target window. Name of the window or frame that displays the results of a hypertext link.

template. See GXML template or HTML template.

template engine. The part of the server responsible for taking HTML template files and merging them with the data from an AppLogic.

template map. An object that maps fields in a template to the data used to replace those fields. With a template map, you can assign values to special placeholders that will be evaluated at run time. You can also use a template map to link column names in a table to field names that you have used in a template. A template map allows your application to use the same template file with data from different data sources.

test server. A version of the iPlanet Application Server that runs in debugging mode for local testing purposes.

tile tag. A type of GX markup tag which repeats the tags and text nested within it. Tile can be used in two ways: repeating a fixed number of times, or repeating for each row in a result set.

tooltip. A word or phrase that appears whenever you briefly place the mouse over a toolbar button. Tool tips are useful reminders of a button's purpose.

transaction. A set of database commands that succeed or fail as a group. All the commands involved must succeed for the entire transaction to be correct.

trigger. A trigger is a stored block of SQL or PL/SQL statements that is associated with a table, runs in response to an INSERT, UPDATE, or DELETE operation, and runs only under certain specified conditions.

Uniform Resource Locator (URL). An address that uniquely identifies an HTML page or other resource. web browsers use URLs to specify which pages to display.

update query. A statement that specifies which data to modify within a database.

URL. See Uniform Resource Locator (URL).

user. A person who runs a computer application.

user validation. Validation written by the user.

validation. A method for ensuring that the contents of a form field are within certain parameters. If a user enters data outside the parameters, a dialog box appears notifying them of the error and what to do to correct it.

valIn. An argument to an AppLogic.

valOut. The return values from internal AppLogic calls.

variable. A named storage location for data that can be modified while a program is running. Each variable has a unique name that identifies it within its scope. Each variable can contain a certain type of data.

Web. See World Wide Web.

web application. A computer program that uses the World Wide Web for connectivity and user interface. A user connects to and runs a web application by using a web browser on any platform. The user interface of the application is the HTML pages displayed by the browser. The application itself runs on a server, connected to the browser through the World Wide Web.

web browser. Software that is used to view resources on the World Wide Web, such as web pages coded in HTML.

web page. See HTML page.

web server. A computer that stores and manages HTML pages and web applications. The web server responds to user requests from web browsers.

wizard. A code generator that provides a framework for creating the most commonly-used types of application development components.

World Wide Web. A network of many computers linked together by their ability to understand the HyperText Transfer Protocol (HTTP). Two types of computers make up the Web: clients and servers. Clients are computers with web browsers installed on them. Servers are computers that store and manage the information requested by the clients.

workspace. The main window of iPlanet Application Builder. The workspace contains the windows, toolbars, and dialog boxes that constitute the user interface.


Previous     Contents     Index     DocHome     Next     
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.

Last Updated April 26, 2000