Regarding Proxies

Hi 2 all,
For making an ABAP Client Proxy we need to make an entry in Exchange Profile which helps in getting the information from Integration Builder for generating interfaces.....
Now my doubt is if i am using 5-6 systems for generating interfaces...suppose for SRM, SEM, CRM...etc...how can i make multiple entries in exchange profile of XI for these different systems for generating interfaces from Integration Builder.
Regards,

My question was related to Proxy Runtime :
1. Why do we make entry in Exchange Profile of XI ?
Like :
Exchange Profile
- IB-Address: Exchange Profil, Sektion Connections: com.sap.aii.connect.repository.name
- IB-Port: Sektion Connections: com.sap.aii.connect.repository.httpport
- Path: Sektion Connections: com.sap.aii.connect.repository.contextroot
- User: Sektion ApplicationSystem: com.sap.aii.applicationsystem.serviceuser.nam
- Password: Sektion ApplicationSystem: com.sap.aii.applicationsystem.serviceuser.pwd
( If i am not wrong then these entries help the application systems to connect with the integration builder on running SPROXY and shows us the interfaces form which we can generate proxy which contains respective msg types, and interfaces etc..)
Kindly correct if i am wrong ..What i feel that the response i got was related to Proxy runtime not with Proxy Generation

Similar Messages

Regarding Proxies execution

hi
how to execute ABAP proxies?client side and server side
thanks

hi
How do you activate ABAP Proxies?
Proxy configuration between R/3 and XI How do you activate ABAP Proxies?
ABAP Proxies in XI(Client Proxy)
ABAP Proxies in XI(Client Proxy)
http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/frameset.htm
How to create proxy.
Smarter Approach for coding ABAP Proxies
Smarter Approach for coding ABAP Proxies
File to R/3 via ABAP Proxy
File to R/3 via ABAP Proxy with good example
BPM : Sending message asynchronously and getting the response from synchronous system using ABAP Proxies
BPM : Sending message asynchronously and getting the response from synchronous system using ABAP Proxies
ABAP Server Proxies
ABAP Server Proxies
simple file 2 server proxy

No proxies generated

Hi there,
I know there are already some threads regarding proxies. But after reading these (mostly not answered) threads, I decided that the problems are too specific and to open a new thread:
After a data loss I have to set up FCSrv again. So far everythings seems to work, but I'm still having problems generating proxies:
In the FCSrv administration I've changed the proxy device (the old one was like "/path/to/proxies/proxies.bundle", so I have also set it up like this, with the filename included). In the preferences I have set the "Proxy Device" to this device and the stopped and restarted FCSrv in the prefpane.
Unfortunately I still get an error message when I try to create proxies: "ERROR: E_FILE unable to stat directory: /path/to/proxies/proxies.bundle No such file or directory"
Does anyone have a idea how to solve this?
Thank you very much!
Best regards,
Lenny

But how is it generated? Only when initializing FCSrv for the first time?
I deleted "proxies.bundle" from the proxy path and now it works. But now FCSrv generates a lot of folders and subfolders inside the parent directory for every proxy. I think this would normally be the content of proxies.bundle, right? Well, no problem for me, I don't need the proxy folder for something else. Is it a problem for FCSrv or might it become a serious problem at some point?
Thanks,
Martin

Error in abap server proxy

hi all here i am facing some problem regarding proxies. here my scenario is file-to- ABAP proxy. when i trigger message it is giving checkered flag in XI where as in receiver side it is showing error as below by giving red flag.
another important thing is the Z table is getting updated. but it is giving error in sxmb_moni of receiver side by red flag. please respond.
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>ZCL_INBOUND_INTERFACE</SAP:P2>
<SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Regards,
Ramana.

Hi Ramana,
there is an runtime error at your proxy. Look to transaction ST22 for details. To find out, what happend follow Stefans blog <a href="/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation: Debug your inbound ABAP Proxy implementation</a>
Regards,
Udo

[SOLVED] Cower fails to build

