Configuring Logging in the Installation Directory

:
<appender name="Product.ActiveTransfer"
class="org.apache.log4j.►
RollingFileAppender">
<param value="
Integration Server_directory
\profiles\IS_default\logs\►
ActiveTransfer.log" name="file"/>
<param value="10MB" name="MaxFileSize"/>
<param value="10" name="MaxBackupIndex"/>
<layout class="com.webmethods.sc.logging.log4j.
AlignedG8dEventLayout"/>
</appender><logger name="com.softwareag.mft"
additivity="false">
<level value="info"/>
<appender-ref ref="Product.ActiveTransfer"/>
</logger>

<param value=" Integration Server_directory \profiles\IS_default\logs\ActiveTransfer.log" name="file"/>
	Provides the log file location and log file name. Make the following modifications: In place Integration Server_directory , specify the exact Integration Server installation directory, or provide any other location of your choice for the log file. If required, you can modify the default log file name, ActiveTransfer.log, to a file name of your choice.
<level value="info"/>
	Is the default log level. You can modify it, if required. The possible log levels are: fatal: Severe errors that might cause ActiveTransfer to abort. error: Errors that caused during the execution of ActiveTransfer operations. info: Informational messages about ActiveTransfer events. warn: Non-critical errors that might potentially lead to unexpected results. debug: Debug information for errors and analysis. trace: Trace information for analysis. off: Turn off logging. If you turn off logging important log messages are not logged. Not recommended at the global level. Note: If you use off, important log messages are not logged. Software AG does not recommend its use at the global level. trace and debug log levels will result in large amount of log messages for analysis.

Note:
If you omit the next step, the global setting for the log level is applied to all modules unless you set the log modules from the user interface. For details on how set up audit logging for modules or sub-modules from the user interface, see Setting Up Audit Logging from the My webMethods User Interface.

ActiveTransfer Module	Possible Module and Sub-Module Values
Ports	com.softwareag.mft.port com.softwareag.mft.port.ftp com.softwareag.mft.port.sftp com.softwareag.mft.port.http com.softwareag.mft.port.message
Event	com.softwareag.mft.event
Remote Server Session	com.softwareag.mft.external.session com.softwareag.mft.external.session.ftp com.softwareag.mft.external.session.sftp com.softwareag.mft.external.session.http com.softwareag.mft.external.session.file
Asset Management	com.softwareag.mft.asset
Common Framework	com.softwareag.mft.common
Database	com.softwareag.mft.database
Tunnel	com.softwareag.mft.acceleration
ActiveTransfer Gateway	com.softwareag.mft.gateway
Security	com.softwareag.mft.security

The messages related to the communication between ActiveTransfer Server and ActiveTransfer Gateway are logged in the com.softwareag.mft.port and com.softwareag.mft.external.session.http modules in ActiveTransfer Gateway. The log level used to store these messages is debug.

The messages related to the communication between an external client and ActiveTransfer Server/ActiveTransfer Gateway are logged in the com.softwareag.mft.port.message module. These messages include commands interchanged, response to commands, and HTTP(S) request and response headers. The com.softwareag.mft.port.message module is also used to log messages related to the communication between ActiveTransfer Server and ActiveTransfer Gateway in ActiveTransfer Server. The log level used to store these messages is debug.