Created log file

Contains information about:

Where the log path is set or where the log file is enabled:

debugger_error.log

Debugger errors

log environment variable

ifs.log

Server activities

Server log location setting.

mgerror.log

Magic xpa component errors or when generating the Data Mapper

logs > magic.ini > [MAGIC_ENV]GeneralErrorLog entry*

migration_error.log

Migration process error. This is only created when there are errors.

logs > migration.ini > [MAGIC_ENV]GeneralErrorLog entry*

<project_name>_error.log

Errors from a specific project. These are Magic xpa errors produced by the project’s engine.

In each project's logs > ifs.ini file > [MAGIC_ENV]GeneralErrorLog entry*

mapper.log

Errors that occurred during runtime when Magic xpi executes a Data Mapper step that uses a database. It also gives partial information about the SQL statements sent to the database. Note that the gateway log shows the actual statement.

For more information, see How Do I Create a Gateway Log for the Magic xpi Server?

Activated from the Debugging Flags area of the Settings dialog box or by setting DebugMapper=Y in one of the .ini files.

Before you add the DebugMapper=Y flag to the Magic.ini file, make sure that it is not included in any of the other Magic xpi configuration files. If the flag is included in any of these configuration files, the flag will be overwritten and the file will not be created.

sfdc_logs folder

Shows the specific IDs created when working with the Salesforce connector's Replicate Last Update method.

MDCRM_Debug.log

Dynamics CRM

Activated from the Debugging Flags area of the Settings dialog box or by setting [MAGIC_IBOLT] DebugMDCRMComponent=Y in the ifs.ini file.

DynamicsAX_[PID].log

Dynamics AX 2012

The logs are configured according to the log4net.config file, which is located at <Magic xpi>/config.

Sharepoint_Debug.log

SharePoint

Activated from the Debugging Flags area of the Settings dialog box or by setting [MAGIC_IBOLT] DebugSharepointComponent=Y in the ifs.ini file.

Exchange_Debug.log

Exchange

Activated from the Debugging Flags area of the Settings dialog box or by setting [MAGIC_IBOLT] DebugExchangeComponent=Y in the ifs.ini file.

HL7Debug.log

HL7

Activated from the Debugging Flags area of the Settings dialog box or by setting [MAGIC_IBOLT] DebugHL7Component=Y in the ifs.ini file.

DynamicsCRM_studio_<<process id>>.log

Dynamics CRM

DCRM design time log file is generated under <Magic xpi installation>\Studio\Log folder.

DynamicsCRM_runtime_<<process id>>.log

Dynamics CRM

DCRM runtime log file is generated under <Magic xpi installation>\Runtime\Logs folder.

The configuration related to Log4net can be provided in Log4net.config file which is located under <Magic xpi installation>\Runtime\Config folder.

Created log file

Contains information about:

Where the log path is set or where the log file is enabled:

general_[PID].log

Third-party programs

logback.xml

magicxpi_[PID].log

The space, including processing units and space services

logback.xml

magicxpi-external_[PID].log

Programs external to the space

logback.xml

stderror.log

Errors encountered while accessing Java classes

logback.xml

stdout.log

Provides output messages

logback.xml

mgxpicmdl.log

The command line, including problems encountered when the GSA tries to load the Magic xpi executable via the command line.

logback.xml

To enable logs for Java-based components, update the logback.xml by changing the level value from “off” to one of the other levels. See the Logging Level section below.

exceptions.log

The exceptions that occur in a project.

logback.xml

root.log

All log files inherit their settings from this file. It does not contain information particular to Magic xpi.

logback.xml

ftptrace_[PID].log

FTP and Directory Scanner FTP activity

logback.xml

enterprisedt_[PID].log

FTP connector infrastructure

logback.xml

ifc.scanner_[PID].log

Directory Scanner component

logback.xml

ifc.email_[PID].log

Email component

logback.xml

ifc.googlecalendar_[PID].log

Google Calendar connector

logback.xml

ifc. googledrive_[PID].log

Google Drive connector

logback.xml

ifc.google_[pid].log

Google connectors’ infrastructure

logback.xml

ifc.sapr3_[PID].log

SAP ERP connector

logback.xml or by setting DebugR3Component=Y in the ifs.ini file.

For more information, see How Do I Create Log Files for the SAP R/3 (JCO) Component?

ifc.sapR3Trigger_[PID].log

SAP ERP trigger connector

ifc.sugarcrm_[PID].log

Sugar connector

logback.xml

ifc.WEBSERVICECLIENT_[PID].log

Web Services Client connector

logback.xml

Note that there are additional log files that you can add in the logback.xml. Open up the file and search for the three <!-- other optional modules:--> tags.

Created log file

Contains information about:

Where the log path is set or where the log file is enabled:

[Date~Time]-[GigaSpaces entity]-{computer name}-PID.log

For example: 2013-10-07~14.07-gigaspaces-lus_5-DEBBIES-7-4400.log

The GigaSpaces infrastructure.

The files without the {computer name} can be ignored.

Created log file

Contains information about:

Where the log path is set or where the log file is enabled:

MG_message_err.log

Messaging components

MessagingErrorLogFile environment variable

Created log file

Contains information about:

Where the log path is set or where the log file is enabled:

[database name].log

For example: mssql.log.

A specific database. This log file is defined when manually installing the database.

Created log file

Contains information about:

Where the log path is set or where the log file is enabled:

*.trc

For example: JCO20121109_120458790.trc

SAP ERP and SAP A1 trace logs. You can add extended trace options using the Magic.ini file’s DebugTraceLevel= configuration flag.

Enabled from the SAP ERP resource's SAP Trace setting and from the SAP A1 resource's SAP Trace setting. By default this is set to No.