Invalidate the Adaptive RFC Dictionary Cache

Hi All,
I had to do RFC interface structure changes for a Webdynpro JAVA application.I had deployed the application and used the administrative function "Invalidate Adaptive RFC Dictionary Cache" within the Web Dynpro console" to explicitly invalidate the metadata cache..
Before using this tool, I was not able to run the application.This tool helped to run the application.
But When I Submit the data to the RFC from this application I get the following Exception:
com.sap.mw.jco.JCO$MetaData.getType(JCO.java:10210)
I understand from the SAP note 859950, Metadata is not invalidated without J2EE Engine restart.
Is there any update from SAP after this note..Pls let me know if some one has done a workaround instead of restarting the SAP NW Application server.
Thanks, Sethu

We went through this same issue many times and we opened an issue with SAP a few months ago.
The invalidate is very limited and does not handle a clustered server architecture. It is meant only for a single node, single server setup. All of our environments are multi-node and multi-server.
The tool will only invalidate the node that the Basis Administrator is currently logged onto. Therefore if your server architecture consists of > 1 node and/or > 1 servers then you will have nodes/servers that still have the previous version of the metadata cached.
SAP said the Basis administrator would have to log onto each node and run the invalidate tool. In a multi-node setup there is no easy way to do this because there is no control which node you will be put on. If you have 1 node per server then yes you can log onto each server and run the tool.
In the end SAP said they do not support the Invalidate tool in a multi-node/multi-server cluster.
They said to perform a J2EE restart, period.
Hope that helps.
Dean Cyril Wood

