Create a database called TemplateRegistry.nsf using TemplateRegistry.ntf as the master design.
For the Template Registry the suggested default ACL is:
Default for author but with create documents
Note: There are no approver or path builder groups in this ACL. This is because only administrators and promoters need access to the functionality. If Build Manager path builders need the ability to promote databases, then these groups should be added with the same rights as the promoters.
Setting up the default Registry
Open the Template Registry database. In the Admin tab, expand ‘Configuration’ and click on Registry Settings.
For basic set up and initial testing fill in the following fields:
General tab: leave the * to indicate any Build Manager can currently access this Template Registry.
Default Target Environment tab: Enter an Environment name and a description. This will be the default Environment for promotions to the Template Registry. For instance, this can be a catch all for any development. So name it ‘Developed – Ready for Test and add a description if required.
In the Advanced options, leave the * to allow any Build Manager to promote from here, (leave the box unchecked).
Target Environments tab: Save and reopen this document and the Default Environment will be listed
Once other logical environments can be created from here, for example; ‘QA Approved’, ‘UAT Complete’, etc. They will all be listed here. See ‘Creating Additional Repository Environments’ below.
Approvals tab: This is only to be completed if approvals are required to update the versioned templates in the repository to the next stage. For both the Workflow Definition Database and the Workflow Instance/Log Database, browse to the workflow.nsf database copied earlier.
For the Workflow category select ‘Template Registry’.
Save and close the document.
Note: Currently approvals have usually been required to put DB’s on the server. This is performed in the BM db not here.
Creating Additional Repository Environments
From the Admin tab click on ‘Environments’ (or if currently setting up the Default Environment, go to the Target Environments tab) and click ‘Create Environment’ from the toolbar.
Fill in the basic details.
The security settings ‘Allow templates to be approved on Build’ should be checked as default. Ignore the ‘Require Template Profile’. The ‘Build Manager Promotion access’ field allows restrictions as to which instance of BM can pull templates from this registry environment.
In the Approvals tab only check the box if movements in the TR are required to be authorized.
Save and close.