Soap to soap scenario with multiple operations

hi experts,
I want to do a scenario in which I have sender RFC(asynchronous) and receiver SOAP(Synchronous) and response will come back to a file.
Can anyone please help me, how many communication channels are required and how to do configuration.
regards,
vineetha chowdary

> want to do a scenario in which I have sender RFC(asynchronous) and receiver SOAP(Synchronous) and response will come back to a >file.Can anyone please help me, how many communication channels are required and how to do configuration.
RFC (ASYNC) --->SOAP(SYNC) ---> FILE(ASYNC)
You can do this with bpm or without bpm.
Doing WITHOUT BPM is simple. Refer the following [link |http://wiki.sdn.sap.com/wiki/display/XI/File-RFC-File%28Without%20BPM%29?bc=true]for handling async sync pattern ...
Follow closely this link .. ONly difference is file (sender) and file receiver are async and RFC is sync. In your case RFC(sender) and FIle(receiver) async and SOAP is sync.

Similar Messages

Problem initiating process with multiple operations using HTTP/SOAP

Hi,
I have defined a process which has multiple operations. My process starts with a pick activity containing onMessage branches for each possible operation. When I initiate this service using the BPEL console, I choose one of the operations and everything works fine.
However, when I initiate this process using an HTTP/SOAP web service call using JMeter, always the first branch is executed regardless of the message I send.
My operations are document/literal. Due to some restrictions, I cannot define a SOAPAction for the operations. Could this be the problem? Is there a workaround for this? If this is not the problem, what could be the cause?
I'm using version 10.1.2.1.
Any help will be appreciated. Thanks in advance..

hi i am using 10.1.3 and still i can not initiate a process with multiple operations. Is there anybody to tell if pick activity works fine and if there are some points to consider?
If there is a problem is there any solution to make a process with multiple operations?

File to Web service (SOAP) to File scenario with out BPM in PI 7.1

Hi All,
I have scenario File to Web service (SOAP) to File scenario with out BPM.i am getting the below error:
1) Error MP: unexpected exception caught com.sap.aii.af.service.cpa.impl.exception.CPAObjectKeyException: Value of key must not be null: ObjectId
2) Error ROB: error during processing: com.sap.aii.af.lib.mp.processor.ModuleProcessorException: Processing Error
PI server is 7.1 with SP:8
I have configured the scenario like this
1) 2 File channels - Sender & Receiver ,1 RFC channel - Receiver. We need to note that, the additional Module parameters need to be added only for sender File channel
2) Created Sender Agreement
3)Created Receiver Determination
4)Created Interface Determination
5)Created Receiver Agreement
Regards,
Ramesh

Hi,
Thanks for your reply!!
My Scenario is File to SOAP to File.
Configred modules in Sender channal below:
Prcessing sequence:
Number       Module Name                                        Module Key
1..........       AF_Modules/RequestResponseBean.......1
2..........       CallSapAdapter..........................................2
3..........       AF_Modules/ResponseOnewayBean.......3
Module Configuration:
Module Key                                       Parameter Name                                       ParameterValue
1                                                        passThrough                                            true
3                                                        receiverChannel                                       receiverChannel name
3                                                        receiverService                                        receiverService name
please tell any more confiration requered.
Regards,
Ramesh

WebService with multiple operations [JCD as WebService]

Hi,
I am using JCAPS 5.1.1.
My requirement is, i need to create a JCD (callable as external soap Webservice) which has multiple operations.
While creating jcd user will be prompted for input,output message and operation name.
But here we can give only one operation. In this case if i want multiple operations to be performed in single JCD what i have to do.
I tried adding methods manually, to that JCD. After this i build it and deployed. When i check the generated WSDL in UDDIdocs directory
manually added methods to jcd were not present in WSDL file at all.
Only one operation name was present that too which i gave at time of creating JCD.
Hence if i want to expose JCD as webservice with multiple operations what i have to do.
Please help me.
Regards
Venkatesh.S

Hi,
I tried do the same, but I was imposible.
In this case I do a bussines process, which implement a wsdl, and the logic all was solved in a java collaboration. That is my jcd was called from bp.
So my wsdl has four operations and my java collaboration receive on the input message operation name, so my java collaboration evaluate this operation and process request.

Execute scenario with multiple variables through ODIInvoke webservice

