No endpoints found for interface

Hi All,
I have the following scenario: RFC in the backend system (ECC 6.0 SP09 no EhP's) and PI 7.1 as an Integration Broker.
I have imported the RFC into Enterprise Services Repository and done the necessary tasks to configure an Enterprise Service.
After that I have published the Interface to the Services Registry, Testing the Interface in WSNavigator is working fine.
I have imported the Enterprise Service into Web Dynpro as a model and when running the Web Dynpro application I am receiving the following error:
com.sap.esi.esp.service.server.query.discovery.ExtendedServiceException: no endpoints found for interface TreeInformationQuery_Out
defaultTrace:
Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for web service mass config parameters service reference ID 'TreeInformationQuery_Out_FICSIT_BASIC' and application name 'demo.sap.com/ficsit~tree'. Check mass configuration has been done properly.
at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:522)
Any idea's?
Regards,
Ridouan

Hi Sergei,
My backend system is ECC 6.0 SP9 (no EhP's) and therefore I can't use the trx SOAMANAGER.
I have imported an RFC from the ECC system into the PI 7.1 Enterprise Services Repository (Builder) and then published the Service (from Sender Agreement) into Services Registry also on the PI 7.1 system.
Testing the service in WS Navigator is working fine, I can see an endpoint here.
Also testing the WSDL with third-party application is working fine.
JAVA Web Dynpro is given me the error: no endpoints found for interface...
Thanks again.
Regards,
Ridouan

Similar Messages

Error. in WS Navigator - no endpoints found for interface

Dear Friends,
I have created a new Enterprise Service Interface and implemented in ABAP. After the implementation I used SOAMANAGER to create the endpoint and publish the service using WSPUBLISH to Service Registry. When I tested this service from SOA Management application(SOAMANAGER), the endpoint is working very good, but when I am testing this service from Service Registry, it is now showing any endpoint in the 'Enter Input Parameters' Step. Also when I am trying to search the Service by using 'Search by Logical Destination', it shows the Service and when I select it, it shows an error message, "no endpoints found for interface (<namespace>/document)<Service Interface Name>_Document".
If some one knows about this issue, please advice me to do next steps.
Also I am planning to call this service from Visual Composer, I have configured the two logical destinations over there, also the service registry, even though, when i am searching the service, it shows an error like "Could not complete search".
Please advice me for the above issue also.
Thanks in advance
Vipindas

Hi,
If you have configured and tested from SOAMANAGER (which opens WSnavigator) then it is configured correctly. May be you are using wrong WSDL address.
Copy url of wsdl from SOAMANGER test screen and use it directly in WSnavigator for testing.
Regarding publishing of service WSPUBLISH should be able to publish correct service into service registry, but if for any reason it is not working then you can "publish" it directly from service registry by using publish option and provide url of wsdl from above option.
If for any reason VC is unable to search service registry then create destination template for your every service by providing WSDL and use it in VC.
Regards,
Gourav

Webservice: No endpoints found

Hi gurus!
I'm not sure on witch forum to post this thread... so here goes...
I'm trying to create a webservice for an RFC function module (ZBAPI_HELLO_WORLD). I've already tried some manuals like http://help.sap.com/saphelp_nw70/helpdata/EN/0d/2eac5a56d7e345853fe9c935954ff1/content.htm, step by step, apparently everything works fine.
I go to SOAMANAGER, Web Service Administrator, select the service, verify that the endpoint is created, and everything seems OK.
However, I go to WSNAVIGATOR, enter the webservice (http://sapdes.bel.com.ve:8000/sap/bc/srt/rfc/sap/ZBAPIHELLOWORLD?sap-client=200&wsdl=1.1), but when I try to test it, I get the following error: No endpoints found for this Web service
I've tried deleting it and creating it again, and again, but so far nothing works, still the same error...
Am I missing something? some step I haven't seen?
Basically I'm using transactions SE37 to create the WS, and SOAMANAGER to test it, nothing more...
Appreciate any help!
Jesus

Hi... I'm working on ECC 6.0, so transactions WSADMIN and WSCONFIG are not available, instead I use transaction SOAMANAGER.
I checked note 1113162, but my system already has the SP level where the note was distributed, so it's already applied.

Webservcie: No endpoints found

Hi gurus!
I'm new to WebServices....
I'm trying to create a webservice for an RFC function module (ZBAPI_HELLO_WORLD). I've already tried some manuals like http://help.sap.com/saphelp_nw70/helpdata/EN/0d/2eac5a56d7e345853fe9c935954ff1/content.htm, step by step, apparently everything works fine.
I go to SOAMANAGER, Web Service Administrator, select the service, verify that the endpoint is created, and everything seems OK.
However, I go to WSNAVIGATOR, enter the webservice (http://sapdes.bel.com.ve:8000/sap/bc/srt/rfc/sap/ZBAPIHELLOWORLD?sap-client=200&wsdl=1.1), but when I try to test it, I get the following error: No endpoints found for this Web service
I've tried deleting it and creating it again, and again, but so far nothing works, still the same error...
Am I missing something? some step I haven't seen?
Basically I'm using transactions SE37 to create the WS, and SOAMANAGER to test it, nothing more...
Appreciate any help!
Jesus

check your URL... it need to have the correct port number, WSDL version etc..
http://<host_name>:<port_number>/sap/bc/soap/rfc
[Refer to this link>>|http://help.sap.com/saphelp_47x200/helpdata/en/2d/64d01de74911d6b2e400508b6b8a93/content.htm]

No endpoints found

Hi,
in the soamanager the webservice has an endpoint but anyway a I get this message
Web Service Navigator.
I am entering the WSDL URL of the Web service and on testing I get the message
No endpoints found for this Web service.
Pls. help me in this matter
Bye
Sw

check your URL... it need to have the correct port number, WSDL version etc..
http://<host_name>:<port_number>/sap/bc/soap/rfc
[Refer to this link>>|http://help.sap.com/saphelp_47x200/helpdata/en/2d/64d01de74911d6b2e400508b6b8a93/content.htm]

No business interface, component interface or web service endpoint interface found for Session Bean SessionEJB

hi ,
i am just using EJb in my Application
just created an SessionBean and with Local interface in it i am getting this wierd exception with weblogic NetBeans and eclipse also
weblogic.ejb.container.compliance.ComplianceException: No business interface, component interface or web service endpoint interface found for Session Bean SessionEJB
weblogic.ejb.container.compliance.ComplianceException: No business interface, component interface or web service endpoint interface found for Session Bean SessionEJB
    at weblogic.ejb.container.compliance.SessionBeanClassChecker.checkInterfacesExist(SessionBeanClassChecker.java:177)
    at weblogic.ejb.container.compliance.Ejb30SessionBeanClassChecker.checkInterfacesExist(Ejb30SessionBeanClassChecker.java:27)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:331)
    at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:280)
    at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:789)
    at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:222)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:461)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:428)
    at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:437)
    at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:795)
    at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:683)
    at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1254)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    at weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:321)
    at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:280)
    at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:789)
    at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:222)
    at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:461)
    Truncated. see log file for complete stacktrace
