15 docs tagged with "Data Engineer"

Qrvey Admin Center is a web-based application that is installed with every instance of the Qrvey platform. You must have an account with the Administrator role to access Qrvey Admin.

Content Deployment enables you to copy the contents of a source Qrvey application, then pass it into a new target application.

Content Deployment enables you to copy the contents of a source Qrvey application, then pass it into a new target application.

The Customization page of Qrvey Admin Center provides administrators with a variety of options for customizing their instance of Qrvey Composer.

A Deployment Definition is a set of instructions for a deployment job. It defines the package version to use, which content from the package to include, and whether any of the content has to be modified during deployment. You can configure the deployment definition to create a new application or to update an existing application.

A Deployment Job executes the type of deployment specified by one or more deployment definitions against one or more target servers. Deployment jobs consist of “blocks” of instructions, with each block configuring the deployment of one deployment definition to any number of users on one destination server. That means that you can have one Deployment Job deploy multiple applications to as many users as necessary, on multiple environments. Deployment jobs require at least one block.

Qrvey Admin Center is a web-based application used by administrators to manage and monitor the Qrvey platform. It is installed with every instance of the Qrvey platform along with Qrvey Composer. For more information on its capabilities, see the following sections:

The Qrvey Admin Center enables you to create and manage user accounts in Qrvey Composer, assign roles and permissions, and set up authentication methods.

The first step with any self-service embedded analytics implementation is to design, develop and then populate the datasets that will become the sources for all charts, metrics and visualizations created in the platform. SaaS organizations building datasets for multi-tenant deployments of embedded analytics must think about the following topics with respect to the data architecture:

Qrvey’s approach to multi-tenant security architecture is to utilize the assert model for both authentication and authorization. The assert model effectively allows you to maintain your existing user accounts, roles/groups and permissions, and then declare a user’s identity and permissions to the Qrvey platform dynamically at runtime. The ability to assert/declare a user’s identity and access permissions is favorable when embedding third party platforms in your core application for a multi-tenancy deployment, because it means that you will not need to redefine and replicate your existing security schema.

In Qrvey, Content Deployment refers to the process of copying content from one application to another, in the same environment or to a different one. Content Deployment is a powerful tool for managing all of the content generated (including Connections, Datasets, Web Forms, Charts, Pixel-Perfect Reports, and Flows) in a multi-tenant deployment.

SaaS organizations that want to embed self-service analytics within their core applications to support a multi-tenant deployment should think about the following considerations:

Solution Architects use the Qrvey Admin Center to manage the infrastructure, users, and content, as well as configure Qrvey Composer. The primary technical resource for the Solution Architect is the Qrvey Admin Center User Guide.

A package enables you to create a snapshot of a selected application with all of its content and dependencies. Each snapshot is called a “version”. You can use the same package to create subsequent versions. This enables you to create different versions of this snapshot over time, as the source application changes.

Each instance of the Qrvey platform is considered a “server”. A server includes Qrvey Composer, Qrvey Admin Center, the ElasticSearch cluster, the users of the instance, and all content and related metadata.