Multiple Operation in Service Interface

Hi Experts,
Here is the problem -
Scenario: SOAP Adapter-> PI (7.1) -> XI Adapter -> ERP Proxy
We have defined multiple operation in Service Interface using Interface pattern "Stateless".
Message posted using SOAP adapter goes through PI alright. But on ERP is throws the error saying "No implementing class registered for the interface"
Well the checklist-
1. Proxy class generated/re-generated. Class/Interface/Methods all activated.
2. If I remove all the operation from Service interface and just have one with the same name as Service Interface (which is also default when you create new service interface) it works fine.
Any idea guys ?
Regards.

Hi Sreenivas,
I appreciate your promptness in answering the query.
1. And I know that if you select Stateless (XI 3.0), in the service interface you just can't have multiple operations.
2. ID contents are generated fine (I dont do it manually. I just import the scenario from ESR).
Please, first test yourself and let me know if you succeed or point me to some document explaining that.
Regards.

Similar Messages

A multi-operation web service scenario

Dear,
We have a simple synchronous scenario: SOAP <-> SAP PI <-> ABAP proxy.
In the outbound and inbound service interfaces, we have multiple operations.
The exact same scenario, using a single operation, works very fine.
Now the question is: is there something wrong with my configuration or it this a little bug in our SAP PI 7.11 SP11?
ESR
Outbound service interface with multiple operations
All based on external definitions
interface pattern is stateless because we have multiple operations
Inbound service interface with multiple operations
all based on created data types/ message types
interface pattern is stateless because we have mulriple operations
Operation mappings and message mappings created accordingly.
Please note that I use a XSLT mapping to read the SOAP header too.
ID
Sender Agreement
linked to sender SOAP adapter with Do Not Use SOAP Envelope used.
SWCV of sender interface indicated
Receiver Determination
SWCV indicated
type of receiver determination is standard
operation-specific
Interface Determination
SWCV of sender interface indicated
Operation mappings indicated
Receiver Agreement
points to a receiver XI adapter for proxy communication with the back end system.
Error
Test message in soapUI:
Thanks a lot!

Hi Dimitri
Here is roughly how the Receiver Determination and Interface Determination objects would look like:-
Receiver Determination
It should be NOT operation specific - either set the SWCV to blank or set the checkbox for "Not Operation Specific". This is because your root node is always <Envelope> (due to the "Do not use SOAP envelope" setting) so it cannot dynamically determine the Operation.
Interface Determination
Here should also be not Operation specific - so set the SWCV to blank.
Similar to the first step, operation cannot be dynamically determined due to root node being always <Envelope>. Therefore use Conditions to select the correct operation mapping and receiver interface/operation.
The condition should be based on the existence of the Xpath of the sender operation, example from Mark's reply above:-
Condition 1 - /p1:Envelope/p1:Body/p2:SenderOperation1_MT EX
Condition 2 - /p1:Envelope/p1:Body/p2:SenderOperation2_MT EX
Then in your OM_Mapping1, you would map from SenderOperation1 to ReceiverOperation1. You can include the XSLT as one of the steps in the OM to retrieve the SOAP header details.
Hope this will be useful.
Rgds
Eng Swee

Mapping in Services Interface with multiple operation... ?

Hi ALL,
I have a SOAP to SOAP scenario here Just PI 7.1 with EHP1 acting a bus no mapping nothing .
1) I have the WSDL file from the receiver system with multiple synchronous operations in it ..i imported the wsdl as External Definition .. i used the same the WSDL file to create the sender Service interface also...
when i created the service interface with the operation in it , i just gave the same operation name from the WSDL.this i followed for the sender and receiver service interface.
1)now the issue is do i need any operation mapping if the service interface has more than one operation ...?
2) I compelted the scenario without any operation mapping ..but i am getting this error ..Problem occurred in receiver agreement for sender -ICRM_D to receiver -EXACTTGETWEBSERVICE_D,http://ICRMtoExactTaetWebservice.com.si_os_ICRM_EXACTTETWEBSERVICE: No standard agreement found for , ICRM_D, , EXACTTARGEBSERVICE_D, http://ICRMtoExactarebservice.com, si_os_ICRM_EXACGETWEBSERVICE..?
pls help me in this issue..
Thanks
Souz

you might want to read this /people/shabarish.vijayakumar/blog/2010/09/08/service-interface-and-multiple-operations--is-it-just-an-hype
you will need to create additional configurations for multiple operations to be supported