>

Hi Rajendar,
I think the problem with having empty interfaces, or interfaces without methods for EJBs, is that they don't really make "sense". After deploying your EJB, a client application will use JNDI or dependency injection to access your EJB. So in your case it will look something like this
@EJB
    mytestSSBLocal myejb; //(In this case we are using the local interface)
In the second step, you will want to do something will your EJB, but since mytestSSBLocal doesn't define any methods, there is nothing you can do with your ejb.
The Exception is telling you that weblogic couldn't find a complaint interface for your EJB.
best regards, Nicolas

The service cannot be found for the endpoint reference (EPR) 127.0.0.1/a

Hi All:
I need help!!!
I am using axis2-1.5.1, jdk 1.6, eclipse 3.5, and Axis2_Codegen_Wizard_1.3.0 and windows xp.
I used Axis2_Codegen_Wizard_1.3.0 to generate the client stub and proxy.
I get the following error when I tried to call the web service:
package com.ttdev.ss.client;
import java.rmi.RemoteException;
import com.ttdev.ss.client.SimpleServiceStub.ConcatRequest;
import com.ttdev.ss.client.SimpleServiceStub.ConcatResponse;
public class SimpleClient
     public static void main(String[] args) throws RemoteException
          try
          SimpleServiceStub service = new SimpleServiceStub();
          ConcatRequest request = new ConcatRequest();
          request.setS1("abc");
          request.setS2("123");
          ConcatResponse response = service.concat(request);
          System.out.println(response.getConcatResponse());
          catch(Exception e)
               System.out.println("e.getMessage():"+e.getMessage());
