Page tree
Skip to end of metadata
Go to start of metadata

Caching a data source

System Connection: RFC

Problem: You use an RFC in Visual Composer on the story board and change the BAPI in the backend afterwards. You want to display the changes in the input/output ports of the data service.

Here are some tips of how to solve that:

  • Make a refresh of the data service (right click on the data service and select Refresh (available when you use queries))
  • Restart the J2EE engine
  • Turn off the caching in VC 7.0: Go to Options, tabstrip Compiler and change the setting of Data service retrieval to Do not cache data services.
  • Make sure that your backend is not caching the changes (may vary from system to system)
  • Modify your connection lifetime setting in the Visual Administrator as it is described in this WIKI entry.
  • Use the attached PAR-file (under tab strip Attachments - don't forget to rename and remove the .jpg)
    • Create an iView from it and just preview it. What it does is just stop and start the ESP framework (not "expensive") and thus releasing the cache. J2EE WS invocation layer caches by default and the only way to release the cache is by code. So, I created this simple PAR file. (Thanks to Netanel Slomianski)
  • No labels


  1. Unknown User (wvdgh5t)

    "Restart the J2EE engine"

    I think this is not practicable solution. I had this problem often, when I develop a new RFC function module. Everytime I change Import or Export Parameters, this error occurs. I cannot restart the J2EE engine, if this error occurs, because we have only one J2EE engine in our R&D department. (sad)

    I hope there is also another solution for this problem. 

    Best regards,


  2. Former Member

    Agree. Let's try to figure out with this page, whether there is a "best practices" usable and working, or if we need to go back to development and report the problem.
    Let's collect here all things that worked for getting over that and figure out what works best.

  3. Unknown User (wvdgh5t)

    Okay Mario, one way is to copy the RFC function module and give them another name. Then you can re-drag it again to the storyboard. This workaround is okay, if you use it once in the model. I wrote a OSS message about this problem. Now I'm waiting for an answer.

    Best Regards,


  4. Unknown User (lqtiorw)


    I am having the same kind of trouble. Did you get any response on the OSS message Marcel?

    Best regards Gunnar Braaten

  5. Hi Guys,

    Actually, we (VC core) found out that the J2EE WS layer is always caching the WS metadata and therefore, you can stand on your head if you'd like - the metadata change will not be reflected in VC unless you:

    1. restart the J2EE server.

    2. Stop and start the ESP WS layer by code.

    I created an iView that restarts the ESP WS layer. It doesn't restart the whole J2EE (wink) if you would like, I can give you the par file and you can use it whe you need it.

    @Mario: Is there a place where we can put this par file for people to download until we create an official note ?



  6. Former Member

    Hi Netanel,

    I am trying to download this par file but it seems to be corrupted. Whenever I try to upload this par file to portal it gives me the following log.

    Application upload failed: VC.par error in opening zip file
     at Method)
     at com.sapportals.portal.prt.deployment.ArchiveIterator.iterate(
     at com.sapportals.portal.prt.deployment.UploadProcess.upload(
     at com.sapportals.portal.prt.deployment.DeploymentManager._uploadArchive(
     at com.sapportals.portal.prt.deployment.DeploymentManager.uploadArchive(
     at com.sapportals.portal.prt.deployment.DeploymentManager.uploadApplication(
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(
     at java.lang.reflect.Method.invoke(
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleRequestEvent(
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(
     at com.sapportals.portal.prt.dispatcher.Dispatcher$
     at Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(
     at javax.servlet.http.HttpServlet.service(
     at javax.servlet.http.HttpServlet.service(
     at Method)

    If you could provide me the proper version of this par file on my email address then I would really be grateful to you.

    Hoping for a quick response.


    Murtuza Kharodawala