XI Configuration incase of Java Proxy

Hello
I am trying Java Proxy scenario in which I generated Java Proxies of my XI interface.I used NetWeaver Developer Studio to implement my business logic using the generated classes from XI.
But I guess its not connecting to XI when tried to execute from NWDS.On XI side I configured Business System with no sender configuration and configured Receiver Determination for the business system (basically similar to what we configure for HTTP Adapter).
Just wanted to get clear whether we need to define Sender(sender comm channel) incase of Proxies or any business system instead of business service.As far as I know since its invoking a EJB directly from the lookup it should not require that but not sure.
Thanks in advance.
Regards
Ashish

Hi,
take a look at Java Proxy Inside Storys:
Part I:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/java proxies and sap xi - the inside story,%20Part%201.pdf
Part II:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/java proxies and sap xi - the inside story,%20Part%20II.pdf
Regards,
Robin

Similar Messages

Java Proxy message in waiting status

Hi,
   Let me explain my case, In our Integration Scenario we have configured an Inbound Java Proxy as the How to guide (HOW TO WORK WITH JAVA PROXIES) expain, but the proxy doesn't hava code, that is, it have the code by default when its created, and when we register it and the scenario runs, in the message monitoring the status of the message to the JP Business Service is in WAITING status, and in the details it says sometimes that an old reference to another JNDI name of bean is doesn't locate or the message "MessageSpecifier could not be reset".
   Remember, the Imp. class has only the default code and the scenario is JDBC --> XI --> JavaProxy
   Any ideas?

Hi Hector,
Status: WAITING
          The message had been sent and it is failed and is currently waiting for another attempt.
Solution :
When the fist attempt to deliver the message has failed (a recoverable exception arose), the message is usually rescheduled and the status is updated to WAITING. As long as the message is in this status, the Messaging System retries to deliver the message according to the configured retry settings (default 3 tries).
Regards
Agasthuri Doss

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].. 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

Java Proxy + hibernate

Hi,
Is posible to configure an Inbound Java Proxy with the Hibernate specification?

Somebody can help me with this? Can I configure a proxy with the Hibernate specifications? I have an inbound proxy that use the Hibernate's classes and the service of the EJB does not start up.
Thanks.

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

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

Direct Connection ABAP Proxy and Java Proxy possible ????

Hi Folks ,
As i read as direct connection possible between 2 SAP systems only ..
and also i read as WS Direct Connection u2013 (Java) ..
What it means ?? is it ABAP Proxy to Java Proxy using Direct connection ?? Like Java Client Proxy and ABAP Server proxy
I am not clear on this.. Could you please explain or help me on this . ??
Siva..

Hi ,
+You can do both for java proxies as well Abap proxies.+
As per the following points
1. Point-to-point connection is a new capability available with SAP NW PI 7.1. It allows applications or systems to send messages using WS-RM without going through a middleware, e.g. PI, but still using a centralized tool to design and
configure the interfaces and connection properties.
2. SAP XI 3.0/PI 7.00 or higher releases can be licensed based on the total volume of messages in
gigabytes (GB) that is processed per month. The size of the payload is determined in the integration
server. The information is then aggregated according to sender and receiver system.
Question :
1. If Message exchange between 2 SAP applications using direct connection .. Then dont we need to consider about licencing cost for volume of messages per month ?
2. So if i use ABAP Client Proxy to Java Server proxy scenario.. can i use direct connection ? Eg., SAP ECC to java application ?
In both the cases PI Runtime is not required .. Am i right ?
Please clarify..
Siva..

XI 2.0 Java Proxy error

Hi All,
I am receiving the following error:
RFC_ADAPTER.JCO_RUNTIME_EXCEPTION:System error when calling the outbound RFC adapter (cannot deserialize JCo request from XML)
The message I'm sending is synchronous coming from a Java Webapp and requesting infomation from R/3.
There are two pieces to the interface I have created. The first is calling a function which validates a few fields then returns 'return codes'. The second will create a sales order and return a few numbers. They are built into the same interface and use message splitting based on an input field. The verification piece is working which tells me that this is not a problem with the actual RFC adapter but when I run the 'create sales order' function I receive the aforementioned error.
n e thoughts?

Hi Stefan, thx for the reply.
I am running the latest version of the function. I do have one date field in the RFC structure, the rest are strings. The data going into that date field is being mapped from a string field in the sent message. This shouldn't be a problem (I don't believe) I have done this in many other interfaces.
I noticed that in my xi monitor (SXMB_MONI) under the column labeled 'Outbound' the acronym 'RFC' shows up for my failing message. When I send a message through the other java proxy interface that works I get nothing in the column. I'm not sure if this means n e thing but I thought I would through that in.
I've also set up my scenario changing from synchronous to asynchronous and using the file adapter and it seems to make it through, minus the error on the return message.
.. I forgot to mention that there have not been any changes to the RFC adapter configuration. ... and I have restarted it to see if that would make a difference. It did not.
n e other ideas?
Message was edited by: Larry Chaput

