Hi,
The <b>Adaptive Remote Function Call (Adaptive RFC)</b> is a technology that enables the Web Dynpro application developer to use the business functions encapsulated in Business APIs (BAPIs) even after a structure modification, without having to provide the new data using a second back end or a new structure with subsequent regeneration of the proxies.
This new RFC model shows adaptive behavior. This means that the RFC proxies do not use the original design time structure definition at runtime. Instead, this Web Dynpro model automatically adapts the data of the structure passed in the Java proxy generation to the current data – that is, a structure definition in the back-end system that may have been modified.
Generated structures are used for the context definition; the context ensures type-specific access to the attributes, as they are valid at runtime. However, the context attribute does not create the structure attributes until runtime and can therefore automatically take any changes made a later stage into account.
All structures, fields, and data types are maintained by the Java Dictionary runtime. A memory is available for this, which acts like a virtual machine: Load definitions are automatically loaded from the back end on demand.
The Web Dynpro context therefore shows adaptive, non-static behavior. At runtime, not just those fields are visible that were generated at design time.
<b>Client side eventing</b> is a portal service that allows event driven manipulations on the web client without causing a server event.
When a business application uses more than one iview you need <b>portal eventing</b> service(EPCF) to communicate between iviews and to transfer data. There is a Java object, called client data bag, that serves as transient data buffer on the browser.
Hope this helps.
Regards,
Pooja.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.