End to End Tracing

(Optional) End to end tracing enables an application developer and end user to trace a request that is sent from the client to the back-end. This spans the entire landscape where you can derive a correlation of traces at the client, server and back-end.

These correlated traces help in performance analysis and are centrally monitored on SAP Solution Manager. These are displayed as reports where you can extract information on failure of delivering a request, time taken for a request to reach a component and so on.

On the client side, the client framework enables an application developer to switch on the trace for messages. The client traces the request at predefined points and all these transactions/requests are recorded in a Business Transaction XML. Additionally, the client maintains a unique identifier in the HTTP header called the SAP Passport that is used to correlate traces across various components. This Business Transaction XML can later be uploaded to the SAP Solution Manager which is a central location to correlate all logging information.

The end to end tracing APIs are available in the SMPClientConnection class.

Note:

For end to end logs to be added to the SAP Solution Manager, configure the Solution Manager URL in SAP Control Center. For more information, see Configuring SAP Solution Manager URL in SAP Control Center for SAP Mobile Platform.
Ensure that the user is selected under domain logs of SAP Control Center to enable any end to end logs.

Syntax

Use the setTraceLevel API to set the trace level in the SAP-PASSPORT and BTX . The trace level can be set to E2EHIGH (3), E2EMEDIUM (2), E2ELOW (1), or NONE.
```
-(void)setTraceLevel:(E2ELevel)value_in;
```
Note: If the trace level is not set using the API, trace level 3 is automatically chosen.
Use the startTrace API to start end to end tracing on the client.
```
-(void)startTrace;
```
Use the stopTrace API to stop end to end tracing on the client.
```
-(void)stopTrace;
```
Use the uploadTraceWithUserName API to generate BTX on the client, and upload the BTX to Solution Manager via the SAP Mobile Platform server.
```
-(void)uploadTraceWithUserName:(NSString*)username passWord:(NSString*)password
        error:(NSError**)error;
```

Examples

Enabling end to end tracing –

 SMPClientConnection* clientConn = [SMPClientConnection initializeWithAppID:@"com.sap.NewFlight" domain:@"default"
 secConfiguration:@"SSO"];
 [clientConn setConnectionProfileWithUrl:@"http://dewdf30185.wdf.sap.corp:8000"]; 

 //Successfully onboard the user 

 [clientConn setTraceLevel:E2EHIGH];
 [clientConn startTrace]; 

 //Perform request response 

  [clientConn stopTrace]; 
  NSError* _uploadError = nil; 
  [clientConn uploadTraceWithUserName:@"supuser" passWord:@"s3puser" error:&_uploadError];
   if(_uploadError)   
 {           
 NSLog(@"BTX UPLOAD ERROR: %@",_uploadError);
 }