MobiLink server logging and SAP Passports

The MobiLink server supports the use of SAP Passports to trace requests from the client through to the backend server.

When a MobiLink client connects using HTTP or HTTPS and the SAP-PASSPORT HTTP header is present, the MobiLink server does the following:

Extracts and interprets the SAP passport.
Issues an error if the passport is malformed.
Appends the passport key information to all of the MobiLink server log lines related to the connection. Passport information is separated from other log output with a hash tag (#) character.
Respects the tracing level in the passport and adjusts the log details for that connection accordingly.

MobiLink clients send an SAP Passport by using the custom_header MobiLink client network protocol option, for example:

"host=myhost.mycorp.com;custom_header=SAP-PASSPORT: 2A54482A03010D890A5341505F4532455F54415F506C7567496E20202020202020202020202020202000005341505F4532455F54415F5573657220202020202020202020202020202020205341505F4532455F54415F526571756573742020202020202020202020202020202020202020202000055341505F4532455F54415F506C7567496E202020202020202020202020202020343633353030303030303331314544304141463544433135443530433146373520202000074635000000311ED0AAF5DC15D50BFF750000000000000000000000000000000000000000000100E22A54482A0100270100020003000200010400085800020002040008300002000302000B000000002A54482A"

The suffix shown in the MobiLink server log for the passport shown above appears as:

#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

The information in the log file varies for each passport. Following is an explanation of the field values for the example above.

Field value	Description
SAP-PPK	Start of passport suffix
V3	SAP passport version
4635000000311ed0aaf5dc15d50c1f75	Transaction ID (unique to each passport)
4635000000311ed0aaf5dc15d50bff75	Root context ID, used to group related passports (unique to each group)
00000000000000000000000000000000	Connection ID, used to distinguish related passports (unique to each connection)
0	Connection counter, used to distinguish related passports

Example

Here is an example of how a MobiLink synchronization might be logged when it contains an SAP Passport:

I. 2014-02-04 16:11:37. <15> Request from "UL 17.0.0000" for: remote ID: 12d88b1b-930b-46ba-ad60-2422ff3830f4, user name: ulhttp02, version: ulhttp02#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> Table #1: ulhttp02, 2 columns#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> rid integer NOT NULL PRIMARY KEY#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> cint integer#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> Table 'ulhttp02' is referenced by publication 'ul_default_pub'#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> The current synchronization is using a connection with connection ID 'SPID 9'#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> Publication #1: ul_default_pub, subscription id: 1, last download time: 2014-02-04 16:11:37.790000#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> The sync sequence ID in the consolidated database: 041990d3fc7b4af8a8440065ef46de3b; the remote previous sequence ID: 041990d3fc7b4af8a8440065ef46de3b, and the current sequence ID: 553e4d716a574ca48c31dc46da1f14db#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> Log Level: 2#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> COMMIT Transaction: Begin synchronization#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> COMMIT Transaction: Upload#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> COMMIT Transaction: Prepare for download#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> Next last download timestamp fetched from the consolidated database is "2014-02-04 16:11:37.807000"#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> Insert/Update row [ulhttp02]:#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15>   -1#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15>   -2#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> Insert/Update row [ulhttp02]:#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15>   -2#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15>   -3#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> Insert/Update row [ulhttp02]:#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15>   -3#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15>   -4#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> Sending the download to the remote database#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> COMMIT Transaction: Download#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> COMMIT Transaction: End synchronization#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0

I. 2014-02-04 16:11:37. <15> Synchronization complete#SAP-PPK#V3#4635000000311ed0aaf5dc15d50c1f75#4635000000311ed0aaf5dc15d50bff75#00000000000000000000000000000000#0