5 RSA Tables
RSA database schema defines various tables used to define and customize the application behavior.
Most of the RSA configuration tables are SO level tables, that is, provisioning in these tables is allowed only from the SO GUI. Only one RSA configuration Tables are NO level tables.
Table 5-1 List of configuration tables for the Rx ShUDR application
Table Name | Table Description | Single row indicator | Table Level |
---|---|---|---|
Rx_Client | This table includes the configuration parameters for each Rx Client regarding the details of Sh Lookup and Topology hiding. This is a table generated by the DCA Framework. | No | NO |
PDNGWHost_PCRF_Mapping | This table contains 1:1 mapping between PDN Gateway Host and PCRF. This is a table generated by the DCA Framework. | No | NO |
Topology_Hiding | This table contains 1:1 mapping between PCRF FQDN and corresponding Pseudo FQDN for each PCRF MPEs. This is a table generated by the DCA Framework. | No | NO |
Error_Action_Config | This table contains the error action configuration parameters to be applied for send answer during runtime errors while processing Sh UDR/UDA message. | No | NO |
System_Config_Options | This table will contain system wide common configurable options required to process Rx-ShUDR application. | Yes | SO |
Configures RSA Configuration tables
RSA configuration table (Error_Action_Config) are pre-populated if RSA is configured using RSA JSON file. See Configuring RSA Mandatory Options for more details.
Alternatively, RSA configuration tables can be configured manually using the following steps. See DCA Programmer’s Guide for detailed information
- From the NO GUI main menu, .
- Select the newly added RSA Version Name.
- Click Config Table and Data.
Note:
If RSA JSON is not used to import RSA business logic and the configuration database schema, then the configured table list is empty. - Click Insert.
- Fill the fields to define the table.
- Click Add to add multiple Table Fields.
- Click OK/Apply.
- Similarly repeat steps 4 to 7 for all other configuration tables.
Provision RSA Tables
This procedure imports RSA default provisioning data using RSA JSON file.
RSA SO JSON filename: Rx_ShUDR_Application-Version1_Default_Config.json
See the DCA Programmer’s Guide for detailed information.
- From the NOAM GUI main menu,
- Select the newly added RSA Version Name.
- Click A Level Config Data in the Import section of the Application Control page.
- Click Browse and select the Rx_ShUDR_Application-Version1_Default_Config.json file.
- Mark the Abort on first error checkbox to abort the import process in case of error.
- Click Import to start the import process.
- From the SO GUI main menu, .
- Select the newly added RSA Version Name.
- Click Config Data.
Note:
If DSA JSON is not used to import RSA business logic and the configuration database schema, then the configured table list is empty. - Select the table that needs to be provisioned.
- Click Provision Table.
- Click Insert.
- Fill the values for required fields of the table.
- Click OK/Apply.