start_trace_session (SAP CC 4.1 Admin+)

start_trace_session

Definition

To start a tracing session for a specific subscriber account

Command Usage

Syntax

start_trace_session <SUAC_CODE> <SUAC_SERVICE_PROVIDER> [<EXPIRATION_DATE>]

Command Arguments

Name	Description
`<SUAC_CODE>`	The subscriber account code
`<SUAC_SERVICE_PROVIDER>`	The service provider that owns both the specified subscriber account and the pricing catalog of the customer service
`<EXPIRATION_DATE>`	Optional: The expiration date (in the ISO 8601 format: yyyy-MM-ddTHH:mm:ss). It is the current time/date plus one hour if not specified.

Detailed Information

As of SP 1 and as an IT administrator, the start_trace_session command allows you to start a tracing session that arms the targeted tracing function for the next charging operation request that relates to the specified subscriber account. The service operation can come via the Web Services (WS) or the Message TCP technical interface.

The rater instance responsible for the subscriber account will equip the selected operation request with a predefined SAP Passport that includes a computed Transaction ID and the following predefined trace flags: ABAP Trace, ABAP Condens. 1, ABAP Condens. 2, and SAT.

These settings will configure the targeted tracing function to:

increase the trace severity threshold to DEBUG
enable recording the trace messages belonging to the PERF (performance traces) and DATA tracing domains

The rater instance responsible for the specified subscriber account generates the trace messages accordingly.

The tracing session automatically stops after the reception of the first charging operation request or after the specified expiration date. If not set with the command, the default expiration date is the current date plus one hour.

The generated traces contain the SAP Passport Transaction ID and also your SAP CC user logon.

Caution

In a productive SAP CC system, do not use this command, except under the direct supervision of a support specialist from your SAP Support Team.

Notes

The trace sessions are stored in memory in a specific instance. When this instance restarts the trace sessions are not kept.
The trace sessions relate to a targeted data object in master data. If the partition map changes and the subscriber account data is handled by another instance, then the running trace session will not trigger the targeted tracing any longer.
The number of trace sessions is limited to 100 sessions per instance in the SAP CC system. When the limit is reached, the oldest session is discarded.
Only a specific set of operations on the subscriber account triggers the targeted tracing. These service operations are: charging, blank charging, and session-based charging.
The SAP Passport is active for the thread that process the request until the request ends and so is also used for other processing activities in the same thread such as other requests without time out configured in the stateful service client implemented in your mediation system or client application.
The recording of traces impacts the global performances of the SAP CC system and may lead to business errors (charging operations not replied on time, response time increase, throughput decrease). These business errors relate both to the operations in the scope of the active targeted tracing but also to all other business operations in progress.

Troubleshooting Operations (Performance)

During the implementation project or the production operation phase, you use this command to troubleshoot performance problems with the charging operations and charging logic execution that relate to a particular provider contract (or subscription).

Refer to the SAP CC Operations Guide to know how to use the tracing tools and performance traces.

Authorization

You must have a specific role in your SAP CC user profile. Refer to the SAP CC Security Guide for more information about the necessary authorizations.

Additional Information

Consult the SAP CC Application Help for more information about the targeted tracing function, the SAP Passport management, and the performance traces.

Messages

Code	Message	Action
invalidArgument	Error: This command requires at least two arguments.
invalidExpirationDateFormat	Error: The specified expiration date does not respect the ISO 8601 format (yyyy-MM-ddTHH:mm:ss): {date}.
invalidExpirationDate	The specified expiration date must be after the current date of the machine that hosts the targeted rater instance: {exception}.	Change the expected expiration date or verify the current date of the SAP CC system hosts.
subscriberAccountDoesNotExist	The specified subscriber account does not exist in the master data owned by the specified contracting service provider: {exception}.	Verify that both command arguments are correct and that the subscriber account exist in the master data owned by the contracting service provider.
interInstanceComm	Error while attempting to communicate with the rater instance: {exception}.
passportTransactionId	The Transaction ID set in the SAP Passport is: {passportTransactionId}.
raterInstanceId	The rater instance ID for the specified subscriber account is: {raterInstanceId}.