I am looking to execute scenario with multiple variables through ODIInvoke webservice but can't seem to get the SOAP request formatted correctly. Here is what I have tried but I get a parsing error.
<invokeScenarioRequest>
<invokeScenarioRequest>
<RepositoryConnection>
<JdbcDriver>org.hsqldb.jdbcDriver</JdbcDriver>
<JdbcUrl>jdbc:hsqldb:hsql://localhost</JdbcUrl>
<JdbcUser>sa</JdbcUser>
<OdiUser>SUPERVISOR</OdiUser>
<OdiPassword>SUNOPSIS</OdiPassword>
<WorkRepository>DEVELOPMENT</WorkRepository>
</RepositoryConnection>
<Command>
<ScenName>I_TEST_WS</ScenName>
<ScenVersion>001</ScenVersion>
<Context>DEVELOPMENT</Context>
<LogLevel>5</LogLevel>
<SyncMode>1</SyncMode>
<Variables>
<Name>SNI.DMN_CD</Name>
<Value>DTA</Value>
</Variables>
<Variables>
<Name>SNI.ADPT_CD</Name>
<Value>RAT_CD</Value>
</Variables>
</Command>
<Agent>
<Host>S119SNIP045166</Host>
<Port>20910</Port>
</Agent>
</invokeScenarioRequest>
</invokeScenarioRequest>
Here is the error I am getting
com.sunopsis.wsinvocation.SnpsWSInvocationException: java.lang.RuntimeException: Unexpected subelement Name
     at com.sunopsis.wsinvocation.client.a.a.d.requestReply(d.java)
     at com.sunopsis.graphical.wsclient.f.b(f.java)
     at com.sunopsis.graphical.tools.utils.swingworker.v.call(v.java)
     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
     at com.sunopsis.graphical.tools.utils.swingworker.l.run(l.java)
     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.RuntimeException: Unexpected subelement Name
     at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
     at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
     at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1515)
     at org.apache.crimson.parser.Parser2.content(Parser2.java:1766)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1494)
     at org.apache.crimson.parser.Parser2.content(Parser2.java:1766)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1494)
     at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
     at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
     at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
     at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
     at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
     at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:1792)
     at com.sunopsis.wsinvocation.client.a.a.d.a(d.java)
     ... 8 more
Caused by:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultSubcode:
faultString: java.lang.RuntimeException: Unexpected subelement Name
faultActor:
faultNode:
faultDetail:
     {http://xml.apache.org/axis/}stackTrace:java.lang.RuntimeException: Unexpected subelement Name
     at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
     at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
     at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1515)
     at org.apache.crimson.parser.Parser2.content(Parser2.java:1766)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1494)
     at org.apache.crimson.parser.Parser2.content(Parser2.java:1766)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1494)
     at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
     at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
     at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
     at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
     at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
     at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:1792)
     at com.sunopsis.wsinvocation.client.a.a.d.a(d.java)
     at com.sunopsis.wsinvocation.client.a.a.d.requestReply(d.java)
     at com.sunopsis.graphical.wsclient.f.b(f.java)
     at com.sunopsis.graphical.tools.utils.swingworker.v.call(v.java)
     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
     at com.sunopsis.graphical.tools.utils.swingworker.l.run(l.java)
     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
     at java.lang.Thread.run(Thread.java:595)
     {http://xml.apache.org/axis/}hostname:S119SNIP045166
java.lang.RuntimeException: Unexpected subelement Name
     at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
     at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
     at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1515)
     at org.apache.crimson.parser.Parser2.content(Parser2.java:1766)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1494)
     at org.apache.crimson.parser.Parser2.content(Parser2.java:1766)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1494)
     at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)
     at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
     at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
     at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
     at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
     at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:1792)
     at com.sunopsis.wsinvocation.client.a.a.d.a(d.java)
     at com.sunopsis.wsinvocation.client.a.a.d.requestReply(d.java)
     at com.sunopsis.graphical.wsclient.f.b(f.java)
     at com.sunopsis.graphical.tools.utils.swingworker.v.call(v.java)
     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
     at com.sunopsis.graphical.tools.utils.swingworker.l.run(l.java)
     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
     at java.lang.Thread.run(Thread.java:595)
If I change it from
<Variables>
<Name>SNI.DMN_CD</Name>
<Value>DTA</Value>
</Variables>
<Variables>
<Name>SNI.ADPT_CD</Name>
<Value>RAT_CD</Value>
</Variables>
to
<Variables>
<Name>SNI.DMN_CD</Name>
<Value>DTA</Value>
</Variables>
the session runs. Does anyone know the syntax for multiple variables being passed?
Thank you,
Troy

Hi,
The xml should be like this
<variables>
<name>SNI.DMN_CD</name>
<value>DTA</value>
<name>SNI.ADPT_CD</name>
<value>RAT_CD</value>
</variables>
Hope this helpful.
Regards

Problem in creating Maintenance Order with multiple operations

