Terminology
From LongJump Support Wiki
This page provides short descriptions of terms, suitable for inclusion in a "rollover" help display. For more detailed descriptions, see the Glossary. For pages that show relationships among terms, see the Ontology.
Usage Notes:
- Terms are displayed with subtle, green, dashed underline.
- Text appears when the cursor hovers over the term.
- Highlighted terms look great and work well, in plain text, [tt] text, or [pre] text.
- Case is significant. So "Tenant" is not found if the term is "tenant".
- For overlapping terms, order is significant. To highlight "system object", it must appear before object in the definition list. Otherwise, object is highlighted, and the larger term is not seen.
- Even when the order is right, the definition you see depends on where you put the cursor. Over the first half of "system object", you get the definition for the whole term. Over the last half, you get the definition for "object". (Livable)
- Plurals are recognized! So when "object" is defined, "objects" is highlighted.
- But if a plural like tenants is defined, that definition is used, even if it occurs later in the definition list. (nice!)
- Blank lines in the file cause a non-fatal error in the processing page (terminology.php). No harm is done, but it may slow things a bit. (Resolved by eliminating blank lines in this file.)
- ACID
- Atomicity, Consistency, Isolation, Durability. A set of properties that define reliable transactions.
- built-in object
- An object that is part of the platform from the moment it is installed.
- custom object
- An object created by an application or a user.
- CRM object
- An object that is part of the standard CRM application available on the platform. These objects are created when the application is installed.
- system object
- An older term used to cover two kinds of pre-defined objects: CRM Objects and Built-in Objects.
- CRUD
- Standard data operations Create, Read, Update, Delete.
- DDL
- Data Definition Language. Database statements that define tables and fields.
- DML
- Data Management Language. Database statements that move, copy, and access data.
- domain
- Service Domain (platform hostname or IP address),
- fieldName
- The name of a field in an object (column name)
- host tenant
- The organization that hosts the platform. The hosting organization is itself a tenant of the platform, and uses that tenancy to administer the platform for other tenants.
- httpd
- Apache HTTP Daemon. A server that handles http requests.
- http
- HyperText Transport Protocol. The foundation of the world wide web.
- https
- An http connection made over a secure SSL connection.
- ISV
- Independent Software Vendor. Someone who builds an package that runs on the platform, for delivery to an MSP, or for providing directly to tenants.
- JVM
- Java Virtual Machine.
- lookup-dependent field
- A field containing identifying information that is populated when a selection is made in a lookup field.
- Lookup-dependent field
- A field containing identifying information that is populated when a selection is made in a lookup field.
- platform_url
- The HTTP address at which your platform is running.
- memcached
- MEMory CACHEing Daemon - a distributed caching service that stores frequently-accessed pages in memory, so they can be served as rapidly as possible.
- MIME
- Multipurpose Internet Mail Extensions. A set of standard designations for different types of data, both textual and binary.
- MSP
- Managed Service Provider. An entity that hosts one or more applications for delivery to tenants.
object
- The fundamental data component of an application. Corresponds to a row in a table, from the standpoint of an application developer. Corresponds to the table itself, to an administrator.
- objectID
- An Object Type identifier generated by the platform when an object is created.
- objectName
- An Object Type identifier specified by the person who created the object.
- Package Data
- Data that is part of an application package. Typically, it is object data, but it need not be.
- Package Installer
- Someone who installs a package, so that applications and other elements it contains are available to users in their organization's tenancy.
- packager
- Someone who creates an application package.
- Platform Installer
- A person responsible for installation, monitoring, system-level maintenance, and/or tuning of the platform.
- platform instance
- An standalone copy of the platform's installable version that is installed and running.
- Quartz
- Timekeeper process. Used by the internal Scheduler to kick off scheduled events.
- RAID
- Redundant Array of Independent Disks. A data storage mechanism that provides protection against disk failure.
- recordId
- A Record Identifier (row ID)
- REST
- REpresentational State Transfer. Defines CRUD operations over the web, using http get, put, post, and delete operations over http.
- SAN
- Storage Area Network. A means of attaching a remote disk to a server, as though it were a local device.
- SSL
- Secure Socket Layer. A protocol for encrypted transmissions over http.
- System Administrator
- Someone responsible for managing users, roles, applications, and other artifacts of an installed platform (a platform instance).
- tenant
- An organizational entity that operates in its own virtual space in the platform. Each tenant has its own database, and may have multiple users.
- Tenant
- An organizational entity that operates in its own virtual space in the platform. Each tenant has its own database, and may have multiple users.
- tenants
- Organizational entities that operate in their own virtual space in the platform. Each tenant has its own database, and may have multiple users.
- Tenants
- Organizational entities that operate in their own virtual space in the platform. Each tenant has its own database, and may have multiple users.
- viewID
- A View identifier