Heloo,
I've recently enabled [testing], and received pacman upgrade which installed libalpm.so.9, but cower was built against libalpm.so.8 on my system. First thought - rebuild cower. Unfortunately I received the following error:
bstaletic@arch cower % makepkg
==> Making package: cower 12-1 (Fri Dec 19 16:43:28 CET 2014)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found cower-12.tar.gz
-> Found cower-12.tar.gz.sig
==> Validating source files with md5sums...
cower-12.tar.gz ... Passed
cower-12.tar.gz.sig ... Skipped
==> Verifying source file signatures with gpg...
cower-12.tar.gz ... FAILED (the public key 487EACC08557AD082088DABA1EB2638FF56C0C53 is not trusted)
==> ERROR: One or more PGP signatures could not be verified!
How do I fix this? Is the key really not trusted or is there something wrong with my archbox?
My ~/.gnupg/gpg.conf looks like this:
# Options for GnuPG
# Copyright 1998-2003, 2010 Free Software Foundation, Inc.
# Copyright 1998-2003, 2010 Werner Koch
# This file is free software; as a special exception the author gives
# unlimited permission to copy and/or distribute it, with or without
# modifications, as long as this notice is preserved.
# This file is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
# Unless you specify which option file to use (with the command line
# option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf
# by default.
# An options file can contain any long options which are available in
# GnuPG. If the first non white space character of a line is a '#',
# this line is ignored. Empty lines are also ignored.
# See the man page for a list of options.
# Uncomment the following option to get rid of the copyright notice
#no-greeting
# If you have more than 1 secret key in your keyring, you may want to
# uncomment the following option and set your preferred keyid.
#default-key 621CC013
# If you do not pass a recipient to gpg, it will ask for one. Using
# this option you can encrypt to a default key. Key validation will
# not be done in this case. The second form uses the default key as
# default recipient.
#default-recipient some-user-id
#default-recipient-self
# By default GnuPG creates version 4 signatures for data files as
# specified by OpenPGP. Some earlier (PGP 6, PGP 7) versions of PGP
# require the older version 3 signatures. Setting this option forces
# GnuPG to create version 3 signatures.
#force-v3-sigs
# Because some mailers change lines starting with "From " to ">From "
# it is good to handle such lines in a special way when creating
# cleartext signatures; all other PGP versions do it this way too.
# To enable full OpenPGP compliance you may want to use this option.
#no-escape-from-lines
# When verifying a signature made from a subkey, ensure that the cross
# certification "back signature" on the subkey is present and valid.
# This protects against a subtle attack against subkeys that can sign.
# Defaults to --no-require-cross-certification. However for new
# installations it should be enabled.
require-cross-certification
# If you do not use the Latin-1 (ISO-8859-1) charset, you should tell
# GnuPG which is the native character set. Please check the man page
# for supported character sets. This character set is only used for
# metadata and not for the actual message which does not undergo any
# translation. Note that future version of GnuPG will change to UTF-8
# as default character set.
#charset utf-8
# Group names may be defined like this:
# group mynames = paige 0x12345678 joe patti
# Any time "mynames" is a recipient (-r or --recipient), it will be
# expanded to the names "paige", "joe", and "patti", and the key ID
# "0x12345678". Note there is only one level of expansion - you
# cannot make an group that points to another group. Note also that
# if there are spaces in the recipient name, this will appear as two
# recipients. In these cases it is better to use the key ID.
#group mynames = paige 0x12345678 joe patti
# Some old Windows platforms require 8.3 filenames. If your system
# can handle long filenames, uncomment this.
#no-mangle-dos-filenames
# Lock the file only once for the lifetime of a process. If you do
# not define this, the lock will be obtained and released every time
# it is needed - normally this is not needed.
#lock-once
# GnuPG can send and receive keys to and from a keyserver. These
# servers can be HKP, email, or LDAP (if GnuPG is built with LDAP
# support).
# Example HKP keyservers:
# hkp://keys.gnupg.net
# Example LDAP keyservers:
# ldap://pgp.surfnet.nl:11370
# Regular URL syntax applies, and you can set an alternate port
# through the usual method:
# hkp://keyserver.example.net:22742
# If you have problems connecting to a HKP server through a buggy http
# proxy, you can use keyserver option broken-http-proxy (see below),
# but first you should make sure that you have read the man page
# regarding proxies (keyserver option honor-http-proxy)
# Most users just set the name and type of their preferred keyserver.
# Note that most servers (with the notable exception of
# ldap://keyserver.pgp.com) synchronize changes with each other. Note
# also that a single server name may actually point to multiple
# servers via DNS round-robin. hkp://keys.gnupg.net is an example of
# such a "server", which spreads the load over a number of physical
# servers. To see the IP address of the server actually used, you may use
# the "--keyserver-options debug".
keyserver hkp://keys.gnupg.net
#keyserver http://http-keys.gnupg.net
#keyserver mailto:[email protected]
# Common options for keyserver functions:
# include-disabled = when searching, include keys marked as "disabled"
# on the keyserver (not all keyservers support this).
# no-include-revoked = when searching, do not include keys marked as
# "revoked" on the keyserver.
# verbose = show more information as the keys are fetched.
# Can be used more than once to increase the amount
# of information shown.
# use-temp-files = use temporary files instead of a pipe to talk to the
# keyserver. Some platforms (Win32 for one) always
# have this on.
# keep-temp-files = do not delete temporary files after using them
# (really only useful for debugging)
# honor-http-proxy = if the keyserver uses HTTP, honor the http_proxy
# environment variable
# broken-http-proxy = try to work around a buggy HTTP proxy
# auto-key-retrieve = automatically fetch keys as needed from the keyserver
# when verifying signatures or when importing keys that
# have been revoked by a revocation key that is not
# present on the keyring.
# no-include-attributes = do not include attribute IDs (aka "photo IDs")
# when sending keys to the keyserver.
#keyserver-options auto-key-retrieve
# Uncomment this line to display photo user IDs in key listings and
# when a signature from a key with a photo is verified.
#show-photos
# Use this program to display photo user IDs
# %i is expanded to a temporary file that contains the photo.
# %I is the same as %i, but the file isn't deleted afterwards by GnuPG.
# %k is expanded to the key ID of the key.
# %K is expanded to the long OpenPGP key ID of the key.
# %t is expanded to the extension of the image (e.g. "jpg").
# %T is expanded to the MIME type of the image (e.g. "image/jpeg").
# %f is expanded to the fingerprint of the key.
# %% is %, of course.
# If %i or %I are not present, then the photo is supplied to the
# viewer on standard input. If your platform supports it, standard
# input is the best way to do this as it avoids the time and effort in
# generating and then cleaning up a secure temp file.
# The default program is "xloadimage -fork -quiet -title 'KeyID 0x%k' stdin"
# On Mac OS X and Windows, the default is to use your regular JPEG image
# viewer.
# Some other viewers:
# photo-viewer "qiv %i"
# photo-viewer "ee %i"
# photo-viewer "display -title 'KeyID 0x%k'"
# This one saves a copy of the photo ID in your home directory:
# photo-viewer "cat > ~/photoid-for-key-%k.%t"
# Use your MIME handler to view photos:
# photo-viewer "metamail -q -d -b -c %T -s 'KeyID 0x%k' -f GnuPG"
keyring /etc/pacman.d/gnupg/pubring.gpg
EDIT:
I tried moving the directory and using the default, which produced the following error:
bstaletic@arch cower % makepkg -- INSERT --
==> Making package: cower 12-1 (Fri Dec 19 17:47:35 CET 2014)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found cower-12.tar.gz
-> Found cower-12.tar.gz.sig
==> Validating source files with md5sums...
cower-12.tar.gz ... Passed
cower-12.tar.gz.sig ... Skipped
==> Verifying source file signatures with gpg...
cower-12.tar.gz ... FAILED (unknown public key 1EB2638FF56C0C53)
==> ERROR: One or more PGP signatures could not be verified!
If I add the last line to gpg.conf, it shows the first error posted.
Last edited by bstaletic (2014-12-19 20:59:05)