Provider proxy error - Service Interface with multiple operations

Hello experts,
I've a synchronous provider proxy scenario using an inbound and outbound service interface.
That service interface contains 3 operations: create, change and delete a table entry.
I created all the necessary repository objects and integration scenario objects.
Next, I generated a provider proxy on the ECC backend system and created an endpoint via SOAMANAGER.
When I test, I get this error:
No implementing class registered for the interface (ABAP interface, request message ...., request message, namespace....)
I currently use a receiver XI adapter in the scenario. Is that ok?
or should I use a receiver SOAP adapter with a SOAP action?
Please advise.
Thanks a lot.
Dimitri

Hi,
Check these
INTERFACE_REGISTRATION_ERROR:No implementing class reg'd for interface
No implementing class registered for the interface
Regards
Seshagiri

PI 7.1 multiple operation interface and SOAP action doubt

Hi guys,
I'm trying to implement a scenario, where I have a single outbound (sender side) interface with multiple operations (as 7.1 allows). The problem is afetr the WSDL generation I have the same SOAP action for each operation. Standardly there should be unique SOAP action per operation, but how to achieve it?
And another question - is it ok to use SOAP sender adapter for this interface?
Thanks for your help,
Olian

Hi Olian,
>>The problem is afetr the WSDL generation I have the same SOAP action for each operation. Standardly there should be unique SOAP action per operation, but how to achieve it?
I dont think you need to have separate action, the Operation Name inside Service Interface differentiate the Request type. Also when you send SOAP message to PI, you are sending it to either
http://host:port /XISOAPAdapter/MessageServlet?channel=p:s:c
(where host is the host name, port is the port number, p is the optional party name, s the service name, and c is the channel name, respectively.The URL given above is valid for 3.0/7.0/7.1.)
or * http://host:port /XISOAPAdapter/MessageServlet?senderParty=FP& senderService=FS& interface=IF&receiverParty=TP&receiverService=TS&interfaceNamespace=IFNamespace *
(7. 10 onwards a new URL syntax is also valid and is recommended to be used. )
>>And another question - is it ok to use SOAP sender adapter for this interface?
Yes
Regards
Suraj
Edited by: S.R.Suraj on Sep 8, 2009 6:23 AM

Does the sender SOAP adapter support multiple operations per interface

Hi guys,
does the sender SOAP adapter support multiple operations per interface? (interface type of 7.1)?
Thanks,
Andrzej

theoretically Yes.
Do have a look into this when you get time
/people/shabarish.vijayakumar/blog/2010/09/08/service-interface-and-multiple-operations--is-it-just-an-hype

Any possiblity to use single Inbound Service Interface with multiple Receiver Agreements

Hi All,
Scenario: PROXY to FILE.
Requirement is to receive to two locations.
Is it possible to use single Inbound interface with multiple Receiver Agreements. I tried using two operation in the Inbound Service Interface, and Operation Specific in Determination. But couldnt proceed further. Do I need to use seperate Service Interface for two receiver locations?
Please suggest some solution.

Hi Naveen,
There is a possibility but in the case in the same server location with dynamic configuration: Placing file in two different directories using single receiver communication Channel
With different location you would need to develop a new adapter module as Amit Srivastava explains and develops here Send File to Two Different Locations using Adapter Module
Regards.

Implementing Multiple operations in a web service in JCAPS 5.1.3

Hi,
I am using JCAPS 5.1.3 and have a requirement where in I have to implement multiple operations and expose them as a webservice.
The complexity of operations is medium, they have to log the input message into database.
In order to achieve this I have come up with two models:
Model-1:1.Create a Business process in eInsight and use event based decisons and implement various operations.
2.Create jcd operations in order to log messages into database.
3.Expose the business process as a webservice
Model-2:1.Create a jcd for each operation and make it Callable as an External SOAP web service.
2.Expose each jcd as a webservice
I would like to know which of these models gives better performance for the webservice .I see eInsight in earlier versions was low in performance.
Please let me know if you have any ideas on this.
Thanks in advance.
Regards,
Nag
Edited by: Nag4.5.3 on Jun 10, 2008 12:02 PM