Here is my SimpleService.wsdl:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="SimpleService" targetNamespace="http://ttdev.com/ss" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://ttdev.com/ss" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<wsdl:types>
<xsd:schema targetNamespace="http://ttdev.com/ss">
<xsd:element name="concatRequest">
<xsd:complexType>
<xsd:sequence>
     <xsd:element name="s1" type="xsd:string"/>
     <xsd:element name="s2" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="concatResponse" type="xsd:string">
</xsd:element>
</xsd:schema>
</wsdl:types>
<wsdl:message name="concatResponse">
<wsdl:part name="parameters" element="tns:concatResponse">
</wsdl:part>
</wsdl:message>
<wsdl:message name="concatRequest">
<wsdl:part name="parameters" element="tns:concatRequest">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="SimpleService">
<wsdl:operation name="concat">
<wsdl:input message="tns:concatRequest">
</wsdl:input>
<wsdl:output message="tns:concatResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="SimpleServiceSOAP" type="tns:SimpleService">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="concat">
<soap:operation soapAction="http://ttdev.com/ss/NewOperation"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="SimpleService">
<wsdl:port name="SimpleServiceSOAP" binding="tns:SimpleServiceSOAP">
<soap:address location="http://localhost:8080/axis2/services/"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
In the dos-prompt, I get the following error message:
[INFO] Listening on port 8080
[ERROR] The service cannot be found for the endpoint reference (EPR) 127.0.0.1/a
xis2/services/
org.apache.axis2.AxisFault: The service cannot be found for the endpoint referen
ce (EPR) 127.0.0.1/axis2/services/
at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPha
se.java:65)
at org.apache.axis2.engine.Phase.invoke(Phase.java:334)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:251)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:160)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReq
uest(HTTPTransportUtils.java:167)
at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:26
6)
at org.apache.axis2.transport.http.server.AxisHttpService.doService(Axis
HttpService.java:281)
at org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(
AxisHttpService.java:187)
at org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpS
erviceProcessor.java:82)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:619)
Thank you for your help!!!
Yours,
John.

I had the same issue and managed to fix it.
I am using tomcat and had a filter configured for AxisServlet to open a hibernate Session. Somehow (I did not figure it out yet) this filter afects the way the AxisServlet resolves the EPR.
My fix was - remove the filter. It worked. Now I am trying to figure out why.
If you have any clues, please drop a line.

Org.apache.axis2.AxisFault: The service cannot be found for the endpoint

Hi Team,
I'm getting following error while runnig WebServices
[ERROR] The service cannot be found for the endpoint reference (EPR) /TestServices/services
org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /TestServices/services
Please guide me where i went wrong
Thanks in Advance
Ravi

I am also facing the same problem. can any body help us?
Thanks
jaya

Endpoints not found for service

hi
We are working on BPM Ce 7.2 where in we have uis in webdynpro java which calls a service from SR.
the service is workign fire from sr and soamanager.
however when we launch the application in portal it says that end point not found for that service.
We have checked Destination templates, system connections in nwa, and portal.
The same code is working fine in dev and wa workign fine in quality also until there was a ehp5 upgrade and refresh.
Has it to do anything with the upgrades and is there any other setting missing.
Any syggestions, please.
regards
Lavanya

Hello Varungulati,
I'm having the same issue, did you manage to solve this problem ?
Thanks,
Nadjia

ERROR in PI : No sender agreement found for , , , , ,

Hello everybody,
i'm working with SAP PI 7.1
it's a new installation.
I created the first easy interface JDBC-Pi-File.
when i activate the CC i don't see any message in SXMB_MONI but in RWM i see the messages in Waiting status and when i look inside i see the follow error:
SOAPFAULT received from Integration Server. ErrorCode/Category: XIServer/INBOUND_BINDING_ERROR; Params: BS_CSIS_DEV, http://xxxx.com/test, SI_DB2SP_DOCUMENTS_AA_02; AdditionalText: null; ApplicationFaultMessage: null; ErrorStack: Error in sender agreement for party , service BS_CSIS_DEV, interface namespace http://xxx.com/test interface SI_DB2SP_DOCUMENTS_AA_02 No sender agreement found for , , , , ,
1-Configuration is ok. I create all steps and sender Agreement exist
2-end point http://yyyyy:50100/sap/xi/engine?type=entry is correct and the same in SLD and sxmb_adm -> Integration Engine Configuration
3-i suppose 50100 port is correct because when i try to use 8010 port i have a different error.
4- i alreadi used CPA cache refresh and SXI_CACHE.
Any suggestion?
thanks

