ABAP Webservice Call issue

Hi
I am trying to use webservice from ABAP ECC to external server (Webspehere ).
I have configured RFC connection G Type HTTP connection to external server in SM59.
Connection sucessfull.we use basic authentication scheme to access external server.
I am able to call webservice method and getting the response in my program. but while calling second time it doesnot able to get the response. when I see the request message to external server second time, looks like some cookie adding to the request and this is causing no response back to my program.
I have raised protocal to HTTP1.1 and also selected "No Cookies"  I got few tests sucessfullbut after some time same cookie issue.   Looks like somewhere request was going with cookies...but not sure where....
anybody have this kind of issue before while calling webservice...? or how to make this cookie to not attach to request ?
or is this cookie is because of authentication set to token system instead of basic authentication at external server ?
Please suggest
Thanks
Praveen

Adding details.......
Experiencing cookie issue while calling webservice to Tivoli system hosted on IBM websphere.
Steps we have done as follows:
1. Created a ABAP Proxy class from Tivoli WSDL.
2. Configured T-Code LPCONFIG to point to above proxy class and logical port.
3. Configured  SM59 RFC connection to point to Tivoli server using basic authentication mechanism (User ID/Password).
4. Called webservice method from ABAP program.
After above steps, we are able to call the webservice method successfully but second time we are experiencing Cookie being adding to the request and eventually no response back to our program.
            When we investigated this cookie issue with IBM Websphere people, they says thay have enabled SSO Config instead of basic authentication and that's why a cookie is being added to the request and fails. when they disabled SSO, we are able to call webservic method sucessfully sevaral times. but now this cannot be no longer disabled as other applications are using SSO enable option. So, we are thinking, is there something that can be done in SAP ECC itself as we see the option of using SSO in SM59 instead of User Id/Password but not sure How?
If anybody has undergone this scenario/SSO config from ECC SM59 successfully, Please reply back.
Thanks in advance
Praveen