I'd try the idea #1 first. EInsight performances could be an issue only for very CPU-intensive operations, but as you need to interact with a database usually this I/O is going to be the real bottleneck. Instead, you should avoid eInsight not mainly because of hypothetical performance issues but when you foresee the need to write very complex logic, which is much easier to code and maintain in Java within JCDs than in BPEL. However remember that JCDs exposed as WS need the latest ESR Rollup to work properly, if I well recall they were single-threaded in plain JCAPS 5.1.3.
By the way, if your WSDL describes multiple operations you could probably implement them one by one by distinct eInsight BPs if you need to distribute them differently, you are not forced to use a single BP with event-based decisions, it is a matter of your taste and requirements. In my experience however in the past I had some annoying issues with WSDL exposing multiple operations and eInsight, hopefully those are gone with the latest Rollup but do some quick test yourself before betting all your money on it.

Multiple Operations in a Single Interface - How To trace the Operations !!!

Hello PI Experts,
We have implemented an interface for Multiple Operations in the client proxy.
We are able to trigger the proxy for the diff methods of the class and the message is flowing to the desired Receiver correctly.
I have 2 queries regarding these mutiple operations workout :-
1.     First thing I am curious about , how PI is knowing/handling the operation details i.e which operation   needs to be carried out & routed to which receiver.
I had a good look at the SOAP Header Message , but there is no trace of the operation name    that is being used.Only the Interface name is tracked over   there.
I just want to know , how PI is handling & determining this whole stuff and where we can find out the operation name which is being used...as it should be   mentioned somewhere in the message header.
2.     Second one is if the sender is other than a webservice/proxy call, how can we make the operation specific calls from the sender for e.g if its a http call ?
Could you please help me out with this.
Thanks in Advance,
Sunil Kumar
Edited by: SUNIL DALAL on Nov 4, 2010 11:23 AM

Yes, its possible no doubt..but how its playing with the operations can you please let me know.
Thanks,
Sunil
Edited by: SUNIL DALAL on Nov 8, 2010 2:26 PM

Service interface with more than one operation

Hi all,
is it possible to have a service interface with more than one operation?
I have found this blog:
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID0209118050DB10459657028039341762End?blog=/pub/wlg/15123
But this sentence:
ABAP proxy (inbound/ outbound) cannot be developed out of a Service Interface having Operations with different type of messages included. If an ABAP proxy is to be developed then all the messages included should be of one type i.e. either the included messages should be Message Type, External Message, IDOC or RFC Message. This behavior can be observed when a Service Interface is created and then subjected for a check
regards

Hi,
now the interface is running but I get another error in .NET.
"The header 'Diagnostic' from the namespace 'http://sap.com/xi/XI/Message/30' was not understood by the recipient of this message, causing the message to not be processed. This error typically indicates that the sender of this message has enabled a communication protocol that the receiver cannot process. Please ensure that the configuration of the client's binding is consistent with the service's binding. "
Any ideas?
regards

Dynamic routing for a Business Service with multiple operations

I have two business services with multiple operations. Business service A (bsA) has operations OpA1 and OpA2. Business service B (bsB) has operations OpB1 and OpB2.
Depending on incoming Proxy message and operation, I have to do one of the following
1. If someValue = A and operation= Op1 then invoke operation opA1 of bsA
2. If someValue = B and operation= Op1 then invoke operation opB1 of bsB
3. If someValue = C and operation= Op1 then invoke operation opA1 of bsA AND* operation opB1 of bsB and return aggregate data of both invocations
1. If someValue = A and operation= Op2 then invoke operation opA2 of bsA
2. If someValue = B and operation= Op2 then invoke operation opB2 of bsB
3. If someValue = C and operation= Op2 then invoke operation opA2 of bsA AND* operation opB2 of bsB and return aggregate data of both invocations
Using a dynamic route node or dynamic routing options, I am able to achieve cases 1, 2, 4, and 5.
But for cases 3 & 6, I can not use a route node. When I use a Service call out instead, then I am forced to create a Operational branch but that does not seem like the best design since for every new operation added to the business services, I have to add a new branch to the Operational branch and redo all the functionality for that branch.
Basically, I am looking to achieve the functionality of the Route node ( no need to specify the operation ).
Any thoughts/ideas on what the best design would be?
thanks

For cases 3 & 6, why don't you route to another proxy service where you can simple do two service callouts, merge output data somehow and return them to the first proxy?
If you look for "special route feature", that could possibly call two services for a single message, I'm afraid you won't succeed.

Service interface with 2 operations

I have a service interface with 2 operations...
so i have 2 operation mappipngs..
but when i create the interface determaination....it shows only one mapping...
should i create 2 interface determaitions????one for each opeartion??
if yes what should be the sender interface in that case while creting the interface determination..as it is not coming in the F4 help

