Symptoms

If your installation contains any custom – i.e. self-developed – plug-in (a payment plug-in developed with Ecommerce SDK C++, or a domain plug-in developed with Domain SDK C++), before changing AES password for BA database you need to follow the procedure described below.

Resolution

Note: Applies to OA 7.2, 7.3 and 7.4 only.

Before changing AES password for BA database you might need to extend the secure fields structure for your custom plug-in is described below:

  1. In .type files of your custom solution, find that types that have ENCRYPT="yes" parameter.
  2. In .lsa files of your custom solution, find all the class attributes that have types from p.1, and corresponding classes.
  3. On the Billing Application node, open the /usr/local/bm/tools/secure_fields_structure file.

  4. Extend the stucture of the secure_fields_structure file by adding the values found in p.2 using the following format:

      'TableName' => { 
                  'FirstColumnName' => {
                                        'type' => 'XVARCHAR(64)',
                                        'null' => '1' 
                                        },
                  'SecondColumnName' => {
                                         'type' => 'XVARCHAR(64)', 
                                         'null' => '' 
                                        }
                 },

where:

  • TableName - name of class (table) from p.2

  • FirstColumnName, SecondColumnName - names of class attributes from p.2

  • type - XVARCHAR(DBLEN of corresponding column type)

  • null -
    • empty if column has NOT NULL parameter, or
    • "1" if column does not have NOT NULL parameter.

After extending the file, you can use it in the procedure of changing AES password. The whole procedure is described in the respective section of OA Billing Deployment Guide (Configuring OA Billing > Changing AES Password).

Internal content