SLAX and XSLT Commit Script Tag Elements to Use When Generating Persistent and Transient Configuration Changes

Junos OS commit scripts enforce custom configuration rules and can automatically change the configuration when it does not comply with your custom configuration rules. Table 1 summarizes the tag elements that you can include in SLAX and XSLT commit scripts to generate persistent and transient changes. To see how data values are supplied within a script, see Example: Generate Persistent and Transient Configuration Changes Using Commit Scripts.

Table 1: Tags and Attributes for Creating Configuration Changes in SLAX and XSLT Commit Scripts
Data Item, XML Element, or Attribute	Description
Container Tags
`<change>`	Request that the Junos XML protocol server load configuration data into the candidate configuration.
`<transient-change>`	Request that the Junos XML protocol server load configuration data into the checkout configuration.
Content Tags
`<jcs:emit-change>`	This is a template in the file junos.xsl. This template converts the contents of the `<xsl:with-param>` element into a `<change>` request.
`<xsl:with-param name="content">`	You use the `content` parameter with the `jcs:emit-change` template. It allows you to include the content of the change, relative to `dot`.
`<xsl:with-param name="tag" select="'transient-change'"/>`	Convert the contents of the `content` parameter into a `<transient-change>` request. You use the `tag` parameter with the `jcs:emit-change` template. By default, the `jcs:emit-change` template converts the contents of the `content` parameter into a `<change>` (persistent change) request.