Java proxy in PI7.1.....

Hi All,
I am having a requirement where i have to develop JAVA proxy in PI 7.1 and for this I am using NWDS 7.1 but the main concern is that i am very new to JAVA proxies. Even though i refer SDN but the blogs and forums mentioned are related to XI3.0/PI7.0.
I would be very pleased if anybody clear some of my doubts:
1) Do we require WAS in order to install J2ee based non central adapter engine?If yes how to install it.
2) How to configure client and server proxies in PI 7.1 using NWDS 7.1?
3) How to deploy and test java proxies?
Thanks In Advance.

Hi,
You can install the Java proxy runtime on the SAP J2EE Engine Release 6.40 SP5 or higher.
The messaging system that the Java proxy runtime uses to send messages to the Integration Server must also be installed on the J2EE server.
To send messages from a J2EE application, the application must be programmed against beans that encapsulate all details about the Java runtime. The following classes are generated:
u2022 Proxy classes that send or receive messages using the Java proxy runtime.
u2022 Bean classes as an outer shell that conform to the J2EE standard. The beans call the proxy classes for communication.
The classes must be deployed on the J2EE server together with their J2EE application
see this link for the example scenario https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
Refer this configuration guide:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ac6de690-0201-0010-54ac-8923089dcc97
Refer these too:
Java Proxy Inside Story Part I
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a068cf2f-0401-0010-2aa9-f5ae4b2096f9
Java Proxy Inside Story Part II
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f272165e-0401-0010-b4a1-e7eb8903501d
Change in PI 7.1
usr/sap/<SID>/DVEBMGS<nr>/j2ee/cluster/server0/apps (xI 3.0)
/usr/sap/<SID>/DVEBMGS<nr>/j2ee/cluster/bin/ (PI 7.1)
Regards
Zahid Ali

Similar Messages

PI7.11 Can I use Java proxy on Advanced Adapter Engine ??

To:PI Specialists
Now I m planning to use Java Proxy on PI7.11.
and I want to know Java Proxy can act on AAE as local processing.
I wonder that Java Proxy do not connect to adapter engine but to integration engine.
If it connect to integration engine I ll not to use Java Proxy on AAE...
Please teach me about Java proxy will do on AAE....
Naoki Kurihara

Now I find out we can't use Java Proxy on AAE....
Please check this pdf page 12.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?quicklink=index&overridelayout=true

Problem with Java Proxy and Socket Connection

Hi Gurus!!
I have developed a Java Proxy that connects via socket with a Server Socket application. This Server Socket application accepts more than one connection at the same time.
When I connect the first time from my Java Proxy, the connection is correctly established. When the first connection opened, if a try a second connection, this is not established.
I use "new Socket(SocketServer,SocketPort);" to open the connection.
I think that all time the Java Proxy is trying to open the same connection, and this is a problem.
Is there a way to indicate to the server that is a new connection and that the existing connections remain?
Anybody could help me, please?
Thanks and regards,
Manuel Míguez.

Sorry!!!!i must give you more information.
The error which i have when i push the submit button is
HTTP Status 404 -
type Status report
message
descriptionThe requested resource () is not available.
GlassFish Server Open Source Edition 3.0.1
My thought is that the error is in this line
String connectionURL = "jdbc:mysql://localhost/mybooking";in mysql when i write this code then the table opens with no problems:
mysql>show databases;
mysql>usebooking;
mysql>showtables;
mysql>describe booking;Furthermore i have added in my web application the library mysql JDBC driver my-sql-connector-java-5.1.6.bin.jar
Edited by: 813355 on Nov 22, 2010 1:50 AM
Edited by: 813355 on Nov 22, 2010 2:00 AM

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 cant 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

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.

Error in generating the Java Proxy

Hi all,
While generating a Java Proxy, I am getting an error :
Unable to generate proxies
Construct not supported
Can anybody please suggest the possible reason and solution for the same.
Thanks and best regards,
Kulwant

In the Integration Repository documentation for External Definitions you find a hint where you can find a document describing restrictions on the handling of XSD.
In that document you can see, that references to global elements are not supported by the java proxy generation.
Therefore, you have to edit your document accordingly.
regards
chandra

Error while running java proxy in PI 7.1

Hi All,
I had created a java proxy using nwds 7.1. This java proxy is called by XI channel and its synchronous.
WHen i run my scenario in PI i am getting a error "Error while sending message: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing inbound message. Exception: No remote bean found for reference of class $Proxy2919
Kindly help me finding what can be the issue.
Regards,
Rajesh

Go to the JNDI Browser (Nwa -> Problem Management), and check if the proxy was deployed correctly with the exact name "Proxy2919".
Also, check the OSS note below.
#1292633 - JPR: Throwing "No remote bean found for reference of class"

