Copying Database-Based Configuration

It is possible to copy database-based configuration, which is stored in a database rather than in property files, from one installation of CMPClosed Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. to another.

This is typically used in testing environments, but it can also be used to copy CMP data between installations. Copying a database-based configuration ensures consistency across environments, and saves time by providing a ready-to-use system with existing records.

Before you begin, ensure that:

  • The source and target versions of CMP are the same, for example, if the source installation is V 8.15.0 Patch Level 2, the target installation must also be V 8.15.0 Patch Level 2.

    You can also compare the module versions of the database in the Admin Console in System Configuration->Modules->Database. The versions for the cmp-database-pkg should be identical.

  • You have a mechanism for transferring a file from the source installation’s database machine to the target installation’s database machine, such as SSH.

  • You are able to log onto both the source and target databases using a profile with sufficient database privileges to read and write data to all tables within the database and run procedures.

To copy the configuration data from one installation to another, follow these steps:

  1. Run the SAVE_CMP_CONFIG_DATA( level_param VARCHAR, file_path VARCHAR) function. This function will exist in the same schema as the CMP tables.

    <level_param> can have one of four values, namely:

    1. Factory_Configuration

    2. System_Configuration

    3. Business_Configuration

    4. Project_Configuration

    These levels specify the different levels of data that you are copying. Factory_Configuration is the most basic CMP config, and Project_Configuration is the most complex.

    <file_path> is a fully qualified name, including path, to a text file that the function will create. This file should not already exist.

  2. Transfer the file specified in <file_path> to a location accessible to the target database box.

  3. Run the LOAD_CMP_CONFIG_DATA (file_path TEXT) function.

    This function will exist in the same schema as the CMP tables in the target database. The <file_path> parameter specifies the fully qualified name of the file produced by the SAVE_CMP_CONFIG_DATA function and should refer to the location where the file was transferred in step 2.

    This function does not raise an error if the data being copied already exists in the target tables, that is, a PK Key conflict.