The following table describes the parameters and their corresponding descriptions:
ESM Policy XML file path. You must specify the path of the ESM Policy XML using this option. The path must exist and be accessible.
Unlike the earlier versions of the migration utility that only required a policy xml as an input, the current version also requires a template folder containing the template files that are included in the ESM policy. The Policy tool when run with the export option for the specified ESM policy, creates the template folder under the parent folder that contains the policy xml.
This option is mandatory. You can specify either NUMERIC or STRING. If NUMERIC is specified, the utility creates CCS check expression based on ESM security message's numeric ID. If you specify the string, the utility creates CCS check expression based on ESM security message's string ID.
This parameter is optional. Output Standard XML file path. You can specify the path for this output standard XML file by using this option. The path must exist and be accessible. The path can be a directory, a filename, or an entire path of a file. By default, output standard XML is created in the current directory and the filename is Standard-<ESM Policy>.xml.
This parameter is optional. If you specify this option, then the migration utility does not migrate the ESM suppressions to CCS Standard.
This parameter is optional. You can customize the default list of the messages categories that are migrated to the standard.
For example, if you do not want to migrate the messages whose categories are system Information, then you can use the -c option with the list of comma separated message categories in addition to the other regular options whilst executing the migration tool.
In the above example,-c 1,2,3,8,500 refers to migration of all messages that belong to the following categories: Policy Compliance, Patch Assessment, Change Notification, ICE, Network Assessment respectively.