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 REST API
  10. Data Integration Service Applications
  11. Enterprise Data Preparation Service
  12. Interactive Data Preparation Service
  13. Informatica Cluster Service
  14. Mass Ingestion Service
  15. Metadata Access Service
  16. Metadata Manager Service
  17. Model Repository Service
  18. PowerCenter Integration Service
  19. PowerCenter Integration Service Architecture
  20. High Availability for the PowerCenter Integration Service
  21. PowerCenter Repository Service
  22. PowerCenter Repository Management
  23. PowerExchange Listener Service
  24. PowerExchange Logger Service
  25. SAP BW Service
  26. Search Service
  27. System Services
  28. Test Data Manager Service
  29. Test Data Warehouse Service
  30. Web Services Hub
  31. Application Service Upgrade
  32. Appendix A: Application Service Databases
  33. Appendix B: Connecting to Databases from Windows
  34. Appendix C: Connecting to Databases from UNIX or Linux
  35. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

Rules and Guidelines

Rules and Guidelines

Refer to the rules and guidelines to use the Data Integration Service REST API.
Consider the following general rules and guidelines when you use the Data Integration Service REST API:

General Rules and Guidelines

  • The timezone attribute accepts values only from java.time.ZoneID(). For example, IST is not supported.
  • Passwords that are encrypted using the pmpasswd utility must be encrypted using the option
    -e=CRYPT_DATA
    .
  • Query parameters are not case sensitive.
  • When you define enumeration data type, don't use white space. The enumeration data type is case-sensitive.
  • Reserved characters in older clients must be percent-encoded.
  • When you compare two mappings that are different, the compare report shows the internal descriptions of the data types.
  • When you compare two mappings that are different and contains Java transformations, the compare report shows Java Bytecode, byte code length as Java.bytecodeLen, and checksum as Java.checkSum.
  • When you compare two mappings and use Blaze as the execution environment, the compare report shows engine as CADIYarnExecutionEngine instead of Blaze.

Application Patch Rules and Guidelines

  • When you deploy objects to an application patch archive file, the default location of the file is $INFA_HOME/tomcat/bin/target. If the Data Integration Service is configured to use operating system profiles and you specify the operating system profile, the archive file is written to $DISTargetDir instead.
  • When you deploy objects to an application patch archive file, you can specify mapping deployment properties to override the default mapping deployment properties. Specify each mapping deployment property as a name-value pair. For information about the mapping deployment properties, see the
    Informatica Developer Tool Guide
    .
  • When you deploy objects to an application patch archive file, the result of the query must contain at least one object that can be run, such as a mapping.
  • When you deploy objects to an application patch archive file and use the archive to deploy the application to another domain, the archive files must be saved to a shared disk location.