SXMB_ADM RUNTIME parameter.....difference bw LOGGING and TRACE_LEVEL

[Former Member]

In SXMB_ADM configuration,

RUNTIME paramaters, what is the difference between

LOGGING and TRACE_LEVEL,

my requirement is to see all the synchronous messages(in all Pipeline Steps),

in SXMB_MONITOR,

what parameter i should switch on exactly.....

moreover the system is production..........means i cant do anything experimentally...

pls help me ...and if possible provide me some link to documents

[Former Member · Accepted solution]

hi,

These may help you

Pls check this conversation:

This Michal's weblog may help you---Personalized logging & tracing

/people/michal.krawczyk2/blog/2007/04/30/xipi-personalized-logging-tracing

Ram

[former_member614185]

Hi,

Check out this thread,

[Former Member]

hi,

how can i set the logging and trace_level in the message header,

?????

[Former Member]

Hello Sudeep,

you dont need to set the logging in message header. Just go to integration engine configuration and set the logging_sync property.

As mentioned earlier .. logging and trace_level is not relevant in your case.

If you need further clarifications reply back..

Regards,

Sumit

[Former Member]

Sumit,

as advised my many,

how can trace_level and logging paramters can be set in the Message_header manually

thanks

[Former Member]

Hi Sudeep,

Check this link..

http://help.sap.com/saphelp_nw04/helpdata/en/d6/49543b1e49bc1fe10000000a114084/frameset.htm

Regards,

Sumit

[Former Member]

Hi Sudeep,

To see the synch messages use the following add the following parameter..

LOGGING_SYNC and give the value as 1. No other parameter is required in your case. Trace_level is by default set to 1.

Logging is to enable logging of xml messages. Trace_level is the level of trace within all the pipeline steps of an xml message.

Regards,

Sumit

<b>Copied from help..</b><i>Parameter LOGGING

Meaning

The parameter LOGGING enables you to locally activate the logging of asynchronous messages for all pipelines of an Integration Engine.

If logging is deactivated, you can reactivate it for particular pipeline services by using the corresponding subparameters. You can select the relevant pipeline services from the input help. Logging of the asynchronous message takes place after the service has been executed.

You can also reactivate logging by using a message. In this case the logging tag in the diagnostic header of the message must be set to 1.

Usage

You set this parameter when you want to analyze message processing as it enables you to document either individual steps or all steps in a pipeline.</i>

<i>Parameter TRACE_LEVEL

Meaning

The parameter TRACE_LEVEL enables you to locally set the trace level for all pipelines in an Integration Engine.

However, the diagnostic header of a message can specify the trace level at which it is to be processed. Runtime then uses the higher of the local trace level and the message trace level.

Usage

You set this parameter when you want to analyze message processing as it enables you to document either individual steps or all steps in a pipeline.

Possible Values

0 Trace deactivated

1 Document important processing steps

2 Document important processing steps and details

3 Document all processing steps and details</i>