cancel
Showing results for 
Search instead for 
Did you mean: 

No receiver found in Receiver Determination

deviprasad_pothireddy
Active Participant
0 Kudos

Hello Experts,

Sub: Calling integration process (which in software component1) from sender service interface_Out (which is in another software component2) in Receiver Determination Fails.

There are two software components, S/W C1, S/W C2,

In S/W C1,->

Integration process (IP1)created in S/W C1, with name space NS1,

Service interface1(abstract) SI1 with message type MT

In S/W C2,->

Sender service interface2 SI2(outbound) with message type MT with namespace: NS2

(MT message type, in both service interface holding the same,

used SI1 In receive step in IP1.

Interface Determination from BS2,SI2,NS2<-> IP1,SI1(No mapping).)

In Receiver Determination,

-


Business system BS2;

Sender Service Interface: SI2;

Name space: NS2,

In Receivers : IP1

-


Problem is : do not find this receiver.

I have to call this process, like this. Please help on this.

Use case is:

single Soap request is coming, many application are using the same using common Receiver determination( which in S/W C2),

Now i have to use the same receiver determination to send this message in IP1 which is in SW C1;

-> any alternative solutions for this

Thanks,

Deviprasad.

Accepted Solutions (0)

Answers (3)

Answers (3)

deviprasad_pothireddy
Active Participant
0 Kudos

Hello,

Thanks for replying all.

Generally we do not face scenarios like this. Initailly I thought like this. Now I have created Receiver determination, object with in same software component.

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

hi,

when you use Integration Process the configuration in the ID must be

Receiver Determination 1:

Sender System: XXX

Enterprice Services (outbound)

Namespaces

Target System: Integration Processes

No Mapping requiered in Interface Determination

Line:

Receiver Determination 2::

Sender System: Integration Process

Enterprice Services (Abstract)

Namespace

Target System: YYYY

No Mapping requiered in Interface Determination

Sender Agreement=1

Receiver Agreement=2

Interface Determination=2

Communication Channels=2

Take in mind that in the Interface determination you have to define as receiver structure the Service Interface (Enterprice Service in PI7.1) type Abstract. if you cant select it delete all filter in the popup qhen you have to select the Inteface in the reciver structure.

Check the Integration PRocess if you define the SI_XXX_abs in the reciver step.

check all changes in the ESR were activated

Check this out and let me know

Edited by: Rodrigo Alejandro Pertierra on Sep 3, 2010 2:42 PM

deviprasad_pothireddy
Active Participant
0 Kudos

Thanks for replying,

Done the same things before itself.

Here, In first Receiver determination, my sender service interface is Software component 1, But my target receiver(Business system/ Integration process) is in another Software component 2,( will it possible possible to like this). if i do like this, at test time, it is saying that," No receiver found".

former_member200962
Active Contributor
0 Kudos

The scenario is a bit confusing; did you try defining dependency between the two SWCVs?

Also did you check the CACHE for your BPM (return code). The config looks fine and ideally possible to implement.

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

hi

Here, In first Receiver determination, my sender service interface is Software component 1, But my target receiver(Business system/ Integration process) is in another Software component 2...

no matter if the receiver system is in another SWC (Service Interface o Integration Process),that depend of the architecture that was defined for the SLD.

please, in the ID go to menu tools---> Test configuration. the parameterization is quiet simple.

Let us know.

Former Member
0 Kudos

Have you defined the IP in the Communication Component in directory? This IP must have sender / receiver abstract message interface.

I think you might have missed this part, that's why receiver determination is failing.