Overview
Configuration Concepts explains how to configure Extole through components, and it is all most readers need. This page describes the parts of a component. Use it when you build components of your own or troubleshoot one in depth. This page gives the ideas and a few examples. It does not list every type or setting, because your account is the accurate source. See It in Your Account links the pages that show them. A component has these parts:
Types, settings, and operations are the component’s interface. Elements are its implementation.
Component Types
A component’s types say what it is. A type name ends in a version, such asbusiness-event-v10.0. These pages leave the version off when they name a type in prose.
A type can have a parent type, and the child is a kind of the parent. A setting that accepts the parent type accepts each type beneath it. For example:
Settings
Each setting has a name, a description, and a type. There are three kinds:
Sockets make the hierarchy of components inside components: a component, the components in its sockets, and the components in theirs.
Operations
An operation is an API call that a component offers, such as an event your servers send to it. Each operation has a name, a description, a path, a method, and the schema of its request and response. A component documents its own API in the same way it documents its settings.Elements
Elements carry out a component’s behavior at runtime. They include the business events a component records (itssteps), the triggers that decide whether an event qualifies, and the actions that run when it does.
A component manages its elements. Its settings supply the values the elements use, which is how a setting changes behavior without a change to an element.
Elements are also what an upgrade replaces. Upgrading Components explains what that means for a change you make to an element.
