Importing and Publishing the New CRD Schema

This section describes how to import and publish the new CRD schema.

To import and publish the CRD schema, use the following configuration:

  1. Log in to the PCF Central GUI.

  2. On the Cisco Policy Suite Central page, navigate to Policy Builder and click the Import/Export link.

    The Import/Export form opens.

  3. In the Import tab, browse to the file that you want to import.

  4. In the Import URL field, enter the URL where the file must be imported. We recommend importing a new URL and verify it using the Policy Builder.

  5. In the Commit Message field, enter the appropriate information.

  6. To enforce import in situations where the checksums don't match, select the Force import even if checksums don't match check box.

  7. Click Import.

Importing the New CRD

To import the new CRD, use the following configuration:

  1. Access the Policy Builder URL and add a new repository.

    1. In the Choose Policy Builder data reposiorty... window, select <Add New Repository> from the drop-down.

      The Repository dialog box appears.

      The following parameters can be configured under Repository:

      Configure the parameters according to the network requirements.

      Repository Parameters

      Parameter

      Description

      Name

      This is a mandatory field. Ensure that you specify a unique value to identify your repository's site.

      Note

      We recommend the following format for naming the repositories: customername_project_date, where underscores are used to separate customer name, project, and date. Date can be entered in the MMDDYYYY format.

      Username and Password

      Enter a username that is configured to view the Policy Builder data. The password can be saved for faster access, but it is less secure. A password, used with the Username, permits, or denies access to make changes to the repository.

      Save Password

      Select this check box to save the password on the local hard drive. This password is encrypted and saved as a cookie on the server.

      Url

      You can have several branches in the version control software to save different versions of configuration data. Create a branch in the version control software before assigning the URL in this screen.

      Enter the URL of the branch of the version control software server that is used to check in this version of the data.

      Local Directory

      Do not modify the value in this field.

      This is the location on the hard drive where the Policy Builder configuration objects are stored in the version control.

      When you click either Publish or Save to Repository, the data is saved from this directory to the version control application specified in the Url text field.

      The field supports the following characters:

      • Uppercase: A to Z

      • Lowercase: a to z

      • Digits: 1–9

      • Nonalphanumeric: /

      Note

      The user must use only the supported characters.

      Validate on Close

      Select this check box to see if the values for Username, Password, or the URL are legitimate and unique. If not, the screen displays an error message and provides a chance to correct the errors.

      Remove

      Removes the display of the repository in Cisco Policy Builder.

      Note

      The remove link here does not delete any data at that URL. The local directory is deleted.

    2. Click OK to save your work to the local directory.

      Note

      When you change screens, the Policy Builder automatically saves your work. We recommend saving your work to the local directory by clicking on the diskette icon on the Policy Builder GUI or CTRL-S on the keyboard.

    3. If you are ready to commit these changes to the version control software, choose File > Save to Client Repository on the Policy Builder home screen.

  2. Log in to the new repository.

  3. Verify the new CRD table schema and publish the changes.

  4. Review the crd-api pod logs for any exception or error related to the duplicate key or duplicate index. If there are no errors, then the CRD is successfully imported.