B2B Integration 10.2 | Administering and Monitoring B2B Transactions | Managing File Transfers with ActiveTransfer | Managing and Viewing Log Information | Configuring Logging in the Installation Directory
 
Configuring Logging in the Installation Directory
Pre-requisites: The relevant ActiveTransfer fix version is installed.
Use this procedure to configure the log file name, log file location, and logging levels on both the ActiveTransfer Server and ActiveTransfer Gateway. If you omit this configuration, all log entries are made in the default log file sag-osgi.log, which is available in the Integration Server_directory \profiles\IS_default\logs directory.
* To configure ActiveTransfer logging
1. In ActiveTransfer Server installation, navigate to the following directory:
Integration Server_directory \IS_default\configuration\logging
2. Using a text editor, open the log_config.xml file.
3. Follow these steps to configure the log appender, which specifies the log file name, log file location, and global log level:
a. Add the following entry:

<!-- Standard Log4j appenders -->:
<appender name="Product.ActiveTransfer" class="org.apache.log4j.►
Rolli​ngFile​Appender">
<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>
b. In the log appender, make suitable modifications to the log file name, log file location, and global log level:
<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.
*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.
4. Add the following logger entries for all relevant modules and sub-modules:
<logger name="com.software.mft.module.sub-module">
<level value="info"/>
</logger>
Where, module or sub-module can be:
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
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
Example:
To get trace level logs for all FTP user sessions, add the following logger entry:
<logger name="com.softwareag.mft.external.session.ftp">
<level value="trace"/>
</logger>
5. Repeat the procedure in the ActiveTransfer Gateway installation.
Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.