Synchronos inbound ( proxy ) configuratin issue ?

[Former Member]

Hello Friends,

I have designed a Synchronos inboud interface where 2 parameters are comming in as request and response is a str with 10 fields. I could have easily done this using RFC,but thought to give a try to proxies...

I have creaed server proxy ( inbound interface ) it has let me created classes and etc. Now my problem is how I can configure the things in integration builder ?

on my search I went to following artical.... seems too much similar what I need:

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50b63e8f-a4bb-2a10-e9b1-ba803fd06739&override...

My problem starts with : Configuring a Service Provider

I cant find t-code SOAMANAGER ( I am having PI 3.0 )............. so could anyone please guide me how I can configure the senario , to get the WSDL ?

I went to following thread too:

where Abhishek is mentioning to have 2 MI's ? but in artical above , he only create one SI ??

Regards,

Edited by: Shah H on Nov 26, 2009 2:22 PM

[Former Member]

Since you are working on XI3.0 so this document will help you while you go for proxy coding in R3..

Inbound Synchronous Proxy

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsa...

Regards,

Sarvesh

[former_member200962]

I am having PI 3.0

In this case i would suggest do not opt for the scenario mentioned in the document.....some features like Enable P2P communication in SI itself are not even present in SAP PI7.1 (the document is based on SAP PI7.1 EHP1)

Please read the Applies To section (very first note on the first page itself) before you proceed further.

My reply in the referenced thread should hold good for SAP XI3.0

The only thing that you need to do is define proxy in the SAP system.

Good Luck!

Regards,

Abhishek.

Edited by: abhishek salvi on Nov 26, 2009 7:23 PM

[Former Member]

Thanks abhishek ,

One question ( you already describe in other thread the things to do for configuration , but you did not mention regarding communication channel ) ? do I require one ?

Please let me know, thanks

and also if there is any artical or doc which described this all or any tutorial, that would be of great help...

as I mentioned I already define the things in design, create the proxy using inboud -syncron interface... etc need to have only wsdl... ( and I tried using wsadmin to genrate the wsdl, but guess its wrong ? )

Regards,

[Former Member]

Hi,

You can start your developement with below mentioned points..

1. Create 2 data types (DT_request & DT_resp ). One for source & other for response.

2. Create 4 message types for the above data type. e.g.

i) MT_req_from_web (DT_request)

ii) MT_req_2_R3 (DT_request)

iii) MT_resp_from_R3 (DT_resp)

iv) MT_resp_2_web (DT_resp)

You can go ahead with 2 message type also by reusing them. But just to make it easy I advise you to create 4.

3. Create 2 message Interfaces. e.g

i) For request it should be outbound Synchronous and define your request & response message type inside it. e.g. MT_req_from_web & MT_resp_2_web

ii) For response it should be inbound Synchronus and there you define the request & response message type. e.g. MT_req_2_R3 & MT_resp_from_R3

4. Create 1 message mapping.

5. Create 1 interface mapping.

Regards,

Sarvesh

[Former Member]

Hello Servesh ,

Do I really need to define message mapping and interface maping ?

Because abhishek in other thread mentioned that no mapping is required for this senario ?