Similar Messages

  • Webdynpro ABAP webservice call to external server  - Cookie issue

    Hi,
    We are experiencing cookie issue while calling webservice to Tivoli system hosted on IBM websphere.
    Steps we have done as follows:
    1. Created a ABAP Proxy class from Tivoli WSDL.
    2. Configured T-Code LPCONFIG to point to above proxy class and logical port.
    3. Configured  SM59 RFC connection to point to Tivoli server using basic authentication mechanism (User ID/Password).
    4. Called webservice method from WebDynpro ABAP program.
    After above steps, we are able to call the webservice method successfully but second time we are experiencing Cookie being adding to the request and eventually no response back to our program.
                When we investigated this cookie issue with IBM Websphere people, they says thay have enabled SSO Config instead of basic authentication and that's why a cookie is being added to the request and fails. when they disabled SSO, we are able to call webservic method sucessfully sevaral times. but now this cannot be no longer disabled as other applications are using SSO enable option. So, we are thinking, is there something that can be done in SAP ECC itself as we see the option of using SSO in SM59 instead of User Id/Password but not sure How?
    If anybody has undergone this scenario/SSO config from ECC SM59 successfully, Please reply back.
    Thanks in advance
    Praveen

    Here is the link that explains how SSO can be configured in SAP.
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/65/6a563cef658a06e10000000a11405a/frameset.htm
    Once done, under Client PSE in Tcode STRUST, you can upload the certificate obtained from the SSO enabled system and use the client PSE (Default)  in the SSL Client Certificate area of SM59
    I see Thomas has already responded to you and he has written a blog on how to set this up as well.
    KK

  • How to Debug ABAP Webservice - called from Form

    Hi All,
    Need to debug a web service (RFC-enabled function module in basis 640). Is it possible? We are calling the web service from an adobe interactive form and need to see what is being passed to the web service.
    (Note: Form is being used in offline mode)
    Please let me know if you can think of a way to do this.
    HTTP-enabled break-point did not work for me.
    Regards,
    Akshay

    Hi,
    If you have defined the Logon Procedure with your SAP Logon ID in the WebService that was created then by placing the External Debugger in the RFC Enabled Function Module you can trigger the Break Point.
    Regards
    Pradeep Goli

  • Ref:Siebel webservice calling issue in Bpel

    Hi,
    Hope you are doing good. Kindly share you valuable ideas regards below issue please.
    I have developed one mediator with 4 Operations namely 1). InsertOrUpdateContactSSM Operation
    2).UpdateContact Operation
    3). UpdateContact Operations
    4).QueryByIdContact Operation.
    I have created 4 BPEL process's for above 4 Operations. Here my SOA suite version is 11.1.1.6.
    I have invoking one Siebel webservice, In this webservice having above operation defined.
    It's developed, it's complied without error and i have deployed into my SOA server it's deployed successfully.
    At testing time it's throwing below :
    Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'InsertOrUpdateContactSSM' failed due to: *SOAP-ENV:Server, error code: There is no active Web Service with operation named 'http://www.absa.co.za/siebel/webservices:InsertOrUpdateContactSSM_Input'.(SBL-EAI-04313)".* The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
    Any one can give proved solution for above error. It's bit Urgent.
    Thanks in Advance.
    regards
    Anil

    Follow the instructions mentioned at this blog to resolve "SBL-EAI-04313" Error
    http://www.soastation.org/2007/05/troubleshooting-siebel-web-services-no.html
    Here is the another link with screen shots:
    https://blogs.oracle.com/pt/entry/siebel_web_service_invocation
    Mark the Posting appropriately as "helpful" or "Correct Answer", if your issue is solved.
    Edited by: 980644 on Feb 27, 2013 6:10 PM

  • Regarding Connection Time Out issue in Webservice call to database.

    Hi,
    We are facing one issue with the webservices call to DB and ILOG. We are declaring and executing the webservice in the following way-
    //Request Object
    EDP.ILog.PEWM_EXPDOC_Help_Information_ProxyService.DecisionServiceRequest helpRequest = EDP.ILog.PEWM_EXPDOC_Help_Information_ProxyService.DecisionServiceRequest();
    //Response Object
    EDP.ILog.PEWM_EXPDOC_Help_Information_ProxyService.DecisionServiceResponse helpResponse = EDP.ILog.PEWM_EXPDOC_Help_Information_ProxyService.DecisionServiceResponse();
    //Proxy Service Object Initialisation
    DecisionServicePEWM_EXPDOC_Help_InformationService helpService = DecisionServicePEWM_EXPDOC_Help_InformationService();
    helpService.executeDecisionService(parameters : helpRequest, out parametersOutput : helpResponse);
    All the webservices are configured corectly in External Resources of Process Administrator. Now, the issue is that whenever we are trying to execute the service with good amount of load on OBPM Process Admin Engine, it is throwing the following exception-
    "Exception:java.net.ConnectException: Connection timed out: connect"
    We are unable to find the root cause of the issue as the webservices call is still throwing the above exception.
    Please provide some resolution as soon as possible.
    Thanks in advance,
    Abhishek

    Just to be sure, we're talking about a client process in BPM accessing an ILOG web service or a DB web service, right? Is this DB web service something custom built?
    Be aware that certain things can run inside the workspace and not the engine. You almost have to work at making this happen. The easiest way is to make this happen is to invoke a BPM object method from within a BPM object presentation or JSP. If you do have this situation open the BPM object method and click on properties and check the box run on server side.
    I can't think of anything that wouldn't scale for connections to Web Services in an engine. I'd be looking at tuning your ILog Web services. Perhaps it can't keep up and the engine gets a timeout. How often does this happen? The engine should retry the automatic until is works. But it tries 3 or so times, it gives up. This retry is configurable.
    HTH,
    Mark

  • Parallel processing of webservice calls in ABAP Proxy

    Within an ABAP Proxy I want to call multiple services in parallel. My thougth was to encapsulate the webservice calls in RFC function modules and then to use "CALL FUNCTION STARTING NEW TASK ..." but anyhow I am wondering if it is possible to use a form within ABAP proxy to collect the RECEIVE data from the modules.

    The Problem was caused by the response of the external AXIS  WebService which contains a multiRef element in the SOAP
    body which is not supported by SAP simple transformation.
    The multiRef  was switched off on AXIS.

  • Issue in Calling https webservice calls from Weblogic

    Hi,
    My application is hosted on the weblogic server.
    I am trying to call http basic authenticated webservice from my application.
    But I am not able to access it. I am getting error.
    Exception occured while calling WS : 2 counts of InaccessibleWSDLException.
    com.sun.xml.ws.wsdl.parser.InaccessibleWSDLException: 2 counts of InaccessibleWSDLException.
    java.io.FileNotFoundException: Response: '401: Unauthorized' for url: 'https://somehost/ws/xyz.wsdl'
    java.io.FileNotFoundException: Response: '401: Unauthorized' for url: 'https://somehost/ws/xyz.wsdl?wsdl'
    I have added the code to authenticate the request. But it seems that it is not working from weblogic.
    class MyAuthenticator extends Authenticator {
    @Override
    protected PasswordAuthentication getPasswordAuthentication() {
    PasswordAuthentication pwa = new PasswordAuthentication(
    "uname",
    "pwd".toCharArray());
    return pwa;
    Authenticator authenticator = new MyAuthenticator();
    Authenticator.setDefault(authenticator);
    PaymentService webForm=new PaymentService(wsURL, getDefaultQName(PaymentService.class)); ---> Exception occurs here.
    PaymentWebForm sessionService=webForm.getPaymentSoap11();
    response=sessionService.getSession(wfSessionRequest);
    Please help. This is not working only from weblogic however if I execute it from standalone Java client then it worked without any issue.
    Is there any configuration needs to be done in Weblogic for secure webservice calls? Please advise.
    Thanks,
    -Pankaj Chomal

    The same probolem happened in my side.
    1.web.xml
    <security-role>
    <description>role for acess the WS api</description>
    <role-name>Admin</role-name>
    </security-role>
    <security-constraint>
    <web-resource-collection>
    <web-resource-name>web service api</web-resource-name>
    <url-pattern>/ws/*</url-pattern>
    </web-resource-collection>
    <auth-constraint>
    <role-name> Admin</role-name>
    </auth-constraint>
    <user-data-constraint>
    <transport-guarantee>NONE</transport-guarantee>
    </user-data-constraint>
    </security-constraint>
    <login-config>
    <auth-method>BASIC</auth-method>
    </login-config>
    2.weblogic.xml have you done?
    <security-role-assignment>
    <role-name>Admin</role-name>
    <principal-name>Administrators</principal-name> //weblogic server group
    </security-role-assignment>
    3.1 calling in a Main method , it works!
    Authenticator.setDefault(new Authenticator() {
         protected PasswordAuthentication getPasswordAuthentication() {
         return new PasswordAuthentication("wsuser", "12345678".toCharArray());
    HrWebService hws = new HrWebServiceService().getHrWebServicePort();
    System.out.println("Result:====="+ hws.getEmpInfoByQryContent("100384"));
    com.jl.ws.hello.AuthHello ah = new AuthHelloImplService().getAuthHelloImplPort();
         System.out.println(ah.say("Edward"));
    3.2 each method as following(including the method above mentioned) called failed in a jsp page, any good idea?
    method a:
    javax.security.auth.Subject mySubject = weblogic.security.services.Authentication.login(
              new weblogic.security.URLCallbackHandler("wsuser", "12345678"));
    weblogic.servlet.security.ServletAuthentication.runAs(mySubject, request);
    method b:
    javax.security.auth.callback.CallbackHandler handler = new weblogic.security.URLCallbackHandler("wsuser", "12345678");
    javax.security.auth. Subject mySubject = weblogic.security.services.Authentication.login(handler);
    weblogic.servlet.security.ServletAuthentication.runAs(mySubject, request);
    method c:
    weblogic.servlet.security.ServletAuthentication.login("wsuser", "12345678", request,response);
    4. excpeiton message
    javax.xml.ws.WebServiceException: Failed to access the WSDL at: http://localhost:7001/jlerp/ws/hr/hrSearch?wsdl. It failed with:
         Response: '401: Unauthorized' for url: 'http://localhost:7001/jlerp/ws/hr/hrSearch?wsdl'.
         at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.tryWithMex(RuntimeWSDLParser.java:172)
         at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:153)
         at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:284)
         at com.sun.xml.ws.client.WSServiceDelegate.(WSServiceDelegate.java:246)
         at com.sun.xml.ws.client.WSServiceDelegate.(WSServiceDelegate.java:197)
         at com.sun.xml.ws.client.WSServiceDelegate.(WSServiceDelegate.java:187)
         at weblogic.wsee.jaxws.spi.WLSServiceDelegate.(WLSServiceDelegate.java:73)
         at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate.(WLSProvider.java:515)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:103)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:95)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:71)
         at javax.xml.ws.Service.(Service.java:56)
         at com.jl.ws.hr.HrWebServiceService.(HrWebServiceService.java:53)
         at com.jl.ws.HrSearchClient.hell0(HrSearchClient.java:32)
         at jsp_servlet._de._jsp.__dejjuserlist._jspService(__dejjuserlist.java:136)
         at weblogic.servlet.jsp.JspBase.service(JspBase.java:35)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.io.FileNotFoundException: Response: '401: Unauthorized' for url: 'http://localhost:7001/jlerp/ws/hr/hrSearch?wsdl'
         at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:474)
         at weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:37)
         at java.net.URL.openStream(URL.java:1010)
         at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.createReader(RuntimeWSDLParser.java:842)
         at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(RuntimeWSDLParser.java:289)
         at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:138)
         at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:284)
         at com.sun.xml.ws.client.WSServiceDelegate.(WSServiceDelegate.java:246)
         at com.sun.xml.ws.client.WSServiceDelegate.(WSServiceDelegate.java:198)
         at com.sun.xml.ws.client.WSServiceDelegate.(WSServiceDelegate.java:190)
         at weblogic.wsee.jaxws.spi.WLSServiceDelegate.(WLSServiceDelegate.java:62)
         at weblogic.wsee.jaxws.spi.WLSProvider$ServiceDelegate.(WLSProvider.java:515)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:103)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:95)
         at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:71)
         at javax.xml.ws.Service.(Service.java:56)
         at com.jl.ws.hr.HrWebServiceService.(HrWebServiceService.java:54)
         at com.jl.ws.HrSearchClient.hell0(HrSearchClient.java:32)
         at jsp_servlet._de._jsp.__dejjuserlist._jspService(__dejjuserlist.java:138)
         ... 10 more
    any info is thankful.
    Edited by: EdwardXiao on Jan 8, 2013 10:48 PM

  • ABAP proxy call to eBay webservice

    Hi,
    I'm trying to configure an ABAP proxy call to the eBay SOAP web services using ECC6 (SP14).
    Has anyone had any experience they can share on how to configure the security for the proxy endpoint in SOAMANAGER to use the ebay services?
    Thanks
    Tim

    Hi,
    Yes, we can do Sysnchronous call in Proxy.
    and we can do the Background job schedule also in Proxy .
    Reffer this help file
    http://help.sap.com/saphelp_nw04/helpdata/en/86/58cd3b11571962e10000000a11402f/content.htm
    Reffer this BLOG also
    /people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
    Regards
    Seshagiri
    Edited by: N V Seshagiri on Feb 12, 2008 11:19 AM

  • How to implement Queuing of WebService call.

    I have to implement a queuing mechanism for webservice.
    The scenario is like a user will invoke the client from his sytem(name:A), this webservice call is received by a server (name:B).
    The webservice will internally call a third system(name:C) , but only one instance or only one call to System C is allowed.
    So system B can get any number of webservice calls but can only invoke system C one at a time.
    The webservice has to be a sync webservice.
    Any help forthese issue is highly appreciated.

    Hi Anton,
    In WD ABAP, if we want to reimport the service call, we need to follow the same steps which we follow to create a service call.
    One thing to notice is that wizard does not allow to give the same method name which we gave/system proposed during the last time service call creation. Hence in the second time when we reimport the service call provide all details and new method name. A new method will be created in Controller (if we use existing controller). During adapting the nodes new nodes/attributes will be created.
    Hence the best approach is to before reimporting the service call is to delete the context, attributes and the method created during the previous service call creation.
    Best regards,
    Suresh

  • Consuming ABAP Webservice in Webdynpro app

    Hi,
    I have wrote a webdynpro app for consuming ABAP webservice. I used the procedure in the link below
    http://wiki.sdn.sap.com/wiki/display/WDJava/ConsumingABAPWebServiceinJavaWD
    Everything seemed to be went well, I created model and Webservice destinations. I have written the code for calling the webservice, which does not return data as part of response. I mean though the RFC returns data at the backend,its not showing the returned records in the webdynpro table.
    I have also tried checking the same by setting external break point. when the webservice is executed from my webdynpro app,it goes to the ABAP debugger and i could clearly see the records in the export parameters of RFC,but the same is not returned in the reponse object.
    Could any one let me know what could be missing. Any help is greatly appreciated?
    I have used the following code in Init method of my View
    Request_ZMYRFC input=new Request_ZMYRFC (model);
    wdContext.nodeRequest_ZMYRFC ().bind(input);
    ZMYRFC  req= new ZMYRFC (model);
    req.setPUserid("EDLAS00C");
    req.setPLtc("E");
    input.setMYRFC (req);
    IWDMessageManager manager = wdComponentAPI.getMessageManager();
        try
        wdContext.currentRequest_ZMYRFCElement().modelObject().execute();
          wdContext.nodeResponse().invalidate();
          wdContext.nodeZMYRFCResponse().invalidate();
          wdContext.nodeReturn_res().invalidate();
         wdContext.nodeItem_res_ret().invalidate();
          wdContext.nodeILtcg_res().invalidate();
          wdContext.nodeItem_res_ltcg().invalidate();
        catch(Exception e)
          manager.reportException(e.getMessage(), false);
    Thanks
    Santhosh

    santosh,
    Check provider system defination in nwa for webservice.After this mapp the provider system and service group after wd app deployed.This is mandatory while consuming webservice in webdynpro for latest versions of CE7.11 or later.for reference check this article/document. http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50d70a19-45a3-2b10-bba0-807d819daf46
    Thanks,
    Murthy.
    Edited by: Murthy Karaka on Mar 22, 2010 12:59 PM

  • Consuming ABAP Webservice from Android device

    Dear Experts,
    I am ABAP developer (limited knowledge on android) trying to connect  Android device to a.SAP Webservice
    Through trial and error and help from SDN and Android forums i managed to link up the ABAP webservice and android using KSOAP2 API.Its working perfectly now but only when i save the username password for SAP access in the webservice settings in transaction SICF.I need to access the service by passing the username and password values through the SOAP request header but so far my efforts have failed me.im presently using the following code to pass my auth values.
    I would be grateful if you can point me in the proper direction.
           String NAMESPACE = "mynamespace (works properly without auth)";
            String METHOD_NAME = "mymethod (works properly without auth)";
            String SOAP_ACTION = "mynamespace/mymethod (works properly without auth)";
            String URL = "myURL{works properly without auth)";
            SoapObject Request = new SoapObject(NAMESPACE, METHOD_NAME);
            Request.addProperty("Purchaseorder","4500001168");
            Request.addProperty("Username", "myusername");
            Request.addProperty("Password", "mypassword");
           SoapSerializationEnvelope envelope = new SoapSerializationEnvelope(SoapEnvelope.VER11);
           envelope.setOutputSoapObject(Request);
           HttpTransportSE androidHttpTransport = new HttpTransportSE(URL);
    try
               androidHttpTransport.call(SOAP_ACTION, envelope);
               SoapObject response = (SoapObject)envelope.bodyIn;
               String testValue =  response.getProperty("PoHeader").toString();
               AlertDialog alertDialog = new AlertDialog.Builder(this).create();
               alertDialog.setMessage(testValue);     
               alertDialog.show();
           catch(Exception e)
                e.printStackTrace();
    Thanx & Best Regards

    Hi,
    you can develop a custom Transport class wich extends the: HttpTransportSE class by authentication features.
    example:
    public class AuthTransportSE extends HttpTransportSE{
         private String username;
         private String password;
         public AuthTransportSE(String url, String username, String password) {
              super(url);
              this.username = username;
              this.password = password;          
         protected ServiceConnection getServiceConnection() throws IOException {
              ServiceConnection midpConnection = new ServiceConnectionSE(url);
              addBasicAuthentication(midpConnection);
              return midpConnection;
         protected void addBasicAuthentication(ServiceConnection midpConnection) throws IOException {
            if (username != null && password != null) {
                StringBuffer buf = new StringBuffer(username);
                buf.append(':').append(password);
                byte[] raw = buf.toString().getBytes();
                buf.setLength(0);
                buf.append("Basic ");
                org.kobjects.base64.Base64.encode(raw, 0, raw.length, buf);
                midpConnection.setRequestProperty("Authorization", buf.toString());
    Afterwards you can initialize the Webservice with:
    AuthTransportSE androidHttpTransport = new AuthTransportSE(URL, userName, pasword);
    Cheers,
    Dennis.

  • How to use ABAP Webservice to Trigger the start of BPMN

    Hello,
    My scenario is that i define a webservice in the SAP ECC system and import it in the process composer as the service interface. As to the start event, i set the above service interface and operation as the trigger service.
    After then, i call this webservice in the user exit of a T-Code. However, the BPMN is not started by this webservice call.
    Anyone can explain on this and tell me how to use the ABAP webservice as the starting event service interface?
    Thanks in advance
    Erick

    Hi Erick,
    When you develop a process model and use some arbitrary service interface in the message start event then this will be exposed on the Java / BPM system you deploed the process definition on.
    That allows you to start the process via this web service once you know its endpoint.
    So in case you want to start your process from the ABAP side you would need to call this endpoint on the Java side out of your ABAP system.
    Simply calling the web service / code on your ABAP system and hoping that this will also invoke the Java stack won't work I AFAIK.
    Best regards,
    Martin

  • Error during webservice call

    Hi all,
    Has anyone worked on Inspire. I am working on a typical scenario integration on primavera with PS.
    But when I do start sync I get " could not start Synch. Error during webservice call"
    When I check Sender SOAP CC in SAP PI in RWB , I get no information. It's status is green and no logs. Also SXMB_moni has no logs.
    Is there a problem with my Sender SOAP CC confihuration .or application has failed
    Can anyone help me on this.
    Regards,

    Hi,
    I tried to reach the URL using SOAPUI but got the following error :
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
                   <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Application:STREAM_TRANSFORMATION_EX:
         at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1193)
         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:592)
         at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
         at $Proxy1413.process(Unknown Source)
         at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:287)
         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:592)
         at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
         at $Proxy788.process(Unknown Source)
         at com.sap.aii.adapter.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:187)
         at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:513)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
         at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:468)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
         at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
         at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)</text>
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    What could  be the issue. Plz help

  • BRM Webservice call from BPM as an automated activity in CE 7.2

    Dear All,
    A simple BRM ruleset is created and published as a webservice. The WSDL is available at NWA ->SOA Management-> Application and Scenario Communication-> Single Service Administration.
    The webservice test in WSNAVIGATOR provides the expected results.
    In the BPM process flow, an automated activity has been created for the webservice call. This activity contains the 'Service Interface' and 'Service Reference' of the imported WSDL.
    Issue:
    When the process is started, the BRM webservice call results in error. The error is not visible in the log but the process flow shows a green symbol on the automatic activity, thereby indicating that the webservice call does not end and the process remains in 'In progress' state.
    Can you please provide your inputs?
    Thanks,
    Pritish

    Dear All,
    The issue is resolved with the help of following document.
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/9009be68-1e9a-2c10-fd91-8f5fcb00474c.
    Regards,
    Pritish

  • JAVA webservice to ABAP Webservice

    Hi,
    There is a Webservice developed in Java and published.
    The same webservice we are now develping in ABAP. Though there is no change in the functionality of the webserice, the WSDL generated for ABAP webservice is looking different than the one for JAVA. How to resolve this issue? I do  not want to ask the service consumer to regenerate the Clinet Proxy for the new WSDL.
    Could you please help me in resolving this issue?
    Thanks & Regards,
    Kishore Babu T

    Hello Johannes,
    Which WSDL do I need ? In the wsnavigator I can choose RPC or Document, and then Default or SAP_WSDL to download the WSDLs.
    Try this: [Accessing a Service|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/b8/a3cca166d440c29931c0c5494c32e5/frameset.htm]
    And do I need to publish the webservice (which I want to consume) on the Java stack ? or ist it already published when the wsnavigator can access it ? (the service resides on the Java stack, and I want to consume it from the ABAP stack from the same system)
    In short, no. You can safely use the Web service without publishing it - as Olivier explained, you need only the WSDL.
    The "publishing" term is usually used when you register (publish) a Web service in the UDDI server or the Services Registry. Publishing is only relevant if you want other people to be able to locate the registered service in the UDDI server.
    Hope this helps,
    Rossen

Maybe you are looking for