Interface and Receiver determination steps

[Former Member]

Dear Experts,

I have list of queries which I am facing issue in ID. I am working on SOAP<->SAP-PI<->PROXY scenario.

1. Created 2 Service Interface i.e. SI_SOAP_OB and SI_PROXY_IB in ESR.

My question is that in the sender and receiver tab what should be the entries in Business System of SOAP and PROXY systems ( i.e. BS system created under the node Communication Component without party). I created this Business System ABAP from the entries of SLD.

2. What is the sequence of steps in the ID i.e. Cc,ID,RD,SA,RA.

3. In the Receiver Determination, I can see in the "Configuration Overview" tab

that the PROXY business system has red entries. I think that this system should show SI_PROXY_IB

but it shows SI_SOAP_OB.

4. When trying to create Interface Determination, I receive "JAVA.lang stack overflow error"

and INTERNAL ERROR.I made sure that there is no inactivated objects under my user.

5. I am sure that the step till creating SI in ESR and sender agreement in ID is correct. Can I create proxy as well as WSDL with end point at this stage.

I need urgent suggestions from experts , kindly help.

Regards

Alice Rebecca

[Former Member · Accepted solution]

Hi,

Before creating the Objects in the ID..

Ensure you have activated all the objects of ESR ...i.e service interfaces...

1. Create communication channels for SOAP and Proxy under respective business systems...

once you associate these business system to the corresponding the Software components in the SLD ..you can be able to see the service interfaces under respective business systems...

sequence i follow for object creations are 1. Sender agreement..2. receiver determination.3 interface determiation and then receiver agreement...

HTH

Rajesh

[Former Member · Accepted solution]

Hi Everyone,

The issue is solved. It was probably the Java cache issue.

Regards

Alice~

[former_member184681]

Hi,

Find many interesting details and examples of Integration Directory configuration [here|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0582487-69f3-2b10-2d99-f34ca50c837c?QuickLink=index&overridelayout=true].

For instance, see chapter 4.5 for an overview of ID configuration and chapter 5 for an example scenario that is just similar to yours.

Hope this helps,

Grzegorz

[Former Member]

Hi Grezg,

I am not using any model in ESR. The chapters mentioned describes the async communication and doesnt briefs when I can not create proxy in application system.

Experts if any one inputs , then please answers in sequence wise.

Waiting for valuable suggestion.

Regards

Alice~

[Former Member]

1. Created 2 Service Interface i.e. SI_SOAP_OB and SI_PROXY_IB in ESR.

My question is that in the sender and receiver tab what should be the entries in Business System of SOAP and PROXY systems ( i.e. BS system created under the node Communication Component without party). I created this Business System ABAP from the entries of SLD.

ANS -

For SOAP, anything like Legacy_filer can be created & used.

For PROXY, use the business system of R/3 system maintained in SLD.

2. What is the sequence of steps in the ID i.e. Cc,ID,RD,SA,RA.

ANS-

Sender CC

Sender Agreement

Rec Determination

Int Determination

Rec CC

Rec Agreement.

Create the steps in COnfiguration Scenario directly.

3. In the Receiver Determination, I can see in the "Configuration Overview" tab

that the PROXY business system has red entries. I think that this system should show SI_PROXY_IB

but it shows SI_SOAP_OB.

-

---

4. When trying to create Interface Determination, I receive "JAVA.lang stack overflow error"

and INTERNAL ERROR.I made sure that there is no inactivated objects under my user.

ANS

its cache error. Go for full cache refresh in IB>AdministrationData cahce--cache refresh.

5. I am sure that the step till creating SI in ESR and sender agreement in ID is correct. Can I create proxy as well as WSDL with end point at this stage.

ANS

Nope. create the structure in ESR & generate proxy for the same in ECC system. that's it. No need of WSDL here.

-santosh.