after 20 minuts i retry.
Now the error message is changed:
Transmitting the message to endpoint http://yyyyyy:8010/sap/xi/engine?type=entry using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.net.ConnectException: Connection refused.
Edited by: apederiva on Aug 25, 2010 11:35 AM

Web Service Error - no service endpoints found

Hi,
I tried to create a web service deployable proxy project to consume an external third party web service url. There were no files generated for Logical Ports and Proxy Classes, though there are files generated for WSDL and SEIs. A further test on http://ip:port/index.html -> web service -> Enter the WSDL URL of the Web service -> No Service Endpoints Found, prove that something wrong with the url.
Any idea for me to check what goes wrong with the web service url? or could it due to firewall?

In the meantime, there are also consuming my java-created web service using the test tool from http://www.soapclient.com/soaptest.html.
Error given as below, from the
wsse:InvalidSecurity0012BF1423AB0047000000350000065C00041741F13F5CDC : Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; 0012BF1423AB0047000000350000065C00041741F13F5CDC : Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext';
From my application log, error shown as below:
#1.5#0012BF1423AB0047000000360000065C00041741F13F5DA5#1151471894671#com.sap.security.core.server.ws.service.ServerSecurityProtocol#sap.com/AdapterWSTabEAR#com.sap.security.core.server.ws.service.ServerSecurityProtocol.handleRequest#J2EE_GUEST#230####800311f0066511dba3770012bf1423ab#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Security/WS/SecurityProtocol#Java###An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
#1.5#0012BF1423AB0049000000370000065C00041741F475BD3F#1151471948578#com.sap.security.core.server.ws.service.ServerSecurityProtocol#sap.com/AdapterWSTabEAR#com.sap.security.core.server.ws.service.ServerSecurityProtocol.handleRequest#J2EE_GUEST#230####a024a020066511db954d0012bf1423ab#SAPEngine_Application_Thread[impl:3]_9##0#0#Error#1#/System/Security/WS/SecurityProtocol#Java###An error occurred while processing the message security. Reason: . See trace entry .#3#com.sap.engine.interfaces.webservices.runtime.OperationNotFoundException#Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:EMMWSWsd'; Key name:'SoapRequestWrapper' key value:'sendMOtext'; #[no trace for com.sap.security.core.server.ws.service.ServerSecurityProtocol (severity above PATH)]#
Anyone has any idea what's the rootcause of all the incompatibility?

After upgrade to 11.1.1.2 Agreement not found for trading partners