Error in scenario for client Java Proxy

2006-04-28 15:30:49 Success Java proxy runtime (JPR) is transferring the request message to the messaging System
2006-04-28 15:30:49 Success Application attempting to send an XI message synchronously using connection JPR.
2006-04-28 15:30:49 Success Trying to put the message into the call queue.
2006-04-28 15:30:49 Success Message successfully put into the queue.
2006-04-28 15:30:49 Success The message was successfully retrieved from the call queue.
2006-04-28 15:30:49 Success The message status set to DLNG.
2006-04-28 15:30:50 Error Received XI System Error. ErrorCode: NO_RECEIVER_CASE_BE ErrorText: ErrorStack: No receiver could be determined
2006-04-28 15:30:50 Error Returning synchronous error notification to calling application: XIServer:NO_RECEIVER_CASE_BE:.
2006-04-28 15:30:50 Error Transmitting the message using connection http://<SERVER>:<PORT>/sap/xi/engine?type=entry failed, due to: XIServer:NO_RECEIVER_CASE_BE:.
2006-04-28 15:30:50 Error The message status set to FAIL.
2006-04-28 15:30:50 Error Returning to application. Exception: XIServer:NO_RECEIVER_CASE_BE:
2006-04-28 15:30:50 Error JPR failed to transfer the request message to the messaging system. Reason: XIServer:NO_RECEIVER_CASE_BE:
I am getting this in the audit log for a Java Proxy <> XI <> RFC scenario. What could be the problem?
the configuration in integration directory seems to be perfectly fine however the message flow fails giving this error NO_RECEIVER_CASE_BE
Regards,
Amol

HI Amol,
Did you check the Message type/Message Inetrface names in the Java Proxy ?
Also check for Receiever Determinations in the configuration.
I assume that , you have created the Communication Channel under the Business System created as Standalone Java System.. If not check this.
Go to SXI_CACHE and check for the Receiever Determination created in the Configuration...
Hope this helps,
regards,
Moorthy

Getting Inbound Java Proxy Exception in method "onMessage"

I have built an Inbound Java proxy, deployed the EJB, viewed it in the J2EE admin tool, registered the JPR settings (also listAll, reviewed results, looks OK), configure the XI scenario. When I run the XI scenario using the Runtime workbench I get the following error in the BPM Synchronous Send step (calling the Java Proxy)
"com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method onMessage".
Does anyone have any suggestions?
What causes an "onMessage" Exception?

