Creating a Configuration Template JSON file - Adaptive Applications - BlueCat Gateway - 25.2

Configuration templates let you manage BlueCat Address Manager (BAM) service configurations for multiple managed servers. A template consists of a JSON file that specifies configuration and preference settings for a DNS/DHCP server.

The easiest way to create a Configuration Template that will be shared by several BlueCat DNS/DHCP Servers (BDDSes) is to set the desired configurations in BAM, target and retrieve the existing configuration as JSON settings, then create a JSON file with those settings and import it into BSUS. To do so:

1. In BAM, configure a BDDS with the desired settings (such as the Firewall, NTP, and SNMP).

2. In BSUS, target that BDDS and retrieve its existing service configuration (its configuration settings in JSON code).

   To do so:

   • In BSUS, click the Dashboard tab in the BSUS header, then click the Name of the Server Batch to which the desired BDDS belongs.

   • Within the server list, in the Configuration Status column for the desired BDDS, click the download button ().

     Save this service configuration as a new JSON file (*.json).

3. In a text editor, modify this new service configuration JSON file to be suitable as a Configuration Template:

   • Remove any configuration items that you don't want to sync between BDDSes.

   • Remove any instances of the following configuration items, which are not supported in the current version of BSUS (BSUS 25.2).

     • interfaces

     • dnsStatistics

     • anycast

     • edgeServicePoint

     • dnsResolver

     • dnsActivity

     • dhcpStatistics

     • gateway

   • Make sure that the defined schema version at the top of the file is either 1.0.0 or 1.1.0:

     {
       "version": "1.0.0",
       (other settings)
     }

     Note: BSUS v24.1 supports only versions 1.0.0 and 1.1.0 of the service configuration JSON schema.

4. In BSUS, add the template as a new Configuration Template.

   For more details, see Adding a Configuration Template to BSUS.

5. Use the new Configuration Template within BSUS as needed. (Typically, you will assign it to batches, then to each BDDS within a batch.)