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: Glossary

Sample Data Encryption Properties File

Sample Data Encryption Properties File

The
Resource Kit
includes a sample data encryption properties file,
dataencription.properties
.
The sample data encryption properties file is in the following directory:
On UNIX.
<
infamdm_install_dir
>/hub/resourcekit/samples/DataEncryption/resources
On Windows.
<
infamdm_install_dir
>\hub\resourcekit\samples\DataEncryption\resources
The following example shows the contents of the sample data encryption properties file:
# This is an example of dataencryption.properties file. # File contains encryptor configuration and different parts of product which should be aware of data encryption # # Encryptor implementation # # main class which implements DataEncryptor interface. If this option is empty encryption is turned off. mainClass=com.informatica.dataencryption.sample.InformaticaDataEncryptor # # Part 1. EjbSiperianClient configuration. # # List of API.<ORS_ID>.<BASE_OBJECT_NAME>.<COLUMN_NAME> which should be encrypted before sending out # and decrypted on return back by EjbSiperianClient. # API.orcl-MDM_SAMPLE.BASE_OBJECT.C_PARTY.DISPLAY_NAME=true API.orcl-MDM_SAMPLE.PACKAGE.PKG_PERSON_IDD_SEARCH.DISPLAY_NAME=true API.orcl-MDM_SAMPLE.PACKAGE.PKG_ORG_IDD_SEARCH.DISPLAY_NAME=true API.orcl-MDM_SAMPLE.HISTORY.C_PARTY.DISPLAY_NAME=true API.orcl-MDM_SAMPLE.XREF.C_PARTY.DISPLAY_NAME=true API.orcl-MDM_SAMPLE.HM_ENTITY_TYPE.Organization.DISPLAY_NAME=true # # Part 2. Cleanse functions. # # List of input and output port of cleanse functions which should take and produce encrypted data. # CLEANSE.firstNameInput=true CLEANSE.firstNameOutput=true # # Part 3. Match Fields # # List of MATCHFIELD.<ORS_ID>.<BASE_OBJECT_NAME>.<MATCH_FIELD_NAME> # The server will decrypt this match field automatically before get_ranges, get_keys, and get_match. MATCHFIELD.orcl-MDM_SAMPLE.C_PARTY.ORGANIZATION_NAME=true

0 COMMENTS

We’d like to hear from you!