Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service Applications
  10. Interactive Data Preparation Service
  11. Enterprise Data Preparation Service
  12. Informatica Cluster Service
  13. Mass Ingestion Service
  14. Metadata Access Service
  15. Metadata Manager Service
  16. Model Repository Service
  17. PowerCenter Integration Service
  18. PowerCenter Integration Service Architecture
  19. High Availability for the PowerCenter Integration Service
  20. PowerCenter Repository Service
  21. PowerCenter Repository Management
  22. PowerExchange Listener Service
  23. PowerExchange Logger Service
  24. SAP BW Service
  25. Search Service
  26. System Services
  27. Test Data Manager Service
  28. Test Data Warehouse Service
  29. Web Services Hub
  30. Application Service Upgrade
  31. Appendix A: Application Service Databases
  32. Appendix B: Connecting to Databases from Windows
  33. Appendix C: Connecting to Databases
  34. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Environment Variables for MapR

Environment Variables for MapR

When the MapR cluster is secured with MapR Kerberos authentication, edit PowerCenter Integration Service properties to enable communication between the Informatica domain and the cluster.
The following table describes properties to define the Kerberos authentication protocol:
Property
Value
JAVA_OPTS
-Dhadoop.login=<MAPR_ECOSYSTEM_LOGIN_OPTS> -Dhttps.protocols=TLSv1.2
where <MAPR_ECOSYSTEM_LOGIN_OPTS> is the value of the MAPR_ECOSYSTEM_LOGIN_OPTS property in the file
/opt/mapr/conf/env.sh
.
MAPR_HOME
Hadoop distribution directory location on the machine that runs the Data Integration Service.
For example,
<Informatica installation directory>/services/shared/hadoop/mapr_5.2.0/lib/*
MAPR_TICKETFILE_LOCATION
Optional. Directory where an additional MapR Ticket file is stored on the machine that runs the Data Integration Service.
When the MapR cluster is configured to enable a user to use Kerberos authentication and MapR Ticket authentication, generate a MapR ticketfile for the user for each authentication mode. Save one ticketfile in
/tmp
. Save the other ticketfile in any directory on the Data Integration Service machine, and provide the location as the value for this property.
For example, for a user id 1234, save a MapR ticketfile named like
maprticket_1234
in
/tmp
, and save another MapR ticketfile named like
maprticket_1234
in the MAPR_TICKETFILE_LOCATION.
The ticketfiles can have the same or different names. You must generate the MapR ticketfiles separately and save one to the MAPR_TICKETFILE_LOCATION.
Changes take effect when you restart the PowerCenter Integration Service.