SAP NetWeaver 04, 7.0, 7.01, CE 7.1, CE 7.11

Size: px

Start display at page:

Download "SAP NetWeaver 04, 7.0, 7.01, CE 7.1, CE 7.11"

Nora Blair
5 years ago
Views:

1 1

2 2

3 3

4 4

Network / Latency: See other TechEd Sessions

Accelerated Application Delivery: Enhancing

5 Network / Latency: See other TechEd Sessions UP360 Enhancing Performance of Web Applications Using Accelerated Application Delivery, 4 hour hands-on, Advanced UP108 Accelerated Application Delivery: Enhancing the Performance of Web Applications, 1 hour lecture, Beginner 5

6 6

7 Maintainability : the ease with which a software system or component can be modified to correct faults, improve performance, or other attributes, or adapt to a changed environment (IEEE 90) 7

8 8

9 9

If you need a new row you simple set the property layoutdata of the first element of the new row to RowHeadData.

10 Prefer the Row Layout to the Grid or Matrix Layout if you don t need horizontal alignment! The row layout allows you to put an arbitrary number of elements in each row (it automatically uses a flow layout for each row). If you need a new row you simple set the property layoutdata of the first element of the new row to RowHeadData. It is also a good idea to use the row layout if you have only one element per row as it is often used to arrange a screen vertically. Prefer the Matrix Layout to the Grid Layout! This won t enhance the performance, but we think it is easier for the application developer to work with it: You don t have to specify a column count and you can put as many controls into one row as you like. If you need a new row you simple set the property layoutdata of the first element of the new row to MatrixHeadData. Additionally, the matrix layout helps to achieve consistent layouting: Other than the grid layout, the matrix layout only allows some predefined values for the cell padding. Instead of the properties paddingtop, paddingbuttom, paddingleft and paddingright it only offers the property celldesign with the following predefined values: 10

11 11

Use load-on-demand (onloadchildren event) to populate large

event handler knows about the context path corresponding to

12 Use load-on-demand (onloadchildren event) to populate large trees: Assign an event handler to the onloadchildren() event of the TreeNode Type. Apply parameter mapping for event property path so that the event handler knows about the context path corresponding to the clicked tree element. Implement the event handler for populating the given context node with node elements. 12

13 13

Performance/flexibility is of course better with ZCI Always use the latest ZCI script from Adobe inside the

14 Usage of Zero Client Installation (ZCI) is strongly recommended: ZCI is the future of Interactive Form. ACF will become obsolete in future. Performance/flexibility is of course better with ZCI Always use the latest ZCI script from Adobe inside the form: From EhP1 onwards Automatic Script Injection is ON by default on the ADS. For older releases, application should do it manually with the migration tool provided. Adobe also recommends the same. 14

15 Do not bind the pdfsource property until and unless the application needs the latest binary PDF available on the server. If the pdfsource property is not bound, XML is interchanged between the server and the client, always, which is much less expensive than binary PDF data transfer. Have a pre-created PDF and then use the same throughout the application session using usepdf mode. Alternative application logic: create PDF form for the first time and then use the same PDF form throughout the session. 15

16 16

The wddomodifyview() hook is designed for the creation of a UI tree or UI sub-tree at runtime in case it is not possible to declare the UI at design time.

Context manipulations are done in wddoinit(), action event handlers or server side event handlers.

17 The wddomodifyview() hook is designed for the creation of a UI tree or UI sub-tree at runtime in case it is not possible to declare the UI at design time. The method is neither intended for fine grain UI manipulations nor for context manipulations. Fine grained UI manipulations are achieve via means of data binding. Context manipulations are done in wddoinit(), action event handlers or server side event handlers. Changing only one single attribute of a single UI element within wddomodifyview() flags the complete view containing the control as dirty and the complete view must be completely re-rendered again depending on the size and complexity of the view this can result in significant performance hits The hook method wddomodifyview() should not be used for the following types of code: Altering UI property values use context binding instead Changing the context in any way! Creating or changing modifiable simple types Storing UI element object references that you then attempt to access outside this method The properties of dynamically created UI elements should be controlled through context binding. Don t store static references to UI elements in the View Controller Don t attempt to refer to static UI element references in any event handler or supply function 17

Web Dynpro's programming model brings views automatically into life when needed, e.g. when a navigation makes a certain view "visible" for the first time.

the current content of a visible (according to its own definition) window, or is 2. the current content of a view container which in turn belongs to a currently visible view.

