Templates
Templates are a key part of deploying and managing Nectari installations. Use templates to migrate data models, prompt lists, global parameters, and more between Central Points, or to perform system backups before making significant changes.
With Nectari, administrators can export templates to a file for backup, transfer, or reinstallation. These files can be imported into another Nectari system or reimported to restore a system to a previous state.
For a detailed installation workflow, see Templates.
| Option | Description |
|---|---|
| Import a template | Import a template file to add new objects or update existing ones in your current environment. Use this for updates, migrations, or rapid deployment. |
| Manage a template | Review all templates installed in your environment and to see the status of executed scripts, resolve errors, or remove templates that are no longer needed. |
| Export a template | Export Nectari objects—including data models, views, prompts, and global parameters—to a ZIP file, so they can be imported into any Nectari installation for migration or backup. |
Import a template
You must configure the required data sources before installing templates.
- From the navigation panel, click the gear icon at the bottom. The Administration page opens.
- Select Templates, then Import Template.
- Click Select files and browse to upload your installation template
.zipfile. - Map the data source from the imported template to existing data source using the dropdown list.
- (Optional) Click Env. & Data Sources to create any missing data sources on the fly.
- Click Next.
- In the Import Template window, review all objects included in the template. For each object, select Add, Update, or Skip.
- Use the Objects tabs on the left to review Data Models, Folders, Dashboards, and other items before confirming import options.
- Click Next to complete the import.
Import template columns
| Column | Description |
|---|---|
| ID in Central Point | Unique ID of the object in the target system. |
| Description in Central Point | Description of the object as it exists in the target system. |
| Current Version in Central Point | Version currently installed in the target system. |
| Installed Version in Central Point | The status of the object in the system (never installed, version number, etc.). |
| ID in Template | Unique ID of the object in the template file. |
| Description in Template | Description of the object from the template file. |
| Version in Template | Version of the object in the template file. |
| Add | Select to create a new copy of the object in the current environment. |
| Update | Select to update/upgrade an existing object with the version from the template. Use if the template version is newer. |
| Skip | Select to leave the current object unchanged. |
Objects tab
Each tab displays objects included in the template and matches them with existing objects in the Central Point.
| Tab | Description |
|---|---|
| Data Models | Lists data models in the template. Compare their version and status with current models. Optionally expand a model to see included views, and choose Add, Update, or Skip for each. |
| Folders | Displays folders in the template and matches them with existing folders. Folders can be renamed if desired. |
| Dashboards | Lists dashboards in the template and matches with existing dashboards. Add new ones or update existing matches. |
| Reports | Lists reports included in the template, matching them with existing reports if possible. Add is only available for new objects. |
| Workbooks | Shows imported workbooks and matches them with those in the system, as above. |
| Global Selection Pages | Lists imported Global Selection Pages, with matching to existing pages. |
| Global Variables | Shows imported global variables, with matching if possible. |
| Applinks | Displays imported application links and matches them with existing links. |
| Global Parameters | Lists imported global parameters and matches them to those in the system. |
| Mapping Language Dictionaries | Displays imported language dictionaries, matching to existing ones. |
| Global Scripts | Lists imported global scripts and matches them with what’s in the Central Point. |
| Cubes | Shows imported OLAP cubes and matches them to system cubes. |
Manage a template
Review executed scripts
- From the navigation panel, click the gear icon at the bottom. The Administration page opens.
- Select Templates, then Manage Template.
- Click Manage All Executed Scripts to review all the scripts that have been executed as part of template installation or update.
- Select an environment from the dropdown list to view executed scripts in that context.
- For each script, review its execution status:
- If you see a check mark, the script ran successfully. Click the script’s name to view its details and revert options.
- If you see a prohibited icon, the script failed. Click the script’s name to display the script, the error message, and information to help you resolve the problem (such as alerts about missing permissions or references).
- Use this view to troubleshoot installation issues, update scripts as needed, or coordinate with database administrators when errors occur.
Remove a template
- In the Manage Template window, select one or more templates you want to delete.
- Click Uninstall.
Export a template
- From the navigation panel, click the gear icon at the bottom. The Administration page opens.
- Select Templates, then Export Template.
- In the Objects tab, select the objects you want to include in your template (such as Data Models, Reports, Dashboards, etc.).
- Use Select All to select every available object in the list at once.
- By default, when you select a data model, all related objects (e.g., prompts, variables, dependencies) are also selected automatically.
- (Optional) Click the View dependencies icon next to an an object to view all related or dependent objects that will be included in the export.
- At the bottom of the window, enter a template name, ID, and description.
- Click Export to generate and download the installation template file.
Always include related dependencies if you plan to import this template into a different Central Point or environment.