Show TOC Start of Content Area

Procedure documentation Invalidating Metadata Caches  Locate the document in its SAP Library structure

Use

When you are using data from an SAP backend system for a Java Web Dynpro application, several caches are involved to keep the backend data values. To encrease adaptability of the backend data you would have to invalidate the metadata cache. The invalidation of metadata caches makes the restart of the Java engine after changes on the backend data unnecessary - the updated backend data is visible for the Web Dynpro application in your browser automatically.

Prerequisites

If you are working with a NetWeaver installation which does not yet support the invalidation tool, you have to deploy the feature to the Java engine.

Procedure

       1.      Start the Web Dynpro Console from the Java Engine homepage, and go to the Admin Menu.

       2.      To start the tool which supports invalidation of several caches, choose Invalidate ARFC Cache Invalidation of ARFC Metadata Cache.

       3.      Press Get JCO Destinations from the upper screen area to make the affected aRFC applications visible in the table.

       4.      In the second Don’t Cache column, you would make settings if there is RFC data that you don’t want to be cached but that shall always be newly fetched from the backend.

Caution

We recommend that you set this flag only if really necessary since during each call ALL metadata is newly fetched. Note that you must not set this flag in a productive system since otherwise you might run into memory and/or performance problems.

       5.      Next step is to invalidate the related Dictionary cache. From the upper table with the RFC connections, you choose the metadata JCO destination in question. Click on Get Dictionaries for Selected JCO Destination to list all the Dictionaries of that JCO destination.

You have to options to invalidate the Dictionary cache: Either by choosing the corresponding Dictionary from a list, or by entering the Dictionary name manually where you can derive the name out of the model package name, appending string .types.

Note

You will get online help for entering the possible correct dictionary names.

       6.      We recommend that you are using the manual way if you have to consider performance for your application administration.

       7.      Choose Invalidate Selected Dictionary Cache, or Invalidate Dictionary Cache alternatively.

       8.      After invalidation, make a browser refresh to make the updated backend and dictionary data such as new data elements, changed enumerations, or new value ranges for domains visible.

End of Content Area