18 Web Dynpro's programming model brings views automatically into life when needed, e.g. when a navigation makes a certain view "visible" for the first time. It is important to understand that the visibility of views and the visibility of UI elements are defined slightly different. A view is called visible when it is part of the current view assembly, i.e. when it is either 1. the current content of a visible (according to its own definition) window, or is 2. the current content of a view container which in turn belongs to a currently visible view. The hierarchy of view inside view containers or windows that you define in the NetWeaver Developer Studio is a hierarchy of possibilities, so to speak. It defines possible and initial (default) embeddings. At runtime, every window and view container contains at most one current view. This is the hierarchy of facts, so to speak, that defines visibility in the above mentioned sense From the definition above, we know pretty good when a view is created. At that time,wddoinit() is called and laterwddomodifyview() is called withfirsttime == true. This allows an application programmer to bring the view into the desired initial state with respect to data and layout. The interesting question now is when will the view be destroyed? And the answer is, as usual, it depends. In this case it depends on the view's lifespan as defined at design time ("Properties" tab of the view). The possible values today are "framework controlled" and "when visible". It is the goal of this item to help you decide which of these values fits best your needs. A lifespan of "when visible" means that a view is destroyed as soon as it becomes invisible. Now what would be the consequences if a view, that has just become invisible temporarily, is destroyed and then created again? First of all, it takes additional time becausewddoinit() must run again. Given a wellwritten application, this should bring back the view into almost the correct state, because data should reside in component or custom controllers and programmatic layout modifications should be based an such data. But what is nearly inevitably lost is "view state", e.g. the first visible row of a table, the currently selected tab of a tab-strip etc. This can make a big difference 18 to the end user, of course.

Previous Slide Notes continued Thus the default lifespan is "framework controlled" and means that the Web Dynpro runtime decides when a view should be destroyed. I.e. our framework reserves the right to do so at its own discretion.

19 Previous Slide Notes continued Thus the default lifespan is "framework controlled" and means that the Web Dynpro runtime decides when a view should be destroyed. I.e. our framework reserves the right to do so at its own discretion. Of course, a view that is currently visible will not be destroyed. In practice, such a view currently lives as long as its component does. This allows views to become temporarily invisible without view state being lost and without additional overhead for initializing the view again. This should be the usual lifespan for ordinary views. Only if you want to improve memory performance, i.e. reduce the current memory usage of your component, and have already identified suitable views should you consider to declare those views' lifespans as "when visible". Good candidates are views that both require a lot of memory (for data and layout) and are (usually) used once and then not needed anymore. If you have e.g. an application that requires the user to create the header of a document before creating its items, you might have two views, one for the header and one for the items, that are shown one after the other. If the header view is sufficiently complex, it may be a good idea to make it live only when visible. In this way, memory is saved during the prolonged time that the user is creating items. In the rare case that she must return to the header (and your application supports that), the header view would be recreated. 19

20 20

21 21

Whar are Typed Context Interfaces? Typed context APIs are context interfaces that are generated for the declared context nodes and attributes.

22 Whar are Typed Context Interfaces? Typed context APIs are context interfaces that are generated for the declared context nodes and attributes. For every declared context node <node name> a corresponding pair of typed context APIs, I<node name>element and I<node name>node, gets generated. Return types and parameter types of typed context API methods are not the generic Web Dynpro context APIs (IWDNode andiwdnodeelement), but the typed context APIs themselves. By setting thetypedaccessrequired property to false, the Web Dynpro Java Generation Framework does not generate typed context interfaces for declared nodes and their elements. NOTE You do not have to declare mapped context elements when the target context belongs to the same Web Dynpro component and when it is used for other purposes than data binding, filtering or having an un-mapped lead selection. Instead, you can also access the typed context APIs of the used controller directly withwdthis.wdget<used controller name>controller().wdgetcontext() method. 22

Q: What is the content of "Perm Space"? A: Permanent Space is not apart of the Java heap. It contains metadata and byte compiled code for the classes already loaded, as well as JIT compiled code.

23 Q: What is the content of "Perm Space"? A: Permanent Space is not apart of the Java heap. It contains metadata and byte compiled code for the classes already loaded, as well as JIT compiled code. In short: Perm Space = class information + hotspot compiled code. Perm space is part of the consumed memory and in some VMs can not easily distinguished from heap memory. In some VMs like the SAP JVM the perm size can be configured and monitored separately. 23

Web Dynpro knows different techniques to share data (objects, values) across controller and component borders: context mapping between controller contexts of the same Web Dynpro component (External)

24 Web Dynpro knows different techniques to share data (objects, values) across controller and component borders: context mapping between controller contexts of the same Web Dynpro component (External) Interface context mapping between controller contexts of different Web Dynpro components server-side eventing with event parameters inside a component or across component borders IPublic API method invocation between non-view controllers of the same component IExternal API method invocation between a controller of another component and the interface controller of the used component Navigation inbound and outbound plugs with defined plug parameters NOTE: When context attributes MUST be defined You must use the context to share objects between non-static event handlers and the static wddomodifyview() hook method, even if these objects (context elements) are not used for data-binding. Do not declare static member variables for this purpose, as static members never store session-dependent objects on controller instance level but session-independent objects on controller class level. 24

The singleton representation minimizes the resources needed as content is only maintained for the current lead selection of the parent and it allows for static binding as no node instance must be

25 The singleton representation minimizes the resources needed as content is only maintained for the current lead selection of the parent and it allows for static binding as no node instance must be named, but only the "class" of the node. To model master-detail relationships within a controller context singleton child nodes (containing the detail node elements for a selected master node element) are mostly sufficient. 25