Could you please also mention something regarding ID ( there I need to define senario or would it be enough to use t-code wsconfig and wsadmin to create the wsdl ?

Thanks

Edited by: Shah H on Nov 26, 2009 4:01 PM

[Former Member]

> Do I really need to define message mapping and interface maping ?

> Because abhishek in other thread mentioned that no mapping is required for this senario ?

Yes you can skip that if you are really not going to do any data manupulation in XI.

> Could you please also mention something regarding ID ( there I need to define senario or would it be enough to use t-code wsconfig and wsadmin to create the wsdl ?

Create a secnario. With 1 RD, 1 ID, 1 SA and 1 RA. You have two create 2 CC, one Sender (adapter type will depent on your sending system) and other is Receiver with adapter type XI.

BTW what is you sending system from which you will get the request?

[Former Member]

Thanks Servash,

Sender is an external system... so actually as I need to provide them with wsdl, they will consuem the wsdl and put the two input paramter and on based of these two input parameter I have to deliver them a result str.

What I did till now is I define two data types, ( dt_req having 2 parameters, and dt_resp having 7 fields )

creted message interface, both synchronous 1.inbound and 2.outbound

now I want to create actions and integration senario so that I cold use them in ID ... ?

do I need to have two CC ? one on sender side and other on backend side ? as i said is synchronus, so sender will get the reciver msg.... ??

Regards,

[former_member200962]

now I want to create actions and integration senario so that I cold use them in ID ... ?

creation of Actions/ Integration Scenarios is not cumpolsory

do I need to have two CC ? one on sender side and other on backend side ? as i said is synchronus, so sender will get the 
reciver msg.... ??

Yes you need two communication channels....one sender and one receiver

Regards,

Abhishek.

[Former Member]

now I want to create actions and integration senario so that I cold use them in ID ... ?

--> As said by Abhishek, Actions and Intg scenarios are not manadatory to create design and configuration objects but still its good to have them to see the overall process/scenario at one place..esp when the scenario is complex.

do I need to have two CC ? one on sender side and other on backend side ? as i said is synchronus, so sender will get the reciver msg.... ??

--> Yes two CC. Sender SOAP/HTTP adapter ; Reciever: PI adapter for server proxies .

FYI, in case of proxu communication, a PI adpater is also used in Intg Engine, at least on the Reciver side. This PI adpater is on ABAP side and does not run on AE. The PI adapter is used only to establish HTTP connection to the reciever.

[Former Member]

Hello,

I am facing a bit problem in doing configuration, ( I successfuly did few for Asynchro, but this is my first sycnhro-- so not sure what I am doing wrong )

As I said I have two MI's

1- MI_Stock_In ( syncro inbound interface ) this I use to create server proxy

2- MI_Stock_Out ( synchro- outbound interface ) this is the interface which I connect or expose to External system.

So in Reciver Determination:

Sender:

Service = External_System

Interface = MI_Stock_Out

namespace = xyz.....

Reciever Agrement:

Sender:

Service = External_System

Reciver:

Service = r3system

Interface = MI_Stock_In

namespace = xyz.....

and CC ( adapter type XI )

Interface Determination:

Sender:

Service = External_System

Interface = MI_Stock_Out

namespace = xyz.....

Reciver:

Service = r3system

Configure inbound interface:

name = MI_StockCompare

name space= xyz....

I have left blank interface mapping, as no mapping is define....

but when colleuge consume the wsdl, he is getting error, reciver is not known ....

Any tip idea what I am doing wrong ?

Thanks and regards,

I am having also confusion,, as its synchro---- it means my sender ( external_system ) is at the same time reciver..... so do I need to have r3system as reciver ??

is there any example tutorail for this ( synchro.... inbound interface and sychrou outbound interface ) ??

Edited by: Shah H on Nov 27, 2009 11:05 AM

Edited by: Shah H on Nov 27, 2009 11:06 AM

[former_member200962]

I have left blank interface mapping, as no mapping is define....

Does that mean you have created Interface Mapping but not included any mapping program?

If there is no mapping involved then do not create Mapping program and also do not create any Interface Mapping.

Interface Determination is however needed

so do I need to have r3system as reciver ??

R3 system should be included as a Business System in SLD and then imported in Integration Directory.

Regards,

Abhishek.

[Former Member]

Hi Shah ,

I am having also confusion,, as its synchro---- it means my sender ( external_system ) is at the same time reciver..... so do I need to have r3system as reciver ??

-

---

> synchronous means your sender will wait for the response from receiver . You need to hav eR3 system as receiver .

is there any example tutorail for this ( synchro.... inbound interface and sychrou outbound interface ) ??

-

---

> check out any File to RFC synchronous scenario configuration will be exactly same at PI level only thing which will differ is the communication channel at receiver end ..for your case it will be XI while in case of RFC it will be RFC adapter .

Hope no doubts left ...!!

Regards ,

[former_member200962]

I successfuly did few for Asynchro, but this is my first sycnhro-- so not sure what I am doing wrong

To be frank we do not do anything great in synchronous flow....other than creating MIs with mode as Synchronous, including the appropriate Message types in the response section, performing Mapping between request and response messages repectively.

Regards,

Abhishek.

[Former Member]

I am getting following error:

<SAP:P2>Error during parsing of the response. No XI response received.</SAP:P2>

<SAP:Stack>Error when receiving by HTTP (error code: 200, error text: Error during parsing of the response. No XI response received.)</SAP:Stack>

Any idea ?

It looks like when XI adapter returns the respond, so its not recieved...., humm.... how I can recieve the response of XI....

Edited by: Shah H on Nov 27, 2009 1:21 PM

[Former Member]

but when colleuge consume the wsdl, he is getting error, reciver is not known ....

Any tip idea what I am doing wrong ?

--> Can you ensure that you have done Reciver agreement in ID ?

+I am having also confusion,, as its synchro---- it means my sender ( external_system ) is at the same time reciver..... so do I need to have r3system as reciver ??+

+is there any example tutorail for this ( synchro.... inbound interface and sychrou outbound interface ) ??+

From you description it seems that it is a simple scenario of SOAP (sync) <>PI<>Server Proxies(sync)

I hope following links will help you:

[https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/5814] [original link is broken] [original link is broken];

[http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417600)ID0597685150DB01818497713931938163End?blog=/pub/wlg/2292]

[http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417600)ID0597685150DB01818497713931938163End?blog=/pub/wlg/1847]

[Former Member]

This error could be bcoz of multiple reasons..one of them is discussed in the thread below...just check if it helps:

[;

[Former Member]

Can u confirm if you have used a synchronous proxy athe reciever side (SAP)..otherwise ..have a look at the below blog :[http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417600)ID0597685150DB01818497713931938163End?blog=/pub/wlg/7032]

[Former Member]

yes I am having synch... proxy senario...

I have went to that thread which you posted, did not help me out much...

Do I need to have 3 CC ? e.g 2 SOAP channel one sender and one reciever ?

Edited by: Shah H on Nov 27, 2009 2:25 PM

[former_member200962]

Only One SOAP Sender channel and One Proxy receiver channel.

When you say Sender is External System does it mean that it is in different landscape? If yes then may be that is a problem.

Regards,

Abhishek.

[Former Member]

Hello Abhishek,

I have to proivde WSDL to external system, yes, Sender is external system and defiened as a third party system...

why, ? is it a problem ??

Regards,