Skip to end of banner
Go to start of banner

Deploying a Self-Managed Snaplex

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

In this Article

Overview

A Self-managed Snaplex is a type of Snaplex that is hosted by the customer, not by SnapLogic. What this means is that you, as the SnapLogic user, define the resources for the nodes in the Snaplex. A customizable Snaplex enables you to configure your Snaplex to the specifications required by your IT infrastructure.

This type of Snaplex is also known as a Groundplex, which is a term used throughout this document to refer specifically to your self-managed Snaplex. Despite what the name implies, you can manage a Groundplex through a cloud service. The assumption behind the use case of a Groundplex is that customer IT environments require customization beyond what a SanpLogic Managed Snaplex offers. Groundplexes allow access to endpoints that are not accessible from outside the customer's network. This setup provides the ability to manage the resources and comply with the security requirements in your computing environment.

You must have Org admin access to enable this feature. Additionally, most administrative tasks generally require Org admin access. The exception is if you are a basic user provisioned as a Snap developer.

List of articles in this section

List of articles in this section

Audience

The audience for this series of Groundplex articles varies. At a large organization, the SnapLogic Org admin who manages Groundplex resources might be or work with a dev-ops engineer or network administrator.

However, the Groundplex can also serve a Pipeline developer’s needs when managing node resources is a requirement for testing Pipelines. In this case, the Pipeline developer is the creator of the Snaplex and controls the underlying node resources.

In this article, the term Org admin access does not distinguish between these roles and assumes that you have access to the underlying resources of your Groundplex nodes.

Key Features

Customization: You manage the resources for the Groundplex node. This enables you to customize both computing resources and network configurations to your specific requirements.

Security: You can install a Groundplex on an end user's local machine that provides access to data both on-premises, behind a firewall, and in the cloud.

Flexibility: You can install a Groundplex anywhere on the end user network that has access to the required data or on-premises application(s).

Efficiency: The advantage of using a Groundplex instead of a cloud Snaplex is that data that resides in the end user data center can be accessed through SnapLogic Pipelines. All Pipelines and associated metadata are stored in the cloud by SnapLogic. When a Pipeline needs to access data residing on-premise, the Pipeline can be run with a Snaplex on-premise runtime path.

Workflow

The following diagram illustrates the workflow for deploying a Groundplex.

Prerequisites

  • You must be an Org administrator to set up a Groundplex.

  • You must have sufficient computing resources to create Groundplex nodes. These resources can be in the cloud or in an on-premises installation or remote data center.

  • For a firewall, you need to have administrator access to your on-premises network.

Support

You can subscribe to Professional Services for assistance with installing and maintaining your Groundplex. To learn more, contact your CSM.

Related Content

  • No labels

Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.