Similar Messages

  • SAP R3 Conector System at the Adaptative RFC model

    Hi folks!
    We´ve generated a Web Dynpro project using the Adaptative RFC model. When running the application we get the exception:
    com.sap.dictionary.runtime.DdException: at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:89)
    This surely happens because we haven´t defined the SAP R3 connector system:
    Could someone please show us how to do this?
    We are using SAP R3 Dedeicated connection, should we use the SAP R3 ConnectionString? At least, we need to know which is the Gateway Host, the SAP R3 machine or the J2EE WAS one? Is the other the Application Server Host? What would be the Gateway Service?
    In the other hand, at defining the RFC Destinations on the SAP R3 server, we´re using the "Registered Server Program" Activation Type. Is this correct? When testing the connection, it fails because the program is not registered at the server.
    Thanks in advance.

    Hi Bernanrdo,
    I have given answer to your another post.
    Just look at that. It will help you.
    Regards,
    Bhavik

  • Can't invalidate the CMP bean's cache. Please help

    Dear all,
    The ClassCastException raised while calling:
    (weblogic.ejb.CachingLocalHome)home).invalidate (Arrays.asList(primaryKeys));
    The CMP bean uses optimistic concurrency and caching between transactions.
    <b> Please advice what weblogic-ejb-jar.xml attributes may be set to cause Weblogic generate proper Home stub that may be cast to CachingLocalHome?</b>
    P.S. weblogic-ejb-jar.xml :
    <weblogic-enterprise-bean>
    <ejb-name>MyEntity</ejb-name>
    <entity-descriptor>
    <entity-cache>
    <concurrency-strategy>Optimistic</concurrency-strategy>
    <cache-between-transactions>True</cache-between-transactions>
    </entity-cache>
    </entity-descriptor>
    </weblogic-enterprise-bean>

    check the documentation for invalidation of RO entity beans there is example code to invalidate on OCE.
    http://e-docs.bea.com/wls/docs81/ejb/entity.html#ChoosingaConcurrencyStrategy

  • Invalidating rfc metadata cache

    hi all,
    i want to invalidate rfc metada cache through adaptive rfc metada cache invalidation tool in webdynpro console..
    can any one plz suggest me the path to find that.
    thanks in advane
    seshagiri

    hi juan,
    it was very helpful solution to our problem that is invalidating rfc metadata.
    after i gone through the pdf,i found it is for NW04S or 7.0 SP12
    but v r using SP09
    so i beleive upgraing is the only solution.right
    or can u suggest any other solution.
    thanks in advance
    seshagiri

  • Error msg-Adaptive RFC reimport could lead to inconsistency of R/3 metadata

    Hi Experts,
    I am trying to reimport the model for Webdynpro application.
    I wanted to include more BAPIs to the existing model.
    When i am trying to do that I get pop up, with following message;
    "Adaptive RFC reimport could lead to inconsistency of R/3 metadata cached on J2ee server.
    Thus it is recommended to invalidate the cache this could be done either by re starting the J2EE server or by using adaptive RFC metadata cache invalidatation tool within webdynpro Console"
    Could anyone one help me in resolving this?
    Thanks and regards,
    Pradnya

    Hi,
    When you reimport an RFC/BAPI the metadata which is stored in the cache is not cleared. So it still refers to the old RFC/BAPI metadata. We need to clear this. This can be done by either restarting the server or webdynpro console.
    For Clearing through webdynpro console the version should be NW04 or 6.40 SP21 Onwards 2. NW04S or 7.0 SP12 Onwards
    Check this link.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10465350-b4f5-2910-61ba-a58282b3b6df
    Thanks,
    Gopi

  • Adaptive RFC model connectivity to SAP R/3 4.6 B

    We are developing a new webdynpro application which uses the backend R/3 version is 4.6B using Adaptive RFC model.
    We are able to connect to Web As systems without any issues but getting error messages while creating the Adaptive RFC model to R/3 4.6 B system as backend.
    Appreicate your help.
    Message was edited by: Udaya Chada

    Hi ,
    I think SLD,s/w Catalog and Creating Logical Systems were Configured,
    Go through the Following Steps Like,
    -- General Data, Enter the Client of the System and Client No. (JCo Connection is Pointing to)
    --J2EE Cluster, Select the J2EE Cluster you wish the JCo destination to be assigned
    -- Select the Destination Type, Either Application/Dictionary data
    -- Appl.Server, You may only select Servers/Logon Groups From the Drop down list that have first been defined as technical Systems in SLD.
    -- Message Server, Application Data JCo destination is connected must have atleast one logon group.( if this is not done ,use SMLG transaction code to create in SAP System)
    --Security, If you have selected connection Type as Application Data , then in the Security Screen you would appear Authentication Techniques and select a appropriate one .
    if you have selected connection type as a Dictionary meta data then provide User Name and Password
    If this is useful to you ,don't forget to award Points
    --Venkat

  • Looking for a beginner guide - Adaptive RFC  call BAPI  in Web Dynpro Java

    Hi,
    im new in SAP Developeing. I developed some basic web Dynpro applications (after some tutorials) and they are all working.
    Now i want to build an Web Dynpro application with an adaptive RFC Model.
    I already imported the adaptive RFC Modell with a function Model (BAPI Z_...) from the R3 System successfully.
    But if i deploy the application i will get following error:
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type extern:mypackages.com.types.BapiModel:mypackages.com.types.Zmbs_Bapi_Dispo_Orderdata could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:305)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:234)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:449)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:387)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:416)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:83)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:125)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:121)
         at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:215)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         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)
    Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:377)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:322)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:181)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:180)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:303)
         ... 49 more
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:152)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:178)
         at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:62)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
         ... 59 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load client to connect to SLD. Please check your SLD connection settings using the Visual Admin.
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:754)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getClient(SystemLandscapeFactory.java:747)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.readJCODestinationFromSLD(JCOClientConnection.java:511)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:439)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233)
         at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
         ... 62 more
    Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Failed to create CIM client. Check via 'Visual Administrator' tool if the secure store is operational.
         at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:117)
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:751)
         ... 70 more
    Caused by: com.sap.lcr.api.cimclient.CIMClientException: java.net.MalformedURLException: URL must have a host part
         at com.sap.lcr.api.cimclient.ClientFactory.createConnection(ClientFactory.java:466)
         at com.sap.lcr.api.cimclient.ClientFactory.createClientImpl(ClientFactory.java:413)
         at com.sap.lcr.api.cimclient.ClientFactory.createClient(ClientFactory.java:363)
         at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:113)
         ... 71 more
    ........Looks like a have a Problem with JCO.
    Is there a good guide, which explains the Basic steps in developeing Web dynpro applications and BAPI ?!

    thank you guys for all the answers.I have to read all the documentations.
    to my szenario:
    I installed on my notebook the Trial Versions of:
    SAP NetWeaver Application Server 7.00/Java AS 7.00
    SAP NetWeaver Developer Studio Version: 7.0.14
    All my basic Web Dynpro Applications in Java are running (even with Adobe Interactive Forms) on the local NetWeaver Trail- Web AS Trail perfectly.
    Now i want to connect per RFC to another SAPERP Server, which is in the intranet.
    I did the whole RFC tutorial with the flights -
    http://help.sap.com/saphelp_nw04/helpdata/en/c3/76b45d9688e04abe1a1070410ddc1e/content.htm (also with the JCO codeing etc)
    so my web dynpro application should work.
    I think I have to configure - like ramesh said something on the NetWeaver Trail.
    So what do i need and configure excactly on my Netweaver Trial to work with RFC - to call the BAPIS in the other System?
    - SLD ? JCO ?
    If i over Web Dynpro - Content Administrator - >
    it says "Connection to System Landscape Directory (SLD) could not be opended successfully." and all the buttons
    create Jco destinations etc. are greyed out.
    I didn´t configured the SLD and JCO in the Netweaver yet.

  • Adaptive RFC 2 gives error: com/sap/ide/jco/service/internal/R3Service

    Hi,
    I've run into the following problem about NWDS. This happens as I create a Model. It appears there is a new version of the Adaptive RFC Model, which is called Adaptive RFC 2 Model.
    1. Right click on Models, and select Create.
    2. Double Click on Adaptive RFC 2 Model
    3. The error pops up. It says "An error has occurred. See error log for more details. java.lang.NoClassDefFoundError". Then if you click details you get "An error has occurred. See error log for more details. com/sap/ide/jco/service/internal/R3Service "
    If you know which log to have a look, or what this error is about please let me know urgently. Any help if much appreciated.
    Thanks,
    Ogeday Isiklar

    Hi,
    I am also getting same problem. Waiting for solution
    Regards,
    Pradeep Kumar

  • What is adaptive RFC and How to Use it

    hi friends
    what is the adaptive RFC
    what is the use of it
    how we can use it
    explain me anyone
    and send pdf also
    thanks
    ramu.

    Hi,
    To give u a brief idea.
    rfcs are used to call data from the backend that is R/3.We use the Bapis from the R/3 system which have some pre defined functionality and data is populated in the correspoding ui elements in webdynpro interface.earlier Rfcs were used but now we have adaptive rfcs in which
    if there are changes in the backend(R/3 system) such as changes in the datatype,structures,fields would be automatically be refllected in the rfcs and there would be no errors in web dyn pro even if there is  a change in the back end
    to be more specific folow this link
    http://help.sap.com/saphelp_nw70/helpdata/EN/41/38bc8f813719488ddc9d9b21251ec3/frameset.htm
    and try out this application
    to use the rfcs firstly check out this document for configurations
    Important Configurations for Calling ABAP Function from Java Web Dynpro Application
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07753b9-fa0c-2a10-64a8-c6754c45396e
    heres the application.
    Creating a Web Dynpro Application Accessing ABAP Functions
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/355b9c90-0201-0010-d2a8-89fece426526
    regards
    Nikhil Tapkir

  • Reimporting of Adaptive RFC model

    Hi all, I have added two fields in the BAPI and i have reimported the Adaptive RFC model in Web Dynpro.
    After running the application and accessing the new fields, i am getting this exception.
    java.lang.ArrayIndexOutOfBoundsException
         at com.sap.mw.jco.JCO$MetaData.getType(JCO.java:10161)
    What could be the reason?

    Hi,
    As the error states MetaData.getType it seems that the new changes are not yet reflected in the J2EE server. You need to restart your engine once. You can search this forum for a workaround  by Valery which doesnot need a restart.
    Regards
    Ayyapparaj

  • Adaptive RFC in webdynpro

    Hi, I developed a custom application in webdynpro and made it to work and in the mean time the sneak preview license expired. I have reinstalled the sneak preview but cannot get the application to work. I had saved the old application in my hard drive and the cannot reimport the model. Any help in this regard is highly appreciated.
    Best regards,
    Srini.

    I found one problem was missing object in the SAP system. Once I got that in place I was able to make the application work. I still have a problem with the Adaptive RFC import. This is the error I get.
    I get this exception in a pop up.
    "An internal error has occured. See error log for more details. "
    Plug in Name - Web Dynpro Model Editor Services
    Plugin Id    - com.sap.ide.webdynpro.service.modeleditor
    Class - com.sap.ide.webdynpro.modeleditor.wizards.model.
            creation.ModelDialog
    Method - nextPressed
    Message - Internal error - see detail information in
              exception trace.
    Exception - org.eclipse.swt.SWTException: Failed to 
                execute runnable 
                (Java.lang.NullPointerException)
    Where can I see more information? what is possiblit=y wrong.
    Also I cannot connect to SAP system from the IDE. So I am missing something. But I could run the old application that accesses SAP without problem.
    Any help in this regard is highly appreciated.
    Best Regards,
    Srini.

  • Adaptive RFC and multiple systems; Mapping JCO_DESTINATIONS by code?

    Hi,
    I have just learned <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/82/76a2406546ba15e10000000a1550b0/frameset.htm">here</a> that I can access several R/3 systems with the adaptive RFC model by using URL parameters like:
    http://<hostname>:<port>/webdynpro/dispatcher/local/ESSProject/ESSApp?
    <b>sap-wd-arfc-useSys=WD_MODELDATA_DEST:ABC&
    sap-wd-arfc-useSys=WD_RFC_METADATA_DEST:ABC</b>
    The parameters are a mapping of the original JCO_DESTINATION (WD_MODELDATA_DEST) called by the WebDynpro application to the target system which instead should be called (WD_MODELDATA_DESTABC).
    Does someone know wheather this mapping can be done by java coding? For example before the execute method will be called.
    Best regards,
    Marcus

    Hi,
    This for If you send destination params are different u sent it thru URL param only.
    For that u need generate URL by using the application .
    For that purpose u need to create two applications u can call the first application in second application u can create URL and send Destination params with URL only.
    Other wise u can create the par file that would be configured in portal and thru worksets u can pass the params like u mention the destinations.
    Or at the time generationg URLS only u can add the destination names.
    Thanks,
    Lohi.

  • Adaptive RFC use in test/dev systems

    The Adaptive RFC model requires a msg.server for metadata. Does that mean it can't be used in test/dev system where there is only an app server? I find that hard to believe.
    Secondly, during the creation of JCO Connections in the webdnypro content admin tool, the drop down boxes for message server and application server are empty. where is this data defined? saplogon.ini + ...drivers/etc/services files were copied to the WAS/SLD host machine.
    Furthermore, is the Adaptive RFC the best way to use SAP data (called from function modules) in a webdynpro?
    Thanks,
    faB.
    Message was edited by: faB

    Hi,
    1.Even in development system you have centrall services, and as part of this you have a message server. So you can use Adaptive RFC model in development sysetems without any problem.
    2.Regarding you second question: you should define you application system in SLD before using JCO destinations. Just search for SLD in this forum and you will fine the how to configure it.
    3. AFAIK, Adaptive RDC model <b>is</b> the best way (it's better to say the <b>proper</b> way) to use your SAP application system in the WAS context.
    Hope it helps.
    Victor.

  • Many Adaptive RFC

    hello all
    I have one question about Adaptive RFC.
    In my project, i have many RFC access. My question is, what best practices for import RFC. One Model and all RFC in this model?
    Each RFC is a Model?
    If each RFC is a model, can i set JCO name equal?
    tks
    Douglas

    Douglas-
    Here are some points to keep in mind when using Adaptive RFC Models:
    1. Use the Adaptive RFC Model for accessing RFCs in an SAP system.
    2. Each Adatptive RFC Model should be in it's own Java package.
    3. Group Adaptive RFC Models based on functionality.
    4. Never have one RFC module per Adaptive RFC Model.
    5. Model your RFC so that it can be reused.
    Cheers-
    Atul

  • Metadata Cache Invalidation for Adaptive RFC Models

    Hi,
    I’m trying the tutorial of the document: Metadata Cache Invalidation for Adaptive RFC Models.
    I’ve downloaded and deployed the EAR for NW7.0 on my server, but when I try to list the JCO destinations I have the following error:
       java.lang.NoSuchFieldError: flush_cache
        at com.sap.invalidation.InvalidationView.onActionGetSLDJCOs(InvalidationView.java:215)
    When I try to invalidate a dictionary, I have the message:
    Cache for Dictionary com.unilog.product.search.model.types.SearchProductModel invalidated
    But the tooltip value is not updated in my application...
    Can anyone give me some tips to use this component?
    Thanks in advance.
    Regards,
    Claire

    hi friends
    u see  this weblogs&pdf,this is helpful for u
    /people/bertram.ganz/blog/2007/01/08/the-top-12-hottest-sap-notes-every-web-dynpro-java-developer-must-know
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f3f93ee7-0c01-0010-2593-d7c28b5377c2
    Regards'
    vino

Maybe you are looking for