Connection Problem With Integration Builder

[Former Member]

Hi Guys,

I have created the message interfaces in my SWCV ,

now I want to create a abap proxy but when I run transaction SPROXY I cant see the SWCV and it's related objects in both XI and in R/3 .

Are there any particular settings to be carried out befor proxy generation.

Regards,

Keith.

[Former Member · Accepted solution]

Hi Keith!

> I have created the message interfaces in my SWCV ,

> now I want to create a abap proxy but when I run

> transaction SPROXY I cant see the SWCV and it's

> related objects in both XI and in R/3 .

Proxies are generated on the receiving or sending business system not on XI.

Thus the business systems need to be connected to the XI Integration Server like described in the XI Configuration Guide chapter "Connecting Business Systems with an Integration Engine to the Central Integration Server".

Then you will be able to see your SWCV in SPROXY and be able to generate the proxies on the business systems.

Regards, Tanja

[Former Member · Accepted solution]

Hello tanja,

I'm aware that proxies have to be generated on the recieving or sending systems. But still shoudn't I be able to see my SWCV when i run the SPROXY transaction in XI. I can see the SWCV SAP BASIS 6.40, the one which u get by defualt when u install XI.

I saw the document that u refferd to, but i'm still not clear on how to connect the business system to the Integration server.CAn u point to me a Blog or any other link that might help me.

[Former Member · Accepted solution]

Hi Keith,

Please follow the following blog by vijaya :

/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

It will help solve your problem perhaps.

Regards,

Sulakshana

[Former Member]

Hi Keith,

are you sure that the connection is correct? Please check if the SPROXY tests work correctly.

Transaction Sproxy> goto>connection test.

Try to find out if the tests are successful.

Jaime

[Former Member]

Hello Jaime,

I went to SPROXY and did what u said. Everything's working properly.

But the problem is still there.