convert_price_plan.jar

Use the convert_pricing_plan.jar command line utility to validate the schema of a pricing XML configuration file against a running MATRIXX Engine. It can also be used to convert an input pricing file into compact MDC, XML, or Stacked Data Container (SDC) format.

Note: Custom MDCs are defined in the /opt/mtx/conf/mdc_config_custom.xml file.

Syntax

java -jar convert_price_plan.jar [-h] [-v] [-address:ipAddress -port:port] mtxPricingFile [--validate-pricing] [--write-txt:txtFilename] [--write-sdc:sdcFilename] [--write-xml:xmlFilename]

Options

-h
Prints help information for this utility.
-v
Runs the utility in verbose mode and prints additional information during processing.
-address:ipAddress -port:portNumber
The IP address and port number of a running MATRIXX Engine or Gateway Proxy from which to retrieve the MATRIXX Engine schema definitions during validation.
-custom:filename

Specify an XML file containing extension MDCs. If custom MDCs are not defined in /opt/mtx/conf/mdc_config_custom.xml, specifying the file prevents errors during price plan loading.

--validate-pricing
Validates the specified pricing configuration file against the MATRIXX Engine schema.
--write-txt:txtFilename
Converts the specified XML or SDC input file to a compact MDC file.
--write-sdc:sdcFilename
Converts the specified XML or TXT input file to an SDC file, which is used internally by the load_pricing.py utility. Customers should never need to convert a pricing file to this format.
--write-xml:xmlFilename
Converts the specified SDC or TXT input file to an element-based xml file. Customers might need to convert an SDC file to this format to revert back to an mtx_pricing.xml file that was wrongly deleted.

Example

Use the configuration of a running MATRIXX Engine to validate the mtx_pricing.xml pricing configuration file.
java -jar convert_price_plan.jar mtx_pricing.xml -port:4070 -address:10.10.11.12 --validate-pricing