Support Article

Data-Admin-Security-Keystore not caching

SA-30775

Summary



Data-Admin-Security-Keystore is not caching for mobile application. This is resulting in additional unnecessary calls to the database.

Error Messages



Not applicable


Steps to Reproduce



Connect soap when the connector setup with authProfile.


Root Cause



The rule instance cache doesnt include the data instances of type keystore, thus additional unnecessary calls are made to the database.

Resolution



Apply HFix-30514. 

                                         HFix-30514 Installation Instructions
  1. Take Database backup
  2. Unzip the attached DDL scripts (Triggers_updated.zip) to a folder, the unzipped content would have DDL scripts specific to the database flavor, for e.g. DB2, MSSQL,POSTGRES and ORACLE. Use the specific flavor. The DB2 folder however contains 2 folders for LUW and ZOS flavors.
  3. There are 3 scripts in each folder the purpose of each script is to keep the rule instance cache in sync in a multimode environment when a particular rule instance is created, deleted or updated.         
  4. Please ensure to update the schema name in each script , for e.g. CREATE TRIGGER GCS04DBO.trpr_dataadm_upd
AFTER update
ON .pr_data_admin
CALL .PRPC_UPDATESCACHE (NEW.PZINSKEY
 
  •  
  1. Please follow either of the steps(a or b) as per feasibility , both should work
    1. DROP and recreate the scripts
      1. Before using the scripts the existing triggers set against PR_DATA_ADMIN table have to be dropped using the conventional drop command.
      2. For e.g. DROP TRIGGER <SCHEMA_NAME>.<TRIGGER_NAME>
      3. After dropping the triggers, the triggers specific a particular database in question needs to be run(from the respective folder in the zip). For e.g. for DB2 the 3 triggers needs to be dropped first and 3 triggers need to be created again.
        1. For e.g for DB2 ZOS , these needs to be created
          1. db2zos08670_DELETE.sql
          2. db2zos08680_INSERT.sql
          3. db2zos08690_UPDATE.sql
 
  1. If you don’t wish to drop the scripts or don’t have admin privileges to drop the scripts, then alter the existing triggers present in PR_DATA_ADMIN table to add Data-Admin-Security-Keystore to the list of cached instances
The final list should contain:-
 
  1.                          'Data-Admin-Operator-AccessGroup',
  2.                         'Data-Admin-Calendar',
  3.                         'Data-Admin-OrgDivision',
  4.                         'Data-Admin-StartingFlows',
  5.                         'Data-Admin-System-WorkSource-Application',
  6.                         'Data-Admin-WorkGroup',
  7.                         'Data-Admin-WebServices-Policy',
  8.                         'Data-Admin-ServicePackage',
  9.                         'Data-Admin-AppID',
  10.                         'Data-Admin-Organization',
  11.                         'Data-Admin-OrgUnit',
  12.                         'Data-Admin-System-Security',
  13.                         'Data-Admin-Security-OAuth-Client-AccessToken',
  14.                         'Data-Admin-WorkBasket',
  15.                         'Data-Admin-ServiceType',
  16.                         'Data-Admin-Security-AuthenticationProfile',
  17.                         'Data-Admin-RequestProcessor-Service',
  18.                         'Data-Admin-RequestProcessor-Connect',
  19.                         'Data-Admin-Security-WSSecurityProfile',
  20.                         'Data-Admin-System-SecurityPolicy',
  21.                         'Data-Admin-System-Targets',
  22.                         'Data-Admin-System-WorkSource',
  23.                         'Data-Admin-System-Settings',
  24.                         'Data-Admin-System',
  25.                         'Data-Admin-Security-Keystore' – This needs to be added.
 
  1. After adding 'Data-Admin-Security-Keystore' to the list , execute the trigger.
  1. After the database operations are performed, The DL item needs to be installed and the server needs to be restarted.
  2. Please make sure you save the already existing keystore instances used in your application either by saving them manually or by running the Revalidate and Save utility and choosing Data-Admin-Security-Keystore as the Type.
            

        
          
          
  

Published November 24, 2016 - Updated December 1, 2016

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.