Hello all,
I am facing problem while creating Maintenance Order with multiple operations and sub-operations. I am using BAPI : BAPI_ALM_ORDER_MAINTAIN.
For single operation it is working fine,but i am unable to create MO with multiple operations and sub-operations.
Please, provide me the inputs required,
I have used methods :
ORDER CREATE,
OPERATION CREATE
and SAVE.
Regards,
Siddhartha

Hi,
The FM you are using is a perfect one. This FM is bit tricky to use. You need to perfectly pass the Reference number field. which links various input table parameters of this FM.
Thanks & Regards,
Navneeth K.

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.

"SOAP:Fault" in scenario with ABAP proxy client

Hello,
I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.
XI:
The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).
CRM:
The proxy generation is ok.
SLDCHECK is ok.
All RFC destinations are ok.
APPINT_200_620 for CRM was installed and configured well (I think so, but...).
When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = DC4424A659314CF18F500002A541D0E7</Trace>
<Trace level="1" type="T">PLNAME = SENDER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
<Trace level="1" type="T">system-ID = EST</Trace>
<Trace level="1" type="T">client = 300</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = BABKIN_RA</Trace>
<Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">
<Trace level="1" type="T">URL for integration server read from global configuration</Trace>
<Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIServer</SAP:Category><SAP:Code area="SECURITY">INBOUND_SECURE_LEVEL</SAP:Code><SAP:P1>DC4424A659314CF18F500002A541D0E7</SAP:P1><SAP:P2/><SAP:P3>HTTP</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP' </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></Trace>
</Trace>
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
<Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
</SAP:TraceHeader>
I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.
Does anybody know where to find a solution?
Regards,
Roman

Hi Roman
There is no need for an XI adapter for client proxy.... we only use that for server proxies.
Vaibhav

Soap to File Scenario with BPM

Hi Guys
I have create my Soap to File Scenario using BPM to split the file on "Transformation step" into 7 files and it must save these files to my FTP Server, when testing on sxmb_moni I don't get any errors but when checking on the FTP server no files are created, and I understand that it should be showing all seven processing on the sxmb_moni, but that is not happening.
I have used the ForEach mode on my Block.
What could I be doing wrong.
Thanks!!
Yonela

go to runtime work bench to see communication channel, especailly the receiver channel.
To see what happened on it

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

Error by invoking BPEL with multiple operations...

Hi,
i am trying to invoke BPEL1 with two operations from BPEL2. I am getting the error below. But the wsdl contains this "work" porttype (I appended the WSDL from the BPELConsole after the error message...). The BPEL1 has a pick for each operation...
ORABPEL-00000 Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is:
"ORABPEL-08010 Failed get operation definition.
Failed to get the WSDL operation definition of "work" in portType
"{http://xmlns.oracle.com/BPELMultOperations}BPELMultOperations".
Please verify that operation "work" is defined in portType
"{http://xmlns.oracle.com/BPELMultOperations}BPELMultOperations". at
com.collaxa.cube.ws.wsdl.WSDLUtils.getOperation(WSDLUtils.java:211) at
WSDL:
snip...
<portType name="BPELMultOperationsCallback">
<operation name="onResult">
<input message="tns:BPELMultOperationsResponseMessage"/>
</operation>
</portType>
<portType name="BPELMultOperations">
<operation name="initiate">
<input message="tns:BPELMultOperationsRequestMessage"/>
</operation>
<operation name="work">
<input message="tns:BPELMultOperationsRequestMessage"/>
</operation>
</portType>
<binding name="BPELMultOperationsBinding" type="tns:BPELMultOperations">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="initiate">
<soap:operation style="document" soapAction="initiate"/>
<input>
<soap:header message="tns:WSAReplyToHeader" part="ReplyTo" use="literal" encodingStyle=""/>
<soap:header message="tns:WSAMessageIDHeader" part="MessageID" use="literal" encodingStyle=""/>
<soap:body use="literal"/>
</input>
</operation>
<operation name="work">
<soap:operation style="document" soapAction="work"/>
<input>
<soap:header message="tns:WSAReplyToHeader" part="ReplyTo" use="literal" encodingStyle=""/>
<soap:header message="tns:WSAMessageIDHeader" part="MessageID" use="literal" encodingStyle=""/>
<soap:body use="literal"/>
</input>
</operation>
</binding>
<binding name="BPELMultOperationsCallbackBinding" type="tns:BPELMultOperationsCallback">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="onResult">
<soap:operation style="document" soapAction="onResult"/>
<input>
<soap:header message="tns:WSARelatesToHeader" part="RelatesTo" use="literal" encodingStyle=""/>
<soap:body use="literal"/>
</input>
</operation>
</binding>
<service name="BPELMultOperations">
<port name="BPELMultOperationsPort" binding="tns:BPELMultOperationsBinding">
<soap:address location="http://uranus042.local:7777/orabpel/university/BPELMultOperations/1.0"/>
</port>
</service>
<service name="BPELMultOperationsCallbackService">
<port name="BPELMultOperationsCallbackPort" binding="tns:BPELMultOperationsCallbackBinding">
<soap:address location="http://set.by.caller"/>
</port>
</service>
<plnk:partnerLinkType name="BPELMultOperations">
<plnk:role name="BPELMultOperationsProvider">
<plnk:portType name="tns:BPELMultOperations"/>
</plnk:role>
<plnk:role name="BPELMultOperationsRequester">
<plnk:portType name="tns:BPELMultOperationsCallback"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>