We just upgraded from 11.1.1.1 to 11.1.1.2 and an existing composite that sends a file from Oracle EBS to an outside trading partner is not working.
We tried importing the Agreement from the 11.1.1.2 and when it did not work, we purged the repository and started from scratch.
The error we are getting is:
Agreement not found for trading partners: FromTP Rheem, ToTP JPMorgan with document type JPPositivePay-1-OUTBOUND
This is a file that we are sending from Oracle EBS to an outside trading partner via FTP.
One thing we are noticing is that when we create the agreement, it does not show up under our host TP, it only shows up under the target TP.
We have set up the TP, Channel, and agreements exactly like they are set in the 11.1.1.1 environment.
Here is the log file in debug mode.
[2010-06-17T07:40:10.471-04:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] oracle.tip.b2b.engine.Engine:handleOutboundException notifying App
[2010-06-17T07:40:10.471-04:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] Notification: notifyApp: Enter
[2010-06-17T07:40:10.479-04:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] Notification: notifyApp: payload = <Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">[[
<correlationId>7F00000112945B5769F00000AEC3D2E0</correlationId>
<b2bMessageId>10011</b2bMessageId>
<errorCode>B2B-50547</errorCode>
<errorText>
<![CDATA[Agreement not found for trading partners: FromTP Rheem, ToTP JPMorgan with document type JPPositivePay-1-OUTBOUND.
]]>
</errorText>
<errorDescription>
<![CDATA[Machine Info: (afsmlnx04.rheem.com)
Description: Agreement not found for trading partners: FromTP Rheem, ToTP JPMorgan with document type JPPositivePay-1-OUTBOUND.
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
[2010-06-17T07:40:10.486-04:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] Notification: notifyApp: Enqueue the exception message:[[
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>7F00000112945B5769F00000AEC3D2E0</correlationId>
<b2bMessageId>10011</b2bMessageId>
<errorCode>B2B-50547</errorCode>
<errorText>
<![CDATA[Agreement not found for trading partners: FromTP Rheem, ToTP JPMorgan with document type JPPositivePay-1-OUTBOUND.
]]>
</errorText>
<errorDescription>
<![CDATA[Machine Info: (afsmlnx04.rheem.com)
Description: Agreement not found for trading partners: FromTP Rheem, ToTP JPMorgan with document type JPPositivePay-1-OUTBOUND.
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
[2010-06-17T07:40:10.492-04:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] Notification: deliverException: Send message to endpoint IP_IN_QUEUE
[2010-06-17T07:40:10.492-04:00] [soa_server1] [TRACE:32] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: log] URL ===== aq://IP_IN_QUEUE@jdbc/SOADataSource
[2010-06-17T07:40:10.514-04:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] oracle.tip.b2b.transport.AppTransportInterface:send TO Endpoint: 509 aq://IP_IN_QUEUE@jdbc/SOADataSource
[2010-06-17T07:40:10.522-04:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.transport] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.transport.basic.TransportLogger] [APP: soa-infra] [SRC_METHOD: log] TransportProperties.TransportProperties():internal=true;aq.sender.queue_name=IP_IN_QUEUE;aq.sender.datasource=jdbc/SOADataSource;aq.sender.queue_payload_col=PAYLOAD;aq.sender.recipients=b2berroruser;
[2010-06-17T07:40:11.356-04:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] oracle.tip.b2b.transport.AppTransportInterface:send Message Successfully Transmitted
[2010-06-17T07:40:11.377-04:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] oracle.tip.b2b.msgproc.MessageHandler:findInvocationContext trying doc ref
[2010-06-17T07:40:11.396-04:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] Notification: notifyApp: Exit
[2010-06-17T07:40:11.396-04:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] oracle.tip.b2b.engine.Engine:handleOutboundException Updated the Error Message Successfully: Error -: B2B-50547: Agreement not found for trading partners: FromTP Rheem, ToTP JPMorgan with document type JPPositivePay-1-OUTBOUND.
[2010-06-17T07:40:11.397-04:00] [soa_server1] [TRACE:32] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@b9d2338] [userId: <anonymous>] [ecid: 0000I_2GB8yFw000jzwkno1C6FTd0000E8,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: log] class oracle.tip.b2b.metric.B2BMessageProperties[[
fromTP : Rheem
toTP : JPMorgan
DocumentProtocol : null
DocumentProtocolVersion : null
DocumentType : JPPositivePay
Agreement : null
MessageSize : 0.0
MessageState : ERROR
FromEndpoint : null
FromEndpointProtocol : null
FromEndpointStatus : null
ToEndpoint : null
ToEndpointProtocol : null
ToEndpointStatus : null
Application : null
Application : null
Composite : null
CompositeVersion : null
Service/Reference : null
]]

In another thread Nitesh states:
b2b.documentProtocolVersion is missing in your properties and b2b.toTradingPartnerId is not set properly.
Below are the property, you should set in composite:
b2b.documentTypeName = <doctype>
b2b.documentProtocolVersion = <docRevision>
b2b.fromTradingPartnerId = <HostTPName>
b2b.toTradingPartnerId = <RemoteTPName>
b2b.messageType = <msgType>
If you want to identify TP based on Identifier then use below for TP:
b2b.toTradingPartnerId = <AS2 Identifier Value>
b2b.toTradingPartnerIdType = <AS2 Identifier>
We are setting the b2b.documentProtocolVersion variable in BPEL:
[2010-06-17T07:40:05.294-04:00] [soa_server1] [TRACE:32] [] [oracle.soa.b2b.engine] [tid: orabpel.invoke.pool-3.thread-11] [userId: <anonymous>] [ecid: 0000I_5hM0hFw000jzwkno1C6FTd0000GQ,0:1:100000028] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [composite_name: RHMAPPositivePayService] [component_name: enquedat] [component_instance_id: 10011] [SRC_METHOD: log] [composite_instance_id: 10011] class oracle.integration.platform.blocks.b2b.B2BReference : oracle.integration.platform.blocks.b2b.B2BReference@8fdf1b3 : Key : b2b.documentProtocolVersion
[2010-06-17T07:40:05.294-04:00] [soa_server1] [TRACE:32] [] [oracle.soa.b2b.engine] [tid: orabpel.invoke.pool-3.thread-11] [userId: <anonymous>] [ecid: 0000I_5hM0hFw000jzwkno1C6FTd0000GQ,0:1:100000028] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [composite_name: RHMAPPositivePayService] [component_name: enquedat] [component_instance_id: 10011] [SRC_METHOD: log] [composite_instance_id: 10011] class oracle.integration.platform.blocks.b2b.B2BReference : oracle.integration.platform.blocks.b2b.B2BReference@8fdf1b3 : Value : 1
Edited by: robn77 on Jun 17, 2010 5:27 AM

S/A bridge problem: No object type found for the message

Hi all,
I've been spending days looking into the following problem. I have a RFCXIFile scenario. The R3 system sends data via an RFC to XI and XI post the data as a flat file on a certain server using FTP.
This scenario worked just fine for 1 exception. I could only run this scenario once. The second time I got timeouts when checking the data sent to my RFC destination using SM58. When I reactivated my RFC communcation channel I could again send 1 RFC to the system. All subsequent tries would fail.
I guess this is due to the fact that I use a synchonous call (RFC) to an asynchronous one. Thus the adapter is still waiting for the response from the XI system and will not accept any further new calls from R3.
So I figure let's use this pattern called the S/A bridge. So I designed everything according to guides and examples and I'm quite certain everything is configured right but when I run the scenario I get the following message:
<i> 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="BPE_ADAPTER">UNKNOWN_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No object type found for the message. Check that the corresponding process is activated</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error></i>
It seems that the adapter cannot find any integration process to send the message into!?
I've looked at numerous threads on sdn and tried all kinds of stuff (looked at the cache==> code 0 = OK , tried to reactivate my integration process, checked the interface determination,...), but to no avail. Does anybody has an idea what could be wrong ?
Any help would be greatly appreciated for I'm all out of clues....
Bob

First of all, Thank you for trying to help me out here.
Some answer to your suggestions/questions:
The IP has return code 0 in SXI_CACHE. so that doesn't seem to be the problem.
I've checked the BPM for syntax errors. I doesn't have any.
I've reimported the BPM into the integration directory.
And did a full cache refresh in SXI_CACHE. Return code is (stays) zero, so that's OK.
I've already included the error message from SXI_MONI. It is in the last step ("Call Adater") that the error occurs.
The other steps execute just fine...
The RFC communcation channel accepts the incoming RFC call and puts into the pipeline, so no problems with the communication channel either. the problem is actually when the pipeline is trying to forward the message into an IP trhough the BPE_ADAPTER (according to SXMB_MONI).
Therefore I'm not able to go to into PE, because the workflow is never started. the BPE_ADAPTER does not find any active process for the interface determination i've entered.
So i can not debug the IP in the PE and check container variables, like some of you mentioned.
Maybe some more information about the scenario:
The RFC is called from an R3 system to XI over the interface "CONTROL_RECIPE_DOWNLOAD", which is an imported RFC, with a request and response message type.
Then I got a receiver and interface determination with lead the incoming RFC message to the IP, into interface "XI_ERP_MF_MD_CONTROL_RECIPE_REQ_AI_MI".
This is an abstract synchronous interface based on the request and response types of the "CONTROL_RECIPE_DOWNLOAD" imported RFC.
This interface is used the first step (receive) of my BPM as the synchronous interface to open the S/A bridge.
The message (container var) used in this step is
name: CORREQ
Category: Abstract interface
type: "XI_ERP_MF_MD_CONTROL_RECIPE_REQ_AI_MI"
The interface "XI_ERP_MF_MD_CONTROL_RECIPE_REQ_AI_MI" is an abstract, asynchronous interface based on the request type of the "CONTROL_RECIPE_DOWNLOAD".
Then there are 2 send steps for putting the flat files into place and finally i close the the S/A bridge using message:
name: CORRES
Category: Abstract interface
type: "XI_ERP_MF_MD_CONTROL_RECIPE_RES_AI_MI"
The interface "XI_ERP_MF_MD_CONTROL_RECIPE_RES_AI_MI" is an abstract, asynchronous interface based on the response type of the "CONTROL_RECIPE_DOWNLOAD".
I hope this information gives you guys a better understanding of hte problem.
Really looking forward to see more suggestions and to solve this nasty problem ...
Regards,
Bob

IDOC to FTP File - Error : SAP:Stack No receiver agreement found for send

Hello Friends,
I need to configure a senario Idoc to FTP File, Í did required settings in R3 and in PI... , did mapping and configuratino in PI... and when I send my idoc I got error msg in monitor
<SAP:Stack>No receiver agreement found for sender ,BMG_ASN_File_Component to receiver ,GTN_224,http://adis-bmg.de/asn,SI_BMG_ASN</SAP:Stack>
I search the fourm but did not got my answer, me just a bit confused...
In my senario I have having followings:
1. Bussiness System ( RFT : sender R3 system). ( I have define a party and make a connection under Idoc Partner )
2. Bussiness Component ( ZTEST_COMP as on Reciever side is File Server, so I define the reciver as bussiness component )
3. Communicatin Channel
    File with protocol FTP having communicatin component as my Bussiness Component ( reciver ). there I defied the required info for FTP
4. Reciever Determination
    Sender:
    - RFT
    - Idoc-Interface
    - urn:sap-com:document:sap:idoc:messages
   Reciever
    communication party = space
    communicatin component = ZTEST_COMP
    Configure Reciever:
   There I again define the communication component as ( ZTEST_COMP)
5. Interface Determination
    -RFT
    - Idoc-Interface
    - urn:sap-com:document:sap:idoc:messages
   Reviever:
    ZTEST_COMP
and define the mapping which I did in design ( although I have seen some threads where mentioned we dont need maaping in this case ) ?
6. Reciver agrement
sender:
- RFT
Reviver:
- ZTEST_COMP
- SI interface ( SI_BMG_ASN )
- http://test-etc.de/asn
and included my CC for file .....
Now when I send Idoc I got error msg that Reciver is not found : am I dong something wrong ? do I have to defien a bussiness system instead of Bussiness Component ?
Pls suggest...

( I have define a party and make a connection under Idoc Partner
Do you really need a party in your communication? Should it not be a partly-less communication.
In the receiver agreement ensure that you have included the inbound message interface.
communication party = space
No need to give any space.
In the Interface Determination i hope that you have included the receiver meessage interface and then the corresponding Interface Mapping.
If still not works then make some dummy changes and again activate....correspondingly check the cache status of the ID-objects
Regards,
Abhishek.

No standard agreement found for BS_A ,, BS_B

Hi Experts,
We are getting a very common error " No standard agreement found for BS_A ,, BS_B https://abc.com,SIOA_forcast,,,
There interface was succsfully executing few days back.
Here are some information abount the interafce.
1) JMS to IDOC
2) IDoc control record mapping
When i checked the pipe line steps in MONI , starngely it is showing
SAME SENDER interface name SIOA_forcast in sender and receiver interface . And thus it got failed in reciver agreent. I could not see the Idoc and IDoc namespace
I have searched in SDN but, did not get any clear picture
I have done the following
1) checked SXI_CAHCE and cahche instance if every object.
All objects are up -to-date
2) Deleted and recreated ID objects
3) Check the interfaces in message mapping , operation mapping , interface determination etc..., all are looking fine.
DId anyone faced this issue before.
I have asked basis for a full refresh , but i am not confident wheather that will solve the issue or not.
Please provide your valuable input and let me understand the issue.

Hi Sam
Was anything changed during last few days?
PI is not able to determine receiver interface and keeps sender inteface details. For this reason it can't find receiver agreement.
Check that your interface determination object is correct and perform a full cache refresh.
Also copy your message payload from SXMB_MONI and use the test tool (Tools -> Test configuration) in ID.
Regards,
Giuseppe

No endpoints found for interface

Similar Messages

Maybe you are looking for