Error on PROXY to FILE scenario

[Former Member]

Hi,

I'm working on a Proxy to FIle Scenario. 1 Proxy is triggered and 7 files should be generated at the target side.

Now when the proxy is triggered all the 7 files doesn't get generated. Instead randomly some 3-4 files are getting generated.

Could not see the rest of the entries in MONI also.

Can someone tell how to monitor this and where exactly to check for the error, as message doesn't reach the MONI and we don't have a sender channel beacuse its Proxy.

Thanks,

Vikas

[Former Member · Accepted solution]

Vikas,

Can someone tell how to monitor this and where exactly to check for the error, as message doesn't reach the MONI and we don't have a sender channel beacuse its Proxy.

-

---

> how 7 files will generate ?

From Proxy level @ ECC it don't seems logical/possible as whole data will be passed as a whole to proxy interface and on some condition basis only you would be creating 7...files . so definitely at SXMB_MONI of XI you can see this .

Try to increase trace_level parameter to 3 (only in development box , as it will consume the server very fast) for better monitoring .

Since the no. of files will be created by file adapter only so those many no. of receiver file adapter calls you can see at RWB.

Regards,

[Former Member]

Also would like to add that once we got the entry in MONI. But when we execute the same interface again with same settings, it does not show up in MONI.

Has it something to do with the data stuck in queue or some where else.

I have unlocked and deleted all the queues using "smq2".

Any help on this?

Thanks,

Vikas

[prasannakrishna_mynam]

Hi Vikas,

In your report check you have used COMMIT WORK cause your one is asyn proxy call, once check in your report for every proxy call you are using COMIMIT WORK. to end the call.

Regards,

Prasanna

[former_member181962]

Hi Vikas,

Do you see something in the SXMB_MONI of the R/3 system ?

Regards,

Ravi

[Former Member]

Check points:

> Do Cache refresh.

> Check Commit work is done after proxy call.

> Execute the outbound report that calls proxy and check the message in MONI of R3. If yes, check that message is in chequered flag. If Yes, logon to XI system.

> If no Check RFC Destination in R3 that pings XI is working fine.

> Check the message in MONI of XI.

> check that message is in chequered flag.

Regards,

Anurag Garg

[prasannakrishna_mynam]

Hello Vikas,

- In order to test the client proxy functionality, in SPROXY you have the option to test(F8) by selecting the OUTBOUND interface. You need to give the interface and name speace details and test the client proxy functionality.

- To check the mesage flow, since the proxy doen't need CC,the message is directly sent from application system's local IE to central PI/XI's IE, the outbound entry should be seen in either application system's(sender) SXMB_MONI or SM58. Check this in sender business system.

Regards,

Prasanna

[Former Member]

Yes we have entry for each receiver based on the data in the first field, tehy are mapped to respective target.

Even if we leave this case alone.

In general also if we have 1 source file and 1 target file to be generated, where can we check for the error for PROXY to File scenario, when we are not getting any entry in MONI.

Thanks,

Vikas

[Former Member]

What exactly is your setup on the receiver side, how many receiver Components do you use?

Did you enter all receiver components in the receiver determination and create an interface determination for each target?

Cheers,

Mane