Java Proxy Receiver - URL - Prefix ?

Hi XI Expert,
Please advise what is the Prefix to connect to the Java Proxy Receiver ?
Currently, i am using this link below but it seems doesn't work ?
http://piserver:50000/MessagingSystem/receiver/JPR/XI
Thank You and Best Regards
Fernand

Hi,
Refer this links
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06315a6-e66e-2910-039c-ba8bbbd23702
http://help.sap.com/saphelp_nw70/helpdata/EN/a4/d5b3b0b16843b3867c0245d9847ae5/frameset.htm
Regards,
Sreeenivas.

Similar Messages

  • URL Prefix in a reverse proxy scenario

    Hi,
    we actually have a problem with url-generation in our reverse proxy scenario.
    We configured our reverse proxy (apache; not a web dispatcher) to map an url from
    > http://external-host/url-prefix/irj/portal
    to
    > http://internal-host:50000/irj/portal
    Our problem is that the html portal logon page generates absolute urls to resources like http://external-host/com.sap.portal.epcf.loader/... As you can see it is dropping the url-prefix. So our pages are not displayed properly and forms cannot be submitted.
    Is there a way to tell the url generator to put a prefix into each generated absolute url?
    We have SAP Netweaver Portal 7.31
    thanks & regards,
      Christian Buschmann

    Samuli Kaski wrote:
    Anything is possible. A recommended configuration would be for you to setup DNS aliases for all of your applications (SAP Portal, Ruby, etc.). That way you can have virtual host specific reverse proxy mappings. Believe me, it will pay off.
    Yeah, that's what we have done on other sites. But it has the drawback that you have to get seperate ssl-certificates (extended validation) for each domain or have to update the existing ssl-certificate with additional dns-aliases.
    So we tried on this site to sepearte each application by url-prefixes. So each application is covered by the same certificate.
    Having a non-standard configuration means you will have to implement tweaks here and there not to mention how painful it is to maintain such a configuration.
    Still, if you want to try it out try the following configuration
    <Directory /app2>          
              ProxyPass /app2/ htp://portalhost/          
              ProxyPassReverse /app2/ http://portalhost/
    </Directory>
    Apache will use URL prefix /app2 for any URL generated by AS JAVA. That said, you will run into problems eventually since URLs get generated in so many ways, including URLs within HTTP responses which Apache will not change.
    That's our problem now. Apache does map the url from http-request but the http-response-content from sap-portal is untouched. So absolute links within html pages generated by sap-portal are pointing to the wrong path. Protocol, host and port are correct but the path is missing the url-prefix.
    So i don't want our apache to correct the links and rather want sap-portal to produce correct links. It's working fine with protocol, host and port for urls, but i can't set an url-prefix for the path-component.
    So my hope is that you can make the url generator from sap portal aware of our url-prefix (maybe depending of virtual host, or by setting a field in http-request) like it's aware of incoming protocol, host and port. So that every generated link will get an url-prefix for it's path component.

  • Error with receiver java proxy

    for a XI type communication channel for receiver Java proxy I see following error in SXMB_MONI.
    <i>Unable to read user password from communication channel of type Error when accessing the secure store (access ID = 3650CAFA1FBAA04E8F260C6C4C1923FA) Error while reading from the secure store: ERROR_UNKNOWN: Cannot find entry in secure store (SECSTORE,023).</i>
    I have specified the correct credentials for the non sap system in authentication data i.e. XIAPPLUSER and its password.
    Any pointers?

    Hi Amol
    Did you solved this problem? I am also getting the same error when calling receiver java proxy with Adapter type XI.
    If you have solved the problem pl let me know.
    Regards
    Prahllad

  • Troubleshooting Java not receiving Proxy information

    Hello,
    I work in an environment where we have Microsoft TMG installed, with the TMG client on every computer.  The TMG configuration with Java 1.6 worked properly on computer previously to an upgrade of Windows 7 & Java 1.7
    Here is the config of an average computer
    Win7 64 bit
    Java 7.51
    TMG client
    IE 8
    The symptom we are experiencing is Java doesn't use the proxy settings that are issued using the TMG's default auto-discovery script found at http://TMGserver:8080/array.dll?Get.Routing.Script
    When we have the "internet settings" under the control panel set to "Automatically detect settings", then Java doesn't seem to detect the proxy settings and use them.  I can verify this by looking in the Java console as I run an app, as I constantly see "proxy=direct" in the trace. 
    I can fix this by
    1. forcing a manual proxy server (with FQDN - simple name doesn't work) in the Java client settings on each user through the control panel applet
    2. putting the manual proxy information in a deployment.properties file on each user, or through the "central admin" method of c:\windows\system32\sun\java\deployment\deployment.config & deployment.properties
    3. Uncheck the "auto detect settings' and "auto config script" check boxes on the TMG server, so they don't propogate to each TMG client, and aren't put in the "internet settings" of the computer
    3. upgrading client to Java 8
    Unfortunately Java 8 isn't supported by another application, so upgrading to Java 8 is not a possible fix.  Neither is having to manually add (even by script) the Java proxy settings for thousands of users.  I've read all about how Java pulls proxy info from the registry, but have proven that Java seems to check multiple places to get proxy info, even if not found in registry.  This seems to be a very distinct problem where Java is not accessing the "automatically detect settings" or "use automatic configuration script" settings as set in the "internet settings."  It may be that something needs to change with the TMG server, but difficult to understand what and why.
    Can anyone point me to useful links or other ideas on how to fix this?  The script being issued by the TMG server is the one created by default.  I have been troubleshooting this a lot, but I'm not getting any traction on understanding why Java 7.51 doesn't grab proxy information.  I would reapply appreciate any assistance that is offered.
    thanks,
    Brian

    When I set the cookiePath to "/" in sun-web.xml, I get the following output ::
    [wfad002] netscape /cbsweb/apps/cwi/sun1/appserver/domains/domain1/server1/log telnet wfad002.csm.fub.com 8400
    Trying 172.1.114.122...
    Connected to wfad002.
    Escape character is '^]'.
    GET /CwiTest/HeaderServlet HTTP/1.0
    HTTP/1.1 500 Internal Server Error
    Server: Sun-ONE-Application-Server/7.0
    Date: Tue, 24 Sep 2002 16:33:52 GMT
    Content-length: 2415
    Content-type: text/html
    Set-cookie2: JSESSIONID=0FD04CF9167377745F25A1B44776F26B;Version=1;Comment=Sun+ONE+Application+Server+Session+Tracking+Cookie;Discard;Path="/"
    Connection: close
    <html><head>
    <title>
    If I don't set the cookiePath in sun-web.xml, I get the following output::
    [wfad002] netscape /cbsweb/apps/cwi/sun1/appserver/domains/domain1/server1/log telnet wfad002.csm.fub.com 8400
    Trying 172.1.114.122...
    Connected to wfad002.
    Escape character is '^]'.
    GET /CwiTest/HeaderServlet HTTP/1.0
    HTTP/1.1 500 Internal Server Error
    Server: Sun-ONE-Application-Server/7.0
    Date: Tue, 24 Sep 2002 16:20:44 GMT
    Content-length: 2415
    Content-type: text/html
    Set-cookie: JSESSIONID=FA32105878E09E03BFC40E443CFC1A64;Path=/CwiTest
    Connection: close
    <html><head>
    <title>
    This shows (as you explained) that when I set the path the Cookie Version changes to "1". Which may not be supported by my Browser.
    Thanks,
    Shaje

  • Java Proxy Runtime:  failure to locate proxy bean on inbound call

    Hello gurus of the SDN,
    I have been trying to get an inbound Java Proxy scenario to work in XI 3.0 but have not been able to get the JPR to recognize my generated and deployed java code.  My scenario is set up to call the java proxies generated from a message interface based on the MATMAS Idoc.  I successfully deployed the generated java proxies on the same host box as is running the XI instance.  The objects are named as follows
    Message interface on XI = Inbound_MATMAS04
    Generated proxy bean = Inbound_MATMAS04_PortTypeBean
    Implementing class = InboundMATMAS04_PortTypeImpl
    Implementing method = inboundMATMAS04
    I used the JPR transport servlet to register the interface and implementing class but am not sure if I did this correctly.  I used the following entry in my web browser:
    http://nadcp786:50000/ProxyServer/register?
    ns=urn:xiTrainingLabs:groupXX:SAP&
    interface=InboundMATMAS04&
    bean=InboundMATMAS04_PortTypeImpl&
    method=inboundMATMAS04
    I also tried using the localejb/ prefix for the bean name in the above step since the code is co-located.  When I trigger the scenario, the Idoc info is passed into XI and the Java Proxy Runtime is called, but I get the following error response back in the SOAP header:
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="PARSING">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Cannot locate proxy bean InboundMATMAS04_PortTypeImpl</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Finally, appended at the end of this post is the audit log of the messaging system showing that the JPR is called but without being able to locate the bean.  I think I am missing a configuration step somewhere, but can’t figure out what it is!!  Can anyone help me? 
    Many thanks in advance.
    Regards,
    Nick Simon
    Time Stamp     Status     Description
    2004-10-25 19:47:32     Success     The message was successfully received by the messaging system. Profile: XI URL: http://nadcp786.bcsdc.lexington.ibm.com:50000/MessagingSystem/receive/JPR/XI
    2004-10-25 19:47:32     Success     Using connection JPR. Trying to put the message into the receive queue.
    2004-10-25 19:47:32     Success     The message was successfully retrieved from the receive queue.
    2004-10-25 19:47:32     Success     The message status set to DLNG.
    2004-10-25 19:47:32     Success     Java proxy runtime (JPR) accepted the message
    2004-10-25 19:47:34     Error     JPR could not process the message. Reason: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl
    2004-10-25 19:47:34     Error     Delivery of the message to the application using connection JPR failed, due to: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl.
    2004-10-25 19:47:34     Error     The message status set to FAIL.
    2004-10-25 19:47:34     Error     Asynchronous error detected: Cannot locate proxy bean localejbs/InboundMATMAS04_PortTypeImpl. Trying to report it.
    2004-10-25 19:47:34     Error     Asynchronous error reported.
    Message was edited by: Nicholas Simon

    Hi
    How do you determine the JNDI naming of the a EJB?
    I have following entry in JNDI directory in the root
    Object Name FlightQueryIn
    Class Name javax.naming.Reference
    Context Name 
    Object Value Reference Class Name:
    Type: clientAppName
    Content: sap.com/JavaProxyEAR
    Type: interfaceType
    Content: remote
    Type: home
    Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundHome4
    Type: ejb-link
    Content: FlightSeatAvailabilityQueryIn_PortTypeBean
    Type: jndi-name
    Content: FlightQueryIn
    Type: remote
    Content: com.sap.aii.proxy.xiruntime.core.AbstractProxyInboundRemote4
    I tried to register the bean with JPR using:
    http://ctsapxid01:50100/ProxyServer/register?ns=http://sap.com/xi/XI/Demo/Airline&interface=FlightSeatAvailabilityQuery_In&bean=FlightQueryIn&method=flightSeatAvailabilityQueryIn
    I followed the following blog
    http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0
    Thanks,
    Chris

  • Proxy receiver communication channel

    Hi Experts,
    When I am executing an interface in XI, I am getting the message in SXMB_MONI.
    <SAP:Stack>Unable to create HTTP client (exception 1)</SAP:Stack>
    The receiver is Proxy here. Where can I get the service number of R/3 system to enter in the XI receiver communication channel and what's the significance of this? I am using Proxy receiver adapter with URL address connection. I have given 8000 as the service number. Not sure whether this is right. What is the path prefix?
    In the SXMB_ADM, do I need to maintain some parameters for proxy?
    Thanks
    Ricky

    I did give the Service number of R/3. My R/3 uname and password for login
    But I am getting the message in MONI "HTTP response contains status code 401 with the description User not authorized for message processing Authorization error when sending using HTTP (error code: 401, error text: User not authorized for message processing". Pls help to sort this out
    Thanks
    Ricky

  • RFC - XI - Java Proxy HTTP_RESP_STATUS_CODE_NOT_OK

    Hi all,
    I need to work on RFC->XI-> Java proxy.
    While excuting, i am getting an error :
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
      <SAP:P1>400</SAP:P1>
      <SAP:P2>Bad Request</SAP:P2>
    Can any body please guide?
    Regards,
    Kulwant

    Hi Kulwanth,
    Plz do check the mentioned possibilities for your error one by one:
    1.Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine? Double click on service and check whether you have entered correct information.
    2.Then you might check the roles of the XIISUSER in SU01. In some case there are some double roles, i.e., two times the role SAP_XI_IS_SERV_USER assigned. One might have the date of the last update, the other one might have apparently the older version. Delete the older roles manually and the error should disappear.
    3.to send messages to xi you need a service id / pwd which is specific to your landscape usually its xiappluser. Contact your basis group for password.
    4.
    Activated all services on the r3 system.
    Create HTTP connection to XI from r3
    sm59-> http connetons to r3
    let us say you have created a HTTP connection in the integrationserver_XI, make sure in its settings the prefix path is set to /sap/xi/engine?type=entry. Also check its log on credentials, you can use xiappluser.
    IN Integration builder, receiver communication channel make sure you have entered proper
    host service number
    path = /sap/xi/enigne?type = receiver.
    5. It might also be that you have authorization problems with your XISUPER. In the visual administrator and in ABAP SU01, make your XISUPER has all the necessary(SAP_SLD* and SAP_XI*) roles assigned to it. If not, try to assign these and see if this can be of any help.
    6. can you also try the following;
    Visual Admin -> start the service,
    "com.sap.aii.af.ms.app".
    Please go through the followings links also :
    http://help.sap.com/saphelp_nw04/helpdata/en/82/f4993c03e0cd37e10000000a11405a/content.htm
    The specified item was not found.
    http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
    I hope the info provided help you solve your error.
    Regards,
    Vinod.

  • Business system for java proxy

    i use xi system as java AS for java proxy. in receiver communication channel i use URL ADDRESS or HTTP destination?????

    please help me its showing following error
    <Trace level="2" type="T">Switch back to normalized party (HTTP response)</Trace>
      <Trace level="1" type="T">Sender scheme external =</Trace>
      <Trace level="1" type="T">Sender agency external =</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Party normalization: receiver</Trace>
      <Trace level="1" type="T">Receiver scheme external =</Trace>
      <Trace level="1" type="T">Receiver agency external =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
      <Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="2" type="T">Undo header mapping (HTTP response)</Trace>
      <Trace level="1" type="T">Sender: Header before undo of mapping</Trace>
      <Trace level="1" type="T">Party =</Trace>
      <Trace level="1" type="T">Agency =</Trace>
      <Trace level="1" type="T">Scheme =</Trace>
      <Trace level="1" type="T">Service = BS_Debashish</Trace>
      <Trace level="1" type="T">Receiver: Header before undo of mapping</Trace>
      <Trace level="1" type="T">Party =</Trace>
      <Trace level="1" type="T">Agency =</Trace>
      <Trace level="1" type="T">Scheme =</Trace>
      <Trace level="1" type="T">Service = XIT4Java</Trace>
      <Trace level="2" type="T">Sender: Header after undo of mapping</Trace>
      <Trace level="2" type="T">Party =</Trace>
      <Trace level="2" type="T">Agency =</Trace>
      <Trace level="2" type="T">Scheme =</Trace>
      <Trace level="2" type="T">Service = BS_Debashish</Trace>
      <Trace level="2" type="T">Receiver: Header before undo of mapping</Trace>
      <Trace level="2" type="T">Party =</Trace>
      <Trace level="2" type="T">Agency =</Trace>
      <Trace level="2" type="T">Scheme =</Trace>
      <Trace level="2" type="T">Service = XIT4Java</Trace>
      </Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 007</Trace>
      <Trace level="3" type="T">Message version 007</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 014</Trace>
      <Trace level="3" type="T">Message version 008</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>

  • RFC - XI - Java Proxy

    Hi all,
    I need to configure RFC -> XI -> Java proxy.
    While doing so, i am getting below error in SXMB_MONI
    HTTP_RESP_STATUS_CODE_NOT_OK
    following error occurred while parsing the HTTP request: com.sap.engine.services.httpserver.exceptions.ParseException: Incorrect request line: [POST MessagingSystem/receive/AFW/XI HTTP/1.0]..&lt;br&gt;&lt;b&gt; Exception id:
    Can any body please suggest the solution.
    Any help will be appriciated.
    Regards,
    Kulwant

    hi
    port 50000 is the dedicated java-http port. port 8000 is the ICM-port (Internet Communictaion Manager). The ICM distinguishes with the URL-path whether it has to forward the request to the ABAP-stack or to the Java stack.
    ICM port for Java server like http://hostname:80nn/index.html.
    For the J2EE Engine, 20 ports are available for the dispatcher element and 80 are available for the server elements, since five is the maximum number of ports for a server process. Therefore, no more than 16 server cluster elements can be created on one instance.
    The default J2EE Engine ports meet the following requirements:
    ●     The port value is a number over 50000
    ●     For each cluster element the ports begin with 50000+100*instance_number, where instance_number is a two digit number from 00 to 99 specifying the number of central instance and dialog instances.
    You can see the instance number from the directory, where the J2EE Engine is installed. Under /usr/sap/<SID>, there is a directory which name contains the instance name including the instance number, for example, JC40 (where 40 is the instance number).
    ○     For dispatcher cluster elements
    The ports are created from 50000100*instance_numberport_index, where port_index is a number from 0 to 19 inclusive.
    check the below link for
    J2EE Engine Dispatcher Ports
    http://help.sap.com/saphelp_nw04s/helpdata/en/a2/f9d7fed2adc340ab462ae159d19509/frameset.htm
    reward points if helpfull
    regards
    kummari

  • [urgent]inbound java proxy

    Hi
    how can i know if receiver XI adapter touch inbound EJB by registering url?
    my scenario is ABAP Proxy to Java proxy Sync.
    i can see mapping error on moni because payload inbound adapter has empty ,
    my issue, XI seems not to call inbound EJB?
    on adapter monitoring, JPR green
    what missing ?
    XI receiver
    HTTP 1.0
    XI3.0
    integration server
    URL Address
    Target Host :  XI IP
    service number : 50000
    path  : /MessagingSystem/receive/JPR/XI
    authentication Type : Use Logon Data for Non-SAP System
    UserName  :  XIAPPLUSER
    password  :  password
    thanks
    ogawa

    Hi,
    Please can you put here what the error is:...check if the mapping is working properly...
    Also can you check if the registering is done correctly.
    Please check on this thread
    Java Proxy Runtime:  failure to locate proxy bean on inbound call
    Regards
    Vijaya

  • Inbound Java Proxy doesnu00B4t work

    Hi
    I have configured the following steps for an Inbound Java Proxy:
    1.- Create a Business System (Web AS Java) where is located the Proxy.
    2.- Create a XI receiver comm. channel with the respective configuration
    3.- Create a Java Proxy and implemented in NWDS
    4.- Generate a .jar archive
    5.- Generate a .ear archive and deploy to the Integration Server.
    6.- Register the Proxy.
    The scenario is JDBC --> XI --> Java Proxy. In the SXMB_MONI TC show no errors but the java proxy doesn´t work, that is, it doesn't do anything. Somebody knows why?

    thanks Krishna, I've look into the RWB and see an error in the Adapter Engine, I attach the Log in the Audit Log Tab of the message:
    Success Message successfully received by messaging system. Profile: XI URL: http://myAppServer:50000/MessagingSystem/receive/JPR/XI Credential (User): XIAPPLUSER
    Success Using connection JPR. Trying to put the message into the receive queue.
    Success Message successfully put into the queue.
    Success The message was successfully retrieved from the receive queue.
    Success The message status set to DLNG.
    Success Java proxy runtime (JPR) accepted the message
    Error Delivery of the message to the application using connection JPR failed, due to: Exception in method $messageSpecifier..
    Success The asynchronous message was successfully scheduled to be delivered at Mon Sep 04 10:43:06 GMT-04:00 2006.
    Success The message status set to WAIT.
    Success Retrying to deliver message to the application. Retry: 1
    I cannot see all the text in the error message, but it tell me that the error is in the JPR?

  • Problem in creating a java proxy for PHP web service

    This is a problem in generating a java proxy for a PHP webservice.
    I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
    The WSDL for the PHP web service is also generated .
    I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
    The wsdl generated by the php program is
    <?xml version="1.0" encoding="ISO-8859-1" ?>
    <definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
    <types>
    <xsd:schema targetNamespace="urn:hellowsdl">
      <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
      <xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
      </xsd:schema>
      </types>
    <message name="helloRequest">
      <part name="name" type="xsd:string" />
      </message>
    <message name="helloResponse">
      <part name="return" type="xsd:string" />
      </message>
    <portType name="hellowsdlPortType">
    <operation name="hello">
      <documentation>Says hello to the caller</documentation>
      <input message="tns:helloRequest" />
      <output message="tns:helloResponse" />
      </operation>
      </portType>
    <binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
      <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
    <operation name="hello">
      <soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
    <input>
      <soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
      </input>
    <output>
      <soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
      </output>
      </operation>
      </binding>
    <service name="hellowsdl">
    <port name="hellowsdlPort" binding="tns:hellowsdlBinding">
      <soap:address location="http://localhost/mywork/myphp.php" />
      </port>
      </service>
      </definitions>After making following changes to the wsdl program, I tried to generate java proxy.
    <definitions name="hellowsdl"
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
    <types>
    <xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
      <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
      <xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
      </xsd:schema>
      </types>
    <message name="helloRequest">
      <part name="name" type="xsd:string" />
      </message>
    <message name="helloResponse">
      <part name="return" type="xsd:string" />
      </message>
    <portType name="hellowsdlPortType">
    <operation name="hello">
      <documentation>Says hello to the caller</documentation>
      <input message="tns:helloRequest" />
      <output message="tns:helloResponse" />
      </operation>
      </portType>
    <binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
      <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
    <operation name="hello">
      <soap:operation soapAction="" style="rpc" />
    <input>
      <soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
      </input>
    <output>
      <soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
      </output>
      </operation>
      </binding>
    <service name="hellowsdl">
    <port name="hellowsdlPort" binding="tns:hellowsdlBinding">
      <soap:address location="http://localhost/mywork/myphp.php" />
      </port>
      </service>
      </definitions>This is how the java stub file looks like:
    public class HellowsdlBinding_Stub
        extends oracle.j2ee.ws.client.StubBase
        implements demo.mypackage.HellowsdlPortType {
         *  public constructor
        public HellowsdlBinding_Stub(HandlerChain handlerChain) {
            super(handlerChain);
            _setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
            setSoapVersion(SOAPVersion.SOAP_11);
            setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
            setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
         *  implementation of hello
        public java.lang.String hello(java.lang.String name)
            throws java.rmi.RemoteException {
            StreamingSenderState _state = null;
            try {
                _state = _start(_handlerChain);
                if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
                    _state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
                InternalSOAPMessage _request = _state.getRequest();
                _request.setOperationCode(hello_OPCODE);
                _state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
                demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
            _myHellowsdlBinding_hello_ReqS.setName(name);
            SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
            _bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
            _bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
            _request.setBody(_bodyBlock);
            _state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
            _send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
            demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
            Object _responseObj = _state.getResponse().getBody().getValue();
            if (_responseObj instanceof SOAPDeserializationState) {
                _myHellowsdlBinding_hello_RespS =
                    (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
            } else {
                _myHellowsdlBinding_hello_RespS =
                    (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
            return _myHellowsdlBinding_hello_RespS.get_return();
        } catch (RemoteException e) {
            // let this one through unchanged
            throw e;
        } catch (JAXRPCException e) {
            throw new RemoteException(e.getMessage(), e);
        } catch (Exception e) {
            if (e instanceof RuntimeException) {
                throw (RuntimeException)e;
            } else {
                throw new RemoteException(e.getMessage(), e);
    *  this method deserializes the request/response structure in the body
    protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState  state) throws Exception {
        int opcode = state.getRequest().getOperationCode();
        switch (opcode) {
            case hello_OPCODE:
                _deserialize_hello(bodyReader, deserializationContext, state);
                break;
            default:
                throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
    * This method deserializes the body of the hello operation.
    private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
        try {
            Object myHellowsdlBinding_hello_RespSObj =
                myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
                    bodyReader, deserializationContext);
            SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
            bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
            state.getResponse().setBody(bodyBlock);
        } catch (DeserializationException e) {
            if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
                e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
            throw e;
    public String _getEncodingStyle() {
        return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
    public void _setEncodingStyle(String encodingStyle) {
        throw new UnsupportedOperationException("cannot set encoding style");
    public ClientTransport getClientTransport() {
        return super._getTransport();
    * This method returns an array containing (prefix, nsURI) pairs.
    protected String[] _getNamespaceDeclarations() {
        return myNamespace_declarations;
    * This method returns an array containing the names of the headers we understand.
    public QName[] _getUnderstoodHeaders() {
        return understoodHeaderNames;
    * This method handles the case of an empty SOAP body.
    protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
        super._initialize(registry);
        myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
        myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
    private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
    private static final int hello_OPCODE = 0;
    private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
    private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
    private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
    private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
    private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
    private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
    private static final String[] myNamespace_declarations =
                                        new String[] {
                                            "ns0", "http://localhost/mywork/hellowsdl"
    private static final QName[] understoodHeaderNames = new QName[] {  };
    }The errors that are produced are-
    java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
         HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
    Kindly help to resolve this.
    Thanks.

    This is a problem in generating a java proxy for a PHP webservice.
    I have a PHP service running on Wamp Server and also a PHP client which is able to call the service.
    The WSDL for the PHP web service is also generated .
    I am trying to create a java proxy using the jdev (10.1.3.0.3) from the wsdl file.
    The wsdl generated by the php program is
    <?xml version="1.0" encoding="ISO-8859-1" ?>
    <definitions xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:tns="urn:hellowsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:hellowsdl">
    <types>
    <xsd:schema targetNamespace="urn:hellowsdl">
      <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
      <xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
      </xsd:schema>
      </types>
    <message name="helloRequest">
      <part name="name" type="xsd:string" />
      </message>
    <message name="helloResponse">
      <part name="return" type="xsd:string" />
      </message>
    <portType name="hellowsdlPortType">
    <operation name="hello">
      <documentation>Says hello to the caller</documentation>
      <input message="tns:helloRequest" />
      <output message="tns:helloResponse" />
      </operation>
      </portType>
    <binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
      <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
    <operation name="hello">
      <soap:operation soapAction="urn:hellowsdl#hello" style="rpc" />
    <input>
      <soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
      </input>
    <output>
      <soap:body use="encoded" namespace="urn:hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
      </output>
      </operation>
      </binding>
    <service name="hellowsdl">
    <port name="hellowsdlPort" binding="tns:hellowsdlBinding">
      <soap:address location="http://localhost/mywork/myphp.php" />
      </port>
      </service>
      </definitions>After making following changes to the wsdl program, I tried to generate java proxy.
    <definitions name="hellowsdl"
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:si="http://soapinterop.org/xsd" xmlns:tns="http://localhost/mywork/hellowsdl.wsdl" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://localhost/mywork/myphpwsdl.wsdll">
    <types>
    <xsd:schema targetNamespace="http://localhost/mywork/hellowsdl.wsdl">
      <xsd:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
      <xsd:import namespace="http://schemas.xmlsoap.org/wsdl/" />
      </xsd:schema>
      </types>
    <message name="helloRequest">
      <part name="name" type="xsd:string" />
      </message>
    <message name="helloResponse">
      <part name="return" type="xsd:string" />
      </message>
    <portType name="hellowsdlPortType">
    <operation name="hello">
      <documentation>Says hello to the caller</documentation>
      <input message="tns:helloRequest" />
      <output message="tns:helloResponse" />
      </operation>
      </portType>
    <binding name="hellowsdlBinding" type="tns:hellowsdlPortType">
      <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
    <operation name="hello">
      <soap:operation soapAction="" style="rpc" />
    <input>
      <soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
      </input>
    <output>
      <soap:body use="encoded" namespace="http://localhost/mywork/hellowsdl" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" />
      </output>
      </operation>
      </binding>
    <service name="hellowsdl">
    <port name="hellowsdlPort" binding="tns:hellowsdlBinding">
      <soap:address location="http://localhost/mywork/myphp.php" />
      </port>
      </service>
      </definitions>This is how the java stub file looks like:
    public class HellowsdlBinding_Stub
        extends oracle.j2ee.ws.client.StubBase
        implements demo.mypackage.HellowsdlPortType {
         *  public constructor
        public HellowsdlBinding_Stub(HandlerChain handlerChain) {
            super(handlerChain);
            _setProperty(ENDPOINT_ADDRESS_PROPERTY, "http://localhost/mywork/hellowsdl.php");
            setSoapVersion(SOAPVersion.SOAP_11);
            setServiceName( new QName("http://localhost/mywork/hellowsdl","hellowsdl"));
            setPortName( new QName("http://localhost/mywork/hellowsdl","hellowsdlPort"));
         *  implementation of hello
        public java.lang.String hello(java.lang.String name)
            throws java.rmi.RemoteException {
            StreamingSenderState _state = null;
            try {
                _state = _start(_handlerChain);
                if (_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS) != null) {
                    _state.getMessageContext().getMessage().setProperty("DimeEncode",_getProperty(ClientConstants.DIME_ENCODE_MESSAGES_WITH_ATTACHMENTS));
                InternalSOAPMessage _request = _state.getRequest();
                _request.setOperationCode(hello_OPCODE);
                _state.getMessageContext().setProperty("oracle.j2ee.ws.mgmt.interceptor.operation-qname",new QName("","hello"));
                demo.mypackage.runtime.HellowsdlBinding_hello_ReqS _myHellowsdlBinding_hello_ReqS = new demo.mypackage.runtime.HellowsdlBinding_hello_ReqS();
            _myHellowsdlBinding_hello_ReqS.setName(name);
            SOAPBlockInfo _bodyBlock = new SOAPBlockInfo(ns1_hello_hello_QNAME);
            _bodyBlock.setValue(_myHellowsdlBinding_hello_ReqS);
            _bodyBlock.setSerializer(myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer);
            _request.setBody(_bodyBlock);
            _state.getMessageContext().setProperty("http.soap.action", "http://localhost/mywork/hellowsdl");
            _send((String) _getProperty(ENDPOINT_ADDRESS_PROPERTY), _state);
            demo.mypackage.runtime.HellowsdlBinding_hello_RespS _myHellowsdlBinding_hello_RespS = null;
            Object _responseObj = _state.getResponse().getBody().getValue();
            if (_responseObj instanceof SOAPDeserializationState) {
                _myHellowsdlBinding_hello_RespS =
                    (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)((SOAPDeserializationState)_responseObj).getInstance();
            } else {
                _myHellowsdlBinding_hello_RespS =
                    (demo.mypackage.runtime.HellowsdlBinding_hello_RespS)_responseObj;
            return _myHellowsdlBinding_hello_RespS.get_return();
        } catch (RemoteException e) {
            // let this one through unchanged
            throw e;
        } catch (JAXRPCException e) {
            throw new RemoteException(e.getMessage(), e);
        } catch (Exception e) {
            if (e instanceof RuntimeException) {
                throw (RuntimeException)e;
            } else {
                throw new RemoteException(e.getMessage(), e);
    *  this method deserializes the request/response structure in the body
    protected void _readFirstBodyElement(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState  state) throws Exception {
        int opcode = state.getRequest().getOperationCode();
        switch (opcode) {
            case hello_OPCODE:
                _deserialize_hello(bodyReader, deserializationContext, state);
                break;
            default:
                throw new SenderException("sender.response.unrecognizedOperation", Integer.toString(opcode));
    * This method deserializes the body of the hello operation.
    private void _deserialize_hello(XMLReader bodyReader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
        try {
            Object myHellowsdlBinding_hello_RespSObj =
                myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer.deserialize(ns1_hello_helloResponse_QNAME,
                    bodyReader, deserializationContext);
            SOAPBlockInfo bodyBlock = new SOAPBlockInfo(ns1_hello_helloResponse_QNAME);
            bodyBlock.setValue(myHellowsdlBinding_hello_RespSObj);
            state.getResponse().setBody(bodyBlock);
        } catch (DeserializationException e) {
            if (e.getSoapFaultSubCodeType() == JAXRPCExceptionBase.FAULT_CODE_NONE && e.getSoapFaultCodeType() != JAXRPCExceptionBase.FAULT_CODE_DATA_ENCODING_UNKNOWN) {
                e.setSoapFaultSubCodeType(JAXRPCExceptionBase.FAULT_CODE_BAD_ARGUMENTS);
            throw e;
    public String _getEncodingStyle() {
        return SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding();
    public void _setEncodingStyle(String encodingStyle) {
        throw new UnsupportedOperationException("cannot set encoding style");
    public ClientTransport getClientTransport() {
        return super._getTransport();
    * This method returns an array containing (prefix, nsURI) pairs.
    protected String[] _getNamespaceDeclarations() {
        return myNamespace_declarations;
    * This method returns an array containing the names of the headers we understand.
    public QName[] _getUnderstoodHeaders() {
        return understoodHeaderNames;
    * This method handles the case of an empty SOAP body.
    protected void _handleEmptyBody(XMLReader reader, SOAPDeserializationContext deserializationContext, StreamingSenderState state) throws Exception {
    public void _initialize(InternalTypeMappingRegistry registry) throws Exception {
        super._initialize(registry);
        myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_ReqS.class, ns1_hello_TYPE_QNAME);
        myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer = (CombinedSerializer)registry.getSerializer(SOAPEncodingConstants.getSOAPEncodingConstants(soapVersion).getURIEncoding(), demo.mypackage.runtime.HellowsdlBinding_hello_RespS.class, ns1_helloResponse_TYPE_QNAME);
    private static final QName _portName = new QName("http://localhost/mywork/hellowsdl", "hellowsdlPort");
    private static final int hello_OPCODE = 0;
    private static final QName ns1_hello_hello_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
    private static final QName ns1_hello_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "hello");
    private CombinedSerializer myns1_hello__HellowsdlBinding_hello_ReqS_SOAPSerializer;
    private static final QName ns1_hello_helloResponse_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
    private static final QName ns1_helloResponse_TYPE_QNAME = new QName("http://localhost/mywork/hellowsdl", "helloResponse");
    private CombinedSerializer myns1_helloResponse__HellowsdlBinding_hello_RespS_SOAPSerializer;
    private static final String[] myNamespace_declarations =
                                        new String[] {
                                            "ns0", "http://localhost/mywork/hellowsdl"
    private static final QName[] understoodHeaderNames = new QName[] {  };
    }The errors that are produced are-
    java.rmi.RemoteException: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found; nested exception is:
         HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 404 Not Found
    Kindly help to resolve this.
    Thanks.

  • Help - how to create java proxy (sender) in NWDS 7.1

    Hi,
    I am trying to develop a java proxy as sender to send message from WAS to PI.
    I am using NWDS 7.1. Let me explain what I have done so far,
    1. Received proxy classes from PI
    2. Created a EJB Project, imported the proxy classes into EJB project
    3. created a EJB bean, local interface in the EJB project and exposed as webservice
    4. added the ejb to an ear
    5. added reference to the following jar files (external library)
    tcaiiproxy_rt_api.jar
    com.sap.aii.af.sdk.jar
    com.sap.aii.utilxi.server.jar
    com.sap.aii.utilxi.core.jar
    com.sap.aii.proxy.svc_api.jar
    6. able to build and deploy the application
    7. able to open the webservice in wsnavigator
    Error encountered:
    "Server Exception: javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoClassDefFoundError: com/sap/aii/proxy/xiruntime/core/AbstractType "
    Questions:
    1. Which method I should execute / call among all the proxy classes from local bean class to send message to PI?
    2. Is it mandatory to add refernces to the application.xml, ejb-jar.xml and other xmls ?
    3. How can I test / monitor the message being sent to PI interface?
    Thanks and best regards,
    Arun prabhu S

    plz cross chk the references under application-j2eeengine.xml and ejb-jar.xml
    http://wiki.sdn.sap.com/wiki/display/Java/JavaProxyChangesinPI7.1fromPI7.0
    u can chk tis article also:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/508bb504-87cf-2c10-2aaf-f3a5df75e651?quicklink=index&overridelayout=true

  • Passing File sender adapter paylaod to Java Proxy

    I have scenarion that I am getting files from a file adapter and I am not using "File Content Conversion" so file adapter is not converting into any dataType I created for this Scenario to run. The receiver is the Java Proxy as you know the java proxies has input as the MessageType. since we are not mapping incoming file content to any message types then java proxies will not receive the actual Payload.
    Question is, How is pass this file content to Java Proxies. 
    Appreciate your help.
    thanks,
    laxman

    hi,
    if you want to put the whole message then you
    try this:
    - put the whole file into one field (with content conversion)
    - then map this one field to one of the fields
    fo the java proxy and insinde the java proxy
    you will have access to the whole not converted message
    Regards,
    michal

  • How to HTTP-Post different XML messages to one receiving URL on XI side?

    Hi
    I have a problem with a HTTP => XI => IDoc scenario.
    A client want to send 4 different XML documents to only 1 receiving URL on the XI side. How can I handle this in XI???
    To send XML data via HTTP to XI you have to specify the namespace, interface and service in the URL. But I only can specify 1 namespace, interface and namespace in the URL...
    But how can I define a generic message interface for all 4 messages.
    The solution with 4 receiving URL's is easy, but not workable for the client
    Thx
    manuku

    You can do following:
    Create an interface with an artificial root node like this:
    root
      - structure message 1
      - structure message 2
      - structure message 3
    A simple XSLT/Java mapping adds that root node to every message.
    Create different mappings based on the structure if the different mappings and do routing based on the same.
    Another option: Upgrade to PI 7.1. Here you can simply create a service interface with different operations and routing/mapping based on the operations.
    Regards
    Stefan

Maybe you are looking for