| CA Technologies |
1.0 IXUTIL Import/Export Utility
1.1 IXUTIL Files
1.2 Data File Types
1.3 IXUTIL Export Syntax
1.4 IXUTIL Import Syntax
1.5 Object Syntax
1.6 Object Syntax Rules and Considerations
1.7 IXUTIL Parameters
1.8 Object Modification
1.8.1 Object Modification Considerations
1.8.2 Date Last Modified Conditions
1.9 Export and Import All Objects
1.10 Preservation of Inheritance
1.11 Export and Import Events, Rules, and Actions
1.12 Export and Import Configurations
1.13 Export and Import Services
1.14 Export and Import Report Data
1.15 Export and Import Business Units
1.16 Import CA Workflow Forms into the Form Designer
1.17 Export and Import Form Designer Forms
1.18 Export and Import Form Designer Forms Associated to Service Option Elements
1.19 Export and Import Policies
IXUTIL is an importing and exporting command line utility that allows the preservation and migration of CA Service Catalog data between systems. For example, you can export offerings (services) from a CA Service Catalog Release 12.7 system and import them as services into a CA Service Catalog Release 12.8 system, using the same XML structure.
You can use IXUTIL to export and import new and updated objects from one CA Service Catalog instance to another CA Service Catalog instance. This migration is primarily intended for both of the following:
IXUTIL does not import or export images of offerings because of the variation of the image file path names on the source and target computers. If you want to retain such images, you must copy and paste them manually, after the initial migration is complete.
Note: Use the CA Workflow IDE, not IXUTIL, to export and import CA Workflow actors and process definitions between systems running the same release of CA Service Catalog; for details, see the CA Workflow IDE online help.
Important! CA Workflow is no longer being enhanced, and its maintenance and technical support are scheduled to be discontinued as of December 31, 2013. Therefore, we strongly recommend using CA Process Automation as your process automation tool.
For Windows, the import/export utility file (ixutil.bat) is located in the USM_HOME\scripts folder.
USM_HOME specifies the CA Service Catalog installation directory on this computer. For 32-bit computers, the default path name is C:\Program Files\CA\Service Catalog. For 64-bit computers, the default path name is C:\Program Files (x86)\CA\Service Catalog.
You can configure IXUTIL by using the ixutil.cfg properties file located in the USM_HOME\scripts folder. This file controls import and export rules, default export file format, error log file and so on. The ixutil.cfg file contains comments and details about each configurable parameter.
Log messages from IXUTIL appear in the USM_HOME\logs\install\ixutil.log file.
For most object types, IXUTIL exports the data in a proprietary XML format, and you must use the same XML format when importing. You can determine the correct XML formats for each object type by examining an exported XML file.
IXUTIL lets you import and export the following types of data:
Examples include Service Level Agreement information, CMDB CI Mapping, permissions, business hours, resource type, application metric, policies and actions, and translations.
The export syntax for using the ixutil.bat (Windows) command is as follows:
ixutil export object –f file –format xml object-specific parameters
Specifies one of the data types.
Specifies the name of the file to be exported to; if omitted, the data is exported to the command window, when the name of the file is provided then the file is created in the default directory that is specified in ixutil.cfg file. The Out of the Box folder is USM_HOME\view\exports in ixutil.cfg file.
USM_HOME specifies the CA Service Catalog installation directory on this computer. For 32-bit computers, the default path name is C:\Program Files\CA\Service Catalog. For 64-bit computers, the default path name is C:\Program Files (x86)\CA\Service Catalog.
Indicates the format of the exported data, when omitted, the default is taken from the ixutil.cfg file; all objects support XML output only.
Indicates that additional parameters can be used depending on the object value.
The import syntax for using the ixutil.bat (Windows) command is as follows:
ixutil import object –f file –format xml object-specific parameters
Specifies one of the objects, using the object syntax
Specifies the name of the file to be imported from. If no folder path is provided, only a file name, the folder used is USM_HOME\scripts.
USM_HOME specifies the CA Service Catalog installation directory on this computer. For 32-bit computers, the default path name is C:\Program Files\CA\Service Catalog. For 64-bit computers, the default path name is C:\Program Files (x86)\CA\Service Catalog.
Indicates the format of the file to be imported, if omitted, the default is taken from the ixutil.cfg file; most objects support XML input only.
Indicates that there may be additional parameters that can be used depending on the object value.
In most cases, you must import or export each type of object in its own separate command, as shown in the following list. For example, you import services, and events in three separate commands. You cannot combine two or more types of objects in a single import command. An exception is the service offering option that contains service option group and service option element as noted in the following list.
Note: You do not literally enter the brackets around these options; the brackets are in this list for readability only.
Configurations
ixutil import configuration [-f file] [-format xml] [-businessunit id] [-group name] [-contentpack name]
ixutil export configuration [-f file] [-format xml] [-businessunit id] [-group name]
Events
ixutil import event [-f file] [-format xml] [-event name] [-rule name] [-action name] [-contentpack name] [-disable] [-disallow_duplicates]
ixutil export event [-f file] [-format xml] [-event name] [-rule name] [-action name]
Forms
ixutil import form [-f file] [-format xml] [-cawf -businessunit id] [-contentpack name] [-modified_only] [-disallow_duplicates]
ixutil export form [-f file] [-format xml] [-folder foldername][-form formname] [-businessunit id]
Services
ixutil import service [-f file] [-businessunit id] [-include_incomplete_sub] [-include_cmdb_ci_mapping] [-include_permissions] [-include_request_sla] [-inlcude_service_hour] [-include_resource_type] [-include_application_metric] [-contentpack name] [-modified_only] [-include_associated_policies_and_actions] [-disallow_duplicates] [-include_translation] [-merge_translation]
ixutil export service [-f file] [-folder name] [-servicename name] [-businessunit id] [-include_forms] [-include_cmdb_ci_mapping] [-include_permissions] [-include_request_sla] [-include_service_hour] [-include_resource_type] [-include_application_metric] [-include_associated_policies_and_actions] [-include_translation] [-extract_translation]
Policies
ixutil import policy [-f file] [-format xml] [-businessunit id] [-disable] [-contentpack name]
ixutil export policy [-f file] [-format xml] [folder foldername[,foldername2]] [-policy policyname[,policyname2]] [-businessunit id]
Report Data
ixutil import report_data [-f file] [-format xml] [-folder name] [-contentpack name] [-disallow_duplicates]
ixutil export report_data [-f file] [-folder name(s)] [-id(s)]
Business Units
ixutil import businessunit [-f file] [-format xml] [-businessunit id]
ixutil export businessunit [-f file] [-businessunit id]
The following rules apply to the IXUTIL command line:
The following considerations apply to the IXUTIL command line:
ixutil export businessunit –f output.xml –businessunit “CA”
ixutil export service –f output.xml -businessunit “CA”
The following parameters are used for the IXUTIL command:
Specifies the Business Unit. For exporting, when the domain (businessunit) parameter is used, the business unit that is specified must exist in the source system to export the objects of that business unit.
When specified during import, business unit refers to the business unit in which the objects are imported.
For exporting policy files, this parameter specifies the business unit that contains the policies being exported. If you are exporting all policies in all business units, omit this parameter; otherwise, this parameter is required.
For importing policy files, you can optionally specify this parameter to import all the policies into a single business unit, as follows:
If that business unit does not exist, the import fails and displays an error message similar to the following:
Invalid Login Domain specified
If that business unit does not exist, the policies assigned to it are instead assigned to the root (top-level) business unit.
Specifies the name of the event as seen in the Event Type list (display_name field in the usm_rule_event_type table). This option is used to export and import event, rule, and action as it appears on the Administration, Tools, Events-Rules-Actions page.
If the name contains spaces, enclose the name in double quotation marks, as follows:
ixutil .. -event "Account Change"
To specify multiple names, enclose the names in double quotation marks, and separate the names with commas, as follows.
ixutil .. -event "Request/Subscription Item Change" -rule "When Status is Pending Approval,When Status is Pending Fulfillment" -action "Notify Requestor on Pending Approval,Launch USM_FulfillmentUSDRequest Workflow"
Specifies the name of the rule as seen in the Rule Type list. This option is used to export and import a rule information about the specified event type.
Specifies the name of the action as seen in the Action Type list. This option is used to export and import action information about the specified event type.
Note: If you specify the -rule option, you must specify the -event option, and the event must contain the rule. Similarly, if you specify the -action option, you must specify the -event and -rule options, and the rule must contain the action.
Specifies the name of the file being exported or imported. This file may contain the policy object or objects that you are exporting or importing. The Catalog system uses an XML file to export and import policy objects.
Specifies the folder from which the objects are exported or the folder into which the objects are imported.
Important! When you run an import command, an error occurs if you specify the name of a folder that does not exist: The system does not create the folder and does not import the objects.
Specifies the format of the export file. By default XML is the format that is used if the –format parameter is omitted. Currently, the only supported export format is XML.
Imports and then deletes the objects (such as services and service option groups) that belong to a subscription that has not yet completed. Use this option when importing offerings (services) or rate plans (service option groups).
If you do not specify this option, the objects that belong to such subscriptions are imported and retained (not deleted).
IXUTIL verifies for subscriptions in all services, including inherited services, child services, and inherited services of child services.
Specifies that the associations between CA Service Catalog services and CA CMDB configuration items are exported when you use the ixutil -export command and imported when you use the ixutil -import command. The -include_cmdb_ci_mapping option applies only when you have integrated CA Service Catalog with CA CMDB. For details, see the Integration Guide.
Important! Verify that the CA CMDB configuration items are already present on the target computer before you run the ixutil command. Copy them to the target computer, if necessary. Also verify that the UUIDs of these configuration items are the same on both the source and target computers. For instructions to copy the configuration items and verify the UUIDs, see your CA CMDB documentation.
Exports or imports the associated request SLAs for each service (offering) while exporting or importing service through service commands.
Sample commands follow:
ixutil export service –f serviceSLAs.xml –servicename blackberry –include_request_sla
ixutil import service –f serviceSLAs.xml –include_request_sla
Exports or imports the associated service hours (outage calendars and business hours) for each service (offering) while exporting or importing services through service commands.
Specifies the configurations that are grouped under various categories. Many groups are configured in the Administration Configurations, Accounting Configurations, Catalog Configurations, and Custom Configurations. The Configuration name to be provided as input in the Group Name text box is displayed in brackets beside the configuration name in the header section in the Graphical User Interface. You can import or export multiple groups at the same time. To export multiple groups, separate the names with commas.
For example, to export a CA CMDB configuration group, provide the input as CMDB. All the configurations under this group are exported or imported. Leave this field blank to export all the configurations irrespective of the group.
Note: The group_name must be in the format <businessunitid>_<cc>_<configuration_form_id> to export the custom configurations.
Exports or imports the associated policies and actions for each service (offering) while exporting or importing services through service offerings.
Exports or Imports the permissions for each service (offering), service option group, and service option element associated with the service.
Important! Restart the CA Service Catalog Windows service to see the new permissions in the product UI.
Exports or Imports the resource type that is associated with the service (offering).
Exports or Imports the application, its metric, and the definition of the service that is associated with the Application Rate item.
Apply only when you localize multiple services. This process is documented in the Localizing Multiple Services scenario.
Note: For details, see this scenario in the Administration Guide or on http://ca.com/support.
Applies only to the import command of different objects. If there is a same object with a similar name and different tracking id (a different object with same name) while importing CA Service Catalog system, then that object is updated and no new object is created. If this parameter is not specified, then a new object with the same name is created. This parameter is important in two circumstances:
Specifies that only the modified objects are imported based on comparison of date last modified. IXUTIL imports all the objects by default without any date last modified comparisons. You must specify this parameter only when you want to import the modified objects. This parameter applies to the service and form objects only.
Specifies that the objects are imported in the disabled state. In event rule actions, the rules, actions are in disabled state and in the case of policy the objects are in inactive state.
By default, policies, events, rules, and actions are imported and exported in their current status. For example, if you export a policy whose status is disabled, the policy remains disabled when you import it. Similarly, if you export a policy whose status is enabled, the policy remains enabled when you import it. However, you can add the -disable option to the command to import the policy (or policies) in disabled status.
Note: The -disable option applies only to the import command; it does not apply to the export command.
Use the form-related parameters to export and import CA Workflow forms and Form Designer forms. The following are the included parameters:
Important! CA Workflow is no longer being enhanced, and its maintenance and technical support are scheduled to be discontinued as of December 31, 2013. Therefore, we strongly recommend using CA Process Automation as your process automation tool.
You can use these parameters to perform the following tasks:
An object can be modified in the following ways:
Note: The consideration for object modifications and the conditions for date last modified are only required if the -modified_only parameter is specified. Refer to the description of -modified_only parameter in IXUTIL Parameters.
Consider the following information when you use IXUTIL for services, service options, and service option groups.
The term objects here means services, service option groups, and service option elements. As a best practice, do not modify objects directly on your production computer. Instead, always modify objects on your test computer first, test them thoroughly, and then export them to the production computer. If you do update objects on both the test and production computers and then export, you may accidentally overwrite changes or data on the production computer. You cannot merge changes between two same-named objects on the source and destination computers. The newer object always take precedence when you run IXUTIL.
The following considerations apply to services, service options, and service option groups objects:
The date last modified is updated under the following conditions:
Note: The time stamp of the folder from which the service was moved (the old parent folder) is not updated, for these reasons: no attributes of the old parent folder are changed, and no attributes of the moved service use the old parent folder.
You can export all objects to the target computer from an existing CA Service Catalog implementation. All the objects in the XML file are imported without any timestamps checks. Use the –modified_only parameter to view the previous behavior of IXUTIL. This parameter is basically introduced for backward compatibility. You can export all objects in the following ways:
ixutil export service -f allservices.xml
ixutil import service -f "pathname\allservices.xml"
When you export services that contain service option groups, and service option elements from one business unit to another, inheritance is supported if you follow these rules. If you do not follow these rules, you can export the objects, but the inheritance is broken.
For example, Service A and Service B have a parent-child relationship in the business unit named BU-x. Use following commands in sequence to export the services with inheritance preserved:
ixutil export service -f output.xml -servicename A,B –businessunit BU-x
ixutil import service -f output.xml –businessunit BU-y
Continuing the previous example, enter the following commands in sequence to export the services with inheritance preserved:
ixutil export service -f output1.xml -servicename A –businessunit BU-x
ixutil export service -f output2.xml -servicename B –businessunit BU-x
ixutil import service -f output1.xml –businessunit BU-y
ixutil import service -f output2.xml –businessunit BU-y
You can use IXUTIL to export and import new and updated objects, including events, rules, and actions, from one computer to another. You can export and import services in the following cases:
Note: You can also use the Import Export Utility on the product UI to import and export configurations. The Import Export Utility provides a GUI to import and export configurations and other objects that is not present for Events.
Follow these steps:
ixutil export event -f file -format xml
ixutil export event -event eventname -f file -format xml
ixutil export event ‑event eventname -rule rulename -f file -format xml
ixutil export event -event eventname -rule rulename ‑action actionname -f file -format xml
Refer to IXUTIL Parameters for more information on the parameters.
ixutil import event -f file
ixutil import event -event eventname -f file
ixutil import event ‑event eventname -rule rulename -f file
ixutil import event ‑event eventname -rule rulename -action actionname -f file
ixutil import event -event eventname -f file -disable
ixutil import event -event eventname -rule rulename -action actionname -f file -disable
Important! If you import objects but do not restart the CA CA Service Catalog service on all CA Service Catalog computers, unpredictable results can occur.
The Event Types page appears.
You have exported and imported events, rules, and actions.
You can use IXUTIL to export and import new and updated objects, including configuration objects, from one computer to another. You can export and import configurations in the following cases:
Note: You can also use the Import Export Utility on the product UI to import and export configurations. This utility provides a GUI for importing and exporting configurations and other objects.
Follow these steps:
ixutil export configuration -f file
ixutil export configuration -f file - businessunit businessunit id
ixutil import configuration -f file -format xml -businessunit businessunit id -group name
Note: You must restart the View service after importing the configuration.
Refer to IXUTIL Parameters for more information on the parameters.
You can use IXUTIL to export and import new and updated objects, including service objects, from one computer to another. You can export and import services in the following cases:
Note: You can also use the Import Export Utility on the product UI to import and export services. This utility provides a GUI for importing and exporting services and other objects.
Follow these steps:
ixutil export service -f file
ixutil export service -f file - businessunit businessunit id
ixutil export service -f file -folder name -businessunit id
To export multiple folders, enclose the names in double quotation marks, and separate the names with commas.
ixutil export service -f file -folder name -servicename name -businessunit id -include_forms -include_cmdb_ci_mapping -include_permissions -include_request_sla -include_service_hour -include_resource_type -include_application_metric -include_associated_policies_and_actions -include_translation -extract_translaton
ixutil import service -f file -businessunit id
The -businessunit business unit id is optional when you import the service. However, consider the important factors explained in the description of this option later in this topic.
ixutil import service -f file -businessunit id -include_incomplete_sub -include_cmdb_ci_mapping -include_permissions -include_request_sla -inlcude_service_hour -include_resource_type -include_application_metric -contentpack name -modified_only -include_associated_policies_and_actions -disallow_duplicates -include_translation -merge_translation
Refer to IXUTIL Parameters for more information on the parameters.
You can use IXUTIL to export and import new and updated objects, including report data, from one computer to another. You can export and import report data in the following cases:
Note: You can also use the Import Export Utility on the product UI to import and export report data. This utility provides a GUI for importing and exporting report data and other objects.
Important! If you export report data objects that are based external data sources, verify that they are imported correctly on the target computer. To verify, review the ixutil log file in the USM_HOME\logs\install folder on the target computer. If necessary, recreate these report data objects on the target computer. For information about log files, including how to set the level of detail, see the Implementation Guide. For information about creating report data objects, see the Administration Guide.Follow these steps:
ixutil export report_data -f file
ixutil export report_data -f file -folder name(s) -id name(s)
To export multiple folders, enclose the names in double quotation marks, and separate the names with commas.
ixutil import report_data -f file -format xml -folder name -contentpack name -disallow_duplicates
Refer to IXUTIL Parameters for more information on the parameters.
You can use IXUTIL to export and import new and updated objects, including business unit objects, from one computer to another. You can export and import business units in the following cases:
Note: You can also use the Import Export Utility on the product UI to import and export business units. This utility provides a GUI for importing and exporting business units and other objects.
Follow these steps:
ixutil export businessunit -f file -businessunit id
Where businessunit id is the root BU (businessunit) id.
ixutil import businessunit -f file -format xml -businessunit id
Refer to IXUTIL Parameters for more information on the parameters.
You can optionally import CA Workflow forms into the Form Designer. For example, you can do so if you upgraded from an earlier release of CA Service Catalog and have existing CA Workflow forms that you want to convert to Form Designer forms before continuing to use them in your services. Converting CA Workflow forms to Form Designer forms can be especially helpful as part of changing your process automation tool from CA Workflow to CA Process Automation.
Important! CA Workflow is no longer being enhanced, and its maintenance and technical support are scheduled to be discontinued as of December 31, 2013. Therefore, we strongly recommend using CA Process Automation as your process automation tool.
Follow these steps:
CA Workflow forms are stored as xml files. If you are using a filestore, they are stored in the FileStore\forms folder.
ixutil import form -f {file|foldername} -format xml -cawf -businessunit id
Imports CA Workflow forms and converts them to Form Designer forms. The CA Workflow forms can be either pre-defined or customized.
Note: The -cawf option is required to import Form Designer forms.
Specifies the business unit login ID, the name used to log in to the business unit.
For example, if the business unit login ID is subBud, specify –businessunit subBud.
When you use the –businessunit businessunit-id option, the imported objects overwrite any existing objects in the domain that have the same name. For example, if you import a service (offering) named Diamonds using the option "-businessunit ABC," then the imported service named Diamonds overwrites the existing service named Diamonds (if one exists) in the businessunit named ABC.
To import an individual CA Workflow form, specify -f file, where file specifies the complete path name of the form.
You can optionally export and import Form Designer forms alone, without any related service option elements, from a source (test) computer to a target (production) computer. Do so when you want to move and re-use one or more forms but not the related service option elements. You can export and import any of the following:
Follow these steps:
ixutil export form -f file -format xml {-folder foldername|-form formname} -businessunit id
Specifies the complete path name of the XML file being exported; specify an intuitive file name. This file contains the forms, service option elements, and other service-related entities that you want to move to the target computer.
Specifies the business unit login ID, the name used to log in to the business unit. Use this option to export all forms in a domain. If you omit this option, the command exports all forms in all businessunits.
For example, if the business unit login ID is subBud, specify –businessunit subBud.
Exports either an individual Form Designer form or all Form Designer forms from a specified folder, as follows:
To export an individual Form Designer form, specify -form formname, where formname specifies the name of the form being exported.
To export all the Form Designer forms from a specific folder, use -folder foldername, where foldername specifies the name of the folder being exported.
Note: For Form Designer forms and folders, use only the form name or folder name; path name is not applicable.
The command runs and creates the XML export file at the location USM_HOME/build/install/view/exports. The file name is the name you specify using the -f file parameter described earlier.
USM_HOME specifies the CA Service Catalog installation directory on this computer. For 32-bit computers, the default path name is C:\Program Files\CA\Service Catalog. For 64-bit computers, the default path name is C:\Program Files (x86)\CA\Service Catalog.
Sample commands follow:
ixutil export form -f file1.xml -format xml -form "Sample Form" -businessunit subBud
ixutil export form -f file2.xml -format xml -folder "My Forms" -businessunit subBud
ixutil import form -f file -format xml -businessunit id
Specifies the complete path name of the XML file being imported.
Note: You already specified form, folder, and domain information when you ran the export command that created this XML file (see Step 1); therefore, in the import command, you specify only this XML file name.
Specifies the business unit login ID, the name used to log in to the business unit. The exported XML file is imported into this business unit.
When you use the –businessunit id option, the imported objects overwrite any existing objects in the domain that have the same name. For example, if you import a service (offering) named Diamonds using the option "-businessunit ABC," then the imported service named Diamonds overwrites the existing service named Diamonds (if one exists) in the businessunit named ABC.
The command runs and imports the form or forms and folders (if applicable) into the target (production or backup) computer, as follows:
Note: The timestamp or the date last modified is no longer available. All that is part of XML file is imported. If you want the timestamp check then you should use the –modifed_only parameter.
If you import a folder, then that folder, its forms, and its child folders are imported, with their folder structure maintained. However, both that folder and its parent folder from the source computer are attached to the root folder (named Forms) on the target computer. If the parent folder contains other child folders besides the one you exported, those other child folders are also exported and are included under the parent folder, with their folder structure maintained.
For example, on the source computer, suppose Folder1 contains Folder2, and Folder2 contains Form1 and Form2. If you export folder 2 from the source computer and import it on target computer, then both Folder1 and Folder2 become root level folders on the target computer. Form1 and Form2 remain under Folder 2. Folder1 on the root folder includes and any forms or child folders that belong to it (except for Folder2).
You can export and import Form Designer forms to include them when exporting and importing service that contains service option elements (rate items), for example, when moving from source (test) to target (production) or from backup to restore.
In IXUTIL export commands for service that has service option elements, specify the –include_forms option to include the Form Designer forms (not CA Workflow forms) associated with the service option elements. The –include_forms option is not valid in IXUTIL import commands; the forms are included in the import automatically if they were included in the export.
Follow these steps:
ixutil export form -f file -format xml {-folder name|-form name} -businessunit id
ixutil import form -f file -format xml -businessunit id
For an explanation of the command options, see the descriptions of these commands in Import and Export Form Designer Forms.
ixutil export {service} -f file {-offering name|-folder name|-businessunit id} -include_forms other options
Includes services (offerings), service option groups (rate plans), and service option elements (rate items).
Note: Service option elements are processed in IXUTIL export service commands only. Therefore, use –include_forms in IXUTIL export service commands only, as explained in this topic.
Includes Form Designer forms (not CA Workflow forms) associated with service option elements (rate items).
Restricts the forms being exported to those that belong only to a specific service (-offering name), folder (-folder name), or businessunit (-businessunit id).
The command runs and creates the XML export file at the location USM_HOME/build/install/view/exports. The file name is the name you specify using the -f file parameter.
USM_HOME specifies the CA Service Catalog installation directory on this computer. For 32-bit computers, the default path name is C:\Program Files\CA\Service Catalog. For 64-bit computers, the default path name is C:\Program Files (x86)\CA\Service Catalog.
ixutil import {service} -f file other options
If you specified service in the original export command, specify service in the corresponding import command.
Specifies the complete path name of the XML file being imported.
The IXUTIL command line utility is an importing and exporting command line utility that allows the preservation and migration of CA Service Catalog data between computers. You can use IXUTIL to export and import new and updated objects, including policies, from one computer to another. You can export and import policies in the following cases:
Note: You can also use the Import Export Utility on the product UI to import and export policies. This utility provides a GUI for importing and exporting policies and other objects.
Follow these steps:
ixutil export policy -f file
ixutil export policy -f file - businessunit businessunit id
ixutil export policy -f file -policy name -businessunit id
If the name contains spaces, enclose the name in double quotation marks, as follows:
ixutil export policy -policy "Mobile Device Policy--Tier 1" ...
ixutil export policy -policy "Mobile Device Policy--Tier 1,Mobile Device Policy--Tier 2,Mobile Device Policy--Tier 3" ...
ixutil export policy -f file -folder name -businessunit id
To export multiple folders, enclose the names in double quotation marks, and separate the names with commas. Use the previous command for multiple polices as a model.
ixutil import policy -f file -businessunit id
The -businessunit businessunit id option is optional when you import the policy file. However, consider the important factors explained in the description of this option later in this topic.
ixutil import policy -f file -businessunit businessunit id -disable
Refer to IXUTIL Parameters for more information on the parameters.
The Policy Builder main page appears.
Copyright © 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.