CC user is a SnapLogic system user, such as cc+<org_name>@snaplogic.com, which is automatically created for use by Snaplexes Snaplex instances for registering with the SnapLogic control plane.
A Snaplex that runs inside the SnapLogic Cloud. A Cloudplex is managed by SnapLogic.
A Snaplex that runs behind a firewall, provides on-premises connectivity at a customer site, and is administered by the customer.
A tab in SnapLogic Dashboard that lets you monitor the health of Snaplexes your Snaplex instances and Pipelines.
The dialog of any Snap where you configure the Snap settings. Infoboxes typically have tabs for Settings, Views, Info, and Accounts associated with the concerned SnapInfo-boxes typically have tabs for , , , and associated with the concerned Snap.
A Snaplex node is one of the virtual machines or a set of computing resources that process data. In SnapLogic documentation, we qualify a node based on context. Snaplex node is the most generic reference, and often introduces contexts that involve the following distinctions:
- Groundplex/Cloudplex nodes: Grounplex Groundplex nodes are customer configured and maintained by a customer, whereas Cloudplex nodes are hosted by SnapLogic. When documentation content is specific to Groundplex users, references to Groundplex nodes indicate that the content is intended for Groundplex users. Likewise, references to Cloudplex nodes are intended for Cloudplex users.
- JCC/FeedMaster Nodenode: The distinction here is of type. A JCC node executes Pipelines, and a FeedMaster node is the queue broker for running Ultra Pipeline Tasks. When the distinction is relevant, both terms typically appear in the documentation.
A dataset whose datapoints data points represent mathematical values. For example, height, weight, age.
An administrative user defined for a company within the SnapLogic application. This user can create users and assign permissions within the organization, create Project spaces and may create projects. Organization Admin is also referred to as an Org admin.
Similar to the On-premises URL, the Override URL can trigger a task to execute on a Groundplex. The Override URL ignores the Task's configured Snaplex and instead executes on the Snaplex that receives the request.
An abstraction used to quantify the resource requirements/usage for a Pipeline. Each Snap in a Pipeline consumes a slot during execution and each slot is a running thread on a Snaplex node.
A tab in SnapLogic Dashboard that lets you view Snaplex statistics.
A SnapLogic reporting interface that provides information on Pipeline runs and SnaplexesSnaplex instances.
SnapLogic user interface where you can select Snaps from the available Snap Packs, build and manage Pipelines, and choose from Pipeline Patterns.