PI 7.1 - Configuring a client proxy - not working.

[Former Member]

I am trying to send a Client proxy from ECC to XI.

This is a new PI 7.1 install so I am trying to test a quick and easy client proxy from ECC to XI and cant even get a message sent to XI.

On ECC, I am getting a weird message in SXI_MONITOR

I get a gray colored flag and when I hover over it, give me the following info:

"Message recorded (Commit Missing)".

Has anyone encounter this type of status.

Basically the message never send out to XI. Also, the message does not let me restart or even cancel the message.

Overall, all the config looks good on ECC

SLDCHECK looks good.

In ECC, I configured the Integration engine config as an Application Server and pointed it to RFC destination that points to the XI server.

-steve

[Former Member]

Hi,

In SPROXY, I was just using the test tool.

In the past this would be enough to send the message out.

Will the test tool not work anymore?

I will can test by putting the proxy in an ABAP program.

-steve

[Former Member]

it shd work.. did you check the connection between ECC and XI?

nope connection shdn't be a problem. as Amit said did you check the commit in proxy code??

Edited by: Chirumamilla Sukarna on Sep 29, 2008 10:10 PM

[Former Member]

Hi,

1) Queues are clean

2) I have checked the RFC Destination for the HTTP connection. It brings back a 500 empty response which is good.

I did a check on the Integration Engine Config and it brings back a yellow status that "Corresponding Integration Server not Maintined"

I wasnt sure if this was an info message that really wasnt an error.....any thoughts?

[Former Member]

Hi Steve,

Did you tried Commit work in your Proxy code?

amit

[Former Member]

that is a warning...where did you get this error? in RWB component Monitoring??

[Former Member]

chirumamilla,

On ECC, I got the warning message on the SXMB_ADM-> Integration Engine then press the check button.

Also, I am in the process of doing a quick dummy program that calls the proxy. Then I will add a commit to see if this works. But I still think the proxy Test tool should take care of any commits that are needed.

[Former Member]

Steve,

I think you have to check the XI system parameters given in ECC.

and aslo please check the status of all the Engines in RWB component monitoring.

[Former Member]

Please add COMMIT WORK at the end of proxy code.

This will resolve your issue.

[Former Member]

Hi,

You need a COMMIT WORK in the client proxy code.So follow the steps below:-

1. Check if you have a commit work statement.

2. Check syntax, save and activate after adding commit work in code..

3. Test the proxy.

4. Execute the proxy.

5. Test in sxmb_moni.

6. If you still get the error , regenerate the proxy in sproxy and retry.

Should work. Incase you have already done these steps pls let us know.

Regards,

Anirban.

[Former Member]

Check the Queues?

did you restart or configure queues after installation?

[Former Member]

Hi,

At the end of your ABAP proxy code you need to write the code 'Commit work' and then only the message will be posted to XI. Hope the solution works.

Thanks

Amit