KEMBAR78
AIF XML Runtime Debugging Guide | PDF | Computers
0% found this document useful (0 votes)
915 views1 page

AIF XML Runtime Debugging Guide

By default, AIF's XML Runtime will process messages asynchronously in the background. However, for testing purposes, you can create a custom Runtime Configuration Group that will execute messages synchronously instead. To do so, go to transaction /AIF/PERS_CGR and create a new runtime configuration group, ensuring the "Runtime Configuration Group Active" indicator is set, without setting the "Run Scheduled" or "Schedule Packages" flags. Then when using the TRANSFER_TO_AIF method, pass the namespace and name of the new runtime configuration group via the IV_QUEUE_NS and IV_QUEUE_NAME parameters to execute messages synchronously and allow debugging with breakpoints.

Uploaded by

Soumava
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
915 views1 page

AIF XML Runtime Debugging Guide

By default, AIF's XML Runtime will process messages asynchronously in the background. However, for testing purposes, you can create a custom Runtime Configuration Group that will execute messages synchronously instead. To do so, go to transaction /AIF/PERS_CGR and create a new runtime configuration group, ensuring the "Runtime Configuration Group Active" indicator is set, without setting the "Run Scheduled" or "Schedule Packages" flags. Then when using the TRANSFER_TO_AIF method, pass the namespace and name of the new runtime configuration group via the IV_QUEUE_NS and IV_QUEUE_NAME parameters to execute messages synchronously and allow debugging with breakpoints.

Uploaded by

Soumava
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

Per default the messages will be processed in background when you use AIF's XML

Runtime.

But for testing porpuses you could create your own Runtime Configuration Group that
will execute the messages in a "synchrously".

Go to transaction /AIF/PERS_CGR and create a new runtime configuration group. Make


sure that you set "Runtime Configuration Group Active" indicator. Furhtermore, do
not set the flags "Run Scheduled" and "Schedule Packages".

Method TRANSFER_TO_AIF provides parameters IV_QUEUE_NS and IV_QUEUE_NAME, pass the


namespace and name of your runtime configuration group to those parameters. Then
you should be able to debug your actions with a normal break-point.

You might also like