Proxy Runtime and J2EE

Hi,
I'm new to proxy scenarios in XI and wanted to ask quite a simple question - is activation of J2EE stack required on application server (R/3) side to implement proxy scenario?
BR,
Reinis Dzenis

Hi,
If you want to use ABAP proxies, you definitely need the J2EE stack of the application system.
Regards
Manish

Similar Messages

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

Idoc Communication Configurations and Proxy Runtime Configurations for PI

We have a fresh PI 7.1 system, fresh ECC6 system, and an existing 4.6C system.
is there any blog/doc with step-by-step instructioins/screenshots for following tasks:
1. Configuring Abap proxy runtime between ECC6 and PI 7.1 Systems, for using sproxy from ECC6.
2. Configuring for IDOC communication between ECC6 and PI 7.1
3. Configuring for IDOC communication between 4.6C system and PI 7.1
It involves creating of sm59 rfc destination creations, usage of idoc related transactions on PI system and the other system.. I searched on sdn/forum, but it seems to be addressing specific issues faced.
Pls suggest any step-by-step instructions docs/blogs available.
thanks in advance.
Madhu.

Madhu,
Refer the links below:
1. /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
2& 3 :
https://wiki.sdn.sap.com/wiki/display/XI/SAPR3%28Idocs%29ToXI--Steps+Summarized
http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c&overridelayout=true
http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
Also, I think u hv just started learning XI ..so following link might help:
http://wiki.sdn.sap.com/wiki/display/NWTech/QAforPI-Onestopforall%28Part-1%29

Difference between WS runtime and proxy runtime

HI,
I'm new to PI/XI. 1) Could anyone please explain about the real difference between WS runtime and Proxy runtime?
2) How to configure the scenario's for WS communication and proxy communication?
3) what is the adapter type we should use for this in ID?
4) How to convert the proxy to webservice? etc.
Thanks in adavnce
Regards,
Baskaran K

I'm new to PI/XI.
I would suggest that you first make use of the Search facility of SDN. If I am not wrong all your questions will be answered by a Search.
Regards,
Abhishek.

PCK and Java Proxy Runtime

Hello,
I am a newbie to XI world and have some questions regarding PCK and Java Proxy Runtime. Is it possible to send the message from PCK by using Java Proxy Runtime as Sender?
If yes what exactly configuration steps have to be done on PCK side like SLD & ExchangeProfile configuration according to Configuration Guide or XI Receiver Adapter with Receiver agreement creation?
Thanks in advance,
Viktar

Hi Stefan,
Thanks for information. We successfully checked a simple test scenarion JPR -> PCK -> File. It was necessary to configure properly XI Sender and File Receiver adapters on PCK.
SLD and Exchange Profile were not required to be configurable but in this case we have to use MessageSpecifier interface in client proxy for sender and receiver determinations.
Regards,
Viktar

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

Runtime Workbench Proxy Runtime Configuration

Hi
I'm trying to setup the RWB proxy runtime configuration. However our ERP system shows up as an ALE-Logical system and not a Business System in the Configuration tab of the RWB and doesnt appear at all in the Component Monitoring tab so we cant monitor messages from it through the RWB.
We've tried deleting the business and technical system and re-registering them with RZ70 as well doing a CPA Cache refresh. But that hasnt resolved the issue.
I have compared this system to another system in the SLD which does show up as a Business System and can be monitored through Component Monitoring. They seem to be exactly the same.
Is there some kind of setting we are missing on the ERP system?
Thanks
Riaz

Hi Riaz & kesava,
RWB Proxy runtime setup can be seen from RWB->Component Monitoring under Components section Domain XI->Integration Engine.
Check the following
1)Can the SLD be reached? - RFC destination, ping, getLCR server, read cache, BS defined
2) Does the Integration Engine know the business system?   - Business system name = BS_100, Role = Application System
3)Are roles in SXMS_CONF_ITEMS and SLD consistent?   - Role = Application System
4)Has an Integration Server destination been defined?   Destination 'XIabcd100' to the Integration Server
Cheers
Veera

Error in Runtime Workbench, Component Monitoring, Proxy Runtime

Hi,
I have the following error in the Runtime Workbench, under Component Monitoring->Integration Engines->Proxy Runtime. The error message is Ping Status: Unable to logon to system xxx in language EN with user XIRWBUSER. However, I am unable to find out where the account and password are specified in order to correct this. Any help would be appreciated.

Hi,
it can be for some system configured on http destination or the sld system configured for this server.
take a look at tx sxmb_adm for the http destination to discover witch destination is been used. then, on sm59, find the server that is been called for this http destination and check on that server if this user is ok there.
to check sld, go to tx sld_apicust discover witch is the sld system configured for this server. After log on to sld system and check the user.
Maybe the user is ok on the destination system, so, check the password on sm59 (if the problem is with an http dest) or sld_apicust (if the problem is the connection to sld).
regards.
roberti

Integration Engine Proxy Runtime Error

Hello,
I have ECC and PI server for my landsacpe. When i ran SXMB_IFR tcode in my ECC server i got the follwing error under Runtime work Bench
Proxy Runtime - it is shows red color.
Unable to log on to system ECC120 in language en with user PIRWBUSER
Details for Ping Status
Message: Unable to log on to system ECD210 in language en with user PIRWBUSER
Stacktrace:
com.sap.aii.rwb.exceptions.OperationFailedException: Unable to log on to system ECD210 in language en with user PIRWBUSER
at com.sap.aii.rwb.core.XIAbapRTCComponent.getConnector(XIAbapRTCComponent.java:114)
at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:581)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:425)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:525)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:552)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:481)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)
at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at jsp_FC_Secure1229621978943._jspService(jsp_FC_Secure1229621978943.java:15)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
When i checked my PIRWBUSER password in abap and poratal level there is no conflicts. Password is correct.
For integration i have created three RFC also
LCRSAPRFC,SLDAPIRFC,SAPJ2EE all these RFC are working fine and there is no error.
Can any one suggest me how to resolve this issue.
I am waiting for your reply.
Regards,
Sankaranarayanan.G
BASIS CONSULTANT