bstaletic wrote:
I've read the news and did what was asked of me, yet the problem is still there.
P.S. Just to be sure, I have just redone the procedure described in the news.
EDIT:
The maintainer of cower just updated the package and his signature and now everythin is working.
As of today I'm having the same issue as you did. Did the maintainer change the gpg key back to the not working one?
I can't seem to get it added to my keyring for some reason.
EDIT: when I add the key 1EB26.. to my pacman-key it shows that nothing changed and the key seems to be fine.
But when I build the package it tells me that the key is an unknown public key.
Last edited by SimbaClaws (2015-01-26 21:50:30)

CREMDM and DEBMDM via Proxy/BAPI

Has anyone used a BAPI/proxy interface for customer and vendor master data instead of IDoc? If so could i get some pointers on where to start or some things that need to be done to make this happen? My scenario is File from MDM and want to use proxy/BAPI to R/3. Hope i am makeing sense. Any help would be greatly appreciated.

Hi Derrik,
there are some BAPI's but I would never use a BAPI when an Idoc is available.
The reason is that the idoc gives you the change to monitor messages in error, reprocess them and so on (like you can do from transaction WE05), instead for BAPI's you do not have these options and you cannot see the result of your operation after you have done it.
Regarding proxies, there is nothing standard in R/3 to send customer/vendors, but in ERP 604 you have the [SupplierERPCreateRequest_In|http://esworkplace.sap.com/socoview(bD1lbiZjPTAwMSZkPW1pbg==)/render.asp?packageid=DE0426DD9B0249F19515001A64D3F462&id=36BA3D85092411DC5A11000F20FCB6A9] ES for Vendors, for customer you have [CustomerERPCreateRequestConfirmation_In|http://esworkplace.sap.com/socoview(bD1lbiZjPTAwMSZkPW1pbg==)/render.asp?packageid=DE0426DD9B0249F19515001A64D3F462&id=E9F7B718706E11DA36BB000F20DAC9EF], which unfortunately is synch ES.
By the way, why you do not want to use DEBMAS and CREMAS?
Regards,
Sergio

Activating ABAP Proxy between business system and XI

I have a question on the release of XI Add-on we need to install on the Business system side for activating ABAP Proxy. We are using XI 3.0 system and want to activate the ABAP Proxy between XI 3.0 system and the R3E system running on WAS 620 SP 45.
I read an excellent SDN Blog from Vijaya Kumari on how to activate the ABAP Proxy. It lists XI Add-on installation on the business system. The XI Add-on (SAPK-20006INAPPINT SP06) is what the XI 3.0 configuration guide refers to in OSS note 439915. Is there a newer XI Add-on to go with XI 3.0 system?
Thanks,
Asif

Hi Asif -
SAPK-20006INAPPINT(SP06) is the latest XI add-on (APPINT 200_620) available. Since your WAS 620 is on (SP45) and the prerequisite for SAPK-20006INAPPINT(SP06) is SAPKB62043, your system looks ready. But of course, refer to the mentioned Note - 439915.
>>><i>Is there a newer XI Add-on to go with XI 3.0 system?</i>
I'm not sure if this is the right question. Any Web AS 6.20 system will require the XI-add on to communicate to XI (2.0 or 3.0) - specifically regarding proxies. WebAS 6.40 systems do not require the add-on.
Let me know if you need any clarification.
Thanks.
Jin

Where can I find a proxy server for firefox?

I would like to try using a proxy. I've looked into it a bit before, but the sites where I found proxy addresses appeared pretty sketch. At one time I found a page on the firefox support site that named some suggested proxy websites, so I assume they are fairly safe. Trouble is, despite an hour of searching, I can't find that page again. Can anyone give me a link to that page? Or provide some suggestions regarding proxies? Thanks

I just want to use portal server and deploy some
applications written in JAVA. Have I made myself
understood?
Still not clear.
Do you want a server application that deploys software. For example you create a game. Someone logs into your "portal server" and downloads the game from that?
Or do you just want to know how to package a java app that you have already written, and then put it on a CD so someone can install that on their computer?

Sproxy: why are ABAP names changed upon regeneration?

Hello, everyone.
I've got a small question regarding proxies regeneration via sproxy. In our system we have a datatype enhancement in ESR with several complex properties (internal tables), say, FIELD_1, FIELD_2 and so on. When the proxy was first created, the system generated types for each of these properties: BLAH_BLAH_TAB1 for FIELD_1, BLAH_BLAH_TAB2 for FIELD_2 and so on.
Recently I had to regenerate the proxy (a new element had been added to the XSD the proxy is based on). What happened next is the following: the sproxy changed the type names for all the complex properties, so FIELD_1 type name is now BLAH_BLAH_TAB2, FIELD_2 is BLAH_BLAH_TAB2, etc. Important note: the types themselves are OK, they conform XSD, however they are now known under different names.
This has caused a huge pain since those auto-generated types are used in several FMs and reports, so I had to change the names back manually (thankfully, sproxy allows names to be defined by hand).
My question is: how can I make sproxy keep the auto-generated names unchanged upon proxy regeneration? Or this is not possible and one should not address those types directly at all (too bad, a lot of code will need to be changed)?
Thanks in advance.

Yes, it has always worked in the past. The past projects audio clips do not change names. I obviously did something different in this current project, but unfortunately I have no idea what.

4.7 to ecc 6.0 by using sap xi

hi expects,
my client has the data in 4.7 but he want to take the data in ecc 6.0 with the help of sap xi.please help me.

Hi Santosh,
in order to integrate 4.7e and ecc 6.0, it's better to plan the interfaces with proxy communication.
please find the some the links regarding proxies.
XI: RFC or ABAP Proxy ? ....ABAP Proxies with attachments
/people/michal.krawczyk2/blog/2006/04/19/xi-rfc-or-abap-proxy-abap-proxies-with-attachments
/people/siva.maranani/blog/2005/04/03/abap-server-proxies - ABAP Server Proxy
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy - ABAP Client Proxy
ABAP Proxy Runtime
http://help.sap.com/saphelp_nw04s/helpdata/en/02/265c3cf311070ae10000000a114084/frameset.htm
Setting Up Point-to-Point Connections with proxy
http://help.sap.com/saphelp_nw04s/helpdata/en/85/78af1bf407434796aaf8dbd6d4e7b7/frameset.htm
Reliable Messaging ? EOIO in ABAP Proxies
/people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3dfac358-0d01-0010-5598-d4900e81a30c
warm regards
mahesh.

Regarding Abap Proxies & User Logins

Hi there
I created a scenario for a proxy to proxy interface. Same system, diffirent client. My question is, the proxy uses a HTTP connection that you setup in SM59. The login of your http connection, should it be tha same as your communication channel (XI Adapter) ? Because I get a error in the sxmb_moni on the receiver side saying "Unable to read user password from communication of channel type"
Thanx,
Jan
Edited by: Jan de Lange on Nov 7, 2008 11:40 AM

Here is the error trace:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_CHANNEL_PASSWORD_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to read user password from communication channel of type Error when accessing the secure store (access ID = 84161349A3EBD315E1000000AC13D508) Error while reading from the secure store: ERROR_UNKNOWN: Cannot find entry in secure store (SECSTORE,023)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Problem in creation of ABAP proxies

Hi,
I am trying to create proxies of Message Interfaces that are built from External Definitions(XSDs). In the scenario, we use two XSDs, one for structure of BAPI and one as Document Envelope containing header level information of the document. Message Interface is created for Document Envelope and internally it references XSD of structure of BAPI.
For e.g. For request message of BAPI_COMPANY_GETDETAIL, we have two XSDs:
1. BAPI_COMPANY_GETDETAIL
2. BAPI_COMPANY_GETDETAIL_Document_Envelope
I create interface for document envelope; interface internally references XSD BAPI_COMPANY_GETDETAIL.
When I try to create proxy for such an Interface I get following error:
Cannot generate proxy (object <element name="BAPI_ACC_DOCUMENT_POST"> missing in WSDL, see long text)
Message no. SPRX084
and diagnosis provided in long text is as follows:
Diagnosis
In the WSDL document, the object
   "<element name="Documents"> <complex/simpleType ..."
from the namespace
"http://mindef.nl/schemas/DocumentEnvelope"
links to the object
   "<element name="BAPI_ACC_DOCUMENT_POST">"
from the namespace
   "urn:sap-com:document:sap:rfc:functions"
However, this last object does not exist in the WSDL document.
System Response
ABAP proxy generation expects that all directly and indirectly referenced objects are in the WSDL document. Therefore, no proxy can be generated for this WSDL and the system displays an error message.
Procedure
This situation can have different causes:
Object "<element name="BAPI_ACC_DOCUMENT_POST">" not been defined
Object "<element name="BAPI_ACC_DOCUMENT_POST">" saved in the wrong namespace
In the reference to object "<element name="BAPI_ACC_DOCUMENT_POST">", the wrong name was specified
In the reference to object "<element name="BAPI_ACC_DOCUMENT_POST">", the wrong namespace "urn:sap-com:document:sap:rfc:functions" was specified
Internal error in the service that constructs the WSDL document
Internal error in ABAP proxy generation
I have checked all the possibilities, there is no inconsistency in WSDL.
Kindly provide some suggestions to tackle this problem.
regards,
Bhavish Bhatia

Hi Bhatia,
You cannot create ABAP proxies from external definitions, IDOC or BAPI, when your application system is based on 6.20.
This works only, when your application system is based on 6.40 or higher.
Regards,
Udo

New Data in R/3 Enterprise - ABAP Proxies - XI what happen?

Hi,
i have a theoretical question:
if i use R/3 Enterprise on WAS and put new Data in the R/3 System and transport them to XI with ABAP Proxies. What happens in the systems?
How do the R/3 System put new data in the proxy runtime and send them to xi?
I want to unterstand how the transport from new data in a R/3 System with ABAP Proxies comes to the XI Integration Server.

Hi Marcel,
>>>>>How do the R/3 System put new data in the proxy runtime and send them to xi?
all you need to do in r3 is to fill tables of a generated structure
and execute one method of a generated class (send....)
then R3 will connect over HTTP to XI and send the data from your structures
structures and class in R3 is being generated automatically via TCODE SPROXY
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Client proxies no longer work after R/3 upgrade to ECC5.0

Hi,
After the above upgrade where WAS of the R/3 systems went from 620 to 640 client side proxies no longer work.
To be able to use client proxies in 620 we had to use a plugin. But in 640 this should be native functionality, so no more plugin for this.
The error seems to lie in the connection from R/3 to XI. If I test the RFC connection that is defined in SXMB_ADM on R/3 I get the following error:
HTTPIO_PLG_ICM_CONNECT_FAILED-Fehlermeldung beim S
Message no. SR000
The IFR address is correctly defined.
The SPROX_CHECK_HTTP_COMMUNICATION test in sproxy-connection tests gives the following detailed info:
When calling the method
CL_HTTP_SERVER=>GET_EXTENSION_INFO
the exception
NO_HTTP_PING_SERVICE_FOUND
was triggered.
Does anyobe know how his can be solved?
Thanks
Tom

HI,
I think some problem with http destinations
Is your R3 system is configured as a Application system ?
Go to SXMB_ADM->Integration Engine Configuration->Check role of business system etc. and corresponding Integrtaion server
Check this guide page no-27
https://websmp102.sap-ag.de/~sapidb/011000358700001697502004E.PDF
Regards,
Moorthy

Dynamic Proxies

I'm trying to implement a way of monitoring method calls on certain objects so that I am able of enforcing security constraints on these calls.
Considering the functionality provided by the reflection API, I thought that dynamic proxies would be a viable solution.
But they have one major restriction:
A dynamic proxy implements interfaces and thus can only be casted to one of these interfaces.
So what can I do if I need a proxy on class instances which do not implement any interface?
I have read a few older threads dealing with this problem, but I couldn't find any satisfying solution.
There where some ideas of runtime creation of byte code and creating classes from it.
Another way would possibly be runtime compilation of dynamically created code.
But aren't there any less cumbersome ways for implementation?
Regards,
Volker.

The idea with the class loader sounds interesting. Although I would have to implement it in a way so that it creates proxies for all classes ever loaded into the JVM. What I am trying to prevent is the following:
Let's say there is an object "secure" which needs access control and there is another object "caller"with a reference to a "proxy" object monitoring the "secure" instance.
The initial creation of proxies would be no problem since the critical objects are stored in a object database where they can only be retrieved from by explicit query calls. Implementing my own query method allows me to exchange the result of the query with proxy objects which then are returned to the caller.
Now "caller" invokes a method on proxy, let's say proxy.doSomething(this) and passes itself as a parameter to the call. Now let's assume "caller" is granted access to the method and the call is delegated to "secure".
In the process of method execution a method of "caller" is invoked (e.g. the equals method to check if the passed parameter is contained in a Collection) which is possible since "caller" has been passed in as a parameter.
Now the caller.equals(Object o) method could possibly recieve an unprotected instance of the secure object or any other unprotected object which requires access control via the parameter o.
Thus I need some way to dynamically generate a proxy class for "caller" which monitors access to its methods and checks if there are any unprotected instances passed as parameters to it and then exchange these instances with another proxy object.
This is exactly the reason why I need to generate proxies for arbitrary classes (not interfaces) dynamically.
Trying to solve the problem with my own class loader would require me to create proxy objects for all classes, even those from the Java API. I am not sure if this effort pays. Anyway it would probably cause severe performance problems.
Another solution would be dynamically subclassing objects and overwriting each method to perform security checks. But this is inconvenient since it is not guaranteed that i can subclass a given class and furthermore I couldn't prevent access to public fields which may exist.
Perhaps there is another solution to the problem.

Regarding Proxies

Similar Messages

Maybe you are looking for