Setting Up Logging for Outbound Requests

1. Enter a URL prefix for which the log handler is to be called.
   For example, "/"
2. Enter a name for the log file. The name must be different to the name of the log file for inbound requests. The same log file cannot be used for both inbound and outbound requests. The ICM checks at each restart whether the file specified as the log file exists. If a file with this name exists, it will write in this file. If no file with this name exists, a new file is automatically created with this name. Operating system specifications must be considered when assigning a name. For example, in Windows colons are not permitted in file names. You can add another timestamp to the file name. The options below are available for specifying the log file.

   %d	Day of the month (1-31)
   %m	Month (1-12)
   %y	Year, in the format YYYY
   %h	Hour (0-23)
   %t	Minute (0-59)
   %s	Second (0-59)
   %%	% character

The following steps are optional.

3. Select or define with LOGFORMAT a log format in which entries are written to the log file.
4. With FILTER enter a filter. The attribute filter has the following syntax: FILTER= {name}typ[={wert}] [ ; {name}type[={wert}] ] .... There are also predefined filters: SAPSMD. This has the form {X-CorrelationId}i. If this predefined filter is set, only requests that contain header field X-CorrelationId are logged. The filter is independent of the selected log file format. Specification of a value is optional. If no value is specified, the existence of the field is checked. By preceeeding the name or value of the field with an \, the characters '=', '}', and '\' can be escaped. The attribute filter has the following syntax:
   The filter property specifies that an HTTP request is logged only when a certain header field (for example, an HTTP header field) is in the request or response. A filter can contain the following fields:

   • {name}i[={value}]

     Filter for a request header field, e.g. {X-Correlation-ID}i.

   • {name}o[={value}]

     Filter on a response header field.

   • {name}c[={value}]

     Filter on a request cookie.

   • {name}F[i][={value}]

     Filter on a request form field, e.g.. {color}F={green} or {color}Fi={green} .

   • {name}E[i][={value}]

     Filter on a request semicolon field.

5. With MAXSIZEKB you can select the maximum size of the log file in kilobytes.
   If this size is exceeded, the current file is closed and a new one (with a new name) is opened. The new file name is unique (this is achieved by specifying time and date fields, see above), or else is made unique by adding _xx to the end (where xx is a number increasing from 0).
6. With SWICTHTF you can configure that a new log file is created at the times specified.

   Hour	A new log file is opened every hour.
   Day	A new log file is opened every day.
   Month	A new log file is opened every month.

7. With FILEWRAP you can configure whether the old log file is overwritten or a new one created.

   If you set FILEWRAP=on, every time a new file is opened (because time or size is exceeded), the existing log file is reset and overwritten. Therefore, there is always only one log file with the current log data.

   If you omit this option, the old log file is not overwritten, and a new one is created.

8. With FLUSH you specify whether each HTTP log entry is written directly to the file system, or not. Possible values are TRUE and FALSE. The default value is FALSE, except for LOGFORMAT=SAPSMD and LOGFORMAT=SAPSMD2.
   This option can cause a reduction in performance on slow file systems.
9. You can specify whether the preceding job must complete successfully or not. Set ACTIVE to TRUE to activate the log handler, or to FALSE to deactivate it. The default value is TRUE.