|
|
|
|
DebugMapper=
|
This flag makes it easier for you to debug the Data Mapper.
When this setting is switched on (DebugMapper=Y) in the ifs.ini file, a log file called mapper.log is created in the logs directory if Magic xpi executes a Data Mapper step using the server.
This log file contains runtime information about the Data Mapper’s database Sources and Destinations only.
Before you add the DebugMapper=Y flag to the Magic.ini file, make sure that it is not also included in the ifs.ini file. If the flag is also included the ifs.ini file, the flag will be overwritten and the file will not be created.
|
|
DebugMDCRMComponent=
|
This flag makes it easier for you to debug the Dynamics CRM connector.
When this setting is switched on (DebugMDCRMComponent=Y) in the ifs.ini file, a log file called MDCRM_Debug.log is created in the logs directory if Magic xpi executes a Dynamics CRM step using the server.
|
|
DebugSharepointComponent=
|
This flag makes it easier for you to debug the SharePoint connector.
When this setting is switched on (DebugSharepointComponent=Y) in the ifs.ini file, a log file called Sharepoint_Debug.log is created in the logs directory if Magic xpi executes a SharePoint step using the server.
|
|
DebugExchangeComponent=
|
This flag makes it easier for you to debug the Exchange connector.
When this setting is switched on (DebugExchangeComponent=Y) in the ifs.ini file, a log file called Exchange_Debug.log is created in the logs directory if Magic xpi executes an Exchange step using the server.
|
|
DebugR3Component=
|
This flag makes it easier for you to debug the SAP R/3 connector.
When this setting is switched on (DebugR3Component=Y) in the ifs.ini file, two log files are created in the logs directory if Magic xpi executes a SAP R/3 step using the server. These files are called ifc.sapr3.log (for SAP R/3 steps) and ifc.sapr3Trigger.log (for SAP R/3 triggers).
|
Note:
|
You can also debug the SAP R/3 connector by changing the debug level in the log4j.xml file. For more information on how to do this, see this topic.
|
|
|
DebugSFDCComponent=
|
This flag makes it easier for you to debug the Salesforce connector.
When this setting is switched on (DebugSFDCComponent=Y) in the ifs.ini file, a log file called SFDC_Debug.log is created in the logs directory if Magic xpi executes a Salesforce step using the server.
|
Note:
|
When working with the Salesforce connector's Replicate Last Update Method, the sfdc_logs folder is created under the logs folder to show the specific IDs that were created.
|
|
|
DebugHL7Component=
|
This flag makes it easier for you to debug the HL7 component.
When this setting is switched on (DebugHL7Component=Y) in the ifs.ini file, a log file called HL7Debug.log is created in the logs directory if Magic xpi executes an HL7 step using the server.
|
