break point

[Former Member]

In TIBCO ,We can set break points and can trace where the error is occuring is it at sender or recever or AE or IE etc...

Do we (in XI 3.0 or in PI 7.0 ) have similar setup

[Former Member · Accepted solution]

No.

You can monitor your message and then conclude the problem.

[Former Member]

Hi,

Check this link for XI Trouble shooting.

http://www.riyaz.net/blog/index.php/2008/06/04/xipi-sap-xi-troubleshooting-guide/

Thanks,

RamuV

[Former Member]

Hi,

In XI there is no break points,

For testing

we use SXMB_MONI and check the communication channel is it correct or not.

In ID part we can check the sender and receiver aggrements, Interface and receiver determination we can check by testing the configuration scenario, Go to Tools -> Test Configuration, provide the sender service, interface, receiver service

and the payload(input data) for the corresponding scenario.

In the SXMB_MONI we can check the pipeline steps in the integration engine.

In the Runtime work bench we can check the all components like message, component, end to end, performance, configuration, cache and alert configurations and Alert inbox.

But there is no Break points in XI/PI.

[prateek]

Not exactly. U cant put such breakpoints in XI. But using the sxmb_moni and RWB, u can always pin point the location of error.

Regards,

Prateek

[Former Member]

Hello Prateek,

Could you pls give some blogs or provide some links to "diagnose the message flow and trace errors "

Could you pls tell how we can analyse the RWB trace steps...

I can see lot of trace steps how the message flowed from the pipelines....

But how to analyse it and trace the error

Edited by: satya kumar on Jul 16, 2008 2:11 PM

[GabrielSagaya]

For getting trace info in SXMB_MONI you need to set MAPPING_TRACELEVEL parameter in SXMB_ADM and then configuration.

Also using MappingTrace/AbstractTrace object in UDF you can get trace info.

AbstractTrace trace= container.getTrace();

trace.addWarning("Trace will be now seen using trace object");

Also, in SXMB_ADM , you can set the TRACE_LEVEL parameters to 1 , 2 or 3. 3 will give you all info all pipeline steps. But, the problem will happen in the fact that memory gets filled up when trace is 3 and so make it 3 only for debugging!

[Former Member]

Hi Satya,

There are many ways to check the status of messages in XI.

Component Monitoring : Where you will be able to understand the status of the adapter is active or not by clicking on Adapter Monitoring.

In Runtime if you need to know about the messages processed by XI enter into RWB, instead of RWB just type MDT[Message Data Tool] at the url which will allow you to show content of the message.

As such there is no way of putting breakpoint and then look for the steps in XI which is true only at the proxy side which is again ABAP Programming.

Thanks

Sudharshan

[Former Member]

Hi,

Message Flow

1.File picked by the adapter,at the A.E it converts to XML format.

2.Generate a msg ID for the file and creates XI header to that file using CPA cache. CPA cache will be having the

information about all the Control(address) data.

3.Module processor

4.The file goes to send queue by the adapter engine, that file will be picked by the internal XI adapter and the file

will be forwarded to the Integration engine.

5.Pipeline steps follow the Integration Engine.

Receiver determination, Interface determination, Msg split, Msg mapping, Logical routing, Receiver aggrement, call adapter

6.The file will go to receive queue, which was taken and forwarded to the adapter engine.

For Diagnose

Mapping Trace

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

This object enables to transfer message to the mapping trace if the trace level set correspondingly

then the trace is visible to message monitoring.

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().

By default this value is 1.

By setting trace value you will get some information based on this we can analyse. For quality system we set trace level as 3

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.

For testing the data in unit testing we can goto the test tab and do the test, here in the

down part besides the execution button Trace level is there, here we can select the required

option(Warning, Info, Debug,all, no trace)

[Former Member]

Hi,

in this blog you fill find a lot of useful links (under SAP XI Runtime & Testing the interfaces):

Regards

Patrick