What is exactly the meaning of TRACE_LEVEL_PROPAGATION ?

[Former Member]

Hi,

I have received recommendation from Early Watch Alert to set TRACE_LEVEL_PROPAGATION = 1 (Currently = 0), I am still couln't understand what is the purpose, set o 1 meaning activate the trace ? would that impact on the performance ?

any advise.

Thank You and Best Regards

Fernand.

[naveen_chichili · Accepted solution]

Hi Fernand,

TRACE_LEVEL_PROPAGATION "1" is to enable the trace of messages where you can trace the details flow for better analysis.

Coming to Impact if this is enabled <set to "1"> for a long time the file system space would pileup and may lead to memory constraints.

Best suggestion is to enable when ever required and change back if not required.

Regards,

Naveen.

[Former Member]

Dear All,

Thank you for all your response. As far as performance concert base on the feedback, I need to turn on the TRACE_LEVEL_PROPAGATION = 1 in the even tracing details is required for interface analysis.

for normal production environment I should deactivate the to 0.

Please correct me if i am wrong.

Thank You and Best Regards

Fernand.

[marksmyth]

Hello

Go to trx sxmb_admin

-> Integration Engine Configuration

-> Configuration

-> (Category) Runtime

-> click on the information button

You will find an explanation for most of the parameters by following these steps.

Regards

Mark

[baskar_gopalakrishnan2]

>what is the purpose

Setting this parameter Trace_Level_Propagation will enable mesg processing tracing in all pipeline steps of Integration Engine.

>set o 1 meaning activate the trace ? Yes

>would that impact on the performance ? Should not give big impact. If you want you can roll back to deactivate after log tracing.

[former_member472138]

Trace Level

*************

The parameter Trace level enables you to logically set the trace level for all pipelines in an

Integration engine, to show the error/success messages.

The trace levels 0 to 3 are associated with the trace levels info, warning, and debug

0 - no trace

1-addwarning

2-addWarning()and addInfo()

3-addWarning()and addInfo()and addDebugMessage().

For the production system we set the tacelevel 1, For quality system we set the trace level 3, because

we should perform test in the maximum ways.

http://help.sap.com/saphelp_nw70/helpdata/en/c8/98e7d5c1620642973565ea3dd319d1/content.htm

http://help.sap.com/bp_bpmv130/Documentation/Operation/XIadministration.pdf -

---

Read from 11 page onwords.

By default it value is 1.

For Trace level settings :

SXMB_ADM --> Double click on the "Integration Engine Configuration" --> Select category as RUNTIME

and click on "Specific Configuration" button --> Here we got TRACE_LEVEL parameter there in Current

Value option is there here we can set the value from 0 to 3.

All users may not have this Authentication.

Regards

Pothana

[mayur_patel6]

Hello Experts,

We have several integrated scenarios in our landscape so that means i won't see any of the detailed tracing in SXMB_MONI.... can someone tell me how do i achieve same but on the Java side in RWB -> Message Monitoring -> Adapter Engine..?

I am looking for pre mapping and post mapping xmls for Integrated Scenarios where we don't go via Integration Engine.

Thanks!!

Edited by: Mayur Patel on Aug 26, 2011 7:39 PM

[Former Member]

Hi Fernand,

The parameter TRACE_LEVEL_PROPAGATION enables you to set locally in the Integration Engine (PI system->sxmb_adm-> Integration Engine Configuration) whether the tracing of a pipeline is passed on to the message.

You can have 2 values ( 0 means No, 1 means Yes).

Use the configuration parameter TRACE_LEVEL (category RUNTIME) to activate tracing locally for the whole Integration Engine

Use the configuration parameter TRACE_LEVEL_PROPAGATION (category RUNTIME) to activate tracing globally. This means that message processing is traced until it is complete on all involved Integration Engines.

As far as performance is considered, the value change should not be a factor.

Cheers,

Souvik