Exporting a Content Switching Virtual Server Configuration to a Template File

You can also export a content switching configuration as an application template. You can export a content switching virtual server configuration to an application template either from the Content Switching Virtual Servers pane or from the Content Switching Visualizer. Configuration information, which includes the content switching virtual server, all associated load balancing virtual servers, services, service groups, and policies, is exported to a template file and all deployment-specific information is exported to a deployment file. The string “_deployment” is automatically appended to the name of the template file to create the name of the deployment file. Both files are in XML format. If you choose to export the application template file to the NetScaler appliance, the template file is stored in the /nsconfig/nstemplates/applications directory on the NetScaler appliance and the deployment file is stored in the /nsconfig/nstemplates/applications/deployment_files/ directory.

For more information about the format of application templates and deployment files, see Understanding NetScaler Application Templates and Deployment Files. The configuration information that is exported includes the content switching virtual server, all associated load balancing virtual servers, services, service groups, and policies.

However, if the content switching virtual server is already configured as the public endpoint for an AppExpert application, you cannot export the configuration to a template file . In this scenario, you must export the associated AppExpert application to a template.

For more information about exporting an AppExpert application to a template file, see Exporting an AppExpert Application to a Template File.

To export a content switching configuration to an application template file from the Content Switching Visualizer by using the GUI:

  1. Navigate to Traffic Management > Content Switching > Virtual Servers.
  2. In the details pane, click the name of the content switching virtual server whose configuration you want to export as a template file, and then click Visualizer.
  3. In the Content Switching Visualizer, click the icon for the content switching vserver, click Related Tasks, and then click Create Template.
  4. In the Export…as Template dialog box, enter a name for the template file, and then do one of the following:
    • To export the template file to the appliance, make sure that Browse (Appliance) is displayed.
    • To export the template file to your computer, click the Browse (Appliance) drop-down menu, click Local, browse to the location to which you want to save the file, and then click Save.
  5. Provide the following information:
    • Introduction Description—Any text that introduces the AppExpert application template during import. This text is displayed on the Specify Application Name page of the AppExpert Template Wizard when the template is imported.
    • Summary Description—Any summary that you might want to display on the Summary page of the AppExpert Template Wizard when the template is imported.
    • Author—The name of the author of the template.
    • Major—The major version number of the template.
    • Minor—The minor version number of the template. This number is appended to the major version number and displayed on the Summary page of the AppExpert Template Wizard, during import, in the format Major.Minor.
  6. Click OK.

To export a content switching configuration to an application template file from the Content Switching Virtual Servers pane by using the GUI:

  1. Navigate to Traffic Management > Content Switching > Virtual Servers.
  2. In the details pane, click the name of the content switching virtual server whose configuration you want to export as a template file, and then click Create AppExpert Template.
  3. Perform steps 4 through 6 described in To export a content switching configuration to an application template file from the Content Switching Visualizer procedure.

Exporting a Content Switching Virtual Server Configuration to a Template File

In this article