This chapter provides reference information for the Oracle Communications Pricing Design Center (PDC) utilities.
Use the ImportExportPricing utility to import and export pricing and setup components from the PDC database by using XML files. See "Importing and Exporting Pricing and Setup Components" for information on using this utility.
The XML files that are used for importing or exporting data must conform to the format detailed in the XML schema definition (XSD) files.
The utility uses separate XSD files for importing or exporting pricing components, setup components, and profile data. The XSD files are available in their respective directories in the PDC_home/apps/xsd directory, where PDC_home is the directory in which the PDC software is installed. See "About the XSD Files" for more information.
ImportExportPricing -export [FileNamePrefix] -config [SetupObjectType1,SetupObjectType2,…] -metadata -expObsolete -pricing [PricingObjectType1,PricingObjectType2,…] -profile [-n "ObjectName1, ObjectName2,…"] [-productSpecName ProductSpecName1,ProductSpecName2,…] [-expRefs -expAllRefs] [–inclFailedObjs] [–brmobject [brmObjectType1, brmObjectType2, …]] [-pricing [PricingObjectType1,PricingObjectType2,…] [-ma time] [-mby user1, user2,… ] [-l loglevel] [-v] [-ow] [-pricingprofilename "Name1, Name2,…"] -appsvruser ApplicationServerUserName -pdcuser PdcUserName [-h]
Exports the data from a PDC database and generates a separate XML file for pricing components, setup components, and pricing profile data in the directory from which you run the utility. The utility generates the file names as:
FileNamePrefix_export_pricing.xml for the file containing pricing components.
FileNamePrefix_export_config.xml for the file containing setup components.
FileNamePrefix_export_profile.xml for the file containing pricing profiles data.
If you do not specify FileNamePrefix, the utility generates the file name as follows:
export_pricing.xml for the file containing pricing components. If this file already exists in PDC, the utility generates the file name as export_pricing_timestamp.xml, where timestamp is the server's local time in the format yyyy-mm-dd_hh-mm-ss.
export_config.xml for the file containing setup components. If this file already exists in PDC, the utility generates the file name as export_config_timestamp.xml, where timestamp is the server's local time in the format yyyy-mm-dd_hh-mm-ss.
export_profile.xml for the file containing pricing profile data. If this file already exists in PDC, the utility generates the file name as export_profile_timestamp.xml, where timestamp is the server's local time in the format yyyy-mm-dd_hh-mm-ss.
Exports all the setup components that are defined in PDC from the PDC database to the XML file. See "About Setup Components" for more information about the setup components that are defined in PDC.
Exports SetupObjectType from the PDC database to the XML file, where SetupObjectType is the setup component type listed in Table 10-1.
Table 10-1 lists the setup component types and the setup components they represent.
Table 10-1 Setup Component Types and the Setup Components They Represent
Setup Component Type | Setup Component |
---|---|
ZONE_MAP |
Value Map |
EVENT_ATTRIBUTE_SPEC |
Event |
PRODUCT_ATTRIBUTE_SPEC |
Service |
CUSTOMER_ATTRIBUTE_SPEC |
Account Attribute |
RUM_CONFIGURATION |
RUM |
ZONE_RESULT_CONFIGURATION |
Impact Category for Zones |
ATTRIBUTE_SPEC_MAP |
Service-Event Map |
BALANCE_ELEMENT |
Balance Element |
GLID |
G/L ID |
TAX_CODE |
Tax Code |
TAX_SUPPLIER |
Tax Supplier |
GEO_ZONE_MODEL |
Geographical Zone Model |
STANDARD_ZONE_MODEL |
Standard Zone Model |
PROVISIONING_TAG |
Provisioning Tag |
HOLIDAY_CALENDAR |
Special Day Calendar |
CUSTOM_ANALYZER_RULE |
Custom Rule |
PROFILE_ATTRIBUTE_SPEC |
Profile Attribute Specification |
ITEM_TYPE_SELECTOR |
Item Type Selector |
If you do not specify SetupObjectType, the utility exports all the setup components from the PDC database to the XML file.
Exports the event, service, account, and profile attribute specifications listed in Table 10-1 from the PDC database to the XML file.
Exports all obsolete pricing components (including the corresponding metadata and setup components).
Exports the components mastered in BRM from PDC into XML file, where BRMObjectype is the setup component type. The following are the BRM component types mastered in BRM that you can export:
GLID
TAX_CODE
TAX_SUPPLIER
PROVISIONING_TAG
Exports PricingObjectType from the PDC database to the XML file, where PricingObjectType is the pricing component type listed in Table 10-2.
Table 10-2 lists the pricing component types and the pricing components they represent.
Table 10-2 Pricing Component Types and the Pricing Components They Represent
Pricing Component Type | Pricing Component Represented |
---|---|
CHARGE_RATE_PLAN |
Charge |
ALTERATION_RATE_PLAN |
Discount |
DISTRIBUTION_RATE_PLAN |
Chargeshare |
ROLLOVER_RATE_PLAN |
Rollover |
ALTERATION_RATE_PLAN_SELECTOR |
Discount Selector |
GENERIC SELECTOR |
Generic Selector |
CHARGE_RATE_PLAN_SELECTOR |
Charge Selector |
PRICE_MODEL_SELECTOR |
Price Selector |
APN_MAP |
APN Selector |
USC_MAP |
USC Selector |
TIME_MODEL |
Time Model |
TRIGGER_SPEC |
Trigger |
CHARGE_SELECTOR_SPEC |
Filter |
ALTERATION_POP_MODEL |
Discount Pricing |
ROLLOVER_POP_MODEL |
Rollover Rules |
RECURRING_POP_MODEL |
Recurring Pricing |
ONE_TIME_POP_MODEL |
One-Time Pricing |
CHARGE_OFFERING |
Charge Offer |
ALTERATION_OFFERING |
Discount Offer |
DISTRIBUTION_OFFERING |
Chargeshare Offer |
ALTERATION_EXCLUSION |
Discount Exclusion |
BUNDLED_PRODUCT_OFFERING |
Bundle |
BUNDLE_TRANSITION |
Bundle Transition |
PACKAGE_OBJ |
Package |
PACKAGE_EXCLUSION |
Discount Restriction |
PACKAGE_TRANSITION |
Package Transition |
PACKAGE_LIST |
Package List |
BEST_PRICING |
Best Pricing |
If you do not specify PricingObjectType, the utility exports all the pricing components from the PDC database to the XML file.
Exports the pricing profile data from the PDC database to the XML file.
Filters the pricing or setup components based on the specified component names. You can use an asterisk (*) at the end of the name to search for variations of that name. For example, searching for chargeoffergsm* yields variations of that name, such as chargeoffergsm1 and chargeoffergsm2.
Note:
When you use the -n parameter, you must specify either -config or -pricing.The parameters -n and -productSpecName are mutually exclusive.
Filters the exported pricing components that are scoped to the specified services.
If you specify this parameter along with PricingObjectType, the utility exports all the pricing object types that are scoped to ProductSpecName. You can use this parameter only for the following pricing object types:
ALTERATION_OFFERING
CHARGE_OFFERING
DISTRIBUTION_OFFERING
CHARGE_RATE_PLAN
If you specify this parameter without specifying PricingObjectType, the utility exports all pricing components scoped to the specified service.
Note:
The parameters -n and -productSpecName are mutually exclusive.Exports all the pricing components referenced by PricingObjectType. For example, if multiple charge offers are referenced by bundles, this parameter exports all the charge offers when exporting bundles. The utility ignores this parameter if it is used with the -config parameter.
Exports all the PDC components (including metadata, setup components, and pricing components) referenced by PricingObjectType. For example, if setup components, such as ratable usage metrics (RUMs) and tax codes are referenced by charge offers, then this parameter exports RUMs and tax codes when exporting charge offers. This parameter applies only to the -pricing parameter.
Exports pricing components modified on or after time. Enter the time in the format yyyy-mm-dd_hh-mm-ss.
Exports the pricing components created or modified by the specified users.
Note:
The parameters -mby and -productSpecName are mutually exclusive.Specifies how much information the utility should log. The logs are stored in the ImportExportPricing_username_timestamp.log file, where username is the name of user who used the utility and timestamp is the time the log file was created in the format yyyy-mm-dd_hh-mm-ss.
Set loglevel to one of the following:
FINE
FINER
FINEST
INFO
OFF
SEVERE
WARNING
The default is INFO.
Displays information about successful or failed processing as the utility runs.
Exports pricing components scoped to the pricing profile names specified in the list.
If this parameter is used with the -pricing parameter when a list of pricing component types is specified, the utility exports all the pricing components of the specified type scoped to the pricing profiles names specified in the list.
If this parameter is specified with the -pricing parameter when no pricing components types are specified, the utility exports all the pricing components that are scoped to a pricing profile.
Specifies the user name to access the WebLogic Server. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
Specifies the user name to access PDC. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
Displays the syntax for this utility.
See Table 10-2 for the list of the pricing component types and the pricing components they represent.
ImportExportPricing -import -metadata -config SetupFileName -pricing PricingFileName -profile ProfileFileName -ignoreID [-l loglevel] [-v ] [-ow] [-changeSetName ChangeSetName] -submitCS -appsvruser ApplicationServerUserName -pdcuser PdcUserName [-h]
Imports the data from the XML file that conforms to the format detailed in the XSD file to the PDC database. You must specify either -pricing, -config, or -profile along with -import.
Imports the metadata from the metadata filename to the PDC database.
Imports the setup components from the SetupFileName to the PDC database, where SetupFileName specifies the full path and file name of the XML file containing the setup components.
Imports the pricing components from the PricingFileName to the PDC database, where PricingFileName specifies the full path and file name of the XML file containing the pricing components.
Imports the profile data from the ProfileFileName file to the PDC database, where ProfileFileName specifies the full path and file name of the XML file containing profile data. If you specify -pricing and -config parameters along with -profile, the utility imports profile data and setup components before importing the pricing components. If the import of the profile data and setup components is not successful, the utility does not import pricing components.
Ignores the internal IDs in the specified XML file and imports the components by the input file name.
Specifies how much information the utility should log. The logs are stored in the ImportExportPricing_username_timestamp.log file, where username is the name of user who used the utility and timestamp is the time the log file was created in the format yyyy-mm-dd_hh-mm-ss.
Set loglevel to one of the following:
FINE
FINER
FINEST
INFO
OFF
SEVERE
WARNING
The default is INFO.
Displays information about successful or failed processing as the utility runs.
Overwrites any existing pricing or setup components available in the PDC database with the specified components. If the specified pricing or setup component does not exist in PDC, the utility creates new pricing or setup components.
Note:
If you do not use the -ow parameter when importing data, the utility generates an error if an object with the same name already exists in PDC.Specifies the name of the changeset used to import setup and pricing components into the PDC database. If you do not specify ChangeSetName, the utility generates the changeset name as ieChangeSettimestamp, where timestamp is the current timestamp in the format yyyy-mm-dd_hh-mm-ss.
Submits the changeset that is used to import the setup and pricing components to the configured billing system database.
Specifies the user name to access the WebLogic Server. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
Specifies the user name to access PDC. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
Displays the syntax for this utility.
ImportExportPricing -publish [Component] [ObjectType1,ObjectType2,…] -target Target_Engine
-appsvruser ApplicationServerUserName -pdcuser PdcUserName
Publishes the following components from PDC to the specified target engines:
metadata. Publishes the metadata in PDC to the specified target engine.
config. Publishes the setup components in PDC to the specified target engine.
pricing. Publishes the pricing components in PDC to the specified target engine.
all. Publishes all the components in PDC to the specified target engine.
Publishes specified components to the target engine; for example, BALANCE_ELEMENT. You can specify [Component] or [ObjectType] for publishing the components. For the list of component types, see Table 10-1 and Table 10-2.
Specifies the following target engines for publishing the components:
Rre. Publishes the components or object types to the real-time rating target engine.
Bre. Publishes the components or object types to the batch rating target engine.
Ece. Publishes the components or object types to the ECE rating target engine.
All. Publishes the components or object types to all the target engines mentioned above.
Specifies the user name to access the WebLogic Server. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
Specifies the user name to access PDC. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
ImportExportPricing -keep [metadata | config | pricing | all] -numVersion N -appsvruser ApplicationServerUserName -pdcuser PdcUserName
Deletes old versions of PDC components that are obsolete in PDC or the associated target engines (for example, Oracle Communications Billing and Revenue Management (BRM) Elastic Charging Engine (ECE)) and keeps only the latest versions of successfully promoted PDC components.
Keeps only the latest specified version of all the successfully promoted objects in the PDC database and deletes the remaining versions, where N is a positive integer that specifies the number of latest successful versions to be kept in the PDC database.
Specifies the user name to access the WebLogic Server. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
Specifies the user name to access PDC. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
ImportExportPricing [-d FilePath][-dp FilePath] -appsvruser ApplicationServerUserName -pdcuser PdcUserName
Deletes the setup components specified in FilePath from the PDC database, where FilePath specifies the full path and file name of the XML file containing the setup components. The utility displays an error message if the data being deleted is dependent on other data.
Deletes the pricing profiles specified in FilePath from the PDC database provided the profiles are not being used by any pricing component, where FilePath specifies the full path and file name of the XML file containing the pricing profiles.
Specifies the user name to access the WebLogic Server. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
Specifies the user name to access PDC. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
ImportExportPricing -t config | pricing -appsvruser ApplicationServerUsername -pdcuser PdcUserName
Displays the list of the setup or pricing component types supported in PDC.
Specifies the user name to access the WebLogic Server. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
Specifies the user name to access PDC. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
Ignores the internal IDs in the specified XML file and imports the components by the input file name.
Specifies the user name to access the WebLogic Server. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
Specifies the user name to access PDC. If you do not specify this parameter, the utility prompts you to enter the user name at the command prompt.
The ImportExportPricing utility notifies you when it runs successfully. Otherwise, look in the ImportExportPricing_username_timestamp.log file, where username is the name of user who used the utility and timestamp is the timestamp of the log file in the format yyyy-mm-dd_hh-mm-ss. This file is in the directory from which the utility was started.