HI ,
-- Create one outbound service interface with mutiple operatiosn name on left hand side.
-- Create One Inbound service interface with mutiple operations on left side.
-- create two operation mappings..
-- while creating operation mapping drag and drop the outbound service interface on sender side and it will show you 2 opetions select one and same case while adding receiver service interface on operation mapping.
repeat the procedure for second operation mapping also.
-- now when you create interface determination on ID side you see two operations on left hand side of interface determination object select first and assign respected operation mapping then select second and assign second operation mapping..
Thanks,
Bhupesh

Eclipelink plsql web services multiple operation

Hi,
In 11.1.2.2 jdev, I can generate a toplink/eclipse link plsql web services easily for one SQL (dbws).
Can I change the web services to support multiple operations, each for different select sql?
I've tried to changed the wsdl file to have multiple operations
and amend eclipse link-dbws.XML to include multiple query tags.
The web services can be run with multiple operation wsdl but the response of each operation
(using Jdev http analyzer) return only the result of the first operaton.
Can anyone help?
Regards,
Neln
Edited by: Nelson Ng on Nov 10, 2012 8:45 PM

Hi,
I think you are asking for multiple select statements processed by a single TopLink DB Service Provider configuration. As far as I know its exactly one per project and service. However, as this feature is coming from EclipseLink you may want to verify it there
Frank

ADF Service Interface: two-phase commit issue for multiple data sources

In FusionApps, For a service interface we had to use two DataSource resources (in the ejb-jar.xml),
one is ApplicationServiceDBDS for SI and the other one is ApplicationDBDS(I don’t know the exact reason why this is needed, but when running the webservice, Framework was throwing an error asking for this) After adding these two, now(while running the webservice) we’re caught up with an error saying that unable to participate in two phase commit. I think this is because we added two dataSources, if we just use one dataSource everything is working fine.
Error message from app server:
"JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source=ApplicationDB"
we have made the changes to ApplicationDB as said in the error message, but then the server is failing to start because of this.

Hi,
this is what the doc says - though not about two phase commit but transaction sharing:
"At runtime, the calling client and the ADF service may or may not participate in the same transaction, depending on the protocol used to invoke the service (either SOAP or RMI). Only the RMI protocol and a Java Transaction API (JTA) managed transaction support the option to call the service in the same transaction as the calling client."
When your application accesses a remote ADF Business Components service, each remote call is stateless, and the remote service will not participate in the same transaction as the business component that uses a service-enabled application module's service interface.
In the majority of the cases, calls to remote services will be informational in nature and will not make changes to remote objects. However, if you must use a remote service to make changes, then keep these points in mind:
An exception thrown by the remote service will cause the local transaction to fail.
If you successfully call a remote service that results in modifying data, and then subsequently your local transaction fails for any reason, then it is the responsibility of your error handling code to perform a compensating transaction against the remote service to "undo" the previous change made."
http://docs.oracle.com/cd/E23943_01/web.1111/b31974/bcextservices.htm
Frank

Multiple Operations in 7.1

Hi,
I would like to know about multiple operations in 7.1.
In what kind of scenarios it can be used. When it can be used?

Hi Abhishek,
> I doubt this statement.....any document available for the same?
Please refer to this [document|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50a1a52b-688c-2a10-bc91-8985e4a188a0] , page 12 specifically. It will answer you doubt.
> If Stateless XI30 Compatible then only one Operation will be visible. Operation name in this case cannot be changed
> For all other Interface Patterns, Operation name can be selected.....they need not (rather cannot) be same as the Service Interface name (they can be similar)
You can always delete the default operation(changing to Stateless temporarily) and create new, but it wont work for XI 3.0 compatible. This case should have same name in operation name as the Service Interface name. By default u cant edit.
> having ERP as source/ target is not mandatory.
> mapping to XI30 compatible is also not mandatory. just refer my blog and it will answer some of your doubts
Yes I agree the ERP is not mandatory. But, the point is that application should be capable of WS-RM protocol. ERP is just an example here.
Its good having discussion on this topic.
Regards,
Vikas
Edited by: Vikas Aggarwal on Oct 1, 2009 5:13 PM
Edited by: Vikas Aggarwal on Oct 1, 2009 5:15 PM

Multiple Operation in Service Interface

Similar Messages

Maybe you are looking for