OWSM 11g: Invoking a secured web service through a java proxy service

Hi All,
I am trying to call a secured bpel service which is expecting a username token password. I have created a java proxy service for the same. I now need to add the username token to the same. Can anyone please guide me in this regard.
Thanks in advance.

Just to add some pointers,
I added the following code to the proxy still the soap headers is not getting propagated.
OrderBookingAndShipment orderBookingAndShipment = orderbookingandshipment_client_ep.getOrderBookingAndShipment_pt();
String username = "OWSM_11g";
String password = "password";
List credProviders = new ArrayList();
//client side UsernameToken credential provider
CredentialProvider cp = new ClientUNTCredentialProvider(username.getBytes(),password.getBytes());
credProviders.add(cp);
Map<String,Object> context = ((BindingProvider) orderBookingAndShipment).getRequestContext();
context.put(WSSecurityContext.CREDENTIAL_PROVIDER_LIST,credProviders);

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

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

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

Including helper classes in java proxy jar file

I must not be using the right header search criteria because I'm sure this question
has been asked before. In a Web Service File (.jws) I've imported a couple of
helper classes that function as data transfer objects. I did this to maintain
consistency with other portions of the application. The Java Proxy jar file generated
by Workshop does not include these files. Is there a way of including these dependencies
or do I need to distribute another jar file with my helper classes?

Hi Naichen,
I was able to successfully run both the autotype and clientgen Ant task, on the
WSDL you provided. The code behind those Ant tasks are pretty much what the WebLogic
Web Services test page run. Are you using WLS 8.1 SP2? If not, you might want
to try with that version.
Regards,
Mike Wooten
"Naichen Liu" <[email protected]> wrote:
>
>
>
Hi,
I am having a warning message when trying to generate java proxy jar
file on weblogic8.1
webservice test web app, the message is as follows:
"Warning Failed to generate client proxy from WSDL definition for this
service.
Prescription Please verify the <types> section of the WSDL."
in the mean time, on weblogic starting terminal, I saw the following
exceptions,
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\AlphaLength4Deserializer.java:36: cannot resolve symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,4L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\OSIFieldAnonTypeDeserializer.java:36: cannot resolve
symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkMaxLengthFacet(__typed_obj,69L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\AlphaLength2Deserializer.java:36: cannot resolve symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,2L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\FreeFormAnonTypeDeserializer.java:36: cannot resolve
symbol
symbol : class FacetUtils"
Can anybody help me about this issue? I attached WSDL file, also United
Airlines
got an enterprise weblogic license deal with BEA, any help will be highly
appreciated.
Thanks!!!
Naichen

Java proxy client logical port transport to Q and prod issue in target addr

Hi All,
I have a java proxy client having a logical port (configured using NWDS) to consume a web service in the provider system.
In the logical port, I have given target address, and logical port name. While moving this client proxy NWDI dev track to Q and prod,
how do I change this target address to point to Q and prod respectively. In other words, even though I am using Visual admin to configure the destination url for the logical port, to point to Q and prod, its still referring to the dev environment provider service after moving the proxy client to Q and prod. What is the suggested approach to take care of this issue
Thx
mike

Hi Michael,
I can only help from that point of view that I believe this question belongs to the forum
Service-Oriented Architecture (SOA) and SAP
Please try to raise this question there.
Thanks and Regards,
Ervin

Give me description about JAVA Proxy Runtime and JAVA Proxy Server

Give me description about JAVA Proxy Runtime and JAVA Proxy Server with some examples.

Hi,
Java proxy runtime :
Using the Java proxy runtime you can receive messages or send messages to the Integration Server.
This will help you
http://help.sap.com/saphelp_nw04/helpdata/en/64/7e5e3c754e476ee10000000a11405a/frameset.htm
Java proxy server :
The connection to the Integration Server by using the Java proxy runtime.
This will help you
http://help.sap.com/saphelp_nw04/helpdata/en/87/5305adc23540b8ac7bce08dbe96bd5/frameset.htm
Regards
Agasthuri Doss

Client Java Proxy - ?xml version="1.0" encoding="UTF-8" tag missing

Hi All,
I have a Java Proxy to File scenario. I am getting the output in the SAP XI but when i check the XML payload <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> is missing from it. Rest of the document is coming fine.
Any idea how to fix it up?
Thanks and Regards,
Anurag Mahendru.

Here it is:
Re: ABAP Proxy -> XI - > File on a Website
As I know, this is still on discussion, if the Java Proxy generation will be replaced by web service proxy generation.
But existing Java Proxy applications definitivley will run in PI 7.1 as well.
Regards
Stefan

Java proxy in PI7.1.....

Similar Messages

Maybe you are looking for