Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Step 2. Configure the Data Encryption Properties File

Step 2. Configure the Data Encryption Properties File

Informatica provides a sample data encryption properties file that includes the parameters that the data encryption implementation requires. You can customize the sample properties file to specify the options for the data encryption implementation.
  1. Find the
    dataencryption.properties
    file in the following directory:
    On UNIX.
    <
    ResourceKit_install_dir
    >/DataEncryption/resources
    On Windows.
    <
    ResourceKit_install_dir
    >\DataEncryption\resources
  2. Create a backup copy of the
    dataencryption.properties
    file.
  3. Use a text editor to open the file and edit the data encryption parameters.
  4. Provide a reference to the DataEncryptor interface implementation.
  5. Configure EJBSiperianClient to encrypt and decrypt base object columns that have sensitive data, their associated tables such as history and cross-reference tables, and packages.
    Use the following syntax to specify the base object column names, the associated tables such as history and cross-reference tables, and packages:
    API.<
    ORS_ID
    >.BASE_OBJECT.<
    BASE_OBJECT_NAME
    >.<
    COLUMN_NAME
    > API.<
    ORS_ID
    >.XREF.<
    CROSS_REFERENCE_TABLE_NAME
    >.<
    COLUMN_NAME
    > API.<
    ORS_ID
    >.HISTORY.<
    HISTORY_TABLE_NAME
    >.<
    COLUMN_NAME
    > API.<
    ORS_ID
    >.PACKAGE.<
    PACKAGE_NAME
    >.<
    COLUMN_NAME
    > API.<
    ORS_ID
    >.HM_ENTITY_TYPE.<
    HIERARCHY_MANAGER_ENTITY_NAME
    >.<
    COLUMN_NAME
    >
  6. If you want to use fuzzy match and fuzzy search operations, specify the match fields to use.
    Use the following syntax to specify a match field name:
    MATCHFIELD.<
    ORS_ID
    >.BASE_OBJECT.<
    BASE_OBJECT_NAME
    >.<
    MATCH_FIELD_NAME
    >
    Ensure that the base object that you specify is the base object that you are matching on, which is the root of the match path component. Even where match field is from a base object that is not the root of the match path component, specify the base object that is the root of the match path component.
    If a match field is a concatenation of multiple columns, you must encrypt each of these columns even if the columns do not contain data.
  7. Configure the input and output ports of cleanse functions that must encrypt and decrypt data.
    Use the following syntax to specify the input and output ports of cleanse functions:
    CLEANSE.<
    PORT_NAME
    >=true
  8. Save the properties file with the same name,
    dataencryption.properties
    .

0 COMMENTS

We’d like to hear from you!