Problem with Soap Sender CC

Question

Hi,
SOAP - Proxy.
I have 3 seperate Scenarios in PI 7.0 in different Name space, with different Message interface names, under same SWC.
I imported them to PI 7.1 and used the same format that help says... with Service:cc and gave it to the calling service.
During my import, I noticed that the Message Interface and Name space were knocked off from the SOAP Sender adapter in PI 7.1. The scenarios are configured and working currently.
I have 3 CC in this format. In Soap sender CC, we will specify NS and Interface name. Thus I had to use 3 CC.
As per SAP Note 856597, the sender CC format should be...
http://host:port/XISOAPAdapter/MessageServlet?senderParty=FP&senderService=FS&interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace
Now, in 7.10 we dont need to specify NS and Message Interface in soap sender CC. Hence, I created 3 sender URL for each scenario to call to PI 7.10 ( based on the interface / NS names ) and I have created 1 CC only instead of 3. This I thought would work because the sender CC is not tied with NS or MI any more, which are included in URL, and thus I have 3 different calling URLs.
Now, when I do this and activate, it is always calling only one service all the time.
Regards,
Venkat.

Answer 1

I have used the other channels in the same format. only NS and MI name changed. Sender and receiver are same.
We do specify outbound Interface and its NS in sender Soap CC prior to 7.1.
Morever, I am following the format as per the note I specified above.
It is able to call PI 7.1 succesfully but failing to call proper IM and MM.
No error mesage but only one scenario is called all the time.
Its like this...
prior to 7.1, we will have MI and NS info on the sender Soap sender CC. Hence we just mention the name of the CC in the target URL along with service. so it picks up the NS and MI from CC.
in 7.1, since we dont specify NS and MI in sender Soap CC, we have to notify the sender side MI and NS and we do that in sender side URL( to be given to the calling system ).
Now as per my understanding, since no NS or MI dependant info is speicfied in CC, I thought we can use one single CC instead of 3.
See my thought looks reasonable ...
but wondering why it isnt working.
Regards,
Venkat.