Hi Tuhin,
I have one more problem now. Intially i have configured my PI development portal.But after some days in my PI server when i ran SXMB_IFR is detecting wrong poral now. I have tried to change from my EXCHANGE Profile under integratrion server parameters i have changed PORT,URL and others.
but it is not come to effect. can you please help me where do i need to chage the portal?
I am waiting for your reply.
Regards,
Sankar.G

Proxy Runtime errors in Integration Engines at RWB

Hi Experts,
We have configured the point to point configuration scenario in our landscape. I have two ABAP systems exchanges data using PI. I have configured both the ABAP systems as Application Systems and Corresponding Integration server as my PI system.
In RWB of PI I can see both these systems as proxy run time under Integration Engines, but are in error status.
Path to the same is Component Monitoring>Components>Integration Engines (here I can my systems as Proxy Runtime BSAB200, Proxy Runtime BSID200).
When run the test got the below error.
Can the SLD be reached? RFC destination LCRSAPRFC does not exist
Does the Integration Engine know the business system?
Are roles in SXMS_CONF_ITEMS and SLD consistent?
Why do we need to create the RFC destination again when we select the related integration server as PI.
Can any one throw some light whey are these errors are occured.
Thanks,
Chinna

Can the SLD be reached? RFC destination LCRSAPRFC does not exist
Reached to SLD but not to exchange profile.
Does the Integration Engine know the business system?
Yes.
Why do we need to create the RFC destination again when we select the related integration server as PI.
A central SLD scenario involves a central SLD, but not a central exchange profile.
The exchange profile used is always the one on the Integration Server the
application system connects to the exchange profile using the SM59 destination
LCRSAPRFC.
Regards
Pothana

ABAP Proxy runtime is showing status as red

We have ABAP Proxy runtime for four different ABAP systems. Except one all the other three proxies are showing the status as red. Could you please help me with this regard - Points guaranteed

Hey,
Go to <b>SM59 -
> R/3 connection to ABAP Systems -
> INTEGRATION_DIRECTORY_HMI</b>
Now press the Connect Test button, and chek it every thing is ok. You should not get any error!!.
If above one is ok in all three systems, then second option is
Go to tcode <b>SICF -
> default_host --->sap -
>xi</b> check if all the services are active (if active, will be in pure black color), if not active then activate them, may be you will require authorizations for this work.
Try the above solution and it will work.
Regards,
Sarvesh
****Reward points if it helped you.

Proxy Runtime configuration in Quality

Dear All,
I am sending data from XI to BI through server proxy.
We have link between ERP quality and XI development. Do i have to do Proxy runtime configuration in quality server directly. Do I need to do it manually or transport from development?
Regards.
SM.

> We have link between ERP quality and XI development. Do i have to do Proxy runtime configuration in quality server directly.
> Do I need to do it manually or transport from development?
You have to do this manually.

Proxy Runtime for Business System not visible in RWB.

Hi,
We are running SAP PI 7.10 SP7.
The current landscape contains currently 2 SAP R/3 application systems and 1 SAP PI systerm that are all registered with the SAP PI SLD.
There is Business Systems configure for both the Application systems in the SLD from the registration.
In the ID it was possible to import these Bussiness systems and to use them in scenarios. It is even posible to post messages to both IE on these Business Systems. If tcode SPROXY is executed on both these business systems then it connects to the same ESR. On both business systems I have created a "PIRWBUSER" with the same password and roles as on SAP PI.
Now my ploblem is that I only see one proxy runtime in the RWB under Integration Engines.
Please can you assist in this matter?
Regards
Willie Hugo

Hi,
The problem is solved with patches to the following JAVA components.
MESSAGING 7.19
SAP_XIAF7.17
SAP_XITOOL7.14
Regards
Willie Hugo

License keys for WAS 640 and J2EE

How does licensing WAS ABAp and J2EE differ....
If I get a key for WAS 640 ABAP and install via SLICENSE does this cover the J2ee engine also? I am running WAS 640 +java addin
Thanks
John

You might need to installed the license for the J2EE engine separately. To see the installed licenses for the J2EE, use Visual Administrator and then: Server -> Services -> Licensing Adapter and under the "runtime" tab, see under installed licenses if you have a license installed, or not.
If not, you can install it there too.
- Fanus

Base64 in Proxy Runtime

Hi gurus,
I'm planning to use Base64 for sending/receiving binary data to R/3. I generated a proxy for a receiver interface which has a field of type Base64 and it is generated as RAWSTRING.
When I send a test XML through a web service (for my SOAP-PI-Proxy scenario) which has a correct Base64 data in the relative field, the proxy runtime in R/3 throws "Error in Control Framework" in SMQ2, even before the message reaches the proxy code.
How does the proxy runtime handle Base64? Does it actually convert it to RAWSTRING or I should use different xsd types for inbound interfaces(such as hexString maybe?). If yes, how to convert?
And what about sending? Is it possible to send Base64 from client proxies?
Regards,
Gökhan

what is the Type that you have defined in DT of XI/PI....it should be xsd:base64Binary.......then you can build your proxy accordingly to accept the base64 message...check it out...
Regards,
Abhishek.

Proxy Runtime and J2EE

Similar Messages

Maybe you are looking for