Activating the data integrity framework

The data integrity framework is not automatically active after installation of FTM SWIFT. You must activate it explicitly, and you can do this at any time. Before activating the data integrity framework, verify your table space allocation as described in Calculating space requirements of the runtime database.

Note: There is no fallback to deactivate the data integrity framework once you have activated it.

To activate the data integrity framework:

Ensure that the policy file required by the data integrity checker is created as described in Java Policy files.
As a data integrity administrator do the following:
1. Create the vault that is required by the data integrity checker by issuing the vault utility command create. For example, to create the vault /var/ftm/swift/v324/run/ftmswift_vault.jceks being protected by passphrase my_passphrase, issue the following command:
```
dnpvault -create -dir /var/ftm/swift/v324/run
         -store ftmswift_vault -passphrase my_passphrase
```
2. Ensure that the following users have read permission for the vault that you created in step 2.a:
  - The Db2® fenced user ID
  - The message broker administrator
3. Initialize the data integrity framework by issuing the data integrity checker command init, for example:
```
dnpdic -init -password my_data_integrity_password
       -Djava.security.policy=/var/ftm/swift/v324/run/ftmswift.policy
       -keystore /var/ftm/swift/v324/run/ftmswift_vault.jceks
       -passphrase my_passphrase
       -dsn DNIDBRUN -schema DNI -uid helen -pw helens_password
```
As an FTM SWIFT system configuration administrator (user ID sa1 or sa2) do the following:
1. For the system OU, add CO DniVault to CT DniFileDir and set its Path attribute to the value that the data integrity administrator specified for parameter -dir when creating the vault file as described in step 2.a, for example:
```
add -ou SYSOU -ct DniFileDir -co DniVault -attr Path -val /var/ftm/swift/v324/run
add -ou SYSOU -ct DniFileDir -co DniVault -attr read
```
2. Commit, approve, and deploy the system OU:
```
com -ou SYSOU
app -ou SYSOU
dep -ou SYSOU
```
Combine trigger module definitions in a single DDL file:
1. Log on as a customizer (ucust1).
2. Create or choose a directory where you want to save the file with the combined data integrity trigger statements. In the following, replace variable trigger_dir with the directory that you have created or chosen.
3. Gather all data integrity trigger modules from the customized administrative scripts directory into a single file:
```
/opt/IBM/ftm/swift/v324/admin/bin/dniczdic
       -collect
       -d /var/ftmswift_v324/cus/depdata
       -i instance
       -l trigger_dir
```
  This command creates the file trigger_dir/dnirundb_dic.ddl.
  Note: Keep file dnirundb_dic.ddl if you want to perform housekeeping tasks by means of Db2. However, if you create or delete an organizational unit you need to re-run the current step and update the file.
Stop your FTM SWIFT business processes, stop all sessions, and stop all services you use.
Reduce the amount of data in your FTM SWIFT database tables:
1. As a database administrator (udb2adm1) do the following:
  - Move historical configuration data to history database tables as described in Saving and purging configuration and security data.
  - For each OU:
    - Archive the audit data in the following database tables:
      
      DNI_A_MSG_ou
      
      DNI_A_USR_ou
    - Reduce the message warehouse data by archiving and deleting records. The database tables used by message warehouse and to be considered are:
      
      DNIMWH_PT_ou
      
      DNFMWHFIN_ou
  - Reduce the RM data in your Relationship Management Data Store (RMDS), for example, by removing history data.
2. As an MSIF operator clean your MSIF data by issuing the MSIF cleanup command.
3. As an event administrator delete all event records that are no longer required. For information on how to do this, see del (delete events from event database table).
Note: Reducing data is optional. However, this step significantly decreases the processing time that is required by step 9.
As a message broker administrator (uwmba1) stop all FTM SWIFT related message flows.
Create the data integrity triggers:
1. Log on as database administrator (udb2adm1).
2. Run the data integrity trigger creation statements:
```
cd trigger_dir
db2 connect to DNIDBRUN
db2 +c -svtd# -z trig.log -f dnirundb_dic.ddl
```

As a data integrity operator run the data integrity checker command build, for example:

dnpdic -build -Djava.security.policy=/var/ftm/swift/v324/run/ftmswift.policy
       -passphrase my_passphrase
       -dsn DNIDBRUN -schema DNI -uid helen -pw helens_password

Maintain the Db2 catalog statistics:
To improve database performance, it is recommended to run the RUNSTATS utility at least for the following table spaces:
- DNIROR
- DNIvMWH if you use message warehouse
- DNIvAUM if you use message audit log

Verify that the data integrity framework was activated correctly:

Log on as a data integrity validator.

Run the check command, for example:

dnpdic -check -Djava.security.policy=/var/ftm/swift/v324/run/ftmswift.policy
       -passphrase my_passphrase
       -dsn DNIDBRUN -schema DNI -uid helen -pw helens_password

The check must finish without reporting problems.

Restart your FTM SWIFT business processes:
1. As a message broker administrator (uwmba1) restart all FTM SWIFT related message flows
2. Restart all sessions and services