Entering content frameBackground documentation Access Logs Locate the document in its SAP Library structure

Access logs contain information about Internet Transaction Server (ITS) service usage.

This information allows you to check how many requests have been made to a service and helps you to identify illegal requests made to the site by unauthorized users.

Access logs are stored on your hard disk in files called access.log (or access_*.log in the case of archived files) under:

C:\program files\sap\its\2.0\<ITS instance>\logs

There is one entry for each request processed by the AGate component of the ITS and each entry can contain the following information:

Information

Description / Possible Values

Entry type

(blank)

No problem detected by the ITS.

w

Warning entry.

Usually issued when the ITS denies access to a session with an invalid session ID due to an invalid random part.

a

Alert entry.

Usually issued when access was attempted with an invalid session ID.

Entry date

Request date.

For example, 2000/05/19 .

Entry time

Request time.

For example, 19:43:56.125 .

This is the local machine time, which includes milliseconds.

AGate instance number

Numbering starts at 0 .

Reqest sequence number since last ITS restart

This number is preceded by the prefix # .

For example, #16 .

IP address of the remote host that issued the request

The address is preceded by the prefix IP .

For example, IP 207.104.133.171 .

If the IP address cannot be determined, or the entry was created due to an ITS action, this value is set to ???.???.???.??? .

Request-specific information

Depending on the entry type, the ITS appends additional information here. See below for details.

Error Entries

If an access error occurs, the ITS may append error messages to the general information.

Example

A log file entry for an error like attempted access with invalid random key 264fc4da could look similar to the following:

w 2000/05/19 19:43:56.125: 0 #16: IP 207.104.133.171,
access with invalid random key: 264fc4da

Command Execution Entries

Whenever a command is executed in response to a ~command=<command> in the request URL, the ITS logs the command name.

Example

A log file entry for ~command=fieldDump could look similar to the following:

2000/05/19 19:45:22.625: 0 #56: IP 207.104.133.171,
command fieldDump

Session Entries

The ITS logs each request to a service or session with the following details:

Request

Value

Start a service or session

*<service name>

Stop a service or session

+<service name>

Access a running service or session

<service name> (no leading * or + )

Timeout of a service or session

–<service name>

The service name of each entry is followed by the user account name for the session.

Example

A log file entry for starting the service paw1 under the user account CONSUL could look similar to the following:

2000/05/19 19:45:47.750: 0 #58: IP 207.104.133.171, *paw1, CONSUL

To define the handling of access log files or change the location of the logs directory, see Setting Log File Parameters.

Leaving content frame