26 26

Example Assume you are displaying a list of flights in a table and have a

Based on the validate-by-rendering technique, the BAPI is called only for

non-singleton child node (with cardinality 1.

27 Example Assume you are displaying a list of flights in a table and have a BAPI to retrieve flight details. Based on the validate-by-rendering technique, the BAPI is called only for those flights that are currently visible in the table by Creating a non-singleton child node (with cardinality 1..1) of the tree's data source to hold the details for each flight. Using a supply function to retrieve the details for one flight via that BAPI. 27

28 28

For more details see See WebLog Uploading and Downloading Files in SAP NetWeaver 7.0 (https://www.sdn.sap.

Tutorial: Uploading and Downloading Files in Web Dynpro Java - SAP NetWeaver 7.0 2.

29 For more details see See WebLog Uploading and Downloading Files in SAP NetWeaver 7.0 ( 1. Tutorial: Uploading and Downloading Files in Web Dynpro Java - SAP NetWeaver Article: Uploading and Downloading Files in Web Dynpro Tables - SAP NetWeaver SDN Wiki Code Tutorial: Exporting Table Data Using On-Demand Streams - SAP NetWeaver

30 30

31 31

32 32

33 33

34 34

35 For more details on this topic, see the Web Dynpro Component Interface Definitions in Practice on SDN. 35

Also Consider to Enter Component Usages in Referencing Mode In case you want to share a reusable Web Dynpro Helper Component across component borders you should not declare component usages with

With lifecycle createondemand every client component would create its own instance of the helper component which might not be necessary in most cases and which causes an unnessecary memory

For this, they must first declare an own helper component usage of lifecyle type manual at design time.

36 Also Consider to Enter Component Usages in Referencing Mode In case you want to share a reusable Web Dynpro Helper Component across component borders you should not declare component usages with lifecycle createondemand to this helper component in all client components. With lifecycle createondemand every client component would create its own instance of the helper component which might not be necessary in most cases and which causes an unnessecary memory overhead. Instead all client components should enter the same helper component usage instance in referencing mode at runtime. For this, they must first declare an own helper component usage of lifecyle type manual at design time. The helper component usage (also lifecycle = manual) and the lifecycle of its associated helper comonent instance can be defined and managed by the root component. At runtime, the root component passes its helper component usage to all client components via component interface controller method invocation, so that these client components can enter the helper component usage in referencing mode. In this way, all client components use the same helper component instance at runtime. 36

37 37

Development Architect, Atos Origin UK) Part 1 Design methodology, concepts, and case study (SPJ, May/June 2008)

38 SAP Professional Journal 2008 Article Series Leveraging component-based architecture in Web Dynpro for Java business applications by Bertram Ganz (Senior Product Specialist, SAP AG) and Richard Tucker (Principal Web Development Architect, Atos Origin UK) Part 1 Design methodology, concepts, and case study (SPJ, May/June 2008) Part 2 Component models (SPJ, July/August 2008) Part 3 Componentization patterns in practice (SPJ, September/October 2008) 38

39 39

Don t transfer table values as export or import parameters Design your RFCs so that all table values are transferred as table parameters and not within export-, import- or changing-parameters (the

40 Don t transfer table values as export or import parameters Design your RFCs so that all table values are transferred as table parameters and not within export-, import- or changing-parameters (the last ones should never be used at all). If possible use a length-limited datatype like char[10] instead of Xstring Don t embed tables within RFC import, export or table parameters When doing this a performance critical overhead of XML metadata has to be transferred. For avoiding this disadvantage complex structures in given RFCs parameters have to be flattened. 40

within a single model. Allows connection sharing between several RFCs in one model.

41 Put as many RFCs in a single Adaptive RFC model as possible A model represents a namespace, therefore, any commonly used datatypes or structures can be shared only within a single model. Allows connection sharing between several RFCs in one model. With the reimport functionality existing models can be updated and further RFCs can be added. 41

42 42

The client then filters this valueset and suggest values without additional server roundtrips.

43 Suggestion and the 200 Values Size Limit There is NO increased number of server roundtrips when the InputField suggestion is based on On-demand valuesets with less than200 values: see WDSimpleValueSupplier. The valueset is retrieved once in a first roundtrip. The client then filters this valueset and suggest values without additional server roundtrips. Static valuesets defined in dictionary simple types with less than 200 values: the client initially retrieves the complete valueset and then filters suggest values purely on client side. 43

44 44

45 45

46 46

47 47

48 48

49 49

50 50

51 Show stacked performance info for ALL roundtrips in running client session with keyboard shortcut combination CTRL+ALT+Shift+I 51

52 52

53 53

54 54

55 55

56 56

57 57

Effective Web Dynpro - Adaptive RFC Models

Effective Web Dynpro - Adaptive RFC Models Bertram Ganz, NWF Web Dynpro Foundation for Java Overview In many Web Dynpro applications, backend access is based on RFC modules in SAP systems. The Web Dynpro