Table of Contents

Search

  1. Preface
  2. Understanding PowerExchange for Microsoft Dynamics CRM
  3. PowerExchange for Microsoft Dynamics CRM Configuration
  4. Microsoft Dynamics CRM Connections
  5. Microsoft Dynamics CRM Data Objects
  6. Microsoft Dynamics CRM Mappings
  7. Microsoft Dynamics CRM Run-time Processing
  8. Appendix A: Microsoft Dynamics CRM and Transformation Data Types

PowerExchange for Microsoft Dynamics CRM User Guide

PowerExchange for Microsoft Dynamics CRM User Guide

Properties.conf Configuration

Properties.conf Configuration

You can use the properties.conf file to change the number of retry counts and intervals while creating a connection. You can change the number of partitions for Microsoft Dynamics online deployment that can be set during bulk load. You can also change the default location of the login.conf and kerberos.conf file.
The properties.conf file must be present in the following location:
Server
<Informatica Installation Directory>\tomcat\bin\msdcrm\conf
Client
<Informatica Installation Directory>\clients\DeveloperClient\msdcrm\conf
The following are the default property keys and values. You can edit the following values:
  • RETRY_COUNT=5
  • RETRY_INTERVAL=1000
  • RETRY_COUNT_FOR_BAD_CONTEXT_TOKEN_RESPONSE=5
The following are the descriptions of the property keys:
  • RETRY_COUNT: Defines the number of times to retry if the connection request fails. You can set this property to work at design-time and run-time.
  • RETRY_INTERVAL: Defines the interval in milli seconds between two retry attempts. Default is 1000.
  • RETRY_COUNT_FOR_BAD_CONTEXT_TOKEN_RESPONSE: Defines the number of times to retry if the IIS fails.
  • MAX_CLOUD_PARTITIONS: The number of partitions that can be defined for online deployment of Microsoft Dynamics CRM. During bulk load, you can set this property to work at run-time.
  • KERBEROS_CONFIG_FILES_LOCATION: The default location of the login.conf and krb5.conf files. You can set this property to work at design-time and run-time. The location of the configuration file and the Kerberos configuration file specified at run-time will take precedence.

0 COMMENTS

We’d like to hear from you!