TIBCO

Glossary

  • Artifact - a managed entity, similar to a file within a file system. All artifacts are contained in a project.
  • Checkpoint - commit all project and artifact modifications in a sandbox to a source code management system.
  • Dependency - a relationship between projects that allows artifacts contained in other projects to be used by reference.
  • Deploy - run, or upgrade an already running, project, containing artifacts.
  • Deploy Context - a named context created by the deploy service when a project is deployed. A deploy context manages one or more execution contexts.
  • Deploy Service - schedules, allocates resources, and manages execution of a deploy context to deploy a project.
  • Historic Data - data that was previously captured from an action or process and stored in a durable storage mechanism, for example a file, or a database. Contrast with streaming data.
  • Model - a mathematical specification of an analytical process to transform a set of input tuples to a set of output tuples. Example specification languages are PMML, Python, TensorFlow, etc.
  • Notification - asynchronous messages containing details on significant actions triggered at design-time or during deployment.
  • Project - a versioned container for artifacts. Projects are the unit of deployment.
  • Publish - push a checkpoint in a sandbox to a space making the changes visible to all users with the required space permissions.
  • Sandbox - a per-user private workspace where all active work occurs. Modified projects and artifacts in a sandbox are only visible within the sandbox.
  • Schema - formal definition of the structure of a tuple, defining types, constraints, and cardinality.
  • Sealed - disallow the changing of configuration using overrides when a project is used as a dependency.
  • Space - a shared container for projects backed by a source code management system. All projects in a space are visible to all users that have the required permissions.
  • Streaming Data - data that is available immediately following an action or process, for example a Kafka message. Contrast with historic data.
  • Tuple - A set of named data values. The data values are stored in fields that are accessed by name. The fields in a tuple are defined by a schema.
  • Validate - verify that an artifact or project is correct and complete and is ready to deploy.