I'm facing the same issue, did you get a resolution to this?
I'm suspecting that you cant use the same variable for 2 different ports.
Any help would be appreciated.
cheers
James

Can you have multiple Rates within one Work Center with multiple operations

We have a work center called Pipeshop. Within the Pipeshop we have multiple operations such as Welding, Threading, Cutting, Grooving etc. Each of these operations have a different cost assoicated with them. How can you have different cost for these operations?
Thank you,
Loretta

Hi,
For this case you need to do following activities.
1 Create individual activity accoding to requirement, that will be used for costing.
2 Activity planning w r t work center. In this cost per unit is declaring.
3. Create Routing and modify the default activity type, w r t required activity type, suitable to operations.
Now Order is referring the activity type, refered in Routing rather than, work center.
Regards
Gururaja Hebbar

One SOAP-SOAP scenario with multiple interfaces

Hi,
I am developing a scenario SOAP-SOAP using PI 7.10 Sp6.
The wsdl has around 8 service interfaces and i am planning to create 8 Outbound and 8 Inbound interfaces for the same mesg type and create a scenario without MM or Operation mapping.
If I plan to use only one Sender CC and only one configuration scenario for this developement, how do I provide my end point in the following format?
http://<host>:<port>/XISOAPAdapter/MessageServlet?senderParty=&senderService=<SEND_BS>&interface=Interface_Out&receiverParty=&receiverService=<RECV_BS>&interfaceNamespace=http://test.com/xi/SAP/
Venkat.

Raj/Pavan,
I added other service interfaces to one service interface in operations.
But the request messages have not appeared because of which it is throwing an exception when I activate the message interface.
I do not have problems on the receiving side, One receiver CC should take care of the problem as we dont specify in the recvr SOAP action attribute.
I am worried about sender side only !
Thanks,
Venkat.
Just now I created a dummy DT, MT and SI and added this to existing even that request message did not show up in the SI.
Edited by: Venkat A on Jun 16, 2010 11:03 AM

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

Biztalk schema exposing as WCF service with multiple operations

Hi,
I am working on a design pattern to expose the BizTalk schema as a WCF service and thought of taking expert’s advice. I have a single schema with 30 different nodes and each one is a different message type. For this 30 message types we need to expose WCF
endpoints to customer for consuming from their application.
When I exposed this schema as WCF service, a single receive location got created in BizTalk application and in IIS there is one .svc file. I defined 30 operations for this while exposing the endpoint with wizard.
Currently I came up with the below 2 approaches but I did not like them as there is more redundancy
Create 30 different orchestrations and each orchestration subscribes to Message Box direct binding with message type as filter.
Create a single orchestration that binds to single receive location( this location got created by wizard..) and access the operation/message type in the expression shape. Based on this value create 30 IF conditions for each message type. For this the
single orchestration receive shape should have a message type of xml document and then access the type. Is it possible?
I don’t like the above approaches as it is very difficult to maintain and also difficult to add for any new message type.
Does anyone has good ideas for doing this?
Thanks
JB

"Canonical Schemas" are used where multiple source messages need to be addressed by a SINGLE Operation !!!
Every operation anyway translates to a separate process. Forget that we're dealing with BizTalk for a minute, when you're writing plain we services, you introduce new service contracts (operations) when you deal with different data contracts. To come back,
in BizTalk your data contracts are your schemas. So when you have multiple schemas, each requiring different processing then you need different orchestrations.
Let us for a minute assume you've defined a single service schema (very possible with a service header and a service details where the service data contract could differ). Now you use this schema to expose ONE service endpoint (good till now). In that service
you're suggesting to ADD decisions (something like a switch statement where you'll do 'x' set of activities is the message is of 'x' type and so on... How is this sustainable? Every time you introduce an new operation, you'll have to tear down and redeploy
the new orchestration which will affect all other operations. During the introduction of ONE op you may touch other parts of the orchestration (multiple branches in a parallel shape anyways make the orchestration very unwieldy from a code management/support
standpoint) and introduce errors in existing ops.
Regards.

Soap to soap scenario with multiple operations

Similar Messages

Maybe you are looking for