Response from Synchronus Proxy

Hi ,
I am sending data from FILE-XI-R/3 through ABAP Proxy to create purchase order.
I want to send back response(PO number created) from Proxy to XI .I want to
keep the response in XI itself.
Do I need BPM to achieve this scenario since FILE adapter is asynchronus?
Thanx.
Rekha.

Hi,
your BPM can look like this:
receive step (FTP adapter) -> transformation step 
(mapping from file message to proxy.request) -> send step
(send proxy message) sync step so you can get the
request -> then if you want you can put another
transformation step to map proxy.response to something
else and send it or not...
you have to create one mapping (file to proxy.request)
if you want you can also do proxy.response to something else)
the same goes with interfaces mappings one or two
if you want you can also use BAPI (wrapped) instead of
usinf proxies as most probaby you'll be using the same
BAPI inside your proxy call
the scenario would be the same but you would use RFC
apdater in the send step
BTW
the bapi you'd have to wrap is: BAPI_PO_CREATE
Regards,
michal

Similar Messages

  • Not getting response from Client Proxy

    Hi,
    We are developing a scenario - File->PI->Proxy using ABAP Proxies.We are posting a file thru PI 7.0 to R/3 .In R/3 the server proxy(Inbound Asynchronous) will receive the message and BAPI will be called. The response from the BAPI will be reaching the server proxy and passed to the client proxy(Outbound Asynchronous).
       Server Proxy(request) --> BAPI --> Server Proxy(response) --> Client Proxy(response)
    The response from the client proxy has to be send to PI and a file will be generated as the output.
    Can anyone provide me suggestions to call client proxy from a server proxy by passing the response message to client proxy???
    Thanks in advance.
    Regards,
    Dibyajyoti

    Hi,
    I hope, you are done till the Implementation of Server Proxy, where you are calling a Bapi and passing the Input variables the Interface received and BAPI is giving a response back.
    Now your question, how to send the response back Asynchronously.
    I think, you have to do the same, what you do for a client proxy  and at last  call the method EXECUTE_ASYNCHRONOUS before the Final Commit Staement. I think this should work.
    But using Synchronous Interface in such cases is always a handy and easier option.
    Regards,
    Subhendu

  • Unable to interpret Response from client proxy

    Hello SAP Guru's,<br><br>
    I am working on trying to consume an external web service using a client (consumer) proxy.<br><br>
    I've created the proxy using the WSDL file provided by the service (see below).  I am able to actually call the proxy and execute the service, however, I cannot seem to properly handle the response coming back from the synchronous service call.  When I use the WSNAVIGATOR to test the service I get the following message: <b>'Part 'processWorkOrderReturn' not found in response !'</b>.<br><br>
    When I try to test it using SE80 and the Test function, I get the following error message: <b>"SOAP:1,023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")"</b>.<br><br>
    <U>Here is the WSDL (edited to protect IP addresses):</U><br><br>
      &lt?xml version="1.0" encoding="UTF-8" ?&gt<br>
    - &ltwsdl:definitions targetNamespace="http://sapphire.aeroint.com/connect/services" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://sapphire.aeroint.com/connect/services" xmlns:intf="http://sapphire.aeroint.com/connect/services" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt<br>
    - &lt!-- <br>
    WSDL created by Apache Axis version: 1.4<br>
    Built on Apr 22, 2006 (06:55:48 PDT)<br>
      --&gt<br>
    &ltwsdl:types&gt<br>
      &ltschema elementFormDefault="qualified" targetNamespace="http://sapphire.aeroint.com/connect/services" xmlns="http://www.w3.org/2001/XMLSchema"&gt<br>
      &ltcomplexType name="WorkOrderType"&gt<br>
      &ltsequence&gt<br>
      &ltelement name="code" nillable="true" type="xsd:string" /&gt<br>
      &ltelement name="description" nillable="true" type="xsd:string" /&gt<br>
      &ltelement name="faultClassification" nillable="true" type="xsd:string" /&gt<br>
      &ltelement name="malfunctionEffect" nillable="true" type="xsd:string" /&gt<br>
      &ltelement name="name" nillable="true" type="xsd:string" /&gt<br>
      &ltelement name="position" nillable="true" type="xsd:string" /&gt<br>
      &ltelement name="status" nillable="true" type="xsd:string" /&gt<br>
      &ltelement name="vehicleSerialNumber" nillable="true" type="xsd:string" /&gt<br>
      &lt/sequence&gt<br>
      &lt/complexType&gt<br>
      &ltelement name="parameters" type="impl:WorkOrderType" /&gt<br>
      &ltcomplexType name="Return"&gt<br>
      &ltsequence&gt<br>
      &ltelement name="return" nillable="true" type="xsd:string" /&gt<br>
      &lt/sequence&gt<br>
      &lt/complexType&gt<br>
      &ltelement name="processWorkOrderReturn" type="impl:Return" /&gt<br>
      &lt/schema&gt<br>
      &lt/wsdl:types&gt<br>
      &ltwsdl:message name="processWorkOrderRequest"&gt<br>
      &ltwsdl:part element="impl:parameters" name="parameters" /&gt<br>
      &lt/wsdl:message&gt<br>
      &ltwsdl:message name="processWorkOrderResponse"&gt<br>
      &ltwsdl:part element="impl:processWorkOrderReturn" name="processWorkOrderReturn" /&gt<br>
      &lt/wsdl:message&gt<br>
      &ltwsdl:portType name="ConnectManager"&gt<br>
      &ltwsdl:operation name="processWorkOrder" parameterOrder="parameters"&gt<br>
      &ltwsdl:input message="impl:processWorkOrderRequest" name="processWorkOrderRequest" /&gt<br>
      &ltwsdl:output message="impl:processWorkOrderResponse" name="processWorkOrderResponse" /&gt<br>
      &lt/wsdl:operation&gt<br>
      &lt/wsdl:portType&gt<br>
      &ltwsdl:binding name="ConnectManagerSoapBinding" type="impl:ConnectManager"&gt<br>
      &ltwsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt<br>
      &ltwsdl:operation name="processWorkOrder"&gt<br>
      &ltwsdlsoap:operation soapAction="" /&gt<br>
      &ltwsdl:input name="processWorkOrderRequest"&gt<br>
      &ltwsdlsoap:body use="literal" /&gt<br>
      &lt/wsdl:input&gt<br>
      &ltwsdl:output name="processWorkOrderResponse"&gt<br>
      &ltwsdlsoap:body use="literal" /&gt<br>
      &lt/wsdl:output&gt<br>
      &lt/wsdl:operation&gt<br>
      &lt/wsdl:binding&gt<br>
      &ltwsdl:service name="ConnectManagerService"&gt<br>
      &ltwsdl:port binding="impl:ConnectManagerSoapBinding" name="ConnectManager"&gt<br>
      &ltwsdlsoap:address location="http://<em>&ltIP Address:Port&gt</em>/connect/services/ConnectManager" /&gt<br>
      &lt/wsdl:port&gt<br>
      &lt/wsdl:service&gt<br>
      &lt/wsdl:definitions&gt<br><br>
    <U>Here is the actual test Request that is passed to the system:</U><br><br>
    POST /connect/services/ConnectManager HTTP/1.1<br>
    Host: <em>&ltIP Address:Port&gt</em><br>
    Content-Type: text/xml; charset=UTF-8<br>
    Connection: close<br>
    SAP-PASSPORT: &ltsome big long number&gt<br>
    Content-Length: 852<br>
    SOAPAction: ""<br><br>
    &lt?xml version="1.0" encoding="UTF-8" ?&gt<br>
    &ltSOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt<br>
    &ltSOAP-ENV:Header&gt<br>
    &ltsapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/"&gt<br>
    &ltenableSession&gttrue&lt/enableSession&gt<br>
    &lt/sapsess:Session&gt<br>
    &lt/SOAP-ENV:Header&gt<br>
    &ltSOAP-ENV:Body&gt<br>
    &ltpns:parameters xmlns:pns='http://sapphire.aeroint.com/connect/services'&gt<br>
    &ltpns:code&gt0200-1&lt/pns:code&gt<br>
    &ltpns:description&gtXVY&lt/pns:description&gt<br>
    &ltpns:faultClassification&gtTestA&lt/pns:faultClassification&gt<br>
    &ltpns:malfunctionEffect&gtTestB&lt/pns:malfunctionEffect&gt<br>
    &ltpns:name&gtWTZ&lt/pns:name&gt<br>
    &ltpns:position&gt02:00&lt/pns:position&gt<br>
    &ltpns:status&gtACCEPTED&lt/pns:status&gt<br>
    &ltpns:vehicleSerialNumber&gt05-12345&lt/pns:VehicleSerialNumber&gt<br>
    &lt/pns:parameters&gt<br>
    &lt/SOAP-ENV:Body&gt<br>
    &lt/SOAP-ENV:Envelope&gt<br><br>
    Please note, this actually does successfully reach out and call the service on the remote system.<br><br>
    <U>Finally, here is the actual Response that is generated and submitted back to me:</U><br><br>
    HTTP/1.1 200 OK<br>
    Server: Apache-Coyote/1.1<br>
    X-Powered-By: Servlet 2.4; JBoss-4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)/Tomcat-5.5<br>
    Set-Cookie: &ltvalue is hidden&gt<br>
    Content-Type: text/xml;charset=utf-8<br>
    Date: Tue, 27 Oct 2009 16:56:58 GMT<br>
    Connection: close<br><br>
    &lt?xml version="1.0" encoding="UTF-8"?&gt<br>
    &ltsoapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt<br>
    &ltsoapenv:Body&gt<br>
    &ltprocessWorkOrderReturn xmlns=""&gt<br>
    &ltreturn>Arising Created in Sapphire&lt/return&gt<br>
    &lt/processWorkOrderReturn&gt<br>
    &lt/soapenv:Body&gt<br>
    &lt/soapenv:Envelope&gt<br><br>
    My Question is this, why isn't our system finding the response structure (or more to the point why isn't it successfully able to interpret the response?).  The 'processWorkOrderReturn' element appears to be in the response and in fact appears to be correct.  Am I missing something?<br><br>
    Thanks,<br>
    -Jon
    Edited by: Jon ***** on Oct 27, 2009 8:04 PM
    Edited by: Jon ***** on Oct 27, 2009 8:05 PM
    Edited by: Jon ***** on Oct 27, 2009 8:13 PM

    Hi Axel,
    Yes, I was able to eventually solve the problem.  The problem was caused by the raw data of the response coming back from the server.  The raw response included an XML tag with no namespace xmlns="".  The SAP system failed to interpret this tag and consequently was not able to process the rest of the message.  I wish the error messages had been a little more clear, but I was able to actually (eventually) debug into the soap runtime engine and spotted that it was failing when attempting to intepret the specific tag ' processWorkOrderReturn xmlns="" '.  From there it was just trial and error to figure out that it needed to have a namespace supplied that matched the definition in the WSDL file.
    Hope your problem is as easy to solve as ours was.
    -Jon
    Edited by: Jon ***** on Nov 30, 2009 1:37 PM

  • Slow response from Webmail Proxy on the first SSL connection

    Hi,
    I encounter a queer problem with Messenger Express 5.2 patch1, acting as a http proxy (Mesenger Express Multiplexor) for another Messaging 5.2P1.
    The first time a user tries to connect through HTTPS since a certain amount of time, it takes about one minute to get the webmail login page. And then it takes one more minute to have the user authenticated after it enters the credentials.
    The next connections are almost immediate.
    Has anyone already seen this problem ?
    The same server doesn't show this problem when connecting on port 80 without SSL.
    It looks like the encryption keys exchange negociation takes a very long time.
    Can this come from a compatibility problem between the client (Communicator 4.75, IE5 or IE6) and the server ?
    Are there recommandations regarding Internal Encryption modules and/or server certificates ?
    (Algorithms , key length...)
    Any answer would be appreciated.
    Regards,
    Vincent MAZARD
    [email protected]
    DML France

    1. Basically, there's a problem on one of the servers which the ASC is hosted on.
    2. It's not at your end. Nothing needs to be or can be done on your devices to resolve it.
    3. No.
    (106571)

  • File To Proxy : Handle the response from ECC to send mail without BPM

    Hi,
    Scenario: FILE To Proxy
    Requirement: We are receiving xml acknowledgement file from bank with IDoc number and status in SAP PI and the file is used to send the status number, message and and IDoc number to ECC. After request is received in ECC BAPI is executed to update the original status of outbound IDOC.
    There would be multiple records in file and PI will send all IDoc acknowledgement to ECC to update the IDoc status.
    Issue: Since PI send all records to ecc, if any single IDoc status update is failing in ECC how would it can be communicated to support.
    ECC can send success or error response in proxy but how we can use the same in PI to send mail to support. Or is there any better error handling we can go for in such scenario.
    Thanks,
    Vertika

    Hi everyone
    thanks for response.
    Interface 1: IDoc (ECC) to File (Bank) --> Done
    Interface 2: Acknowledgment File (Bank) to BAPI (ECC) where BAPI will update the status of IDoc sent in first interface.
    For Interface 2 : PI will receive file from Bank with multiple records i.e multiple IDoc numbers and their status. PI will invoke proxy to send the IDoc number and status number (eg 16) for all the records together. Now if BAPI fails to update status of any single IDoc in that file how support team will know that the particular record is failed. To handle this error ECC is saying they can send Error and Success back to PI. But the problem is how we can use that response in PI in the same interface to send emails to support team. Bank does not want any response back in this case. This is just to ensure proper error handling since this is bank related interface.
    Splitting the interface in two interfaces will definitely help. But is there some way which can be used in same interface and based on error response from ECC mail is triggered.
    If any one has better suggestion for such kind of error handling, please post the same.
    Thanks,
    Vertika

  • "500 Internal Server Error" response from asynchronous AquaLogic proxy

    Hi,
    We have a proxy service deployed to AquaLogic Service Bus (alsb) v3.0 as a WSDL-based SOAP/HTTP service. The WSDL for the proxy defines a single one-way operation (i.e. no response message is defined), making it an asynchronous operation. The proxy routes the request through a couple business services and then routes the response to a URL specified in the request (in the ReplyTo element of a WS-Addressing header). Essentially it's an asynchronous request-response pattern that accepts requests from a web service and calls back to that web service with the response.
    This proxy service works perfectly when run from the test page in the ALSB console. However, when calling the proxy from the real client web service, AquaLogic returns a "500" response from the HTTP POST. The WSDL and everything look correct, and we can use the proxy's URL to download the WSDL with no problem.
    Is this a known problem?
    Thanks!
    -Eric

    HI,
    I am looking for a solution to the problem (i am using Oracle service Bus_10.3).
    After publishing, I can get the wsdl from the web browser but calling the proxy service directly results:
    com.bea.control.ServiceControlException: Unexpected exception raised invoking getTerminalDistance on control com.demo.control.TerminalLocationServiceControl. Use getCause() to see the root cause.[java.rmi.RemoteException: SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [BEA-380001: Internal Server Error] FaultActor [null] Detail [<detail><con:fault xmlns:con="http://www.bea.com/wli/sb/context"><con:errorCode>BEA-380001</con:errorCode><con:reason>Internal Server Error</con:reason><con:location><con:node>RouteNode3</con:node><con:path>response-pipeline</con:path></con:location></con:fault></detail>]; nested exception is:
         weblogic.wsee.jaxrpc.soapfault.WLSOAPFaultException: BEA-380001: Internal Server Error]
         at com.bea.control.servicecontrol.impl.ServiceControlImpl.invoke(ServiceControlImpl.java:696)
         at com.demo.control.TerminalLocationServiceControlBean.getTerminalDistance(TerminalLocationServiceControlBean.java:132)
         at com.demo.control.TerminalLocationImpl.getTerminalDistance(TerminalLocationImpl.java:51)
         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.wsee.component.pojo.JavaClassComponent.invoke(JavaClassComponent.java:112)
         at weblogic.wsee.ws.dispatch.server.ComponentHandler.handleRequest(ComponentHandler.java:84)
         at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:141)
         at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:114)
         at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
         at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66)
         at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44)
         at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:285)
         at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:169)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3504)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2186)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2092)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.rmi.RemoteException: SOAPFaultException - FaultCode [{http://schemas.xmlsoap.org/soap/envelope/}Server] FaultString [BEA-380001: Internal Server Error] FaultActor [null] Detail [<detail><con:fault xmlns:con="http://www.bea.com/wli/sb/context"><con:errorCode>BEA-380001</con:errorCode><con:reason>Internal Server Error</con:reason><con:location><con:node>RouteNode3</con:node><con:path>response-pipeline</con:path></con:location></con:fault></detail>]; nested exception is:
         weblogic.wsee.jaxrpc.soapfault.WLSOAPFaultException: BEA-380001: Internal Server Error
         at weblogic.wsee.jaxrpc.StubImpl.throwRemoteException(StubImpl.java:296)
    I have implemented one testservice and trying to invoke Aqualogic proxy using service control generated through weblogic workshop and getting above error. but if I use test console of Service bus to test this proxy, it runs fine. Also I have configured proxy service message flow where i am using "Replace" action to replce the header from the incoming reuest with the following as my business service expects this security token:
    <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soap:mustUnderstand="1">
    <wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="UsernameToken-24512621">
    <wsse:Username>sample:parlayx</wsse:Username>
    <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">1234</wsse:Password>
    </wsse:UsernameToken>
    </wsse:Security>
    </soap:Header>
    please Please share any additional configuration/settings needed.
    thanks
    Narendra

  • Remove SOAP Header Element from ALSB Proxy Service Response

    I've got a client of one of my ALSB Proxy services that needs the SOAP header element removed from the response. I'm struggling to find a way to do that with a WSDL-based proxy service. Do I need to change my service to an Any XML Service or is there an easier way?

    At the same time, could you please also tell me how do i convert a XML Response from a business service to a SOAP Response in Proxy Service.
    My client is expecting a soap response and the backend gives back only the XML Response
    Thanks in advance!!
    ~Swagat

  • Proxy error - Invalid response from upstream server

    We are using Oracle Application Express Listener for requests between a Web browser and Oracle Application Express engine.
    Tomcat and Java version on the web server (Windows 2008):
    TomCat v 6.0
    Java version "1.6.0_25"
    Application Express version - 4.0.2.00.07
    Access to APEX site happens via Reverse Proxy.
    One of the reports is giving following error message from past few days and there are no log entries in Tomcat server.
    Proxy Error+
    The proxy server received an invalid response from an upstream server.
    The proxy server could not handle the request GET /appname/f.
    Reason: Error reading from remote server
    What could be possible reasons for this proxy error? Please help with the possible solutions to this problem.
    I have tried restarting Tomcat service, used different browsers, cleared browser cache but for no avail. Error is only on one particular report page.

    Hi,
    Have you tried to access the page directly via tomcat without the reverse proxy? This way you can determine if the problem arises at the reverse proxy or tomcat.
    You say it happens only on 1 specific report page, this makes me think there is something with that page and not with the reverse proxy or tomcat. Arises the error when you access the page directly or via a menu option? Maybe the menu link is not correct otherwise i suggest that you take a good look at that page.
    Kees Vlek.

  • No response message in Proxy to JDBC synchronous scenario

    Dear Team,
    I am working on synchronous scenario Sender ABAP proxy <===> SAP PI 7.31 <===> Oracle Database.All the necessary proxy configuration has been successfully tested.
    Business Scenario:
    ABAP proxy will send a single Vendor Id to Oracle DB as request and in return , it has to retrieve all the columns related to Vendor as response.Oracle Database stores all the Vendor information.There are 11 columns including the vendor Id in the view for the Vendor records.
    Design :
    For Request structure:
    a-->Created MT for Sender ABAP Proxy with only 1 field for Vendor Id.
    b-->Created MT for Receiver JDBC  with Action as SELECT , Table with "View Name" , Access with Constant Blank for all 11 column and Key as Vendor Id.
    I have been following  the link and Bhavesh Kantilal document.
    http://help.sap.com/saphelp_nw73/helpdata/en/44/7b7171fde93673e10000000a114a6b/content.htm?frameset=/en/44/7b7855fde93673e10000000a114a6b/f
    rameset.htm&current_toc=/en/ca/b977f1c7814201954f20bb87ad7aab/plain.htm&node_id=71
    For Response structure:
    Created MT for Receiver JDBC with All the column names.
    Created MT for target ABAP ECC with the same 11 column name of JDBC response.
    Note :
    1.Database team shared a excel file as a sample payload which has all the column names of a vendor and I created my DT with the same naming conventions as they are maintaining in their database i.e. Column names are in CAPs, in the same order and even the special characters in the column name.
    2. The PING test connection for Cc works fine to database.
    Please read out my queries as the I am not receiving any response from Oracle DB and gives error as timeout exception:
    1.Since I am trying to retrieve all the column of the view , am I doing the correct procedure of putting all the column name in the JDBC request structure and making a Select statement. Can I add < * > to fetch all the column name and if so where can I add it.
    2. Whats the difference between SELECT and SQL_QUERY and on what circumstances I can add it?
    3. How can I test ICO in ID?
    4. Can I use any SOAP tool to test the messages? Is there any functionality in NWA to test the messages directly to JDBC .
    Hope all your inputs can improve my design part.
    Regards
    Rebecca

    Hi Rebecca,
    Did you go through all of these links below?
    PROXY to JDBC- SYNC
    Proxy to JDBC Sync, with Idoc Receiver
    JDBC to PROXY Sync Scenario | SCN
    JBDC Receiver Insert Statement Response
    Re: Synchronous JDBC select
    receiver JDBC structure
    Regards,
    Jannus Botha

  • How to get response from an asynchronous BPEL process in Java

    I'm experimenting with BPEL and doesn't seem to be able to get response from an asynchronous BPEL process. Here's the deal:
    I have a BPEL process that takes a string as input, and gives another string as output. This is a asyncronous process.
    I want to initiate this BPEL process as a web service so I generate a Webservice Proxy in JDeveloper 10g (10.1.3.0.4). The function to call the process is now called "initiate" and takes three arguments: the input string, a "org.xmlsoap.schemas.ws._2003._03.addressing.EndpointReferenceType replyTo" and a
    "org.xmlsoap.schemas.ws._2003._03.addressing.AttributedURI messageID".
    HTTP-Analyzer shows that invoking the BPEL process with initiate("somestring", null, null) results in sending a SOAP message to the BPEL process, which returns a "202 Accepted". How do I get the response from the process? My intuition tells me that I have to use that second argument, that EnpointReferenceType thing. How do I use that?
    Another question: If a asynchronous BPEL process does not exists (so the endpoint does not exist) the Java proxy does not throw an error when runned. It does not even sends a message. It exits with status 0! (This happens for example when deploying a new version of a process and when the "old" version is undeployed). Calling a non-existing synchronous BPEL process, the Java proxy DOES throw an error.

    Clemens,
    That all sounds logical. But somehow it is still a mystery for me ... Somehow I don't see what should be done.
    To call the async BPEL process I have the following procedure:
    initiate(String input, org.xmlsoap.schemas.ws._2003._03.addressing.EndpointReferenceType replyTo, org.xmlsoap.schemas.ws._2003._03.addressing.AttributedURI messageID)
    The first argument is the input for my BPEL process. The second is the address to a webservice that should handle the callback, right? The third is a messageID (makes sense, but why of the type AttributedURI?).
    Here lies my problem. It is not clear to me how these EndpointReferenceType & AttributedURI work. I can't find anything on the net about it. The AXIS examples as where mentioned earlier use other types (namely the "org.xmlsoap.schemas.ws.addressing.MessageID" and "org.xmlsoap.schemas.ws.addressing.ReplyTo") which are completely different.
    What I did so far:
    - I created an webservice proxy that listens on the onResult endpoint of the BPEL process.
    - I created an webservice proxy that calls the BPEL process through the initiate procedure, but it is not completely clear to me how to construct the EndPointreferenceType replyTo, and the MessageID. I did something like this:
    EndpointReferenceType replyTo = new EndpointReferenceType();
    // callback service running on local machine
    // This URI class is the java.net's version
    URI replyToURI = new URI("http://vaccinatie:8988/syncro-callback-context-root/stringconcatCallbackBindingPort");
    // This AttributedURI is the org.xmlsoap.schemas.ws._2003._03.addressing's version
    AttributedURI address = new AttributedURI();
    // the only public methos that made sense to me:
    address.set_value(replyToURI);
    replyTo.setAddress(address);
    // call the BPEL process
    myPort.initiate("test123", replyTo, address);
    But the above doesn't work (largely because I don't know what I'm doing here prob.:-) ) It does send the "test123" message, and the BPEL process does process it, but I don't seem to get the callback right.
    I hope this makes my problems somewhat clearer. I hope someone can help me, because I'm just a beginner in this whole "web service area" and seems to do something terribly wrong here, because it should be very simple. Thx.

  • Urgent :: 11g Invoking Composite from Java/From Webservice Proxy

    Hi All,
    i have a requirement where in need to when ever the exception occurs it invokes custom java and then it invoked a BPEL process to handle the errror.
    in 10.1.3.4 i used to Java Api to invoke the BPEL process and it works fine.
    1) . now we are migrating to 11g, i know this API wont work with 11g as the server is on weblogic and client librairies may be different for invoking in composite it in 11g. if any body has invoked a composite using java and the using 11g libraries to invoke the composite ? if so can you please post here ?
    2). otherway i tried to create a Web Service proxy using Jdeveloper for the composite, when i test it using Jdeveloper it is working fine, but when i place it in the lib directory, im getting a bad response from server 503.
    please see logs below for the second approch
    Caused by: javax.xml.ws.WebServiceException: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 503 Service Unavailable
         at oracle.j2ee.ws.client.jaxws.DispatchImpl.invokeOneWay(DispatchImpl.java:989)
         at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:224)
         at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invokeOneWay(OracleDispatchImpl.java:102)
         at oracle.integration.platform.blocks.soap.AbstractWebServiceBindingComponent.dispatchRequest(AbstractWebServiceBindingComponent.java:447)
         ... 61 more
    Caused by: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Bad response: 503 Service Unavailable
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call2(HttpSOAPConnection.java:209)
         at oracle.j2ee.ws.common.transport.HttpTransport.transmit(HttpTransport.java:73)
         at oracle.j2ee.ws.common.async.MessageSender.call(MessageSender.java:64)
         at oracle.j2ee.ws.common.async.Transmitter.transmitSync(Transmitter.java:134)
         at oracle.j2ee.ws.common.async.Transmitter.transmit(Transmitter.java:90)
         at oracle.j2ee.ws.common.async.RequestorImpl.transmit(RequestorImpl.java:273)
         at oracle.j2ee.ws.common.async.RequestorImpl.invokeOneWay(RequestorImpl.java:169)
         at oracle.j2ee.ws.client.jaxws.DispatchImpl.invokeOneWay(DispatchImpl.java:985)
         ... 64 more
    Caused by: javax.xml.soap.SOAPException: Bad response: 503 Service Unavailable
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.processHttpResponseCode(HttpSOAPConnection.java:603)
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.post2(HttpSOAPConnection.java:469)
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:1203)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call2(HttpSOAPConnection.java:207)
         ... 71 more
    if any body has already implemented the invocation of composite in one of above approaches, please let me know.
    any pointers to resolve this will be of great help
    Thanks
    Nadh

    Here is sample to invoke a composite from JSP, this should be same from Java Class. Note that the composite should use adf binding and not ws binding.
    Here is snippet of composite.xml service:
    <service name="rmibpel_client_ep" ui:wsdlLocation="RMIBPEL.wsdl">
    <interface.wsdl interface="http://xmlns.oracle.com/Application1/RmiVsSOAP/RMIBPEL#wsdl.interface(RMIBPEL)"/>
    <binding.adf serviceName="rmibpel_client" registryName=""/> </service>
    Note the binding should be binding.adf and not binding.ws
    Sample jsp:
    <%@page import="java.util.Hashtable" %>
    <%@page import="java.util.Map" %>
    <%@page import="javax.naming.Context" %>
    <%@page import="oracle.soa.management.facade.Locator" %>
    <%@page import="oracle.soa.management.facade.LocatorFactory" %>
    <%@page import="oracle.fabric.common.NormalizedMessage" %>
    <%@page import="oracle.soa.management.util.NormalizedMessageImpl" %>
    <%@page import="oracle.soa.management.facade.Composite" %>
    <%@page import="oracle.soa.management.facade.Service" %>
    <html>
    <head>
    <title>Invoke HelloWorld</title>
    </head>
    <body>
    <%
    String msg = request.getParameter("world");
    if(msg == null)
    msg = "World";
    String xml = "<process xmlns=\"http://xmlns.oracle.com/Application1/RmiVsSOAP/RMIBPEL\"><input>" + msg + "</input></process>";
         Hashtable jndiProps = new Hashtable();
         jndiProps.put(Context.PROVIDER_URL,"t3://strec03-1.us.oracle.com:8001/soa-infra");
    jndiProps.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
    jndiProps.put(Context.SECURITY_PRINCIPAL,"weblogic");
    jndiProps.put(Context.SECURITY_CREDENTIALS,"weblogic");
    jndiProps.put("dedicated.connection","true");
    Locator locator = LocatorFactory.createLocator(jndiProps);
         String compositeDN = "default/RmiVsSOAP!1.0";
    Composite composite = locator.lookupComposite(compositeDN);
    String serviceName = "rmibpel_client_ep";
    Service deliveryService = composite.getService(serviceName);
    System.out.println("composite=" + composite);
    System.out.println("deliveryServce=" + deliveryService);
    // construct the normalized message and send to Oracle WLS
    NormalizedMessage nm = new NormalizedMessageImpl();
    nm.getPayload().put("payload", xml );
         NormalizedMessage res = null;
         try {
              res = deliveryService.request("process", nm);
         catch(Exception e)
         e.printStackTrace();
    Map payload = res.getPayload();
    out.println( "BPELProcess HelloWorldService executed!<br>");
    //See below output in log file
    oracle.xml.parser.v2.XMLElement elem =
         (oracle.xml.parser.v2.XMLElement) payload.get("payload");
    elem.print(System.out);
    %>

  • Unable to read SEARCH response from backend server

    Currently we have problem when searching huge amounts of users against new SunOne Directory Server v6.3
    in production and acceptance.
    [17:12:43] root@ecdiala03-2[!]# /opt/app/sun/ds6/bin/dsadm -V
    [dsadm]
    dsadm : 6.3 B2008.0311.0058 NAT
    [slapd 64-bit]
    Sun Microsystems, Inc.
    Sun-Java(tm)-System-Directory/6.3 B2008.0311.0058 64-bit
    ns-slapd : 6.3 B2008.0311.0058 NAT
    Slapd Library : 6.3 B2008.0311.0058
    Front-End Library : 6.3_MTR_5087249_1_20081209 B2008.1210.1821
    ==============================================================
    It’s not working while searching huge amounts of users against DPS.However, It’s working while searching huge amounts of users against DS.
    Below is the error from access log of DPS when the problem occurred.
    ==================================
    31/Mar/2009:14:08:17 +0200] - CONNECT - INFO - conn=4565433 client=153.88.247.15:2719 server=ecdiala03-1:389 protocol=LDAP
    [31/Mar/2009:14:08:17 +0200] - PROFILE - INFO - conn=4565433 assigned to connection handler cn=default connection handler, cn=connection handlers, cn=config
    [31/Mar/2009:14:08:17 +0200] - OPERATION - INFO - conn=4565433 op=0 BIND dn="uid=itimadm1,ou=system accounts,o=ericsson" method="SIMPLE" version=3
    [31/Mar/2009:14:08:17 +0200] - SERVER_OP - INFO - conn=4565433 op=0 BIND dn="uid=ITIMADM1,ou=system accounts,o=Ericsson" method="SIMPLE"" version=3 s_msgid=17 s_conn=ecditna03-2:72725
    [31/Mar/2009:14:08:17 +0200] - SERVER_OP - INFO - conn=4565433 op=0 BIND RESPONSE err=0 msg="" s_conn=ecditna03-2:72725
    [31/Mar/2009:14:08:17 +0200] - PROFILE - INFO - conn=4565433 assigned to connection handler cn=BindDone,cn=connection handlers,cn=config
    [31/Mar/2009:14:08:17 +0200] - OPERATION - INFO - conn=4565433 op=0 BIND RESPONSE err=0 msg="" etime=0
    [31/Mar/2009:14:08:17 +0200] - OPERATION - INFO - conn=4565433 op=1 msgid=2 SEARCH base="ou=External,o=Ericsson" scope=2 filter="(objectclass=inetorgperson)" attrs="*"
    [31/Mar/2009:14:08:17 +0200] - SERVER_OP - INFO - conn=4565433 op=1 SEARCH base="ou=external,o=ericsson" scope=2 filter="(objectclass=inetorgperson)" attrs="*" s_msgid=18 s_conn=ecditna03-2:72725
    [31/Mar/2009:14:12:25 +0200] - OPERATION - INFO - conn=4565433 op=1 SEARCH RESPONSE err=1 msg="Unable to read SEARCH response from backend server : Timeout when waiting to read from input stream" nentries=33959 etime=248309
    [31/Mar/2009:14:17:25 +0200] - DISCONNECT - INFO - conn=4565433 reason="other" msg="Exception caught while polling client connection LDAP.153.88.247.15.2719 -- java.io.IOException: Connection reset by peer"
    ================================
    >>
    > > [15:12:29] root@ecdiala03-1[!]# ./dpadm -V
    > >
    > > [dpadm]
    > >
    > > dpadm :
    > >
    6.3_PD_COMBO_CUMULATIVE_VIRTUAL_15112008_ED2.0+6774589+6780423+6778308+6782659_2
    > > B2008.1212.0459 NAT
    > >
    > >
    > >
    > > [DPS]
    > >
    > > Sun Microsystems, Inc.
    > >
    > >
    Sun-Java(tm)-System-Directory-Proxy-Server/6.3_PD_COMBO_CUMULATIVE_VIRTUAL_15112008_ED2.0+6774589+6780423+6778308+6782659_2
    > > B2008.1212.0436
    > >
    > > =================

    We have changed the value of data-source-read-timeout in DPS from 20s to 30m.As per application test, the "time out" error has gone, but we get a new error as following.
    ==========================
    [27/Apr/2009:05:28:36 +0200] - SERVER_OP - INFO - conn=209469 op=8 SEARCH base="ou=internal,o=ericsson" scope=2 filter="(objectclass=ericssonInternal)" attrs="EriCA-AttesterNL EriCA-EmploymentForm EriCA-KeyRecoveryNL-Auth EriCA-NL-Auth EriCA-NLOTP-Admin EriCA-NLOTP-User EriCA-accountExpires c cn departmentNumber description displayName eriCompanySynch eriCountry eriCountryCode eriEmployeeStatus eriExpired eriIsManager eriMasterDomain eriOpOrgUnitAbbreviation eriOpOrgUnitIdentifier eriOpOrgUnitName eriOperationalManager eriPartner eriPartnerTrigram eriPwSynchDate eriSignType eriSignum eriSignumStatus facsimileTelephoneNumber givenName isMemberOf l mail memberOf mobile objectClass ou sametimebrowseldap sametimehomeserver sametimeuser smChallResp smDisabled smXauthRADIUSServer sn telephoneNumber title uid uidNumber " s_msgid=27 s_conn=ecditna03-2:8645
    [27/Apr/2009:06:06:23 +0200] - SERVER_OP - INFO - conn=209469 op=8 SEARCH RESPONSE err=0 msg="" nentries=236367 s_conn=ecditna03-2:8645
    [27/Apr/2009:06:06:23 +0200] - OPERATION - INFO - conn=209469 op=8 SEARCH RESPONSE err=0 msg="" nentries=236367 etime=2266483
    [27/Apr/2009:06:11:27 +0200] - DISCONNECT - INFO - conn=209469 reason="other" msg="Exception caught while polling client connection LDAP.153.88.247.15.4862 -- java.io.IOException: Connection reset by peer"
    ================
    Each time while application client (153.88.247.15) connecting DPS to read, they will exit with “connection reset” error.
    Could you please kindly give us some suggestion if this error is realted to the DPS?

  • SAP Idocs -How to handle response from target system

    Hi,
    I am working on a scenario in which I will send Idocs asynchronously from SAP thro a SOAP adapter to a  webservice deployed on the target system.
    After the Idoc data is posted in the target system,the target system will send the acknowledgement for the receipt(basically response message).How to handle this scenario?
    SAP Idoc( outbound asynchronous)---> SAP XI3.0(soap adapter) ---> Target system(inbound synchronous)
    Do I need to go for BPM to handle this situation?
    Is there any alterantive to BPM.
    If any of the forum members who have worked on the similar scenario could help me in finding a better solution,I will be thankful to them.
    Thanks,
    Leo

    Hi Udo,
    Thanks for the info.My scenario is like this.
    SAP R/3 Idoc -> SAP XI 3.0 <-> Webservice in the target system.
    The webservice in the target system will receive the Idoc as a request messsage and send a response message synchronously.
    Since Idoc is sent asynchronously( I believe Idocs sent from SAP are always asynchronous),there is no Proxy waiting in SAP R/3 to receive the response message from the target system.
    If I go for BPM for the above scenario,will the BPM steps look like the following.
    1)Receive Idoc from SAP.
    2)Send Idoc sysnchronously to webservice
    3)Receive the response from the webservice synchronously.
    4.Post the response message to a proxy which can handle it further in SAP R/3.
    Please note that my knowledge in BPM is limited and correct me if I am wrong.
    Thanks in advance
    S.Banukumar

  • No response from server HTTP 500

    Hi all,
    I am new to Widget world (in fact this is the first one). I am trying to implement Job Monitoring widget as explained in the weblog:
    /people/sergio.cipolla/blog/2007/02/19/widgets-benefits-jobs-monitor-video
    I have created wrapper function module : ZBP_JOB_SELECT_SM37B
    Created Webservice called:  ZBP_JOB_SELECT_SM37B
    I tested this web service (via web browser providing WSDL url in web services navigator) and it is working fine.
    When i specify the web service URL in Widget prefernces and click on search, i m getting error "No response from server". I have followed all the steps mentioned in the web log but still i am getting errors.
    I am accessing internet via proxy. Can this be a issue?
    Also i read other posts regarding the same issue, which suggested to Enable all logons in SICF. Can some one give details as how to enable all logons in SICF?
    Correct answers will be rewarded.
    Thanks a lot.
    Rashmi

    Hi Sergio,
    The WSDL is:
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions targetNamespace="urn:sap-com:document:sap:rfc:functions" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="urn:sap-com:document:sap:rfc:functions" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    - <wsdl:types>
    - <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="urn:sap-com:document:sap:rfc:functions" targetNamespace="urn:sap-com:document:sap:rfc:functions" elementFormDefault="unqualified" attributeFormDefault="qualified">
    - <xsd:simpleType name="RfcException.Message.Number">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      <xsd:pattern value="\d*" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char1">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="1" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char10">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="10" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char12">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="12" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char128">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="128" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char18">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="18" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char2">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char20">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="20" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char32">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="32" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char40">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="40" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char64">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="64" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char70">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="70" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="char8">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="8" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="clnt3">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="date">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="10" />
      <xsd:pattern value="\d\d\d\d-\d\d-\d\d" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="numeric2">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2" />
      <xsd:pattern value="\d*" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="numeric3">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="3" />
      <xsd:pattern value="\d*" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:simpleType name="time">
    - <xsd:restriction base="xsd:string">
      <xsd:maxLength value="8" />
      <xsd:pattern value="\d\d:\d\d:\d\d" />
      </xsd:restriction>
      </xsd:simpleType>
    - <xsd:complexType name="TBTCJOB">
    - <xsd:sequence>
      <xsd:element name="JOBNAME" type="tns:char32" />
      <xsd:element name="JOBCOUNT" type="tns:char8" />
      <xsd:element name="JOBGROUP" type="tns:char12" />
      <xsd:element name="INTREPORT" type="tns:char40" />
      <xsd:element name="STEPCOUNT" type="xsd:int" />
      <xsd:element name="SDLSTRTDT" type="tns:date" />
      <xsd:element name="SDLSTRTTM" type="tns:time" />
      <xsd:element name="BTCSYSTEM" type="tns:char32" />
      <xsd:element name="SDLDATE" type="tns:date" />
      <xsd:element name="SDLTIME" type="tns:time" />
      <xsd:element name="SDLUNAME" type="tns:char12" />
      <xsd:element name="LASTCHDATE" type="tns:date" />
      <xsd:element name="LASTCHTIME" type="tns:time" />
      <xsd:element name="LASTCHNAME" type="tns:char12" />
      <xsd:element name="RELDATE" type="tns:date" />
      <xsd:element name="RELTIME" type="tns:time" />
      <xsd:element name="RELUNAME" type="tns:char12" />
      <xsd:element name="STRTDATE" type="tns:date" />
      <xsd:element name="STRTTIME" type="tns:time" />
      <xsd:element name="ENDDATE" type="tns:date" />
      <xsd:element name="ENDTIME" type="tns:time" />
      <xsd:element name="PRDMINS" type="tns:numeric2" />
      <xsd:element name="PRDHOURS" type="tns:numeric2" />
      <xsd:element name="PRDDAYS" type="tns:numeric3" />
      <xsd:element name="PRDWEEKS" type="tns:numeric2" />
      <xsd:element name="PRDMONTHS" type="tns:numeric2" />
      <xsd:element name="PERIODIC" type="tns:char1" />
      <xsd:element name="DELANFREP" type="tns:char1" />
      <xsd:element name="EMERGMODE" type="tns:char1" />
      <xsd:element name="STATUS" type="tns:char1" />
      <xsd:element name="NEWFLAG" type="tns:char1" />
      <xsd:element name="AUTHCKNAM" type="tns:char12" />
      <xsd:element name="AUTHCKMAN" type="tns:clnt3" />
      <xsd:element name="SUCCNUM" type="xsd:int" />
      <xsd:element name="PREDNUM" type="xsd:int" />
      <xsd:element name="JOBLOG" type="tns:char20" />
      <xsd:element name="LASTSTRTDT" type="tns:date" />
      <xsd:element name="LASTSTRTTM" type="tns:time" />
      <xsd:element name="WPNUMBER" type="xsd:int" />
      <xsd:element name="WPPROCID" type="xsd:int" />
      <xsd:element name="EVENTID" type="tns:char32" />
      <xsd:element name="EVENTPARM" type="tns:char64" />
      <xsd:element name="BTCSYSREAX" type="tns:char32" />
      <xsd:element name="JOBCLASS" type="tns:char1" />
      <xsd:element name="PRIORITY" type="xsd:int" />
      <xsd:element name="EVENTCOUNT" type="tns:char8" />
      <xsd:element name="CHECKSTAT" type="tns:char1" />
      <xsd:element name="CALENDARID" type="tns:char2" />
      <xsd:element name="PRDBEHAV" type="tns:char1" />
      <xsd:element name="EXECSERVER" type="tns:char20" />
      <xsd:element name="EOMCORRECT" type="xsd:int" />
      <xsd:element name="CALCORRECT" type="xsd:int" />
      <xsd:element name="REAXSERVER" type="tns:char20" />
      <xsd:element name="RECLOGSYS" type="tns:char10" />
      <xsd:element name="RECOBJTYPE" type="tns:char10" />
      <xsd:element name="RECOBJKEY" type="tns:char70" />
      <xsd:element name="RECDESCRIB" type="tns:char10" />
      <xsd:element name="TGTSRVGRP" type="tns:char40" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="TBTCJOB_BK">
    - <xsd:sequence>
      <xsd:element name="JOBNAME" type="tns:char32" />
      <xsd:element name="JOBCOUNT" type="tns:char8" />
      <xsd:element name="JOBGROUP" type="tns:char12" />
      <xsd:element name="INTREPORT" type="tns:char40" />
      <xsd:element name="STEPCOUNT" type="xsd:int" />
      <xsd:element name="SDLSTRTDT" type="tns:date" />
      <xsd:element name="SDLSTRTTM" type="tns:time" />
      <xsd:element name="BTCSYSTEM" type="tns:char32" />
      <xsd:element name="SDLDATE" type="tns:date" />
      <xsd:element name="SDLTIME" type="tns:time" />
      <xsd:element name="SDLUNAME" type="tns:char12" />
      <xsd:element name="LASTCHDATE" type="tns:date" />
      <xsd:element name="LASTCHTIME" type="tns:time" />
      <xsd:element name="LASTCHNAME" type="tns:char12" />
      <xsd:element name="RELDATE" type="tns:date" />
      <xsd:element name="RELTIME" type="tns:time" />
      <xsd:element name="RELUNAME" type="tns:char12" />
      <xsd:element name="STRTDATE" type="tns:date" />
      <xsd:element name="STRTTIME" type="tns:time" />
      <xsd:element name="ENDDATE" type="tns:date" />
      <xsd:element name="ENDTIME" type="tns:time" />
      <xsd:element name="PRDMINS" type="tns:numeric2" />
      <xsd:element name="PRDHOURS" type="tns:numeric2" />
      <xsd:element name="PRDDAYS" type="tns:numeric3" />
      <xsd:element name="PRDWEEKS" type="tns:numeric2" />
      <xsd:element name="PRDMONTHS" type="tns:numeric2" />
      <xsd:element name="PERIODIC" type="tns:char1" />
      <xsd:element name="DELANFREP" type="tns:char1" />
      <xsd:element name="EMERGMODE" type="tns:char1" />
      <xsd:element name="STATUS" type="tns:char1" />
      <xsd:element name="NEWFLAG" type="tns:char1" />
      <xsd:element name="AUTHCKNAM" type="tns:char12" />
      <xsd:element name="AUTHCKMAN" type="tns:clnt3" />
      <xsd:element name="SUCCNUM" type="xsd:int" />
      <xsd:element name="PREDNUM" type="xsd:int" />
      <xsd:element name="JOBLOG" type="tns:char20" />
      <xsd:element name="LASTSTRTDT" type="tns:date" />
      <xsd:element name="LASTSTRTTM" type="tns:time" />
      <xsd:element name="WPNUMBER" type="xsd:int" />
      <xsd:element name="WPPROCID" type="xsd:int" />
      <xsd:element name="EVENTID" type="tns:char32" />
      <xsd:element name="EVENTPARM" type="tns:char64" />
      <xsd:element name="BTCSYSREAX" type="tns:char32" />
      <xsd:element name="JOBCLASS" type="tns:char1" />
      <xsd:element name="PRIORITY" type="xsd:int" />
      <xsd:element name="EVENTCOUNT" type="tns:char8" />
      <xsd:element name="CHECKSTAT" type="tns:char1" />
      <xsd:element name="CALENDARID" type="tns:char2" />
      <xsd:element name="PRDBEHAV" type="tns:char1" />
      <xsd:element name="EXECSERVER" type="tns:char20" />
      <xsd:element name="EOMCORRECT" type="xsd:int" />
      <xsd:element name="CALCORRECT" type="xsd:int" />
      <xsd:element name="REAXSERVER" type="tns:char20" />
      <xsd:element name="RECLOGSYS" type="tns:char10" />
      <xsd:element name="RECOBJTYPE" type="tns:char10" />
      <xsd:element name="RECOBJKEY" type="tns:char70" />
      <xsd:element name="RECDESCRIB" type="tns:char10" />
      <xsd:element name="TGTSRVGRP" type="tns:char40" />
      <xsd:element name="PROGNAME" type="tns:char40" />
      <xsd:element name="XPGPROG" type="tns:char128" />
      <xsd:element name="EXTCMD" type="tns:char18" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="BTCSELECT">
    - <xsd:sequence>
      <xsd:element name="JOBNAME" type="tns:char32" />
      <xsd:element name="JOBCOUNT" type="tns:char8" />
      <xsd:element name="JOBGROUP" type="tns:char12" />
      <xsd:element name="USERNAME" type="tns:char12" />
      <xsd:element name="FROM_DATE" type="tns:date" />
      <xsd:element name="FROM_TIME" type="tns:time" />
      <xsd:element name="TO_DATE" type="tns:date" />
      <xsd:element name="TO_TIME" type="tns:time" />
      <xsd:element name="NO_DATE" type="tns:char1" />
      <xsd:element name="WITH_PRED" type="tns:char1" />
      <xsd:element name="EVENTID" type="tns:char32" />
      <xsd:element name="EVENTPARM" type="tns:char64" />
      <xsd:element name="PRELIM" type="tns:char1" />
      <xsd:element name="SCHEDUL" type="tns:char1" />
      <xsd:element name="READY" type="tns:char1" />
      <xsd:element name="RUNNING" type="tns:char1" />
      <xsd:element name="FINISHED" type="tns:char1" />
      <xsd:element name="ABORTED" type="tns:char1" />
      <xsd:element name="ABAPNAME" type="tns:char40" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="RfcException.Message">
    - <xsd:sequence>
      <xsd:element name="ID" type="xsd:string" />
      <xsd:element name="Number" type="tns:RfcException.Message.Number" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="ZBP_JOB_SELECT_SM37B.RfcException">
    - <xsd:sequence>
      <xsd:element name="Name" type="tns:ZBP_JOB_SELECT_SM37B.RfcExceptions" />
      <xsd:element name="Text" minOccurs="0" type="xsd:string" />
      <xsd:element name="Message" minOccurs="0" type="tns:RfcException.Message" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="TableOfTBTCJOB">
    - <xsd:sequence>
      <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:TBTCJOB" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:complexType name="TableOfTBTCJOB_BK">
    - <xsd:sequence>
      <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:TBTCJOB_BK" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:simpleType name="ZBP_JOB_SELECT_SM37B.RfcExceptions">
    - <xsd:restriction base="xsd:string">
      <xsd:enumeration value="INVALID_DIALOG_TYPE" />
      <xsd:enumeration value="JOBNAME_MISSING" />
      <xsd:enumeration value="NO_JOBS_FOUND" />
      <xsd:enumeration value="SELECTION_CANCELED" />
      <xsd:enumeration value="USERNAME_MISSING" />
      </xsd:restriction>
      </xsd:simpleType>
      <xsd:element name="ZBP_JOB_SELECT_SM37B.Exception" type="tns:ZBP_JOB_SELECT_SM37B.RfcException" />
    - <xsd:element name="ZBP_JOB_SELECT_SM37B">
    - <xsd:complexType>
    - <xsd:sequence>
      <xsd:element name="ENDDATE" minOccurs="0" type="tns:date" />
      <xsd:element name="ENDTIME" minOccurs="0" type="tns:time" />
      <xsd:element name="JOBSELECT_DIALOG" type="tns:char1" />
      <xsd:element name="JOBSELECT_JOBLIST" minOccurs="0" type="tns:TableOfTBTCJOB" />
      <xsd:element name="JOBSELECT_JOBLIST_B" type="tns:TableOfTBTCJOB_BK" />
      <xsd:element name="JOBSEL_PARAM_IN" minOccurs="0" type="tns:BTCSELECT" />
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
    - <xsd:element name="ZBP_JOB_SELECT_SM37BResponse">
    - <xsd:complexType>
    - <xsd:sequence>
      <xsd:element name="JOBSELECT_JOBLIST" type="tns:TableOfTBTCJOB" />
      <xsd:element name="JOBSELECT_JOBLIST_B" type="tns:TableOfTBTCJOB_BK" />
      <xsd:element name="JOBSEL_PARAM_OUT" type="tns:BTCSELECT" />
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:schema>
      </wsdl:types>
    - <wsdl:message name="ZBP_JOB_SELECT_SM37B">
      <wsdl:part name="parameters" element="tns:ZBP_JOB_SELECT_SM37B" />
      </wsdl:message>
    - <wsdl:message name="ZBP_JOB_SELECT_SM37BResponse">
      <wsdl:part name="parameters" element="tns:ZBP_JOB_SELECT_SM37BResponse" />
      </wsdl:message>
    - <wsdl:message name="exception00">
      <wsdl:part name="exception00" element="tns:ZBP_JOB_SELECT_SM37B.Exception" />
      </wsdl:message>
    - <wsdl:portType name="ZBP_JOB_SELECT_SM37B">
    - <wsdl:operation name="ZBP_JOB_SELECT_SM37B">
      <wsdl:input message="tns:ZBP_JOB_SELECT_SM37B" />
      <wsdl:output message="tns:ZBP_JOB_SELECT_SM37BResponse" />
      <wsdl:fault name="exception00" message="tns:exception00" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="ZBP_JOB_SELECT_SM37BSoapBinding" type="tns:ZBP_JOB_SELECT_SM37B">
      <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="ZBP_JOB_SELECT_SM37B">
      <soap:operation soapAction="" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
    - <wsdl:fault name="exception00">
      <soap:fault name="exception00" use="literal" />
      </wsdl:fault>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="ZBP_JOB_SELECT_SM37BService">
    - <wsdl:port name="ZBP_JOB_SELECT_SM37BSoapBinding" binding="tns:ZBP_JOB_SELECT_SM37BSoapBinding">
      <soap:address location="http://bladecx1.vshodc.lntinfotech.com:8000/sap/bc/srt/rfc/sap/ZBP_JOB_SELECT_SM37B?sap-client=100" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>
    The Web Service URL specified in Widget Prefernces is:
    http://bladecx1.vshodc.lntinfotech.com:8000/sap/bc/srt/rfc/sap/ZBP_JOB_SELECT_SM37B?sap-client=100&wsdl=1.1
    The only thing that i I have modified in the original widget is the name of Function Module in the main.js file. The function Module created by me is  'ZBP_JOB_SELECT_SM37B'.
    Regards,
    Rashmi

  • How to Serve HTML from a Proxy Service?

    I am trying to serve HTML from a proxy service.
    I set up a Messaging Service with request type = 'None' and response type = 'Text'; with Endpoint URL = '/OSB_Project/Proxy_Services/InfoPingerProxyService.html'.
    In my incoming request pipeline I set an html Transport Header action to define Content-Type = 'text/html'.
    In the response pipeline I replace the body with the html document contents...
    Trouble is, when I access the proxy (via a standard browser GET), I always produce an XML file with an <?xml...?> processing instruction:
    <?xml version="1.0" encoding="UTF-8"?>
    <html>
    Also: the browser always sees an XML response regardless, it seems.
    Any suggestions gratefully accepted.
    Cheers,
    Alph

    More on this.
    I made an "educated guess' that the path should be
    {code}./ctx:transport/ctx:response/tp:headers/http:Content-Type{code}
    But take a look at the following, you will see that the content type IS now text/html, but the XML processing instruction is still there...
    {code}
    :\BIN\wget-1.11.4-1-bin\bin>wget -d http://localhost:7001/Test_Project/ProxySe
    rvice1?q=1
    SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
    syswgetrc = C:\BIN\wget-1.11.4-1-bin/etc/wgetrc
    DEBUG output created by Wget 1.11.4 on Windows-MinGW.
    --2010-09-15 15:33:17-- http://localhost:7001/Test_Project/ProxyService1?q=1
    Resolving localhost... seconds 0.00, 127.0.0.1
    Caching localhost => 127.0.0.1
    Connecting to localhost|127.0.0.1|:7001... seconds 0.00, connected.
    Created socket 268.
    Releasing 0x0063a620 (new refcount 1).
    ---request begin---
    GET /Test_Project/ProxyService1?q=1 HTTP/1.0
    User-Agent: Wget/1.11.4
    Accept: */*
    Host: localhost:7001
    Connection: Keep-Alive
    ---request end---
    HTTP request sent, awaiting response...
    ---response begin---
    HTTP/1.1 200 OK
    Connection: Keep-Alive
    Date: Wed, 15 Sep 2010 05:33:17 GMT
    Content-Length: 61
    Content-Type: text/html; charset=utf-8
    X-Powered-By: Servlet/2.5 JSP/2.1
    ---response end---
    200 OK
    Registered socket 268 for persistent reuse.
    Length: 61 [text/html]
    Saving to: `ProxyService1@q=1'
    100%[=====================================> ] 61 --.-K/s in 0s
    2010-09-15 15:33:17 (1.23 MB/s) - `ProxyService1@q=1' saved [61/61]
    C:\BIN\wget-1.11.4-1-bin\bin>type "ProxyService1@q=1"
    <?xml version="1.0" encoding="UTF-8"?>
    <server>8088</server>
    C:\BIN\wget-1.11.4-1-bin\bin>
    {code}
    (I know that the actual CONTENT [ie "<server>8088</server"] is not really HTML at the moment...this is just intermediate testing content...)
    Back to the issue of how to get rid of that processing instruction...
    The proxy service is configured as a messaging service with request = none and response = text.
    Cheers,
    Alph

Maybe you are looking for