Thanks Sudhir Here is the process I am following to deploy my Proxy, would you please validate it. Created EJB Project in NWDS, unziped XI gened proxies into ejbModule folder, renamed *PortTypeImpl.template to *PortTypeImpl.java (will add real code later), compiled all code (no errors), edited ejb_jar.xml to match your suggested format, can view EJB Candidates (and see my Proxy Bean), built EJB.JAR file (via Wizard), created new Enterprise Application Project and pointed build path to my EJB Project, within the Enterprise Application Project I built an EAR file (which includes the "EJB Project JAR File", Deployed Enterprise Application Project to the XI J2EE Engine. I can log into XI J2EE Admin and see my EJB Project and the Proxy Bean I am trying to execute. Is this the process you used to deploy the proxy bean?
Also you you turn on JPR Tracing to see what parameters are passed into the JPR engine?

Sender java proxy don't work

Hello!
i configured a test xi scenario: JSP->(JAVA Proxy)-> XI -> file adapter.
Jsp is in the same bean of proxy.
I deploy this j2ee application in the same j2ee of XI.
When I open jsp page with browser and send data, nothing appened.
I check also in adapter engine monitor and xml monitor but i can't see any message.
I think the problem is inside java bean because if i fix the output data, after post action i see data in jsp page.
this is the class for call proxy:
public class InvokeProxy {
     public String getRole(String name, String pwd){
          String role="";
          UsersSyncMI_PortTypeLocalHome queryOutLocalHome=null;
          UsersSyncMI_PortTypeLocal queryOutLocal=null;
          try{ Context ctx = null; Object ref = null; Properties p = new Properties();
          p.put(Context.INITIAL_CONTEXT_FACTORY,"com.sap.engine.services.jndi.InitialContextFactoryImpl");
          p.put(Context.PROVIDER_URL, "server:50004");
          p.put(Context.SECURITY_PRINCIPAL, "user");
          p.put(Context.SECURITY_CREDENTIALS, "pwd");
          ctx = new InitialContext();
          queryOutLocalHome = (UsersSyncMI_PortTypeLocalHome)ctx.lookup("java:comp/env/ejb/UsersSyncMI_PortTypeBean");
          queryOutLocal = queryOutLocalHome.create();
          MessageSpecifier msg = queryOutLocal.$messageSpecifier();
          msg.setSenderService("BS_XID_PROXY");
          queryOutLocal.$messageSpecifier(msg);
          UserDT_Type reqtype = new UserDT_Type();
          reqtype.setUsername(name);
          reqtype.setPassword(pwd);
          UsersDBDTResponse_Type response = new UsersDBDTResponse_Type();
          response = queryOutLocal.usersSyncMI(reqtype);
          role = role + response.getStatementResponse().get_as_listRow().getRow(0).getRole();
           } catch(Exception ex){
               System.out.println(ex.getMessage()); } return role; }
any suggestion
thanks Ale

I haven't J2SE in my scenario. I can't try.
anyway, the code that i'm using now for call proxy is:
try{ Context ctx = null; Object ref = null; Properties p = new Properties();
            ctx = new InitialContext();
          ref = ctx.lookup("java:comp/env/ejb/MIZPROTOTIPOOUT_PortTypeBean");
          queryOutLocalHome = (MIZPROTOTIPOOUT_PortTypeLocalHome)ctx.lookup("java:comp/env/ejb/MIZPROTOTIPOOUT_PortTypeBean");
          queryOutLocal = queryOutLocalHome.create();
          MessageSpecifier msg = queryOutLocal.$messageSpecifier();
          msg.setSenderService("BS_XID_PROXY");
          queryOutLocal.$messageSpecifier(msg);
          DTZPROTOTIPOOUT_Type reqtype = new DTZPROTOTIPOOUT_Type();
          reqtype.setData1(name);
          reqtype.setData1(pwd);
          DTZRETURN_Type response = new DTZRETURN_Type();
          queryOutLocal.mIZPROTOTIPOOUT(reqtype);
          String respons = "work!";
          role = respons;
           } catch(Exception ex){
               System.out.println(ex.getMessage());
               String error = ex.getMessage();
               role = error;
      return role; }

SXMB_MONI shows error in Java Proxy (Inbound)

Hi All,
My scenario is FTP->XI->Java Proxy->FTP
I have configured the JPR Adapter and registered it correctly. But in SXMB_MONI, I am getting the error in JPR Adapter(Response) stating that,
Error when receiving by HTTP (error code: 108, error text:)
What could the problem?
Rgds,
-Prasad U

please change the time in the 'end of execution until' and check.Try giving it as 00:00:00 of the next day instead of 24:00:00 of the same day if you want to check the messages for that particular day.This might help.

How to test Java Proxy Classes in Portal

I have created a Java Project in NWDS and have added Java Proxy classes for BAPI_EMPLOYEE_GETDADA. I have created a main class to call the Java Proxy Classes.
I have noticed that I can not export it as .PAR file so I exported it as .JAR file. Now I logged into my Portal Server to test this new Java Proxy class but I do not see the .JAR file that I had created. Do I need to explicitly import it into Portal Server (I was thinking that similar to .PAR files, .JAR file will get transferred to the portal server automatically upon chosing Export from NWDS)
I am also not sure if I can create JAVA iView based on the .JAR file.
Please advise me on how can I test my Java Proxy Class.
Thanks a lot in advance.
Regards,
Sanjay Gera

Hi,
You can try with HTTP as sender. Send a HTTP request using HTTP Client code and check out the response.
For HTTP, sender communication channel is not required. All other steps in Configuration will be similar to any simple scenario.
Regards,
Uma

Java Proxy Exception

Hi all,
We are implementing a Inbound syncronous java proxy in our scenario. We were able to create and deploy the EJB successfully in the J2EE engine. The adpater configuration is also working fine. When we fire the message we are getting an exception in RWB saying
Delivery of the message to the application using connection JPR failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in method onMessage.: com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method onMessage.. Setting message to status failed.
I'm unable to understand the error. Can somebody tell me what this exception means?
Regards
Arvind

Satish,
Thanks for the reply. My biggest confusion here is if the control is actually going to the proxy class.
>>>Delivery of the message to the application using connection JPR failed>>>
When it says delivery of message failed what does it mean , is the message not reaching the proxy class or is it becuase the proxy class is not able to send the message to atrget URL which is the logic which I have implemented in the class.
regards
Arvind

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

XI Configuration incase of Java Proxy

Similar Messages

Maybe you are looking for